Dear Hannes!
On 13 November 2010 18:42, Hannes Hochreiner <hannes@xxxxxxxxxxxxxx
<mailto:hannes@xxxxxxxxxxxxxx>> wrote:
I completely agree on your suggestions for improvement. The
rendering in different browsers can be quite different.
Unfortunately, there is little that can be done by JessyInk to
improve this (other then submitting bugs). I check my presentations in
One possibility would be to implement the JessyInk functionality with
GWT and let the magic of Google's wisdom optimise the code for different
browsers. They have many good workarounds for different browsers built
into it. It's on my list of things to try, but I probably won't find
time for it too soon.
If I understand your suggestion correctly, you would like to have
the images and fonts copied into a defined location and linked with
relative paths from the svg file so that you can put all the parts
on a web-server and have the presentation display correctly. So far
I tried to embed as much as possible into the svg file, but having
images and fonts separately might actually be a good idea.
Even the JessyInk script could be in a separate file. That would make it
possible to upgrade to a new version of the script without having to
open all presentations in Inkscape again. What I wanted to try for some
time is to write a GWT application that would load the SVG file and
display it the same way as JessyInk does. The advantage would be that
the code can be written in Java and would be automatically optimised for
different browsers by the GWT compiler. You can also implement other
functionality easily, like mixing presentations, hiding some slides,
reordering them, etc.