This page concerns the development for new PyMOL Plugin Architecture. We are requesting ideas, code, etc on how to best implement a successful plug in system.
PyMOL enjoys widespread use as 3D molecular visualization program with strengths in rendering and visualization. PyMOL at current does not have a robust extension mechanism for adding new plug-in based features to PyMOL. It only allows a script of one file and has very limited support for installation and removal. This project aims to correct that lacking functionality. We aim for simplicity and robustness especially in a cross-platform manner.
A Plug-In (or Plugin) is a modular piece of software that extends PyMOL's functionality.
If you want to take part in helping out with this, please send Jason Vertrees an email letting him know as such.
Review of Current Plugin System
Essentially the current system inits all the scripts in the startup directory, which adds their entry to the Plugins menu. When called, it fires off a command passing to it PyMOL's Tk menu. The instance can get access to pymol's cmd layer with,
from pymol import cmd
. Also, as it's in Python, the user can extend Python (even in C) or call low-level functions utilizing the web or touching the file system.
- For a tutorial on the current system. see Plugins_Tutorial.
Ideas/Features for the New Plugin System
- Plugins must be safe. That is, they must not destroy the users' data for file system.
- Plugins must be secure in that they do not transmit data the user doesn't want transmitted.
- We can take an approach like Warren did with sessions--warn the user on sessions s/he didn't create and ask for trusting or not.
- Plugins should be able to query PyMOL for features
- PyMOL should take care of unpacking, installing, uninstalling, updating (?) the plugins
- MUST be backwards compatible with the current system
- MUST run cross platform
- Save user-specific information
More than one file per plugin
I'd like plugins that behave like proper Python modules with the ability to span multiple files/directories. One simple way to do this would be to distribute plugins as zip files. E.g. if we have a directory Foo that contains
MyMod __init__.py """Some documentation here""" Foo.py def doit(): print "It is done!"
We can zip it up like
zip MyMod.zip Foo/*
If you stick MyMod.zip in a plugins directory like /blahblah/Pymol/plugins/MyMod.zip you can then say this:
sys.path.append('/blahblah/Pymol/plugins/MyMod.zip') from MyMod import Foo Foo.doit()
Python does not impose the restriction that the module/directory name (MyMod) should be the same as the zip file name (MyMod.zip), but we might want to.
Then we need to formally spell out the API by which the Plugin is launched.
This makes it very easy to install/uninstall plugins, and PyMOL can just have a simple loop that iterates over the plugins directory, adds the appropriate things to sys.path, verifies that the resulting objects support the API, and adds them to the menu.
Some sort of persistent config files where users can store things like paths to relevant files, settings, etc. would be very useful. The APBS plugin, for instance, is a bit of a bother to use when you have APBS installed in a non-standard location. It would be very convenient if you could set the location once and have it persist.
Liked Plugin Systems
- FireFox Devel/Docs
- Google Chrome -- URL?
Disliked Plugin Systems
Links on the topic
- Plugins, Plug-Ins?