Le 16 nov. 2012 à 18:04, Robert Hanson a écrit :

> ....
> Ultimately, I think we will still end up with the full load of 600 or so .js 
> files. I know that sounds ridiculous, but really what it means is that there 
> are so many options in Jmol, that defining or implementing all of them at 
> once is not feasible. Instead, little bits of Jmol will fly over AJAX as 
> needed no matter what the installation involves. About 300 of those files 
> will never load and are not needed because their classes are present in 
> j2s/java/core.z.js, which is loaded initially. Those are basically what it 
> takes to deliver a simple model of caffeine. But I'm not sure it makes any 
> sense to selectively remove those from the distribution. (What do others 
> think?) 
At the moment, after cafeine is loaded, when I load 1crn.pdb, an extra 40 files 
are requested before the pdb file. I am currently on a rather slow internet 
connection and each file request has a latency of about 150ms according to 
chrome dev tools. Thus, delivering those 40 files as one package would 
certainly speed the process noticeably at least when cache is empty.
As for the 300 files never loaded, I am not sure I get your point correctly : 
do you mean that those files are in the distribution but are never loaded ?
If that's the case, I don't think it really matters. I suppose that at some 
stage we might move to a developer version with all the plain javascript files, 
to a deployment version with minimified packaged files (maybe served from a CDN 
service if one is available to our purposes). For now we only have the 
developer version.
> 
> Jmol itself already does this modular packaging to a certain extent, 
> delivering a 1 Mb chunk initially, then smaller chunks. This class-on-demand 
> scheme with JSmol is better in some ways, as all the additional files are 
> relatively small, and the core package can be kept reasonably small. (3 Mb). 
> 
> I would be very interested in having some help on the following issues:
> 
> -- pop-up menu -- how to implement? We can easily get a structured list of 
> what's on the menu, the question is how to present it in HTML5. 
jqueryui is a framework that comes with a menu widget : 
http://jqueryui.com/menu/
it's another 40kB + 20kB css...
> 
> -- console -- how to implement a simple pop-up console, if people feel that 
> is important.
jqueryui has a dialog widget which could be suitable to this end : 
http://jqueryui.com/dialog/#default
> 
> -- PROMPT command. The simple question/answer one is easy, but Jmol allows a 
> richer context, with button lists and such. How should we implement this in 
> JSmol?
> 
maybe another dialog widget ?

------------------------------------------------------------------------------
Monitor your physical, virtual and cloud infrastructure from a single
web console. Get in-depth insight into apps, servers, databases, vmware,
SAP, cloud infrastructure, etc. Download 30-day Free Trial.
Pricing starts from $795 for 25 servers or applications!
http://p.sf.net/sfu/zoho_dev2dev_nov
_______________________________________________
Jmol-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/jmol-users

Reply via email to