On 16 Jul 2006 at 10:58, Brian Salter-Duke wrote:
> Hi Angel,
>
> Great. Did you write all that lot in response to my question? These
Well, yes. Just as I was reading your message, I had the very clear idea that this was
easy to do, so I **had** to go and do it --instead of the planned Saturday morning task
of doing some cleaning on the house, so merit is reduced ;-) --. Then I got hooked on
improving it, that's why there are 5 versions (really, only 2 methods, nr.1 with pop-up
and nr. 2 with inline frame which later I went polishing).
I am sure this will be of use for me too at some time; I am always worried about the
delay in Jmol loading, form the user interface point of view.
> options are really just what I think is needed. I'm impressed if not
> overwhelmed. I will try to use these in the Jmol wiki. I may point a few
> people to your site to have a look too.
Good. Although it is a testing area URL, I will try to leave it there. Finally, the actual
location of Jmol files, molecules and images have to be modified in the code, although
this is easy.
What has still to be tested is the suitability of this code to be integrated within
Wikipedia, which I assume has automatic backends, database integration and so on.
That's why I went on versions 4 and 5 trying to make the code as portable and
generalizable as I could, thinking on not-hand-made pages and different molecules.
The setup is so:
- A single, common file Jmol_frame.htm holds the applet and the desired controls -like
spin on/off, spacefill, sticks, etc.- This page points to Jmol.js and the JmolApplet files.
- A single, common file Jmol_caption.htm holds the message being shown by default,
which in v.5 also includes a still image (taken manually by screen capture of the Jmol
view).
- The page itself where the contents are, invokes Jmol_caption.htm via IFRAME
SRC="" and invokes Jmol_frame.htm via a _javascript_ function that receives the
molecule's filename and displayed name. The size of the applet is specfiied also in this
page via a variable JmolSize that will be read by Jmol_frame.
- Fonts, colors, etc. can be changed by editing the code in a couple of places. This
could also be centralized via _javascript_ variables, so that the 2 common files need not
to be changed.
On the other hand, I wouldn't think this way of integration will be any difference
regarding security, or lack of it (with respect to other integration methods like the
MediaWiki extension).
Please, anyone do give any ideas as to which featuures would be interesting to add.
------------------------------------------------------------------------- Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________ Jmol-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/jmol-users
