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 "JFace Data Binding"
| Line 1: | Line 1: | ||
| − | == What is JFace Data Binding? == | + | == What is JFace Data Binding? (code name: Krispy Kreme) == |
Developing line of business applications as Eclipse Rich Client Platform applications presents a number of unique challenges. | Developing line of business applications as Eclipse Rich Client Platform applications presents a number of unique challenges. | ||
| Line 21: | Line 21: | ||
* [[JFace Data Binding Scenarios]] Document | * [[JFace Data Binding Scenarios]] Document | ||
| − | == Introduction to | + | == Introduction to JFace Data Binding == |
| + | |||
| + | Traditionally, database-driven line of business applications are organized into tiers: a database tier, a business or domain model tier, and a presentation tier. The communication paths between these tiers are organized along the routes that data flows within and among these tiers. | ||
| + | |||
| + | Recently, Hibernate, EJB3, and Rails technologies have emerged as a means of automating the data flow between the business tier and the database tier. | ||
| + | |||
| + | By analogy, just as Hibernate helps automate the data flow between the business tier and the database tier, JFace Data Binding helpse automate the data flow betweeen the business tier and the presentation tier. | ||
| + | |||
| + | == 12,500 foot (about 4000 meters) view of JFace Data Binding == | ||
Revision as of 12:29, 22 March 2006
Contents
What is JFace Data Binding? (code name: Krispy Kreme)
Developing line of business applications as Eclipse Rich Client Platform applications presents a number of unique challenges.
- How does one validate data entry when the number of possible interactions between validation rules rises proportional to the square of the number of data entry fields on an input form?
- How does one avoid coding repetitive, dull, tedious, and error-prone SWT event handlers?
- How can one improve reuse of data-driven user interfaces?
All of these concerns are improved using JFace Data Binding.
Status of JFace Data Binding
Note: The JFace data binding framework is new in 3.2 and is now provisional API for Eclipse 3.2. This means that although there is "internal" in the package names, you can use the APIs and we intend to publish the APIs as full APIs in the next version of Eclipse. However, although we will try to minimize breaking changes, there are no guarantees that we will not make breaking changes before the API is published.
For comments, design feed back, and bug reports, please enter bugs against Platform/UI using [DataBinding] in the summary.
- Data Binding HOWTO Document
- JFace Data Binding Design Document
- JFace Data Binding Scenarios Document
Introduction to JFace Data Binding
Traditionally, database-driven line of business applications are organized into tiers: a database tier, a business or domain model tier, and a presentation tier. The communication paths between these tiers are organized along the routes that data flows within and among these tiers.
Recently, Hibernate, EJB3, and Rails technologies have emerged as a means of automating the data flow between the business tier and the database tier.
By analogy, just as Hibernate helps automate the data flow between the business tier and the database tier, JFace Data Binding helpse automate the data flow betweeen the business tier and the presentation tier.