Re: Why does GWT's API differ so much from the Javascript one?

org.w3c.dom is such a pain to work with, you'd better define your own API that you implement on top of it (or JDOM or dom4j or whatever) on the server-side, and com.google.gwt.xml or com.google.gwt.dom on the client-side. This is exactly what the Wave guys did, and it works pretty well: https://svn.apache.org/repos/asf/incubator/wave/trunk/src/org/waveprotocol/wave/model/document/MutableDocument.java (their implementation is a bit convoluted, as it's layered with IndexedDocument that is necessary for the Operational Transformation operations, but my point is that it's possible and quite easy); it allows for such things like easy iteration: https://svn.apache.org/repos/asf/incubator/wave/trunk/src/org/waveprotocol/wave/model/document/util/DocHelper.java and https://svn.apache.org/repos/asf/incubator/wave/trunk/src/org/waveprotocol/wave/model/document/util/DocIterate.java

--
You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group.
To view this discussion on the web visit https://groups.google.com/d/msg/google-web-toolkit/-/7Oe1B80oJ-wJ.
To post to this group, send email to google-web-toolkit@googlegroups.com.
To unsubscribe from this group, send email to google-web-toolkit+unsubscribe@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.