After my last post on custom event types in Model-Glue 3, the reaction was pretty much universal. Nice - but why can't we define these guys in XML? As of about an hour or so ago, Joe checked into the MG3 Subversion repo an update that now allows you to do custom event types in XML, and frankly, it kicks butt. To define a custom event type, you create a new section of your ModelGlue.xml file named event-types. Here is an example:
   view plainprintabout
1  <event-types>
2      <event-type name="templatedPage">
3          <after>
4              <results>
5                  <result do="template.main" />
6              </results>
7          </after>
8      </event-type>
9  </event-types>
In general these follow the same formats as events, but they are separated into a before and after section. You would put broadcasts in the before block. Here is an example Joe created showing a security custom event type:
   view plainprintabout
1  <event-type name="securedPage">
2      <before>
3          <broadcasts>
4              <message name="doSecurityCheck" />
5          </broadcasts>
6      </before>
7  </event-type>
Using the custom event type hasn't changed. You simply provide the name:
   view plainprintabout
1  <event-handler name="page.index" type="templatedPage">
And of course you can use multiple custom event types:
   view plainprintabout
1  <event-handler name="page.index" type="securedPage,templatedPage">
Can I get an "Amen" from the Model-Glue crowd?? (Thanks Joe!)