In Jmol.js there is no special modification needed for jmolInitialize().
Please do not comment out the check, or -- if that is your intent, realize
that you don't have to. All you have to do is indicate the directory with
a SPACE prior to "http://";
Thus:
jmolInitialize(" http://kadfjadjl";)
works just fine. No comment is generated.
Bob Hanson
> [EMAIL PROTECTED] wrote:
>>De: Brian Salter-Duke <[EMAIL PROTECTED]>
>>
>>>>>1. When trying to incorporate jmol in wiki pages. One user doing this
>>>>>reports that ../extensions/jmol is needed for it to work in preview
>>>>> and
>>>>>./extensions/jmol when the article is saved (I could have these the
>>>>>wrong way round). An absolute address would fix this. I can not even
>>>>> get
>>>>>it to work like that user reports. I'm still struggling.
>>>>>
>>
>>Clodoaldo also struggled with Jmol to put it on the Fah Wiki.
>>Here's is what he told me about the solution he put in place:
>>"I made the paths relative to the server root and comented out the alert
>> in jmolInitialize() and now it works both in the saved page and the
>> preview page."
>>
>>So he is using absolute path ("/....") and he made a simple modification
>> in Jmol.js.
>>
>>I will work on a cleaner solution next month.
>>
>>
>
> I don't know why Miguel is trying to force people to use only one of the
> three possible ways to provide the path (directory-relative,
> DocumentRoot-relative, absolute). There are advantages and disadvantages
> with all three ways. It depends on each individual case which solution
> is the most adequate one.
>
> I think that he views this too much from the perspective of an applet
> developer. The directory-relative variant he wants to force is often not
> very suitable for interface developers, because it restricts the
> location of the pages to the same directory level. The devolepment area
> is for example often in a totally different part of the WWW server
> directory tree as the pages provided for users. Therefore the movement
> from the development area to the productive area would always require
> editing the page (or changing the CGI script configuration) with
> directory-relative path specifications.
>
> I like the idea of an additional switch that would avoid having to
> modify 'Jmol.js' each time it is updated, if Miguel still thinks he
> should direct the user to the directory-relative path specification.
>
> Regards,
> Rolf
>
>
>
> -------------------------------------------------------
> This SF.Net email is sponsored by xPML, a groundbreaking scripting
> language
> that extends applications into web and mobile media. Attend the live
> webcast
> and join the prime developer group breaking into this new coding
> territory!
> http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642
> _______________________________________________
> Jmol-users mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/jmol-users
>
-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642
_______________________________________________
Jmol-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/jmol-users
