Context Navigation

Changes between Version 17 and Version 18 of TracPluggableModules

v17	v18
36	36
37	37	The plug-in manager should probably be part of the environment, or in other words, for any environment there should be one plug-in manager. Plug-in ''discovery'' would presumably be based on a given path (list of directories) that contain python modules. The {{{PluginManager}}} class would collect all classes that somehow identify themselves as Trac plug-ins (for example by sub-classing a central {{{Plugin}}} class). There could also be a 'plugins' folder in Trac environments that would be added the path by default.
	38
	39	''Does it make sense to have the notion of namespaces on plugins? If all of the plugins that come with Trac and are the vanilla ones that we all know and love currently are marked as com.edgewall.ticket and com.edgewall.wiki, others can make more. Chris Lenz's super-duper Ticket plugin could be de.gmx.cmlenz.ticket, for instance. -- brad''
38	40
39	41	== The Plug-in Interface ==