Hi Brett, I've already designed, implemented and used a similar framework - use XML to configure and drive Java components into an UI (not related to GWT).
In the end, you may come to an conclusion, that configuring Java with XML is not the right thing to do, because you are losing the static typing and the "self awarenness" of the Java language, so well supported by tools like Ecplise. Imagine the XML reaching sizable proportions - how manageable will it be? In Eclipse, you do Ctrl+T on a type or function, Ctrl+Alt+H on a function, or a Java-search on a type and you know everything. You can also refactor, etc. Whith XML approach, you first need to evolve the supporting tools, and it could be a long path. This is not to discourage you, just to (possibly) provide some insight I've learned by experience. I currently use java annotations where possible, altough they are a bit limited, mainly because they don't support inheritance, and cannot be instantiated. But annotations stay glued to the Java code, so if it changes, the annotations adapt (or break visibly). J. On Jul 15, 5:40 am, "brett.wooldridge" <[email protected]> wrote: > On second reading, what is that UIBinder doesn't do that you want it > to do? > > It can do layout: > > <ui:UiBinder > xmlns:ui='urn:ui:com.google.gwt.uibinder' > xmlns:g='urn:import:com.google.gwt.user.client.ui'> > <g:HTMLPanel> > Hello, <g:ListBox ui:field='listBox'/>. > </g:HTMLPanel> > </ui:UiBinder> > > And even "raw" layout: > > <ui:UiBinder xmlns:ui='urn:ui:com.google.gwt.uibinder'> > <div> > Hello, <span ui:field='nameSpan'/>. > </div> > </ui:UiBinder> > > It instantiates the controls (ListBox in this case), and automatically > binds them to annotated fields: > > @UiField ListBox listBox; > > Certainly because nobody outside of Google has seen UIBinder it is > early to say what it is or is not capable of, but from my reading of > the proposal it would seem the basics of layout, instantiation, and > initialization are covered. If you want code-generation and the > ability to intermingle layout with code in the same file, certainly > UIBinder isn't the tool, but I would argue that's because doing so > isn't best practice. > > On Jul 15, 12:27 pm, "brett.wooldridge" <[email protected]> > wrote: > > > If that's what you're after, I would suggest looking at Kiyaa. It > > seems the most robust implementation out there. > > > On Jul 14, 11:28 pm, Ainata-Leb <[email protected]> wrote: > > > > Thanks for the info guys, but with the UIBinder it looks like we are > > > going back to html. What about instantiation/initialization/laying out > > > GWT widgets? > > > > Thanks. > > > > On Jul 13, 8:50 am, "brett.wooldridge" <[email protected]> > > > wrote: > > > > > I'm waiting for UIBinder as well, but this project seems full featured > > > > and was used on a large project: > > > > >http://code.google.com/p/kiyaa/ > > > > > If the Google guys can't surface UIBinder soon, I may bite the bullet > > > > and use Kiyaa now and convert later. The markup looks fairly similar > > > > between them. > > > > > Brett > > > > > On Jul 13, 5:52 pm, mars1412 <[email protected]> wrote: > > > > > > maybe UI-binder is what you are looking > > > > > for:http://code.google.com/p/google-web-toolkit-incubator/wiki/UiBinder > > > > > > On Jul 12, 4:38 pm, Ainata-Leb <[email protected]> wrote: > > > > > > > Is the GWT team working on a declarative way to build/layout UI? > > > > > > Some > > > > > > XML based way similar to Flex MXML. Or does anyone know if there is > > > > > > a > > > > > > GWT lib that does that? > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/Google-Web-Toolkit?hl=en -~----------~----~----~----~------~----~------~--~---
