> > From an outsider's perspective, this is not only unfinished code, but > probably abandoned since it has been left unfinished for so long. If it > isn't going to be finished/maintained, it should be deprecated, wait a > version and remove it, otherwise it should be 'completed'. Another option > would be to factor it out to its own jar so that it doesn't appear to be an > integral part of User... but the hooks in DOM.java will make that hard, and > the 'only com.google.gwt code can write uibinder parsers' make this even > tougher. >
+1 for removing / externalizing it. Not now, but definitely in the (not so far) future. >From the outside these two "features" are an undocumented mess and I would say that no one except Google depend on them. And given that GWT is in a process of moving away from older browsers it is quite questionable to keep this code. In modern browsers it is very likely that you don't see any speed gains by using these features as long as you work on detached DOM trees when setting up the UI. -- J. -- You received this message because you are subscribed to the Google Groups "GWT Contributors" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/google-web-toolkit-contributors/85923ef8-e5c0-4c3d-99cf-2b73f3582f8a%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
