Friday, June 19, 2015

Research on Elemental

Hi,

i watched the "GWT 2.8 and beyond" video and was excited by the direction GWT is heading for. One advice for new future oriented projects was to use the Element library, so i started using it. The low level programming style feels really great, but i'm having issues so i set Elemental up as an Eclipse project. This is what i did:

1. cloned GWT from git
2. "ant elemental"
3. copied the elemental src files from the build into a new GWT-Eclipse project
4. errors showed up on the super-directory, so i excluded it from build.
5. now i put this on project on the build-path of other projects and start experimenting

Is this a reasonable approach, or how do you GWT experts would setup Elemental for development?


The Elemental project looks like this:

Now Elemental consists of interfaces e.g. in the html-package and implementations e.g in the js.html-package. Where is the glue between them? I tried to modify some JSNI in the implementations, but compiler-errors occur and i think it's because i'm violating some type-contraints with the interfaces. Could i just throw away the interfaces and adapt the implementations, so the whole project would become simpler? Would that be i good idea?

--
You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group.
To unsubscribe from this group and stop receiving emails from it, send an email to google-web-toolkit+unsubscribe@googlegroups.com.
To post to this group, send email to google-web-toolkit@googlegroups.com.
Visit this group at http://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.

No comments:

Post a Comment