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 "Incubator/Platform/UFacekit"
(→Background) |
(→Background) |
||
| Line 7: | Line 7: | ||
==Background== | ==Background== | ||
| + | Since the 3.3 release Eclipse ships one a top-notch databinding libaries to easy development of UI-Application backed with a model. In time of 3.4 we saw adoption of Eclipse-Databinding in many RCP applications and new libraries supporting model implementations (EMF) beside JavaBeans(tm). On the UI-library side we didn't saw this adoption though Eclipse-Databinding is designed in a way to support any Widget-Toolkit because Eclipse until now only provides observable implementations for SWT/JFace. | ||
| + | |||
UFacekit was started a year ago by James Strachan and Tom Schindl with the following set of targets: | UFacekit was started a year ago by James Strachan and Tom Schindl with the following set of targets: | ||
* promote reuse of rich UI code across Eclipse (JFace/SWT), GWT and Swing runtimes by providing a facade around different UI-Technologies | * promote reuse of rich UI code across Eclipse (JFace/SWT), GWT and Swing runtimes by providing a facade around different UI-Technologies | ||
* promote the use of JFace Data Binding within GWT and Swing communities by providing Eclipse-Databinding-Observable implementations for them | * promote the use of JFace Data Binding within GWT and Swing communities by providing Eclipse-Databinding-Observable implementations for them | ||
* simplify rich UI development by providing simpler facades and powerful binding | * simplify rich UI development by providing simpler facades and powerful binding | ||
Revision as of 15:32, 4 September 2008
Introduction
UFacekit is a proposed open source component under the Eclipse Platform Incubator project. UFacekit's purpose is to:
- improve adoption of Eclipse Core technologies (like Eclipse-Databinding) outside RCP and SWT (e.g. Swing, GWT-Applications)
- improve usability of Eclipse-Databinding by providing a high-level Widget-API
This proposal is in the Project Proposal Phase (as defined in the Eclipse Development Process document) and is written to declare the intent and scope of the component. This proposal is written to solicit additional participation and input from the Eclipse community. Everyone is invited to comment on and/or join the component. Please send all feedback to the eclipse.platform newsgroup (please prefix the subject with [UFacekit]).
Background
Since the 3.3 release Eclipse ships one a top-notch databinding libaries to easy development of UI-Application backed with a model. In time of 3.4 we saw adoption of Eclipse-Databinding in many RCP applications and new libraries supporting model implementations (EMF) beside JavaBeans(tm). On the UI-library side we didn't saw this adoption though Eclipse-Databinding is designed in a way to support any Widget-Toolkit because Eclipse until now only provides observable implementations for SWT/JFace.
UFacekit was started a year ago by James Strachan and Tom Schindl with the following set of targets:
- promote reuse of rich UI code across Eclipse (JFace/SWT), GWT and Swing runtimes by providing a facade around different UI-Technologies
- promote the use of JFace Data Binding within GWT and Swing communities by providing Eclipse-Databinding-Observable implementations for them
- simplify rich UI development by providing simpler facades and powerful binding