On Dec 3, 9:55 pm, Robert Bradshaw <[EMAIL PROTECTED]> wrote: [...] > In principle it should be able to download the necessary jars without > the user having to install anything (beyond Java itself). This is why > the initial download is so large. Obviously there are robustness > issues. Also, it should be possible to install the necessary jars and > a lightweight version of the applet could then be used, and jar > caching needs to improve too. [...] The thing is - It's not just a matter of jar-files. The java3d install process drops 2 library files in place: creating: lib/ creating: lib/i386/ inflating: lib/i386/libj3dcore-ogl.so inflating: lib/i386/libj3dcore-ogl-cg.so creating: lib/ext/ inflating: lib/ext/vecmath.jar inflating: lib/ext/j3dcore.jar inflating: lib/ext/j3dutils.jar You can't possibly expect to be able to ship those over to the browser. Therefore, the instructions should be very clear about the fact that one actually has to install 3d *client-side* to get nice graphics. Given that people already have to install java and fonts, I don't think that's too much of a penalty.
Given how well the four-by-four applet behaves inside the browser, I think you should try for an inlined applet that gets "enlivened" when necessary and "freezes" when it's no longer necessary to be responsive. --~--~---------~--~----~------------~-------~--~----~ To post to this group, send email to sage-devel@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/sage-devel URLs: http://sage.scipy.org/sage/ and http://modular.math.washington.edu/sage/ -~----------~----~----~----~------~----~------~--~---
