I tend to use my own implementations of the mvcs classes, as I
just don't use any of the event based things. It's a strength of rl
that it is so flexible, but it also means that I am out of synch
with the standard.
What I would LUV would be an opt it for everything. You start
with a.bare context that has nothing but the injector, then every
thing else is pluged in with a line of.code.
That way I.don't have to hack out bits I don't want.
i have used RL on a few projects...been working with extjs 3/4
for the last few months. My return to actionscript is currently
with swiz. I miss RL. I will provide any help needed. Would love to
be involved in some way.
sorry for not getting back earlier - most of the RL team was at a
conference last week.
The good news regarding that is that we worked hard at getting RL 2
closer to release during that week. The bad news for you is that it
will still be a couple of months until that new version is
production-ready. So if you're developing right now and want to start
porting sooner rather than later, I'd recommend starting with what's
We will enable full or, at the very least, almost full backwards
compatibility, meaning that getting started with porting to RL 2 will
in the best case simply mean switching out a .SWC file and in the
worst case doing some simple search-and-replace stuff on your
codebase. Also, keeping conceptual backwards compatibility is one of
our highest priorities. That means that what you'll learn about RL 1
now won't be a waste as the fundamental concepts won't be thrown out
Saw your talk at FOTB this year, it was most excellent!
Quick question for RL 2.0: will there be any features added to the
core of the MVCS implementation that deals with asynchronous
command chaining? This 'commandmap.loadFlow(...)' you hinted at
sounds like it may be something along these lines. Most of my apps
go through a bootstrap process to load external resources, hit
various webservice APIs etc. before I can put my view in 'ready'
mode. Since switching to RL I've tried chaining synchronous
commands (feels dirty), tried Joel's state mancine utility (pretty
verbose), and various other approaches. I still haven't managed to
find the procedure that feels as nice as the asynchMacroCommand
utility I used in the PureMVC days: http://trac.puremvc.org/Utility_AS3_AsyncCommand
even though this approach might be a bit 'naughty'
Support Staff40 Posted by creynders on 27 Oct, 2011 02:06 PM
Will RL2 have some kind of hooking mechanism to allow to react
to object instantiation?I saw in the_future branch of SS that he's
implementing various events to be dispatched upon mapping,
instantiation etc. Will these allow us to hook into the process and
for instance map a command that configures an instance when it's
created? Allowing for lazy instantiation and
configuration? Are these events system wide? Or SS adapter
specific? And I suppose there'll be some kind of mechanism to map a
command to a specific class instantiation?
I'll stop with the questions now. :)
RL2 will most likely do away with the adapters as it is becoming
unfeasible to do an adapter that still allows you to fully exercise
the Swiftsuspenders API. So yeah: You'll be able to hook into all
instance creation internal to RL2.
I'm not sure I understand what you mean by "I suppose there'll be some
kind of mechanism to map a command to a specific class instantiation",
can you clarify?
How could I let this opportunity to piggy-back pass by?
If you want to do a first step towards converting your existing apps
to RL2, you can do so by using RL1 in conjunction with Swiftsuspenders
2. I have uploaded a special build of Robotlegs 1.5.2 to my fork on
This build contains Swiftsuspenders 2 and a modified Injector adapter
and context to make it a drop-in replacement for Swiftsuspenders 1. In
theory, and I hope in practice, too, everything should continue to
work as before. I'd be happy to get confirmations for that or bug
Also, if you want to start using the new API of Swiftsuspenders 2, you
can simply inject the injector itself with the type "Injector" instead
of "IInjector" and do so. An oh so very short outline of that new API
can be found in the README here: