Jump to: navigation, search

Difference between revisions of "Eclipse Techs For GWT/Databinding"

(Porting process)
 
(3 intermediate revisions by 2 users not shown)
Line 22: Line 22:
 
   <li>org.eclipse.core.databinding: Status <font color="green">useable</font></li>
 
   <li>org.eclipse.core.databinding: Status <font color="green">useable</font></li>
 
</ul>
 
</ul>
To not move the package our modules have to use <source path="" /> like documented [http://code.google.com/webtoolkit/documentation/com.google.gwt.doc.DeveloperGuide.Fundamentals.Modules.ModuleXml.html here]
+
To not move the package our modules have to use like documented [http://code.google.com/webtoolkit/documentation/com.google.gwt.doc.DeveloperGuide.Fundamentals.Modules.ModuleXml.html here]
 
</li>
 
</li>
 
<li>Factor out not compilable code from Databinding e.g. the whole auto-conversion stuff can't work in GWT (no BigDecimal, no NumberFormat, no DateFormat)
 
<li>Factor out not compilable code from Databinding e.g. the whole auto-conversion stuff can't work in GWT (no BigDecimal, no NumberFormat, no DateFormat)
Line 28: Line 28:
 
<li>Create a set of scripts to automatically create GWT-Lib from Databinding-Sources</li>
 
<li>Create a set of scripts to automatically create GWT-Lib from Databinding-Sources</li>
 
</ol>
 
</ol>
 +
 +
== Reimplementations ==
 +
 +
* Reimplementation of the standard converters and validators
  
 
== Additional things to consider ==
 
== Additional things to consider ==

Latest revision as of 14:37, 28 March 2009

Disclaimer

This is not part of the Official Databinding Effort lead by the Platform/UI-Team nor a project of the Eclipse-Team. The work done here is fairly experimental!

Target

The main goal of this project is to make the current Eclipse-Databinding project compiled into JavaScript using the GWT-compiler. There are the following things to consider:

  1. GWT only provides a very small class lib (e.g. only ArrayList is available no LinkedList, no System.arraycopy)
  2. There are no threads, ... a possible solution to this could be later on Google-Gears
  3. Keep the footprint as small as possible this might also mean to split the current plugin into multiple ones (e.g. the core one and another one with the automatic converter stuff)

Porting process

  1. Things we have to port are:
    • org.eclipse.core.runtime (partly): Status useable
    • org.eclipse.core.databinding: Status useable

    To not move the package our modules have to use like documented here

  2. Factor out not compilable code from Databinding e.g. the whole auto-conversion stuff can't work in GWT (no BigDecimal, no NumberFormat, no DateFormat)
  3. Create a set of scripts to automatically create GWT-Lib from Databinding-Sources

Reimplementations

  • Reimplementation of the standard converters and validators

Additional things to consider

  1. There's no Reflection available in GWT and as a result of this no Beans-Support, we have to think about an other solution. As of now I see the following possibilities:
    • Get Core-EMF to compiled with GWT
    • Provide our own small EMF (I called it PEMF for PoorEMF) for this it would be handy to have PropertyChange-Support from the java.beans package available. A possible solution is to copy them from Apache Harmony project