On 4/28/14, 7:21 PM, Patrick Hanevold wrote:
There is only the github at the moment
(https://github.com/patrickhno/cocoa).
If you guys have a suggestion for a particular flavor of mailing list,
sure - I can set one up and participate.
Patrick
How does this gem compare to rubyobjc:
https://gi
There is only the github at the moment (https://github.com/patrickhno/cocoa).
If you guys have a suggestion for a particular flavor of mailing list, sure - I
can set one up and participate.
Patrick
On 29. apr. 2014, at 01:10, "Perry E. Metzger" wrote:
> On Mon, 28 Apr 2014 23:00:28 +0200 Patri
On Mon, 28 Apr 2014 23:00:28 +0200 Patrick Hanevold
wrote:
> I suggest people interested in cocoa in ruby help out refining the
> cocoa gem instead of hoping for any progress on mac ruby which is
> abandoned by its creators for commercial interests. The cocoa gem
> is quite useful all ready, but n
At this point, is there any active development left in the MacRuby
world or is it time to do things like shutting down the mailing list
etc.?
Perry
--
Perry E. Metzgerpe...@piermont.com
___
MacRuby-devel mailing list
MacRuby-devel@lists.
I suggest people interested in cocoa in ruby help out refining the cocoa gem
instead of hoping for any progress on mac ruby which is abandoned by its
creators for commercial interests.
The cocoa gem is quite useful all ready, but need to mature a bit in some cases.
Sent from my iPad
On 28. apr.
On 4/28/14, 8:52 AM, Shannon Love wrote:
Macruby rewrote ruby from the ground up in objective-c. It installed an
entirely different framework and generated it's own gems etc. When you
compiled the app, you got objective-c, not ruby, at runtime. You did end up
with the entire MacRuby framework
