Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
Difference between revisions of "OTExample Observer"
(New page: '''This is a reusable implementation of the omnipresent design pattern "Observer".''' Note, that a well designed program in Object Teams will usually not require an explicit Observer infr...) |
m (Index.php?title=OTExample Observer moved to OTExample Observer: correct broken title (included URL part)) |
(No difference)
|
Revision as of 06:32, 23 February 2010
This is a reusable implementation of the omnipresent design pattern "Observer".
Note, that a well designed program in Object Teams will usually not require an explicit Observer infrastructure. See the Stopwatch example for an example, how a plain callin-binding suffices.
This demo should, however, give a quick understanding to some techniques of Object Teams for all who are familiar with the Observer pattern (the OTDT ships with a simpler version of this pattern).
protocol/
|
This implements the GoF pattern very straight forwardly.
Open spots are:
|
flower_example/
|
Implement some base entities |
flower_example/
|
Two applications of the Observer pattern binding the above open spots using callin and callout bindings. |
flower_example/
|
A simple main program |