I must admit that if pressed to pick an idea I liked best, I like having the ability to have multiple <event-handlers> blocks with an eventType attribute which overrides the event type attribute on the <event-handler> tag.
Doug Hughes, President Alagad Inc. [email protected] 888 Alagad4 (x300) Office: 919-550-0755 Fax: 888-248-7836 On Wed, May 20, 2009 at 3:14 AM, Chris Blackwell <[email protected]> wrote: > We can def do without any more wars :) > I've been thinking about how i use event types and looking back over a few > apps i never use an event type for every event (ie a default event), or have > an event type thats used in a single place (which is pointless). I'm always > using event types on groups of handlers. > > So specifiying an all encompassing default type doesn't do much for me as > i'd have to pick my most commonly used types then override on every handler > where i need a different type or adding type="" where I don't want a > default, which seems wrong. > > Adding an optional attribute doesn't seem like anymore of a change than a > config property. If allowing multiple <event-handlers> blocks in a single > config file is a problem, then i'd settle for splitting my differently typed > events into separate files, but as it wouldn't break any existing apps I > think it would be fine. > > Back to some real work now > Chris > > 2009/5/20 Gmail <[email protected]> > >> I'm not prepared to wage war over it, but I suggest that the simple >> version (allowing for a single list of default event types in the model-glue >> config) is not really a change to the framework. >> >> Event types are new to MG3, so now's the time to make sure that they are >> implemented in the most useful way. I truly believe that this would be a >> very useful feature and really is in keeping with the spirit of event types >> (which is to save on having to specify the same logic in multiple places). >> >> I agree that the suggestions that result in added complexity to the XML >> file might not be the best route, even though they may extend the usefulness >> of the feature. >> >> So I suppose my stance is that default event types should be made >> available, but perhaps only in the simplest way. >> >> Cheers, >> Bob >> >> > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "model-glue" 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/model-glue?hl=en For more about Model-Glue, check http://www.model-glue.com . -~----------~----~----~----~------~----~------~--~---
