He's probably using Signals differently, and doing more dependency injection
with them than I currently am. He's the pro. On my end, I have found the
opposite to be true, since most of the time when you create a Signal, unlike
custom events, you don't have to create any classes. If you have to inject a
signal, sure, you create a class for that, but the same would be true of custom
events (and in fact every custom event would have to have an associated class
in every situation, unlike Signals), and creating a Signal class is simpler
because you don't have to add any boilerplate code like you do for custom
events. To me, Signals (simply declared as a public property, or with an
associated class than extends Signal) are simpler and more elegant to handle
than custom events.
Overall, I would far prefer to use Signals over Events in a Robotlegs project
(that said, I'm only on my third Robotlegs project now).
Jason Merrill
Instructional Technology Architect
Bank of America Global Learning
___
From: David Wilcox [mailto:dwgoldfi...@gmail.com]
Sent: Sunday, July 24, 2011 1:27 AM
To: Merrill, Jason
Subject: Re: [Flashcoders] Signals in Robotlegs
Thanks for the advice. I had also asked the same question on the Robotlegs
Forums, but Flashcoders gave a faster response. I did eventually get a response
from Joel Hooks, and he linked a conversation here:
https://m.google.com/app/plus/mp/451/#~loop:backv=notificationsaid=z13cf5ub5n3vfn4cw23wv3abfu2aed0d3type=1fr=1view=activity
in which he said signals have a significant cognitive overhead in larger
projects because of all the extra classes he has to create, but either way I'll
take what you've said into account when I apply changes to my app.
Thanks again,
Dave Wilcox
On 21 July 2011 23:26, Merrill, Jason
jason.merr...@bankofamerica.commailto:jason.merr...@bankofamerica.com wrote:
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.commailto:flashcoders-boun...@chattyfig.figleaf.com
[mailto:flashcoders-boun...@chattyfig.figleaf.commailto:flashcoders-boun...@chattyfig.figleaf.com]
On Behalf Of David Wilcox
Sent: Wednesday, July 20, 2011 11:35 PM
To: flashcoders@chattyfig.figleaf.commailto: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.commailto: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
