The $op is relatively easy to understand but clunky to use. So I would certainly find individual hooks/functions for each one of the states a cleaner way to do things.<br><br>How complicated would it be to move to a true event-based model, where modules register as listeners to events and respond to them rather than hook in through functions that have the right names? I was thinking that a structure similar to menus would be nice and would replicate ideas from other parts of Drupal meaning that newcomes have fewer concepts to learn. A module registers to an event/hook the same way it relates a URL to a callback function and the callback function is where the module performs actions related to that event.<br>
<br>Best,<br><br>Ronald<br><br><br><div class="gmail_quote">On Tue, May 13, 2008 at 7:45 AM, David Timothy Strauss <<a href="mailto:david@fourkitchens.com">david@fourkitchens.com</a>> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div class="Ih2E3d">----- "David Timothy Strauss" <<a href="mailto:david@fourkitchens.com">david@fourkitchens.com</a>> wrote:<br>
> * With a combination of break statements and fall-through switches<br>
> (intentional lack of breaks between cases), it can be difficult to<br>
> quickly understand control flow. Unlike for if/else structures,<br>
> control does not follow indentation.<br>
<br>
</div>Whoops, I meant "fall-though cases."<br>
</blockquote></div><br>