Filipe Correia wrote: > Hi all, > > I'm a newbie to trac and am looking into writing my first plugin. Yet, > I'm finding it a bit "burocratic", so to speak. Is it really necessary > to cook a python egg to deploy a plugin to a trac installation? I was > thinking the process of deploying would be simply to copy something to > the .../trac/plugins directory, but couldn't find any reference that > confirms this assumption. It would certainly ease testing during > develop time though. > > I've read both: > [1] http://trac.edgewall.org/wiki/TracDev/PluginDevelopment and > [2] http://trac-hacks.org/wiki/EggCookingTutorial/BasicEggCooking > > Is the extension points list on [1] complete? I found references to an > IContentConverter interface, but it's not included there. > > Yes, that something is either a python file (for smaller, one-off stuff), or an egg containing source, templates, etc. For development, most people use setuptools' "develop" mode, which lets you run the plugin directly from the source file. This is even better when combined with tracd --autoreload option, that reloads the server on any code change. In general IRC is probably the best resource for plugin development. I am there at unpredictable hours, but will usually be able to answer plugin-related questions (I am coderanger in #trac).
--Noah Plugin Guru
signature.asc
Description: OpenPGP digital signature
