Over 10 years of community discussion and knowledge are maintained here as a read-only archive.
By the way, I think that chaining asynch transitions (I mean visual transitions), should be managed in the view region of the framework into a transition manager or something like that. Commands should only start a transition chain/sequence and let the transitionsManager or specialTransition mediator handle everything as a blackbox. It may send a notification when the sequence of transitions is finished. But such notifications should be used precautionously to avoid having visual transitions to call commands on proxy, which sounds to me not very clean and logicall, isn't it?I wonder what is your recommandations on this point Cliff.What would be the best practice to manage transitions and their chaining? (especially if they do not depends on built in Flex transition (between states), but on third parties Tweening packages). Should we use a kind of delegate on mediators to link to transition manager?
I believe some thought should be put into the matter of states/effects/transitions being managed.
public interface IAsyncCommand { /** * Execute the <code>ICommand</code>'s logic to handle a given <code>INotification</code>. * * @param note an <code>INotification</code> to handle. * @param responder an <code>IResponder</code> to report the result of the command. */ function execute( notification:INotification, responder:IResponder ) : void; }
public class SimpleAsyncCommand extends Notifier implements ICommand, INotifier, IResponder { ... }