Skip to main content
Jump to: navigation, search

Difference between revisions of "RIC Ideas"

 
Line 4: Line 4:
 
* Should and not contain styling/layout information in it's schema
 
* Should and not contain styling/layout information in it's schema
 
* Should support render specific hints (like "custom attributs")
 
* Should support render specific hints (like "custom attributs")
 +
 +
=== Editor ===
 +
* Provide a graphical editor (handwritten GEF or VEP based)
  
 
== Databinding ==
 
== Databinding ==

Revision as of 15:12, 12 June 2006

XUL

  • 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")

Editor

  • Provide a graphical editor (handwritten GEF or VEP based)

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

Back to the top