New REPL in version 3.30?

[tsugua]

During the #inspect 2014 conference Eloy said there would be a new REPL (Reload Epic Production Loop). Any timeline for this feature?

[Fang Zhigang]

Doesn't seem like it's in this version...

[Brent Wejrowski]

Yeah I really want to know when this feature will be out. I couldn't find anything on it since that conf video. Would be nice to know when.

[tsugua]

Maybe if enough of us comment on this thread Colin will give us an update... :)

[Colin T.A. Gray]

Haha you're probably right!

Unfortunately, I have nothing to report at the moment. Eloy and Watson have been focused on maintaining the iOS/OS X compiler while Laurent continues to build and improve the android compiler, and the live code reloading has taken a back seat.

Colin T.A. Gray

Community Manager

HipByte 

On Jan 2, 2015, at 6:20 PM, tsugua <sh...@eoslightmedia.com> wrote:

Maybe if enough of us comment on this thread Colin will give us an update... :)

--
You received this message because you are subscribed to the Google Groups "RubyMotion - Ruby for iOS, OS X, and Android" group.
To unsubscribe from this group and stop receiving emails from it, send an email to rubymotion+...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/rubymotion/fd9b5725-e73e-4644-9a2f-a9531d029267%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[tsugua]

Thanks for the update Colin, I'm looking forward to the release of this feature!

[Brent Wejrowski]

Yeah definitely want to see it! Doing little design tweaks and recompiling is probably the most tedious thing for me right now.

[Andy Park]

+1 

[JJ]

+10^6 ;-)

--

You received this message because you are subscribed to the Google Groups "RubyMotion - Ruby for iOS, OS X, and Android" group.
To unsubscribe from this group and stop receiving emails from it, send an email to rubymotion+...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/rubymotion/725aa75d-061d-4578-9443-73dbe2f895a2%40googlegroups.com.

[Hwee-Boon Yar]

If this comes down to a vote, I'm going to say a 100x NO.

While I appreciate a much improved REPL (I think I filed a feature request for it a long time ago), live-coding support, the number 1 feature I would like to have (other than keeping up with new APIs) is stability. The guys have been great at supporting us, but it's clear the focus needs to be keeping things that are working working, fixing those that aren't, and not adding fancy features until things are stable.

Appreciate your work, guys, especially Watson and Eloy who gets to hear from me every few days, but keep your eye on the prize :)

–

Hwee-Boon

[Matthew Nguyen]

I support Hwee-Boon on this one.

RubyMotion should focus on fixing issues/improving documentation rather than adding new features.

Or at least, having a version naming system that enables to have at least one stable release that receives only bug fixes, no new potentially bugged features.

[Jay Bostock]

I'm keen to see improvements to the REPL, this (live code reloading) would improve my dev cycle loads... I think.

I just don't want the push to get Android support working properly to delay improvements to the iOS ecosystem. Android support is great, and hopefully brings WAY more users to the RM community, but I'm not using it (at the mo) so I kinda want my needs focussed on as well, is it okay to say that?

[Jamon Holmgren]

I'd really like to see the live code reloading feature. I'd also +1 Hwee-Boon's comment about stability. That's really important! But live code reloading would make a massive difference too in our workflow.

Jamon