Notice: This Wiki is now read only and edits are no longer possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
Difference between revisions of "Selector Architecture Harmonization"
| Line 1: | Line 1: | ||
Since Selectors use most of the Higgins Components, work on harmonizing the Higgins selectors into a single architecture would be a huge step towards overall Higgins architecture harmonization/convergence. | Since Selectors use most of the Higgins Components, work on harmonizing the Higgins selectors into a single architecture would be a huge step towards overall Higgins architecture harmonization/convergence. | ||
| − | + | A good first step in converging the selectors is start by harmonizing the [[GTK and Cocoa Selector]] and the [[Adobe AIR Selector]]. | |
===Top Level Diagram=== | ===Top Level Diagram=== | ||
[[Image:Selector-harmonized-1.1.107.png]] | [[Image:Selector-harmonized-1.1.107.png]] | ||
| + | |||
| + | Notes | ||
| + | * The "Selector UI" component would be either GTK, Cocoa or AIR-based, but the underlying services would be common. | ||
Revision as of 11:45, 4 December 2008
Since Selectors use most of the Higgins Components, work on harmonizing the Higgins selectors into a single architecture would be a huge step towards overall Higgins architecture harmonization/convergence.
A good first step in converging the selectors is start by harmonizing the GTK and Cocoa Selector and the Adobe AIR Selector.
Top Level Diagram
Notes
- The "Selector UI" component would be either GTK, Cocoa or AIR-based, but the underlying services would be common.