While I agree that HotCocoa should not aspire to wrap all APIs, I think that providing a mapping file for NSWorkspace is nevertheless a good idea. #workspace could return the shared workspace by default (I'm not even sure if you can get a different workspace instance) then we could create a custom #open method. workspace.open('http://google.com') Thoughts? Laurent On Nov 9, 2008, at 10:30 AM, Eloy Duran wrote:
On 9 nov 2008, at 16:19, Matt Aimonetti wrote:
hmm I guess I disagree but since I just got started with MacRuby and don't know Cocoa I might be totally wrong.
Yes, this is what I thought too when first starting with Cocoa in RubyCocoa, but I was very wrong. Most helpful docs/references are either from Apple or by googling for other source etc which are all in Objective-C.
Now imagine everything would be wrapped and abstracted away from MacRuby users, then all these resources out on the web are useless…
For instance, the RubyCocoa syntax, is imo very easy to read compared to what the Apple references mention, however even this was too hard to understand for a lot of starting users.
My hope is to have all the common cocoa methods available in Ruby so I can quickly create simple apps without always having to dig into the cocoa documentation and create this kind of super long/not so obvious method calls.
I would really hope HotCocoa will not aspire to wrap everything, except for where it _really_ makes sense. And my advice to you would be to re-evaluate this after you have had the chance to really do something with Cocoa.
Cheers, Eloy
_______________________________________________ MacRuby-devel mailing list MacRuby-devel@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel