Almost all of the "problem's" listed below are bad advice and I suggest you disregard them. Except for the "it's a graphic designer mindset" - this statement is correct. Thankfully we no longer need to code our layout and style in java!
The main problem I have with UiBinder is that when you try and use it with the MVP architecture "best practice", you have to boilerplate all the parent/child (view) widget's. Which means you'll see a lot of..... @UiField(provided=true) You then need to programatically decide/code when the uibinder should be called. I would still recommend it. On Mon, Jun 21, 2010 at 11:47 PM, Stefan Bachert <stefanbach...@yahoo.de>wrote: > Hi, > > I don't use UiBinder in general. It may be nice for some hacks. > > UiBinder has a lot of problems > * a further language. No way to debug it * limited to a set of widgets > * it is a graphic designer mindset (we do this app, the app is our > concern) not a developer mindset (we do this class of apps, we > separate concerns) > * no clear separation, no SoC. A big bunch of widgets and css-styles. > * no separation of theme/skin > > When you watch the video with Ray Rian (gwt wave, discussion) you > clearly read between the lines that he doesn't like UiBinder, too. > > The only advantage I see, it is faster to create a fragment of HTML > code than to build it via java/javascript code. But how often you will > create a html-structure? In a good design this will rarely happen. > And performance is one but the only design goal. > > Stefan Bachert > http://gwtworld.de > > > On Jun 21, 3:23 am, spierce7 <spier...@gmail.com> wrote: > > Does using the UI Binder provide any benefits? I watched some of the I/ > > O conference, and it seemed like they made reference that the UI > > Binder using the browsers native rendering engine (or something like > > that), and it being a lot faster, but they didn't really specify > > whether that was the layout panels, or using the ui binder. > > > > What are the benefits to using the UIBinder, and where can I learn to > > use it? > > -- > You received this message because you are subscribed to the Google Groups > "Google Web Toolkit" group. > To post to this group, send email to google-web-tool...@googlegroups.com. > To unsubscribe from this group, send email to > google-web-toolkit+unsubscr...@googlegroups.com<google-web-toolkit%2bunsubscr...@googlegroups.com> > . > For more options, visit this group at > http://groups.google.com/group/google-web-toolkit?hl=en. > > -- You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group. To post to this group, send email to google-web-tool...@googlegroups.com. To unsubscribe from this group, send email to google-web-toolkit+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
