[MacRuby-devel] 0.3 available for testing

Richard Kilmer rich at infoether.com
Mon Sep 8 06:04:55 PDT 2008


On Sep 7, 2008, at 3:15 PM, Joshua Ballanco wrote:

> Ditto, looking good, especially HotCocoa! There still seem to be a few

HotCocoa is coming along and we have quite a bit yet to do!  Cocoa, as
we all know is a huge API.  Making sure we have good wrappers for the
majority of the classes is something I am targeting for 0.4.  The big  
one
right now is working through NSAttributedString and the NSText
subsystem of classes.

I need to methodically go through the mappings we have and build out
the delegate mappings.  I did delegate mappings for NSWindow only right
now.

We are also trying to strike a balance between simply 'rubifying' ObjC
methods (camelCase to under_score) and providing truly better APIs
(such as view << subview), constants mapped to symbols, and the like.
My current perspective is to not just rubify things and work through
the harder problems.  My vision for HotCocoa is to create a "Interface
Builder in code" solution.  The key value of IB is smart defaults,  
simple
configuration, layout, and bindings.  If HotCocoa could do this same
thing we would not have to use IB to build UIs but just Ruby.  This is
the reason for the app directory structure in HotCocoa.

I also want to come up with a good way to getting to the documented
methods on things in something better than the current OS X doc
browser.  There is a RubyCocoa project which does something like this
which I hope to port over to MacRuby then including documentation on
HotCocoa mappings as well.  It would be nice to come up with a better
visual tool for documentation too.  I am so tired of the same old web
L&F for docs.  I hope to come up with something for 0.4 in this.

Charles had indicated in a recent post on his blog that folks were  
working
on this type of "nice Ruby layer" stuff over Java libraries on JRuby  
too.
I hope that HotCocoa does, indeed, work as a nice approach to wrapping
the Cocoa classes because I think it will help Rubiests come to
MacRuby and be able to effectively leverage the massive set of
frameworks on OS X.

Best,

Rich

>
> issues with macgem. I tried removing GitHub from my sources
> (processing gem metadata from GitHub was causing issues), and that
> left my .gemrc corrupt (I've attached the corrupted version). It seems
> like the issue is with YAML processing. After getting that worked out,
> I was able to install the 'git' gem with no problem, but installing
> ActiveRecord failed. I get:
> ERROR:  Error installing activerecord:
> 	activerecord requires  ()
> Which, btw, are there plans on merging MacGem with RubyGems 1.2? I
> noticed that macgem --version is still reporting 1.1.1
>
> I'll keep banging on it and let you know if I come across anything  
> else.
>
> Cheers,
>
> Josh
>
>
> On Sep 7, 2008, at 2:48 PM, Charles Oliver Nutter wrote:
>
>> Built and installed ok for me, btw. I don't have any apps to run  
>> but a
>> few tests I tried seemed ok. OS X 10.5.4.
>>
>> Laurent Sansonetti wrote:
>>> Hi,
>>>
>>> It's time for another release, this time 0.3. The content of trunk
>>> was
>>> merged into the testing branch, and unless something really bad is
>>> reported, it will be released tomorrow to the public.
>>>
>>> There has been a lot of work on trunk recently, here are some
>>> important changes:
>>>
>>> - HotCocoa! This is a new core library that ships with MacRuby, and
>>> greatly simplifies Cocoa programming, using Ruby idioms when
>>> necessary. Rich Kilmer is the man behind most (to not say all) this
>>> work. There are a few samples in the HotCocoa subdirectory, and some
>>> bits of documentation in http://www.macruby.org/trac/wiki/HotCocoa
>>> (which will be improved soon). It's still a work in progress, but
>>> it's
>>> very promising, and also it's very simple to help by contributing
>>> mappings.
>>>
>>> - MacRuby is now using the Objective-C runtime to implement the Ruby
>>> class semantics and also to dispatch Ruby methods. This is an
>>> important change because it simplifies the core implementation a  
>>> lot,
>>> and also eliminate ambiguities between both worlds. Performance wise
>>> we should be as performant as yarv, faster in some cases, slower in
>>> others. There are still a few things I can do to improve them  
>>> though.
>>>
>>> - Interface Builder support. IB will automatically recognize  
>>> classes,
>>> outlets and actions that you implement in Xcode. I implemented a new
>>> parser in MacRuby for that, based on ripper, and it should work with
>>> both RubyCocoa and MacRuby files.
>>>
>>> - Lots of bug fixes, especially regarding Ruby and Cocoa
>>> compatibility. We are able to run RubyGems and LimeChat! And I  
>>> ported
>>> the PagePacker application to MacRuby (you can find it in the sample
>>> code too), which uses many Cocoa features.
>>>
>>> Please give it a test if you can!
>>>
>>> $ svn co http://svn.macosforge.org/repository/ruby/MacRuby/branches/testing
>>> macruby-testing
>>> $ cd macruby-testing
>>> $ rake
>>> $ sudo rake install
>>>
>>> Laurent
>>> _______________________________________________
>>> MacRuby-devel mailing list
>>> MacRuby-devel at lists.macosforge.org
>>> http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
>>
>> _______________________________________________
>> MacRuby-devel mailing list
>> MacRuby-devel at lists.macosforge.org
>> http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
>
> _______________________________________________
> MacRuby-devel mailing list
> MacRuby-devel at lists.macosforge.org
> http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel



More information about the MacRuby-devel mailing list