Hi Team: Converting a RubyCocoa project to MacRuby should I convert my Objective C objects to normal Ruby objects (excluding NS objects) and get rid of the call to alloc? Bob Rice
Hi, the XCode MacRuby templates are generating .nib files instead of xib files (like Obj-C projects). (.xib is better for diffs in git or svn) Bernd
Indeed, .xib is probably the way to go now. if one wants to submit a patch for this I will merge it :) Laurent On Oct 12, 2009, at 9:04 AM, B. Ohr wrote:
Hi,
the XCode MacRuby templates are generating .nib files instead of xib files (like Obj-C projects).
(.xib is better for diffs in git or svn)
Bernd _______________________________________________ MacRuby-devel mailing list MacRuby-devel@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
Hi Robert, Could you be more explicit? I don't understand your question :) Thanks, Laurent On Oct 12, 2009, at 8:15 AM, Robert Rice wrote:
Hi Team:
Converting a RubyCocoa project to MacRuby should I convert my Objective C objects to normal Ruby objects (excluding NS objects) and get rid of the call to alloc?
Bob Rice
_______________________________________________ MacRuby-devel mailing list MacRuby-devel@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
Hi Laurent: In my RubyCocoa code I found that I had to create Obj C objects (using alloc and an init call to super) to pass to NS tables since the UI keeps copies of my objects. If all objects in MacRuby are Objective C objects are the calls to alloc and to super still required? Bob Rice On Oct 12, 2009, at 3:15 PM, Laurent Sansonetti wrote:
Hi Robert,
Could you be more explicit? I don't understand your question :)
Thanks,
Laurent
On Oct 12, 2009, at 8:15 AM, Robert Rice wrote:
Hi Team:
Converting a RubyCocoa project to MacRuby should I convert my Objective C objects to normal Ruby objects (excluding NS objects) and get rid of the call to alloc?
Bob Rice
_______________________________________________ MacRuby-devel mailing list MacRuby-devel@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
_______________________________________________ MacRuby-devel mailing list MacRuby-devel@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
You can now pass true Ruby objects to a table or outline view datasource (since MacRuby doesn't use proxies) but keep in mind that you must always pass the same unique references and not copies, as mentioned in the documentation. http://developer.apple.com/mac/library/documentation/Cocoa/Reference/Applica... Also, check out the OutlineView sample code that ships with MacRuby as an example. HTH, Laurent On Oct 12, 2009, at 2:00 PM, Robert Rice wrote:
Hi Laurent:
In my RubyCocoa code I found that I had to create Obj C objects (using alloc and an init call to super) to pass to NS tables since the UI keeps copies of my objects. If all objects in MacRuby are Objective C objects are the calls to alloc and to super still required?
Bob Rice
On Oct 12, 2009, at 3:15 PM, Laurent Sansonetti wrote:
Hi Robert,
Could you be more explicit? I don't understand your question :)
Thanks,
Laurent
On Oct 12, 2009, at 8:15 AM, Robert Rice wrote:
Hi Team:
Converting a RubyCocoa project to MacRuby should I convert my Objective C objects to normal Ruby objects (excluding NS objects) and get rid of the call to alloc?
Bob Rice
_______________________________________________ MacRuby-devel mailing list MacRuby-devel@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
_______________________________________________ MacRuby-devel mailing list MacRuby-devel@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
_______________________________________________ MacRuby-devel mailing list MacRuby-devel@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
participants (3)
-
B. Ohr
-
Laurent Sansonetti
-
Robert Rice