Skip to main content

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.

Jump to: navigation, search

Difference between revisions of "Selector Architecture Harmonization"

Line 13: Line 13:
 
* 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.
 +
 +
===To Do===
 +
 +
The first objective is to perfectly align the existing [Components] with the above diagram.
 +
* Jeesmon: Split the shared tcpserver project into multiple projects to align with above. Suggestions for new names:
 +
** org.eclipse.higgins.hss for http://wiki.eclipse.org/Components#Higgins_Selector_Selector_.28HSS.29
 +
** org.eclipse.higgins.hss.manager for http://wiki.eclipse.org/Components#HSS_Manager
 +
** org.eclipse.higgins.hss.launcher for http://wiki.eclipse.org/Components#Higgins_Launcher
 +
** org.eclipse.higgins.hbx.ie (NOT hbxie! (taken)) for http://wiki.eclipse.org/Components#Higgins_Browser_Extension_.28HBX.29
 +
* Jeesmon: Merge the HSS connectors into .higgins.hss

Revision as of 13:26, 10 December 2008

{{#eclipseproject:technology.higgins}}
Higgins logo 76Wx100H.jpg

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

Selector-architecture-1.1.109.png

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.

To Do

The first objective is to perfectly align the existing [Components] with the above diagram.

Back to the top