Eric, You might like to star issue #3914.
http://code.google.com/p/google-web-toolkit/issues/detail?id=3914 - Isaac On Thu, Jan 21, 2010 at 7:13 AM, Eric <[email protected]> wrote: > I was trying to create an application-level logical event class, and I > realized that the plugin could provide a wizard to create the class > and its associated handler. Since this task invariably requires the > author to create three related Java files, and since most of the code > is boilerplate, a wizard could do all the mechanical work. The wizard > would ask for: > > 1. A package name, > 2. An event class name fitting the pattern XyzEvent. > > The plugin would also create a handler interface named XyzHandler. It > would contain a method with signature > > public void onXyz(XyzEvent event); > > This method would also be invoked in the generated dispatch() method > of the new event class. > > Finally, the plugin would create a client interface named > HasXyzHandlers extending HasHandlers. The plugin would also have the > standard option to add Javadoc comments and header comments. > > I could also see a modification to the module plugin; the plugin could > give the author the option to create the module in a new Eclipse > project, which would necessitate changes to the .classpath > and .project files. > > Respectfully, > Eric Jablow > > -- > 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. > > > >
-- 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.
