> 1. get a copy of the plugin module file [...] > 2. put it in the instance directory > 3. edit tiddlywebconfig.py
I think a significant bottleneck here is #3 - at least with regards to the initial setup. It's also problematic because it means the respective user/admin has to write at least a tiny bit of Python code. As discussed a few months ago, it might be nice if TiddlyWeb were to automatically pick up all plugins in a given directory. Since direct inclusion might be a bit odd due to sys.path and whatnot, perhaps twanager could do some "preprocessing" to amend the configuration before starting the server? > updating TiddlyWeb plugins [...] can be a bit tedious True - that's a different angle from the above though... > the leading contender for "how to distribute" TiddlyWeb plugins is > simply to distribute them as Python packages While this might work for a default set of "official" plugins, I'm not sure it's a good idea for smaller projects (think devtext store). I also share the concerns about nam(espac)ing. (Though I'm currently not very familiar with how PyPI actually works... ) How about something similar to instance_tiddlers - i.e. automatically pulling in a set of TiddlyWeb plugins when creating/updating an instance? -- F. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
