|
|
| (3 intermediate revisions by the same user not shown) |
| Line 1: |
Line 1: |
| − | == XUL ==
| + | Delete |
| − | * Developers describe views in XML and/or Java
| + | |
| − | * Should be really simple
| + | |
| − | * Should and not contain styling/layout information in it's schema
| + | |
| − | * Should support render specific hints (like "custom attributs")
| + | |
| − | | + | |
| − | == Databinding ==
| + | |
| − | * Developers bind data to views using Java
| + | |
| − | * Databinding synchronizes data in Java classes (beans) with data shown in views
| + | |
| − | * Synchronization happens transparently in the background, developers should not care
| + | |
| − | * Developers don't have to care about communication between renderer and the server, i.e. it's up to the renderer to provide a communication implementation
| + | |
| − | | + | |
| − | == Rendering ==
| + | |
| − | * Views can be rendered in Eclipse RCP and Internet applications
| + | |
| − | * Views are skinnable in Internet applications
| + | |
| − | * Initial set of renderers
| + | |
| − | ** RCP Renderer
| + | |
| − | ** GWT Renderer
| + | |
| − | | + | |
| − | == OSGi ready ==
| + | |
| − | * Supply bundles
| + | |
