Hi Cliff:
As a test I tried to extend the AsyncMacroCommand Pattern to accommodate adding other AsyncMacroCommands, just like MacroCommand could not only execute SimpleCommands but other MacroCommands as well.
I edited single line in my own local copy to make it work inside AsyncMacroCommand.prototype.nextCommand
var isAsync = commandInstance instanceof puremvc.asynccommand.AsyncCommand || commandInstance instanceof puremvc.asynccommand.AsyncMacroCommand;
It works fine, UberAsyncMacroCommand executes FirstAsyncMacroCommand which executes all of it's sub AsyncCommands in sequence (asynchronously) and then turns to SecondAsyncMacroCommand executing it's series of AsyncCommands (asynchronously) and finally UberAsyncMacroCommand onComplete.
The exception that individual AsyncMacroCommands' onComplete functions are taken over by the Uber AsyncMacroCommand, i.e. no custom onCompleteHandlers for each subAsyncMacroCommands.
any thoughts on this on? or even should we have individual custom onComplete handlers for each subAsyncMacroCommands?