There's a new paper posted in the OE Principles area extending the set of papers on a class-based implementation of the OERA. It illustrates a couple of very useful and not well-advertised features of OE Architect. One is the ability to save data from the T4BL component designer in a database, so that you can get at the data more easily to extend what the component designer generates. This option has always been there, I believe, but there were problems with the use of the database in the first releases of OEA that have since been corrected, so it is more usable. The second feature is the ability to extend the standard OEA menus with your own custom menu items, and to associate those with an ABL procedure to run when the menu item is selected, and to respond to standard built-in OEA events by subscribing to them using the standard ABL SUBSCRIBE statement. Putting these together lets you extend Architect just by writing ABL code, without needing to understand Eclipse architecture or things like the JET (Java Emitter Template) syntax.