Changes between Version 2 and Version 3 of TracDev/PluginDevelopment/ExtensionPoints/trac.versioncontrol.web_ui.browser.IPropertyRenderer

Timestamp:

Jan 22, 2012, 11:10:45 AM (12 years ago)

Author:

Peter Suter

Comment:

—

TracDev/PluginDevelopment/ExtensionPoints/trac.versioncontrol.web_ui.browser.IPropertyRenderer

@@ -16 +16 @@
 Implementing the interface follows the standard guidelines found in [wiki:TracDev/ComponentArchitecture] and of course [wiki:TracDev/PluginDevelopment].
 
-A class implementing !IPropertyRenderer directly can advertise variable levels of support for rendering any property in `match_property`, by matching on property `name` or `mode`.
+A class implementing !IPropertyRenderer can advertise variable levels of support for rendering any property in `match_property`, by matching on property `name` or `mode`.
 
 `name`: Different version control backends make different properties available, exposing metadata specific to that system. This is controlled by the [[trac.versioncontrol.api.IRepositoryConnector]] and its `Node` and `Changeset` subclasses.
@@ -31 +31 @@
  - `Markup` or other Genshi content: the property will be displayed normally, using that content as a block-level markup
 
-For rendering properties on a new kind of page call the appropriate implementation via `trac.versioncontrol.web_ui.BrowserModule(env).render_property()` or `render_properties()`.
+For rendering properties on a new kind of page call the appropriate implementation via `trac.versioncontrol.web_ui.browser.BrowserModule(env).render_property()` or `render_properties()`.
 Usually the properties to be rendered are obtained from the `get_properties()` methods of `trac.versioncontrol.api.Changeset` or `Node` subclasses.