My advice: Don't use current Elemental. I tried to migrate a medium sized project to Elemental and finally gave up.
1. I still use classic Dev Mode in Chrome 34 for most of the time and page reload is really slow with Elemental. 2. It's too buggy. I got some minor problems fixed, but faced some serious ones in more complicated code that's not worth to work on. 3. In my opinion the code of Elemental is overengineered. Literally everything is abstracted by interfaces. The type hierarchy seems to not really fit on the JavaScript world. Probably because it's partly generated by IDL. I started to write my own Library. First i tried to use JsInterop, but it doesn't support Classic Dev Mode and i don't know how to write browser shims with it. So now it's based on simple overlay types without abstraction or super sourcing => Very fast page reload, easy code. Am Freitag, 3. Juli 2015 07:56:54 UTC+2 schrieb James Horsley: > > Is it recommended to use the current elemental API even though it's not > based on JsInterop yet? For example, if I use the current elemental API, > can I expect that Elemental 2.0 should be a fairly easy transition? > >> >> -- 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 [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/google-web-toolkit. For more options, visit https://groups.google.com/d/optout.
