>> Otherwise, I will feel compelled to argue for splitting the applet >> into two jars so that people who are running simple applications will >> not have such a heavy cost in download time. > > Does "two jars" mean a core jar and a set of additional functionality > that is loaded on demand? That is correct. A 'core' jar which is always loaded and a 'suplemental' jar which is loaded if/when needed.
Sounds useful. So the user would download the minimal applet and then if they want to read (say) a FOO file the system woudl say "wait a few seconds while we load the FooReader...". I assume the user does not have to know any of this.
It is certainly a good idea to get some sort of display up rapidly. Peapole will be more tolerant if they know what is happening.
P.
> I would not like to see the absolute > functionality of the applet reduced, especially since we have built a > considerable amount of our operation round it. Certainly the goal is to keep adding functionality :-)
Miguel
------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf _______________________________________________ Jmol-developers mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jmol-developers
