From: Otis R. <osr...@ch...> - 2010-09-25 14:54:04
|
Bob - The full email re the following message bounced because of size. I'll send the entire email off list. Bob, In my second note, I was only referring to the extracted file approach. With state saving, I still have the bond issue. I should mention that I'm using the following to "restore:" jmolScript("script ../temp/" + "555556565656" + ".txt") The basic idea is that two users "checks out" a modelkit identified by a unique 12 digit number. Changes to this model are recorded in a server text file, and the remote users see these changes via the shared number and the above script. The state file below (end of email) should be 2-butyne that started from an ethene molfile load. The model kit edit shows 2-butyne, but here is what the above script produces from the state file: Otis Rothenberger chemagic.com On 9/25/2010 8:46 AM, Otis Rothenberger wrote: > Bob, > > I stand corrected. I do not lose rotation affects by using the > extracted molfiles. So the only issue for our application is partial > charges on files that contain this information. > > Exchange of models originating from NIH are also a problem. Although > the state file has the inline load data, I assume this problem is > related to the fact that the NIH model url has only a temporary > existence. > > I'm thinking extracted molfiles are my best bet at this point. > > Otis > > > Otis Rothenberger |