[Mono-osx] [Cocoa-sharp] Crash Cocoa-Sharp

Chuck Esterbrook chuck.esterbrook at gmail.com
Wed Dec 16 23:24:32 EST 2009

On Wed, Dec 16, 2009 at 8:11 PM, Ryan Boggs
<rmboggs.obsd.ports at gmail.com> wrote:
> On Wed, Dec 16, 2009 at 7:41 PM, Chuck Esterbrook
> <chuck.esterbrook at gmail.com> wrote:
>> On Wed, Dec 16, 2009 at 7:31 PM, Ryan Boggs
>> <rmboggs.obsd.ports at gmail.com> wrote:
>>> Another question,
>>> If cocoa-sharp is unmaintained and people, like me, are being directed
>>> away from cocoa-sharp to other projects, why is it still included with
>>> the mono releases?  Unless there are some internals that still depend
>>> on it, cocoa-sharp seems to be just added fat.
>> My understanding is that it is there for any projects that might have
>> started using it. So that if you upgrade Mono, your Cocoa# app doesn't
>> break.
> This makes sense to me.  However, wouldn't those projects start
> breaking as well?
>> I agree it's problematic in that it's distracting to new users.
> Agreed.  Wouldn't it be possible to maybe mark cocoa-sharp as
> depreciated or would that be too much for something like this?
>> I wouldn't mind seeing it pushed out to a separate project and a Mono
>> wiki page directing people to the various choices for Obj-C bridging.
> Yeah, something like this would be good.  It would be better than
> having stale pages referring to cocoa-sharp.

This type of stuff is up to Miguel and company.


More information about the Mono-osx mailing list