I'm not sure that there is a recommended way. Its really up to you or the coding style of your team.
I tend to use 1. for most simple implementations (e.g. if I want a button click to call a method elsewhere) and 2. for more complex implementations (e.g. if I am adding a series of buttons programmatically, each of which will trigger an RPC call with unique parameters when clicked). I've never used 3 and it doesn't strike me as a great way to do it, but that's just me. On Jan 30, 3:38 pm, Ajay Garg <ajaygargn...@gmail.com> wrote: > Right, and so that brings to the query in my first post :: What is the > recommended way to attach a clicklistener to simple widgets like > Button and Hyperlink :: > > 1. Let a Button be listened by itself ? > 2. Let a Button be listened by a bigger widget (eg. DeckPanel, > HorizontalPanel ..) encapsulating it? > 3. Let a Button be listened by the module of which it is a part? > > Ajay Garg > > On Jan 30, 9:08 am, ajay jetti <programmera...@gmail.com> wrote: > > > The Answer to second question depends on the scenario , but multiple > > listners on a single button? i din know if that is possible --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
