Hi Thanks. You are probably right. It's really the model I want to reuse and not the presentation. It's just handy sometimes to reuse the same widget.
Anyway, I sorted it out, for the time being, by calling a view interface method in my activity start method that reattaches those common widgets to the view being viewed. It's far from satisfactory though, as for example I cannot use those widgets in Uibinder anymore, I need some placeholder panel. I'll see in the long run how it goes, if it is useful and if I find a better pattern. On Nov 27, 2:04 am, Andrei <vol...@spiraluniverseinc.com> wrote: > Thomas, > > You have an interesting idea. I am not sure, however, how much you are > going to win by trying to reuse a single copy of a widget. I have some > very complex widgets in my app, and they render very quickly (I must > add I use plain GWT). If I ever notice a delay, it's caused by loading > data, not rendering of widgets. I also don't think you will get any > reduction in the compile code size - may be a few bytes here and there > - as long as you create your own custom widgets and reuse them > consistently throughout the app. So, unless I miss something, just > define your own custom widgets and use them in your code and in the > Ui:Binder. > > Andrei -- 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-toolkit@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.
