At the moment the usual way to use a TiddlyWeb plugin with your
instance is to:

1. get a copy of the plugin module file (e.g. static.py) somehow
(usually out of http://svn.tiddlywiki.org/)
2. put it in the instance directory
3. edit tiddlywebconfig.py to change system_plugins or
twanager_plugins

This generally works okay, but it means that updating TiddlyWeb
plugins in a TiddlyWeb instance can be a bit tedious.

I'm considering various ways of making this easier and would like some
input on what people think will be best over the long run.

Because TiddlyWeb plugins are just Python packages that are imported
at server or twanager startup time, they can be distributed and
installed like normal python packages. Plugins in tiddlywebconfig.py
are imported from Python's sys.path so there's no requirement they be
in the instance directory.

So the leading contender for "how to distribute" TiddlyWeb plugins is
simply to distribute them as Python packages, allowing them to be
installed and updated in the same way as TiddlyWeb itself: using
easy_install and/or setup.py.

This raises some interesting issues around naming, because (as far as
I know) it is hard to manage namespaces with the egg files that
easy_install likes to use, so may not be an ideal solution. Any Python
folk know the right thing to do in these cases?

Another option is to provide some twanager functionality that makes it
easy to update plugin code in place.

Do you have any ideas?

Thanks.

P.S. Many of the concepts related to plugins have a growing set of
documentation linked from:

  http://tiddlyweb.peermore.com/wiki/#%5B%5BTheory%20of%20Operation%5D%5D

I added a fair amount of stuff today.
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"TiddlyWikiDev" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to 
[email protected]
For more options, visit this group at 
http://groups.google.com/group/TiddlyWikiDev?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to