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

From Eclipsepedia

Jump to: navigation, search
(Porting process)
(Target)
Line 6: Line 6:
 
<li>GWT only provides a very small class lib (e.g. only ArrayList is available no LinkedList, no System.arraycopy)</li>
 
<li>GWT only provides a very small class lib (e.g. only ArrayList is available no LinkedList, no System.arraycopy)</li>
 
<li>There are no threads, ... a possible solution to this could be later on [http://code.google.com/apis/gears/api_workerpool.html Google-Gears]</li>
 
<li>There are no threads, ... a possible solution to this could be later on [http://code.google.com/apis/gears/api_workerpool.html Google-Gears]</li>
 +
<li>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)</li>
 
</ol>
 
</ol>
  

Revision as of 17:14, 2 October 2007

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. Copy over the whole databinding stuff to the required .client-package:
    • org.eclipse.core.runtime => org.eclipse.core.runtime.gwt.client
    • org.eclipse.core.databinding => org.eclipse.core.databinding.gwt.client
  2. Provide a replacement for Sytem.arraycopy (Maybe we could move them to a utility class?). We should implement as much our own but if bigger classes are needed later on e.g. BigInteger, ... lending those classes from Apache Harmony might make sense.
  3. Factor out not compilable code from Databinding and move the compilable code to base classes e.g. the whole auto-conversion stuff can't work in GWT (no BigDecimal, no NumberFormat, no DateFormat)
  4. Create a set of scripts to automatically create GWT-Lib from Databinding-Sources
  5. Explore whether there's a work-around client-package limitation

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 able. A possible solution is to copy them from Apache Harmony project