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 "Selector Architecture Harmonization"
| Line 1: | Line 1: | ||
| + | {{#eclipseproject:technology.higgins}} [[Image:Higgins_logo_76Wx100H.jpg|right]] | ||
| + | |||
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. | ||
Revision as of 17:10, 4 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 "package" -- a service that can be implemented by different component(s) for different deployment environments
- 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.