Hi Bob,
Could you elaborate more on the first issue? That seems like a regression but I
didn't have that issue myself.
Also, could you please open it as a ticket on github?
The second issue I can confirm, but that code hasn't changed recently, so I
think that bug has been there for quite some t
Hi Jim,
I can only speak for myself, but moving (to another continent even), starting a
new job, and having a new baby would, I think, qualify as busy! ;-)
Admittedly the mailing list activity has dropped off a bit, but I do still and
try to monitor #macruby on Freenode and the GitHub project h
Hi Mark,
Specifically, the current nightly build installer creates a sim link for
macruby_deploy in /usr/local/bin/ to
"/tmp/macruby-nightly/Library/Frameworks/MacRuby.framework/Versions/Current/usr/bin/macruby_deploy"
instead of an executable. I get "command not found" trying to run
macruby_d
Oh, that's totally my fault. A recent change related to making MacRuby
installable to locations other than /Library/Frameworks. It has broken how the
nightly build script creates the installer package. I will try to have this
fixed for the next nightly build.
Thanks for the info,
Mark
Josh,
The recent Github activity is nice to see, and your point about MacRuby being
fairly mature is well-taken.
When I saw that Watson joined the RubyMotion team, saw the commits slow down,
and noticed the lack of mailing list activity (especially compared to the
RubyMotion Google group activ
On Sep 28, 2012, at 11:42, Jim Getzen wrote:
> Hopefully, we will see some of the RM code (such as the memory
> management model) make it back into the MR code.
I'd love to see a cooperative and friendly relationship grow
between the MR and RM communities, but I'm not sure that this
will flower wi
