I just use Joel Hook's stuff. I wouldn't know if Lindquist's methods are better, but Hooks classes work just dandy. I use any of the Signals-specific stuff for Robotlegs like SignalMediator instead of Mediator, SignalCommand instead of Command (though in general, you can just use Command) and SignalContext instead of Context, and I set the signalCommandMap.mapSignalClass method inside of SignalContext to map Signals in my SignalContext.
>From there, everything works as you would expect for Signals and Robotlegs. Jason Merrill Instructional Technology Architect Bank of America Global Learning _______________________ -----Original Message----- From: flashcoders-boun...@chattyfig.figleaf.com [mailto:flashcoders-boun...@chattyfig.figleaf.com] On Behalf Of David Wilcox Sent: Wednesday, July 20, 2011 11:35 PM To: flashcoders@chattyfig.figleaf.com Subject: [Flashcoders] Signals in Robotlegs What's the best way to add signals to robotlegs? Those of you coding in Robotlegs are probably familiar with signals being used as a replacement for events. I'm looking to replace events in my app for signals but there seem to be two methods of implementing them. The first has been demonstrated by John Lindquist here: http://johnlindquist.com/2010/01/21/as3-signals-tutorial/ . He uses signal methods like 'suphero.punch(string)' to get this done. The other method uses Joel Hook's CommandSignal and SignalContext (github here: https://github.com/joelhooks/signals-extensions-CommandSignal ). This can be coupled with Stray's SignalMediator ( https://github.com/Stray/robotlegs-utilities-SignalMediator ) and instead of using signal methods like John, it involves creating a single signal for a given command. This would probably involve creating many more classes than the first method. This is what I understand of the two methods. Does anybody know why I would want to do one over the other? And if they do would they have any advice on how best to implement it (particularly with the CommandSignals and how to best deal with so many classes floating around)? _______________________________________________ Flashcoders mailing list Flashcoders@chattyfig.figleaf.com http://chattyfig.figleaf.com/mailman/listinfo/flashcoders ---------------------------------------------------------------------- This message w/attachments (message) is intended solely for the use of the intended recipient(s) and may contain information that is privileged, confidential or proprietary. If you are not an intended recipient, please notify the sender, and then please delete and destroy all copies and attachments, and be advised that any review or dissemination of, or the taking of any action in reliance on, the information contained in or attached to this message is prohibited. Unless specifically indicated, this message is not an offer to sell or a solicitation of any investment products or other financial product or service, an official confirmation of any transaction, or an official statement of Sender. Subject to applicable law, Sender may intercept, monitor, review and retain e-communications (EC) traveling through its networks/systems and may produce any such EC to regulators, law enforcement, in litigation and as required by law. The laws of the country of each sender/recipient may impact the handling of EC, and EC may be archived, supervised and produced in countries other than the country in which you are located. This message cannot be guaranteed to be secure or free of errors or viruses. References to "Sender" are references to any subsidiary of Bank of America Corporation. Securities and Insurance Products: * Are Not FDIC Insured * Are Not Bank Guaranteed * May Lose Value * Are Not a Bank Deposit * Are Not a Condition to Any Banking Service or Activity * Are Not Insured by Any Federal Government Agency. Attachments that are part of this EC may have additional important disclosures and disclaimers, which you should read. This message is subject to terms available at the following link: http://www.bankofamerica.com/emaildisclaimer. By messaging with Sender you consent to the foregoing. _______________________________________________ Flashcoders mailing list Flashcoders@chattyfig.figleaf.com http://chattyfig.figleaf.com/mailman/listinfo/flashcoders