April 2014 - MacRuby-devel - lists.macosforge.org

Re: [MacRuby-devel] How dead is dead...
by Patrick Hanevold 02 May '14

02 May '14

OK, lets do a poll then, the target audience is right here I would guess. What's your preferred flavour of mailing list / group manager for the cocoa gem? Patrick On 29 Apr 2014, at 15:57, Perry E. Metzger <perry(a)piermont.com> wrote: > On Tue, 29 Apr 2014 15:48:38 +0200 Patrick Hanevold > <patrick.hanevold(a)gmail.com> wrote: >> >> There is only github for now: >> https://github.com/patrickhno/cocoa > > You should fix that. It would make it easier to have a community > develop, and google groups are trivial to start... > > Perry > >> >> Pro tip: Quite easy to look up the repository origin of gems on >> rubygems.org >> >> Patrick >> >> On 29 Apr 2014, at 15:42, Perry E. Metzger <perry(a)piermont.com> >> wrote: >> >>> You mention no mailing list or web site... >>> >>> Perry >>> >>> On Tue, 29 Apr 2014 10:07:50 +0200 Patrick Hanevold >>> <patrick.hanevold(a)gmail.com> wrote: >>>> (Sorry if this mail shows up multiple times, the mailing list >>>> suddenly has some issues with my gmail accounts, so this is yet >>>> another repost attempt) >>>> >>>> Cool, another dead horse to kick. >>>> It works for starters. >>>> >>>> cocoa is a more direct approach where methods are equivalent to >>>> the apple docs - as they are bindings, not some wrapped up stubs. >>>> I would probably guess there is a lot of stuff not even >>>> accessible through rubyobjc - if you even get that 6 year old >>>> thing up and running. >>>> >>>> cocoa exploits modern ruby to use keyword arguments and >>>> everything that makes ruby quite equivalent to what you would do >>>> in objective-c. >>>> >>>> cocoa is a modern integration, and here is a example usage that >>>> will probably massage your marble for a moment. >>>> Here you see multiple tasks of NSTableViewDelegate. Notice how >>>> cocoa exploit keyword arguments to allow you to define the same >>>> method twice, with different keyword arguments equivalent to the >>>> two tasks selectors. >>>> >>>> >>>> def tableView(table_view, objectValueForTableColumn: nil, row: >>>> nil) >>>> cache[row].send(objectValueForTableColumn.identifier.to_s.to_sym).to_s >>>> end >>>> >>>> >>>> def tableView(table_view, shouldSelectRow: nil) >>>> hooks[:on_select_row].call(shouldSelectRow) if >>>> hooks[:on_select_row] true >>>> end >>>> >>>> Patrick >>>> >>>> Mvh. >>>> Patrick Hanevold >>>> >>>> >>>> >>>> On Tue, Apr 29, 2014 at 2:48 AM, Kevin Walzer >>>> <kw(a)codebykevin.com> wrote: >>>> >>>>> 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://github.com/timburks/rubyobjc >>>>> >>>>> ? >>>>> >>>>> >>>>> -- >>>>> Kevin Walzer >>>>> Code by Kevin/Mobile Code by Kevin >>>>> http://www.codebykevin.com >>>>> http://www.wtmobilesoftware.com >>>>> >>>>> _______________________________________________ >>>>> MacRuby-devel mailing list >>>>> MacRuby-devel(a)lists.macosforge.org >>>>> https://lists.macosforge.org/mailman/listinfo/macruby-devel >>>>> >>> >>> >>> >>> -- >>> Perry E. Metzger perry(a)piermont.com >> > > > > -- > Perry E. Metzger perry(a)piermont.com

3 4

How dead is dead...
by Perry E. Metzger 29 Apr '14

29 Apr '14

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. Metzger perry(a)piermont.com

4 7

Re: [MacRuby-devel] Trying to embed standard Ruby in an app...how does MacRuby do it?
by Kevin Walzer 28 Apr '14

28 Apr '14

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 in every app and IIRC, any gems you wished as well. As a result, even a very simple Macruby app had a huge disk footprint. > > Looks like install_name_tool's entire point is to copy a tool into a project and then alter the paths to be relative to the executable. If it's not doing that it's likely a config problem with the tool and not the nature the Ruby install. Actually, I found a configure flag for Ruby that makes this feasible: --enable-load-relative After that, I was able to do some additional jiggering with install_name_tool to get things running as expected in an app bundle. --Kevin -- Kevin Walzer Code by Kevin/Mobile Code by Kevin http://www.codebykevin.com http://www.wtmobilesoftware.com

1 0

Trying to embed standard Ruby in an app...how does MacRuby do it?
by Kevin Walzer 28 Apr '14

28 Apr '14

I'm trying to embed standard Ruby 2.1 (MacPorts installed) in an app using a stub launcher that calls an embedded interpreter. I've run install_name_tool correctly on the Ruby dylib and bundles, etc., but I'm having trouble: the app is still looking in the MacPorts directory (/opt/local) for its load path. Running "strings" on my bundled Ruby dylib shows that search paths are hard-coded into the dylib itself, so install_name_tool has no effect. How did MacRuby handle this? Did MacRuby bundle the entire Ruby runtime into the app or did it rely on the system installation of MacRuby? If the latter is the case, and it simply isn't possible to make a truly relocatable Ruby app using install_name_tool, then my job is a lot easier, because Mavericks has standard Ruby (2.0) bundled in. --Kevin -- Kevin Walzer Code by Kevin/Mobile Code by Kevin http://www.codebykevin.com http://www.wtmobilesoftware.com

1 0