Re: [Inkscape-devel] A documentation browser
Thanks, Cedric. I has been completely immersed working in my thesis the last few weeks. Today I finished writing and will be exposing next week. Then back to work with you guys.Also, I feel that now that 0.44 is almost out we can spend more brain in what's next :-) . However, I have a few ideas and opininons, will be posting them right now in the wiki.
On 6/21/06, cedric GEMY <radar.map35@...8...> wrote:
I think you should talk about your work in that new place : http://wiki.inkscape.org/wiki/index.php/Embedded_Help
May be you could get some help.
Cheers
dsign <dignor.sign@...400...> writes:
Thanks, Cedric. I has been completely immersed working in my thesis the last few weeks. Today I finished writing and will be exposing next week. Then back to work with you guys.
Cool, can't wait to see it!
Cheers, Colin
By the way, I was looking at the documentation directory in the repos, and it seems to me that java and Saxon are being using to do xsl processing. If that's the case, then there is no way to move the final xsl processing to the browser, not without forcing the final user to a have a lot of tools installed. Anyone can say more about this?
On 6/22/06, dsign <dignor.sign@...400...> wrote:
By the way, I was looking at the documentation directory in the repos, and it seems to me that java and Saxon are being using to do xsl processing. If that's the case, then there is no way to move the final xsl processing to the browser, not without forcing the final user to a have a lot of tools installed. Anyone can say more about this?
Saxon is required only for creating SVGs because this involves calculating the height of all paragraphs by calling Inkscape on a temporary file via a Java class. But for XML->HTML conversion, any XSLT processor can be used.
bulia byak wrote:
On 6/22/06, dsign <dignor.sign@...400...> wrote:
By the way, I was looking at the documentation directory in the repos, and it seems to me that java and Saxon are being using to do xsl processing. If that's the case, then there is no way to move the final xsl processing to the browser, not without forcing the final user to a have a lot of tools installed. Anyone can say more about this?
Saxon is required only for creating SVGs because this involves calculating the height of all paragraphs by calling Inkscape on a temporary file via a Java class. But for XML->HTML conversion, any XSLT processor can be used.
Actually, since around JDK1.4, XSLT has been in the core Java classpath: http://java.sun.com/javase/6/docs/api/javax/xml/transform/package-summary.ht... (which might actually -be- Saxon in a wrapper)
So unless Saxon provides some special functionality, this might be an unnecessary lib.
bob
On 6/22/06, Bob Jamison <rwjj@...127...> wrote:
So unless Saxon provides some special functionality, this might be an unnecessary lib.
There are two things that make it possible to generate SVG only via Saxon (if you can propose a better and more general method, you are welcome):
1. saxon:assign
2. running external java class org.inkscape.xslt.files with methods for checking for existence of files and for running external process (inkscape) and returning its output
There's also saxon:function but this one should be easier to work around (especially if we use XSLT 2.0).
participants (4)
-
Bob Jamison -
bulia byak -
Colin Marquardt -
dsign