tag:robotlegs.tenderapp.com,2009-10-18:/discussions/robotlegs-2/6-robotlegs-20-the-path-from-hereRobotlegs: Discussion 2018-10-18T16:35:36Ztag:robotlegs.tenderapp.com,2009-10-18:Comment/82922372011-06-30T17:36:38Z2011-06-30T17:36:39ZRobotlegs 2.0 - the path from here<div><p>Hey Stray</p>
<p>I would love to be a Beta Tester for Robotlegs, just let me
know!</p>
<p>=)</p></div>Silvio Paganinitag:robotlegs.tenderapp.com,2009-10-18:Comment/82922372011-06-30T17:58:24Z2011-06-30T17:58:24ZRobotlegs 2.0 - the path from here<div><p>I would love to test both alpha and beta!</p></div>creynderstag:robotlegs.tenderapp.com,2009-10-18:Comment/82922372011-06-30T18:01:27Z2011-06-30T18:01:27ZRobotlegs 2.0 - the path from here<div><p>We won't have any "internal" betas anyway: Everything more than
one of<br>
us gets to see will be on github, as that's what we're using
for<br>
collaboration. For the more unstable releases, you might have to
keep<br>
an eye on what's happening on github, while we'll send out<br>
informational posts to the mailing list for milestones we want
people<br>
to test.</p></div>Till Schneidereittag:robotlegs.tenderapp.com,2009-10-18:Comment/82922372011-06-30T18:17:50Z2011-06-30T18:17:50ZRobotlegs 2.0 - the path from here<div><p>Ah yes - thanks Till, it was a bit misleading. To clarify that -
anyone can get their hands on the releases, so what I'm aiming to
have is a list of people who give us feedback and who we can ask
directly to switch in new builds and see what is fixed /
borked.</p>
<p>Silvio & Camile - thanks, you're on my list.</p></div>Straytag:robotlegs.tenderapp.com,2009-10-18:Comment/82922372011-06-30T19:20:42Z2011-06-30T19:20:42ZRobotlegs 2.0 - the path from here<div><p>Count me in!<br>
Would love to contribute!</p>
<p>/ @laveklint</p></div>Pierre Laveklinttag:robotlegs.tenderapp.com,2009-10-18:Comment/82922372011-06-30T19:39:29Z2011-06-30T19:39:29ZRobotlegs 2.0 - the path from here<div><p>Ah, I thought we would be handed out mirror glasses, green ties
and one hour valid passwords for testing the various releases ...
Damn open-source projects! ;)</p>
<p>Just a note of concern: I think many people will be upset if
you're abandoning FP9 though. I suppose maintaining a FP9-fork will
be an insane amount of work, right?<br>
I'm just wondering whether vectors will be worth it.</p></div>creynderstag:robotlegs.tenderapp.com,2009-10-18:Comment/82922372011-06-30T19:48:14Z2011-06-30T19:48:14ZRobotlegs 2.0 - the path from here<div><p>If you insist, we might be able to arrange some green ties. The
mirror<br>
glasses, though: Just no. Oh, but we can give you a password to
be<br>
used as you desire - for exactly one hour - if that helps.</p>
<p>As for FP9 - you might be right about that. I will post to the
mailing<br>
list to gauge the general feeling of people. If it turns out to
be<br>
really important to many developers, maintaining a<br>
backwards-compatible version might not be too hard after all. In
fact,<br>
I discovered today that Swiftsuspenders just doesn't use Arrays
enough<br>
to even bother with Vectors.</p></div>Till Schneidereittag:robotlegs.tenderapp.com,2009-10-18:Comment/82922372011-06-30T19:54:34Z2011-06-30T19:54:34ZRobotlegs 2.0 - the path from here<div><p>Ditto on the FP10 thing - it's useful for places where you can
pass an Array of X where we otherwise need to check types to defend
against errors, but I don't think that maintaining both forks would
be hard - we'd use that fancy regex stuff to simply downgrade
Vector references in method sigs in most places I guess.</p></div>Straytag:robotlegs.tenderapp.com,2009-10-18:Comment/82922372011-06-30T20:16:59Z2011-06-30T20:16:59ZRobotlegs 2.0 - the path from here<div><p>happy to help in what ever way</p></div>neiltag:robotlegs.tenderapp.com,2009-10-18:Comment/82922372011-07-01T02:43:01Z2011-07-01T02:43:03ZRobotlegs 2.0 - the path from here<div><p>I'll definitely try to contribute as much as possible. I also
really want to create a larger example app for modular
applications.</p>
<p>@Stray: I'm curious if the team talk about adding modular
support into RL2. Also am curious if there will be a
RL_PopupManager to help with mediating Popups.</p>
<p>And is there a dev-forum or IRC channel where someone interested
in contributiong could go? I just joined #robotlegs-dev on
freenode. but it wasn't even registered or anything...</p>
<p>Thanks! I love RL!</p></div>seantag:robotlegs.tenderapp.com,2009-10-18:Comment/82922372011-07-01T08:06:09Z2011-07-01T08:06:09ZRobotlegs 2.0 - the path from here<div><p>Hi guys and gal,</p>
<p>Looking forward to the new API, because I'm really curious what
new additions you've come up with to make RL even better than it
already is.</p>
<p>Cheers and see you in Brighton!<br>
Erik</p></div>eriktag:robotlegs.tenderapp.com,2009-10-18:Comment/82922372011-07-01T08:48:15Z2011-07-01T08:48:15ZRobotlegs 2.0 - the path from here<div><p>Wow, now that's teasing right here!<br>
Stray, you're really good at it.</p>
<p>Of course I'll test the alpha and beta versions. Of course I'll
share feedback.<br>
That <code>commandMap.loadFlow</code> is mysterious, can't
wait!</p></div>Quentintag:robotlegs.tenderapp.com,2009-10-18:Comment/82922372011-07-01T09:25:04Z2011-07-01T09:25:04ZRobotlegs 2.0 - the path from here<div><p>Great news Stray! You can count on me. And of course Flash
Player 10 is a way to go.</p></div>Michal Wroblewskitag:robotlegs.tenderapp.com,2009-10-18:Comment/82922372011-07-01T09:27:44Z2011-07-01T09:27:44ZRobotlegs 2.0 - the path from here<div><p>@sean: There will be support for multiple contextViews and an
easy way to register them. I hope that that will cover Flex popups.
If it does<br>
not, there shall be a utility!</p></div>Till Schneidereittag:robotlegs.tenderapp.com,2009-10-18:Comment/82922372011-07-01T09:39:56Z2011-07-01T09:39:56ZRobotlegs 2.0 - the path from here<div><p>Thanks all of you - we spent a lot of time while away just
marvelling about how amazing the RL community is!</p>
<p>@neil - we want to talk to you about state machines in the
coming weeks!</p>
<p>@sean - I can confirm that we spent a lot of energy thinking
about multi-context apps and the biggest changes in RL2 under the
hood are linked to this. We've got a very small amount of detail on
that left to figure out, but the intention is that modular apps
will 'just work'. The trick with modular is that you also want your
modules to be viable as individual units - and so we're trying to
figure out the 'least brain confusion' way to do that... and I see
Till just beat me to that! But yes, demos that provide rich use
cases will be really, really valuable so I shall poke you about
that for sure.</p>
<p>Also - on the IRC thing, as soon as we've got the core sorted,
I'll try to figure out some sort of schedule where you can know
that at certain times of the week you can get real-time support
from someone on the core dev team in IRC. Does that sound useful?
Kind of an online-tutorial-group scenario, maybe?</p>
<p>Is IRC the best format / tool for that, or would something like
Adobe Connect be more appropriate? I've (shock!) never really used
IRC so I'm not sure what it gives you.</p>
<p>Stray</p></div>Straytag:robotlegs.tenderapp.com,2009-10-18:Comment/82922372011-07-01T09:46:06Z2011-07-01T09:46:06ZRobotlegs 2.0 - the path from here<div><p>ooh super! you know where to find me :)</p></div>neiltag:robotlegs.tenderapp.com,2009-10-18:Comment/82922372011-07-01T09:59:43Z2011-07-01T09:59:44ZRobotlegs 2.0 - the path from here<div><p>@Till: I like it!</p>
<p>@Stray: It's really just a simple chat room, people can bounce
in and out off. I don't think it would replace things like this
newsletter that you want people to have a hard copy of. But it is
very nice for quick communication.</p>
<p>Not to compare apples to oranges. But most other frameworks that
I participate in (Zend, Mootools, Fedora) have 2 or 3 different IRC
channels. one for basic support/discussion/hangout room
(#robotlegs) and the other for framework development
(#robotlegs-dev?).</p>
<p>Fedora takes it to another level because of it's massive
following. They have a designated #fedora-meeting for developer to
schedule meetings based on a certain issue/problem/task. Because
there other 2 channels have over 500 people at all times.</p>
<p>Right now #robotlegs is lucky to have 10 people in there at a
time. I've started trolling our #robotlegs channel lately thou,
trying to give as much support as possible.</p></div>seantag:robotlegs.tenderapp.com,2009-10-18:Comment/82922372011-07-01T16:42:18Z2011-07-01T16:42:18ZRobotlegs 2.0 - the path from here<div><p>I've used RL 1.x for several projects and really want to test
2.x. Maybe it will wash away some angst I've got about OOP/OOD when
I started to dig into functional programming.</p>
<p>P.S.<br>
RL 1.x saved me days of writing boilerplate code. Thanks!</p></div>nikdudniktag:robotlegs.tenderapp.com,2009-10-18:Comment/82922372011-07-01T18:23:46Z2011-07-01T18:23:47ZRobotlegs 2.0 - the path from here<div><p>Sounds like a great path for 2.0. I'd be happy to provide
feedback with the process of migrating a 1.x app to 2.x.</p></div>Mike Hauglandtag:robotlegs.tenderapp.com,2009-10-18:Comment/82922372011-07-02T01:52:19Z2011-07-02T01:52:21ZRobotlegs 2.0 - the path from here<div><p>Used RL on pretty much every project for the last 18ish months,
would love to be involved.</p></div>matttag:robotlegs.tenderapp.com,2009-10-18:Comment/82922372011-07-05T07:37:28Z2011-07-05T07:37:29ZRobotlegs 2.0 - the path from here<div><p>This all sounds great! I'll also be happy to provide
feedback.</p>
<p>On the FP9 issue, I personally dropped it a few months ago, I
managed to make our clients realise the benefits. So I'm ready for
no FP9 support, save every millisecond where possible!</p>
<p>So let me know where I can help out!</p>
<p>:D Excited :D</p></div>Matan Ubersteintag:robotlegs.tenderapp.com,2009-10-18:Comment/82922372011-08-12T00:49:54Z2011-08-12T00:49:54ZRobotlegs 2.0 - the path from here<div><p>Sounds like excellant news, will keep my ear to the ground on
beta rumblings when you release the version. One suggestion from
me, There seems to be alot of SIgnal implementations of Robotlegs
that I'm utilizing. SignalMediator, SignalCommand, SignalMap,
etc... I wondered if you've thought about having RL 2 being purely
signal based? or a port that is?</p></div>Karl Freemantag:robotlegs.tenderapp.com,2009-10-18:Comment/82922372011-08-12T12:05:15Z2011-08-12T12:05:15ZRobotlegs 2.0 - the path from here<div><p>@Karl: I was thinking about this as well. For example, I never
use events in my current projects, it's all based on Signals. This
means support for events is unnecessary in these projects. I think
it would be very interesting to have a barebone MVCS implementation
and to, for example at Context startup, have the option to add
support for either events or signals, or both! :D</p></div>Abel de Beertag:robotlegs.tenderapp.com,2009-10-18:Comment/82922372011-08-12T12:09:58Z2011-08-12T12:09:59ZRobotlegs 2.0 - the path from here<div><p>@Abel I like the concept of supporting both. Think that would go
down a storm rather than lots of utility classes scattered around.
For instance a base MVCS that you then extend upon for
implementations. IContext anyone? with a SignalContext and
EventContext?</p></div>Karl Freemantag:robotlegs.tenderapp.com,2009-10-18:Comment/82922372011-08-12T13:42:42Z2011-08-12T13:42:42ZRobotlegs 2.0 - the path from here<div><p>One of the great things about RL is it's lightweight. Events are
native, therefore they don't add any weight, so IMO it's only
logical that the main notification system is based on it. One of
the main advantages of having scattered utilities and extensions is
that you can cherrypick them and only add what you really want.
It's one of the things I regret with GreenSock's libs that they
come out-of-the-box all inclusive.<br>
That having said, extensibility is one of the things that should
definitely be rewritten entirely for RL 2. At the moment I think
I'd favor a modular/plugin approach. For instance you could have a
Signal stack that contains signalcommands, signalcommandmap and
signals. Drop it in and you're ready to go.<br>
If such an approach would be chosen, it would be imperative to have
a centralizing dashboard/website/whatever in which you can easily
find and add modules/plugins. It's one of the reasons drupal is so
popular I think: tons of modules and a very easy way to find
them.</p></div>creynderstag:robotlegs.tenderapp.com,2009-10-18:Comment/82922372011-08-12T13:49:29Z2011-08-12T13:49:30ZRobotlegs 2.0 - the path from here<div><p>@creynders Couldn't agree more. For sure don't rip out events
but I think a think about how to integrate Signals without 4
different utilities would be an excellant step forward. With
regards to GreenSock, If you use TweenLite's TweenPlugin you
should'nt have that issue of an out-of-the-box all-inclusive
feeling with TweenMax ( something which I share with you and don't
much like )</p></div>Karl Freemantag:robotlegs.tenderapp.com,2009-10-18:Comment/82922372011-08-12T14:07:25Z2011-08-12T14:07:25ZRobotlegs 2.0 - the path from here<div><p>@Karl @Abel @creyenders - in RL2 you won't be extending a
context class manually - there will be a much more flexible way of
composing the context instead.</p>
<p>On Events / Signals - the view in the team is that we will get
the bare bones working with Events, and because of the new "compose
features" approach, switching from events to signals or a
combination of the two should be a line or two (assuming people
build out equivalent signals-based functionality for the event
driven parts).</p>
<p>Meanwhile, Robert is targeting the 1.0 release of Signals, which
would make a big difference.</p>
<p>We do have it on our radar - it's the number one thing we all
wanted to change from Robotlegs 1.</p></div>Straytag:robotlegs.tenderapp.com,2009-10-18:Comment/82922372011-08-12T14:09:09Z2011-08-12T14:09:09ZRobotlegs 2.0 - the path from here<div><p>@Karl: yeah I know about TweenPlugin, but actually it's little
more than a convenience method for making sure the plugin class
gets compiled into the binaries. Thing is that the .swc and the src
contain all possible GS classes. The former being a problem if you
want to load it dynamically and the latter being a horrible mess
with unclear dependencies. Especially with having all tween facade
classes in the main package and the loading facade classes on the
other hand buried inside the loading subpackage. I'm an esthete, I
guess ;)</p></div>creynderstag:robotlegs.tenderapp.com,2009-10-18:Comment/82922372011-08-12T14:12:07Z2011-08-12T14:12:07ZRobotlegs 2.0 - the path from here<div><p>@stray ah, glad to hear it. Composition FTW of course. If you
need a hand with the signals-based equivalents, I would be glad to
help.</p></div>creynderstag:robotlegs.tenderapp.com,2009-10-18:Comment/82922372011-08-12T14:15:16Z2011-08-12T14:15:16ZRobotlegs 2.0 - the path from here<div><p>@stray Music to my ears. At some point alcohol / caffeine needs
to be bought for the RL gang. Keep up the good work.</p></div>Karl Freeman