Changes between Version 2 and Version 3 of TracDev/ComponentArchitecture

Timestamp:

Aug 9, 2005, 5:40:18 AM (19 years ago)

Author:

Matthew Good

Comment:

use the Image macro to include the attached images

TracDev/ComponentArchitecture

@@ -9 +9 @@
 Components can declare ''"extension points"'' that other components can “plug in” to. This allows one component to enhance the functionality of the component it extends, without the extended component even knowing that the extending component exists. All that is needed is that the original component exposes – and uses – one or more extension points.
 
-http://projects.edgewall.com/trac/attachment/wiki/TracDev%252FComponentArchitecture/xtnpt.png?format=raw
+[[Image(xtnpt.png)]]
 
 A component can extend any number of other components and still offer its own extension points. This allows a plugin to itself offer a plugin API (i.e. extension point). This feature is the basis for a plugin-based architecture.
@@ -29 +29 @@
   Every extension point specifies the contract that extenders must conform to via an {{{Interface}}} subclass.
 
-http://projects.edgewall.com/trac/attachment/wiki/TracDev%252FComponentArchitecture/comparch.png?format=raw
+[[Image(comparch.png)]]
 
 == Declaring a component ==