I think I disagree with you on almost all points. I have been using UIBinder much before GWT2.0 was officially released, and I think to use GWT straight-from-trunk to leverage UIBinder was the best architectural decision we made.
a further language. No way to debug it Its the language of the web. If you are building websites, you ought to know html. There is no escaping that fact. And because it is HTML, debugging layout problems is just a matter of pulling out tools like firebug and the like. limited to a set of widgets .. but you are free to develop and use your own widgets. Besides, you have the full power of HTML. And, when it comes to widgets, its GWT in general which is poor; it has nothing to do with UiBinder. I mean, there are only 4-5 widgets that are supported by GWT but not by UIBinder. 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. It actually is the best possible separation of concerns. Graphic designer works on the *.ui.xml - its just html, so he doesn't need to learn anything new. The developer works on the corresponding *.java file - he doesn't care about the layout or styling information. Both teams make changes almost independently, and its best utilization of each teams skills. When you watch the video with Ray Rian (gwt wave, discussion) you clearly > read between the lines that he doesn't like UiBinder, too. Er, no. I certainly didn't read such a message. But how often you will create a html-structure? In a good design this will > rarely happen. I find myself creating or changing HTML a lot frequently than changing the logic. Again, as I said, you are building for the browser, and there just isn't a way to escape HTML. Embrace html, and you will surely be a lot more productive. And performance is one but not the only design goal. Agree that performance is not the only goal. But when you make a web-application (think gmail) that will not be refreshed/reloaded for long time periods, you cannot afford to perform DOM manipulations all the time. innerHTML is order of magnitudes faster than corresponding dom insertions.. --Sri On 21 June 2010 19:47, 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. > > I think the decision to build from gwt trunk was the best architectural decision we took -- 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.
