Dear Eric, You are certainly welcome to contribute and reorganize contents in the Wiki as you feel necessary. Your point of view is appreciated and sound.
1. I agree that the documentation is in a weak state. As you know, it is not easy to write and keep up good documentation, and it takes time and manpower. I've tried to contribute what I could, but there is still much room for improvement. And my time is limited. 2. Historical reasons and the fast development of J(S)mol are part of the reason for the current state. Any moment is good for redesign, particuarly after some thought which you probably can bring in. 3. I understand that the jargon is tricky. What is JSmol? The non-Java version (I like to use "modality" since the core is the same). BUT... there is nothing different in the way a page author has to proceed in order to setup a JSmol page versus a Jmol page. I think this is the major reason why JSO is still the main (unfriendly) entry. JSO is the method to implement Jmol Objects (Jmol-Java, JSmol, WebGL...) in a webpage. I agree the more technical explanations may be put to a second line, not to scare away users. Please go ahead and start an "easy to read" page for JSmol which then links to more "technical" page for JSO. That's probably a better solution. But I wonder what contents the JSmol page will have, in practical terms. Even if you don't call it that way, "using" JSmol --which means implementing JSmol-- requires some understanding of JSO. Of course, this might be "copy and paste this piece of code", without many explanations. 4. What is now the meaning of "Jmol"? Jmol (Java applet) is implemented also using JSO, and with exactly the same method, code, syntax, etc. as JSmol --except for the single line with the "use" variable. > "The Jmol-JSO is the library upon which JSmol is built. The Jmol-JSO is the library used to implement both JSmol and Jmol objects in a web page -- and to interact with them via scripts and UI controls such as buttons etc. > 2. Problem: For people like me, the section "converting pages from > jmol to jsmol" is too technical and does not provide a step by step > guide. Right. But I feel the conversion is technical, has to be. And also because there are a few alternatives for the conversion. In part, because conversion may or not be trivial or direct, depending on some issues such as how simple the former code was --I have experienced that with my pages; some solutions do not work if the pages are ellaborate. But let's try and start an easy, step-by-step guide. Having someone coming with clean views is good to sort out the current maybe obscure parts. ------------------------------------------------------------------------------ Infragistics Professional Build stunning WinForms apps today! Reboot your WinForms applications with our WinForms controls. Build a bridge from your legacy apps to the future. http://pubads.g.doubleclick.net/gampad/clk?id=153845071&iu=/4140/ostg.clktrk _______________________________________________ Jmol-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/jmol-users
