Difference between revisions of "Talk:MediaWiki"
(New format for jmol extension) |
(Evolution of Jmol extension) |
||
| Line 7: | Line 7: | ||
The idea is to use a single tag (<jmol>) instead of one tag for each component (<jmol>, <jmolButton>, ...). | The idea is to use a single tag (<jmol>) instead of one tag for each component (<jmol>, <jmolButton>, ...). | ||
| − | The reason behind this is mainly to have only one tag for the extension rather than several (especially since other controls than Button are in the work also). | + | The reason behind this is mainly to have only one tag for the extension rather than several (especially since other controls than Button are in the work also). {{Done}} |
| − | |||
| − | |||
| Line 31: | Line 29: | ||
Other ways need to be available: | Other ways need to be available: | ||
* Accessing a file previously uploaded in MediaWiki (how can we do ?) | * Accessing a file previously uploaded in MediaWiki (how can we do ?) | ||
| − | * Accessing a file through an URL. That may require several other modifications: | + | * Accessing a file through an URL. That may require several other modifications: {{Done}} |
| − | ** Possibility to disable this feature in LocalSettings.php | + | ** Possibility to disable this feature in LocalSettings.php {{Done}} |
| − | ** Possibility to use the signed applet to access a remote file (configurable in LocalSettings.php) | + | ** Possibility to use the signed applet to access a remote file (configurable in LocalSettings.php) {{Done}} |
''Note: Accessing files will also give the possibility to load gzipped files directly since Jmol read gzipped files as well as non-compressed files.'' | ''Note: Accessing files will also give the possibility to load gzipped files directly since Jmol read gzipped files as well as non-compressed files.'' | ||
Revision as of 21:15, 12 April 2006
Please, post your suggestions concerning the Jmol extension here.
Contents
Use a single <jmol> tag
The idea is to use a single tag (<jmol>) instead of one tag for each component (<jmol>, <jmolButton>, ...). The reason behind this is mainly to have only one tag for the extension rather than several (especially since other controls than Button are in the work also). DONE
Adding other components
Suggestion
List of components to add (feel free to add other components) :
- Checkbox
- Radio button
Comments
Reading files
Suggestion
Currently, the only way of giving a datafile to the applet is directly through the <contents> tag.
Other ways need to be available:
- Accessing a file previously uploaded in MediaWiki (how can we do ?)
- Accessing a file through an URL. That may require several other modifications: DONE
- Possibility to disable this feature in LocalSettings.php DONE
- Possibility to use the signed applet to access a remote file (configurable in LocalSettings.php) DONE
Note: Accessing files will also give the possibility to load gzipped files directly since Jmol read gzipped files as well as non-compressed files.
Comments
- all files should be accessible via a common category, this will allow to browse to all files at the same time. In other words, this will allow to build up a data repository, which allows downloading all at once.
- If possible a second tool should be able to generate an archive file out of that.
- Is it possible to extend this approach also to JChemPaint and CDK/JOELib to get 2D drawings and calculate physicochemical properties? E.g. toxicity, solubility, etc.?
Extending to other tools of the Blue Obelisk
Since this approach is quite general for other tools, too. It might be interesting to include also other tools of the Blue Obelisk Movement, e.g.:
- 2D layout and drawings: JChemPaint
- feature calculation: CDK,JOELib
- NMR predictions: CDK
- etc.
Contributors
AngelHerraez, NicolasVervelle, JimHu, Joerg Kurt Wegner, Mevans86, Bduke
