On Fri, Jan 14, 2011 at 1:42 AM, zixzigma <[email protected]> wrote:
> Thank you very much for sharing your experience. > > on this comment, > > " I also pay close attention to widget lifecycles which is critical to > successful implementations of widgets that get attached, detached and > reattached and so on and so on. " > > why widget lifecycle is important ? > why is it important when they are attached/detached ? > Please have a look at the followig: * http://googlewebtoolkit.blogspot.com/2009/05/widget-best-practices-widget-building.html * > > and how can you monitor it ? (logging your java code or viewing resulting > html markup gwt creates ?) > GTW widgets already provide numerous methods such as onLoad, onAttach, etc. that provide all you need to know. There are many things you can use these methods for and all that is required is that you override them. > > how can you tell in what state a widget is: attached/detached ? > what are the states ? only attached and detached ? > > *isAttached*, *isOrWasAttached*, *etc*. Check out the documentation for *Widget *and *Composite* - both provide numerous methods for maintaining and inquiring about a widget's state. Jeff Thank You > > > -- > 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]<google-web-toolkit%[email protected]> > . > For more options, visit this group at > http://groups.google.com/group/google-web-toolkit?hl=en. > -- *Jeff Schwartz* -- 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.
