Context Navigation

Changes between Version 11 and Version 12 of TracPluggableModules

v11	v12
35	35	There needs to be a central facility that manages the discovery and loading of plug-ins as well as the communication between them. We'll call this the {{{PluginManager}}} for now.
36	36
37		The plug-in manager should probably be part of the environment, or in other words, for any environment their 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.
	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	38
39	39	== The Plug-in Interface ==