i use "custom code" in 90% of the cases. to me, the ui binder is just another way of describing the ui. i'd use it if i wanted to outsource the ui work to some css-guy that has no java skills. what is cleaner depends on what you do, imho. if you're going to do a dynamic panel with components that depend on which setting you made elsewhere in the ui, i don't see how to do that cleaner using the ui binder.
2014-02-23 15:19 GMT+01:00 Jens <jens.nehlme...@gmail.com>: > You should use whatever fits best to your use case. I use UiBinder 90% of > the time. The remaining 10% are custom widgets/view that would have an > empty UiBinder XML file because their content is generated dynamically. > > The main benefit of UiBinder is that your code becomes cleaner and you can > quickly see the structure of an UI component by looking at the UiBinder XML > file. > > -- J. > > -- > 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 google-web-toolkit+unsubscr...@googlegroups.com. > To post to this group, send email to google-web-toolkit@googlegroups.com. > Visit this group at http://groups.google.com/group/google-web-toolkit. > For more options, visit https://groups.google.com/groups/opt_out. > -- 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 google-web-toolkit+unsubscr...@googlegroups.com. To post to this group, send email to google-web-toolkit@googlegroups.com. Visit this group at http://groups.google.com/group/google-web-toolkit. For more options, visit https://groups.google.com/groups/opt_out.
