Your simple, many-classes design is actually a Good Thing. Event objects should really only do one specific step in the workflow of your application. Lots of small, discrete and completely specific action classes is far preferrable to a smaller set of classes that contain if-then-else trees and switch statements.
Don't be afraid of lots of small classes, it is usually a good thing. As Grady Booch once wrote, if your application code is too complicated to understand, break things down further with more classes. -- 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=.
