Skip to main content

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.

Jump to: navigation, search

Difference between revisions of "Databinding For GWT"

(Porting process)
(Replacing page with 'Move to Databinding/GWT Databinding/GWT')
Line 1: Line 1:
== Target ==
+
Move to [[Databinding/GWT Databinding/GWT]]
 
+
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:
+
 
+
<ol>
+
<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>
+
</ol>
+
 
+
== Porting process ==
+
 
+
<ol>
+
<li>
+
Copy over the whole databinding stuff to the required .client-package:<br />
+
<ul>
+
  <li>org.eclipse.core.runtime => org.eclipse.core.runtime.gwt.client</li>
+
  <li>org.eclipse.core.databinding => org.eclipse.core.databinding.gwt.client</li>
+
</ul>
+
</li>
+
<li>Provide a replacement for Sytem.arraycopy (Maybe we could move them to a utility class?)</li>
+
<li>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)
+
</li>
+
<li>Create a set of scripts to automatically create GWT-Lib from Databinding-Sources</li>
+
<li>Explore whether there's a work-around client-package limitation</li>
+
</ol>
+

Revision as of 17:02, 2 October 2007

Move to Databinding/GWT Databinding/GWT

Back to the top