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 9: | Line 9: | ||
Notes | Notes | ||
− | * Introduce the notion of a " | + | * Introduce the notion of a "Component Set" -- a set of components |
* This architecture would run on Windows, Mac OSX, Linux and (with further work) potentially smart phones | * This architecture would run on Windows, Mac OSX, Linux and (with further work) potentially smart phones | ||
* This architecture should support IE, Firefox and Safari browsers | * This architecture should support IE, Firefox and Safari browsers | ||
* The "Selector UI" component would be either GTK, Cocoa or AIR-based, but the underlying services would be common. | * The "Selector UI" component would be either GTK, Cocoa or AIR-based, but the underlying services would be common. |
Revision as of 13:45, 5 December 2008
{{#eclipseproject:technology.higgins}}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
- Introduce the notion of a "Component Set" -- a set of components
- This architecture would run on Windows, Mac OSX, Linux and (with further work) potentially smart phones
- This architecture should support IE, Firefox and Safari browsers
- The "Selector UI" component would be either GTK, Cocoa or AIR-based, but the underlying services would be common.