[Setools] Actions in OB

[Alexandre Bergel]

Hello Colin,

People at esug enjoyed OB. I am now with Damien hacking it a bit.

We identified two problems with OB:
- the method actionsForNode: has to be overridden whenever a new  
action for a class has to be added.
Damien and I produced a dynamic actions discovery mechanism with  
pragmas. The idea is when someone wants to add a new actions to a  
class node, he just has to extend the class OBClassActor with  
something like:
OBClassActor>>actionFileOutAsText: aClassNode
	<OBActionDefinition>
	^ OBAction
		label: 'file out as latext'
		receiver: aClassNode
		selector: #fileOutAsText
		arguments: {}

- There is a huge method actionsForNode: in OBClassNode and  
OBMethodNode.
Why not to move everything in OBClassActor and OBMethodActor (that we  
will create).

What do you think?

Cheers
Damien & Alexandre
-- 
_,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
Alexandre Bergel  http://www.cs.tcd.ie/Alexandre.Bergel
^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.