Changes between Version 3 and Version 4 of TracDev/PluginDevelopment
- Timestamp:
- May 21, 2005, 8:26:19 PM (19 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
TracDev/PluginDevelopment
v3 v4 13 13 * {{{trac.web.chrome.INavigationContributor}}} [[BR]] 14 14 Allows plugins to extend the navigation menus of the web interface. 15 * {{{trac.Timeline.ITimelineEventProvider}}} 15 * {{{trac.Timeline.ITimelineEventProvider}}} [[BR]] 16 16 Allows plugins to contribute events to the [wiki:TracTimeline timeline]. 17 17 * {{{trac.mimeview.api.IHTMLPreviewRenderer}}} [[BR]] … … 41 41 return 'helloworld' 42 42 def get_navigation_items(self, req): 43 yield 'mainnav', 'helloworld', '<a href="%s">Hello World</a>' 43 yield 'mainnav', 'helloworld', '<a href="%s">Hello World</a>' \ 44 44 % self.env.href.helloworld() 45 45 … … 106 106 == Disabling built-in components == 107 107 108 Sometimes you might want to write a plugin that completely replaces a built-in component, for example to develop an advanced variant of an existing module. Trac uses a list of default component to load, as specified in the {{{default_components}}} 108 Sometimes you might want to write a plugin that completely replaces a built-in component, for example to develop an advanced variant of an existing module. Trac uses a list of default component to load, as specified in the {{{default_components}}} list in [source:/trunk/trac/db_default.py#latest trac.db_default]. These built-in components are always loaded, and might therefore conflict with your replacement plugin. 109 109 110 110 You can however disable built-in components using a special [wiki:TracIni trac.ini] section called {{{[disabled_components]}}}. This section contains the qualified name of the components to disable, along with a boolean value (yes/true/1 or no/false/0), where a positive value means the component is disabled, and a negative value means its enabled.