On 8/09/2010, at 6:31 PM, Laurent Sansonetti wrote:
> Hi Henry,
>
> Sorry for the late response.
>
> On Sep 6, 2010, at 5:52 PM, Henry Maddocks wrote:
>
>> I've been working on a MacRuby/Cocoa app and I'm getting to close to
>> release. Is their any docs on how to prepare your app for release
Yes, I am very, very sorry I forgot the completely necessary `if (self = [super
init])`. It's been a while since I last wrote actual Obj-C code haha.
Thank you for correcting me!
--
Thibault Martin-Lagardette
On Sep 8, 2010, at 16:27, russell muetzelfeldt wrote:
> On 09/09/2010, at 4:22 AM,
On 09/09/2010, at 4:22 AM, macruby-devel-requ...@lists.macosforge.org wrote:
> Date: Wed, 8 Sep 2010 11:22:37 -0700
> From: Thibault Martin-Lagardette
>
>> I don't think I've seen any examples using the initWith method. Is that
>> method called after init?
>
> Simply something of the like:
>
> 3) If I have an empty init, e.g.,
>
> def init; super; self; end
>
> Can I always delete the empty init and get the same result through
> inheritance?
Yes, you can omit the #init declaration in this case, it works like a charm,
because every Obj-C object (and thus every MacRu
Here is an example: http://macruby.labs.oreilly.com/ch01.html#_class
- Matt
On Wed, Sep 8, 2010 at 10:52 AM, Robert Rice wrote:
> Thanks Matt:
>
> I don't think I've seen any examples using the initWith method. Is that
> method called after init?
>
> Bob Rice
>
>
> On Sep 8, 2010, at 12:22 PM,
Thanks Matt:
I don't think I've seen any examples using the initWith method. Is that method
called after init?
Bob Rice
On Sep 8, 2010, at 12:22 PM, Matt Aimonetti wrote:
> initWith
___
MacRuby-devel mailing list
MacRuby-devel@lists.macosforge.org
On 8 Sep 2010, at 17:22, Matt Aimonetti wrote:
> 3) If I have an empty init, e.g., def init; super; self; end
>Can I always delete the empty init and get the same result through
> inheritance?
Yes. Ruby will look for the method in your subclass, then go up the class
hierarchy to the
1) Does MacRuby distinguish between Objective C subclasses and other Ruby
classes or are all classes treated the same?
Not really but Cocoa classes expect to be returned self in the init process
and the Cocoa convention is not to overwrite init but to create your own
initializer using the initWith
Nope:
In consideration of your agreement to abide by the following terms,
and subject to these terms, Apple grants you a personal, non-exclusive
license . . . to use, reproduce, modify and redistribute the Apple
Software, with or without modifications, in source and/or binary
forms; provided that
Laurent,
Do I need to get some sort of internal apple approval post this project on
github?
Matthew
On Sep 7, 2010, at 11:33 PM, Laurent Sansonetti wrote:
> Hi Matthew,
>
> Looks like a valuable addition to me :) Thanks for proposing to work on this.
> It looks ambitious so if you need help
Thanks Matt:
Good tutorial on super. Maybe someone could add a keyword section to ruby-doc.
This leads me to a couple more questions on super and MacRuby inheritance:
1) Does MacRuby distinguish between Objective C subclasses and other Ruby
classes or are all classes treated the same?
2) Can m
Hey Matthew,
I'd probably be interested in contributing to a MacRuby implementation
of Slides. Please post here if you create a repo at github, codaset,
or something like that.
/Felix
> Laurent
>
> On Aug 27, 2010, at 7:52 PM, Matthew Smith wrote:
>
>> I'm looking at implementing the Cocoa Slide
12 matches
Mail list logo
