Re: [Rails-devel] 1856 bugs in Rails 1.3 -- undoduringCGRformationhangs game

[Erik V. <eri...@xs...>]

* My own first idea was to use a specific trigger interface and require 
triggers to be explicitly defined. But I realized that the moves are 
excellent triggers and the Moveset a very good place to pass the messages.
Moveset could still delegate the task to a TriggerManager, if a better 
separation is required.

And I want low-level triggers, to avoid that every (high-level)
implementation 
has to remember to call the trigger.

[EV] I still don't like at all to use the Move/MoveSets. I'd much prefer to
keep these clean. 
How are you going to tell an object Move that it is a trigger and what it
must call if it is? Or should all object moves always call all triggerables,
or the TriggerManager (and how can it find that one)? I completely don't
understand how you see this working, and what's the benefit of using the
Moves. 

Take the example: A candidate in the long run ist the function that checks
if 
a company is floated. Every (high-level) method that moves shares out of IPO

has to check if the company has floated. If the trigger is used, this is
done 
automatically. This would also cover special cases in games, which are not 
yet implemented.

[EV] What is exactly registering to what in this example? And what is
triggering what? And how can both the registerer and the triggerer find
their callees?

Erik.