Changes between Version 2 and Version 3 of TracPluggableModules

Timestamp:

Nov 18, 2004, 10:54:02 PM (19 years ago)

Author:

Christopher Lenz

Comment:

—

TracPluggableModules

@@ -5 +5 @@
 Adding new functional areas (aka modules) to Trac currently requires some heavy lifting, touching various parts of the code base. Extending Trac on specific sites will therefore quickly become a maintenance nightmare, because those customized and/or extended installs will not be easily upgradeable.
 
-For these reasons it would be highly desirable for the Trac project to provide support for ''pluggable modules'', so that non-core functionality could be maintained separately from Trac (at least to a certain degree). This would for example be used by the Wiki module to build the list of names of existing wiki pages.
+For these reasons it would be highly desirable for the Trac project to provide support for ''pluggable modules'', so that non-core functionality could be maintained separately from Trac (at least to a certain degree).
 
 == Introduction ==
@@ -39 +39 @@
 ''An alternative and possibly more efficient but also more cumbersome approach would be to require the user to specify the "fully qualified" name of every additional module, for example in TracIni. Modules such as the timeline would be in the list by default, but could be disabled by removing them.''
 
-Modules would get loaded as any other python module, but should also be able to hook into the initialization of the system via an exported function.
+Modules would get loaded as any other python module, but should also be able to hook into the initialization of the system via an "exported" function. This would for example be used by the Wiki module to build the list of names of existing wiki pages.
 
 == The Module Interface ==