On Fri, Mar 18, 2011 at 10:16, Benjamin Dreux <[email protected]>wrote:
> As you explaint it, it's clear to me that this solution is more
> complicated, or at least equivalent to mine.
> In both we bind a fsm event to a button or what ever event.
> And then, one of our state/transition is enabled by this fsm event.
> The benefite of your solution is that we can precise the source of the
> event.
> Am i right?
>
The difference lies in the fact that multiple events may occur in any one
state, and you'd like for each of those events to potentially lead to a
unique transition. By listing the friendly names of the objects on which the
single "execute" event can occur while in a state, you can let the FSM
direct the event to the correct transition automatically. In a large
application this can greatly reduce the amount of code you need to write.
The FSM is very powerful. Your solution is fine for a fairly small
application, and you may even have a way to scale it to a larger
application. A good example would certainly help make it clear, but isn't
currently available. If you're writing a larger application, or one that
will make a lot of use of the FSM, it's probably worth your while to take
the time to study the FSM classes, to take best advantage of their
capabilities. If your application will be small, the mice-maze way of doing
things should be adequate for you.
Cheers,
Derrell
------------------------------------------------------------------------------
Colocation vs. Managed Hosting
A question and answer guide to determining the best fit
for your organization - today and in the future.
http://p.sf.net/sfu/internap-sfd2d
_______________________________________________
qooxdoo-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
