> But once you get experienced with Cocoa and Objective-C, you can build
applications or rewrite them fairly quickly, IMHO.
Yeah but Objective-C is slowly being phased out. Someone from Apple already
said in a previous e-mail newer APIs are only available for Swift.
As for Cocoa it seems like it w
>
> On Oct 4, 2019, at 23:43, Michael Hall via Cocoa-dev
> wrote:
>
>
>
>> On Oct 4, 2019, at 2:41 PM, Lars C. Hassing via Cocoa-dev
>> wrote:
>>
>>
>> On 4 Oct 2019, at 21.00, Jens Alfke wrote:
>>
>> The people I hear complaining about this are those who, like you, didn't
>> move to Co
> On Oct 4, 2019, at 2:41 PM, Lars C. Hassing via Cocoa-dev
> wrote:
>
>
> On 4 Oct 2019, at 21.00, Jens Alfke wrote:
>
> The people I hear complaining about this are those who, like you, didn't move
> to Cocoa. Carbon was a _temporary_ transition API*. It was necessary when Mac
> OS X shi
> On Oct 4, 2019, at 12:41 PM, Lars C. Hassing via Cocoa-dev
> wrote:
>
> "Apple is committed to the HIViews, Carbon events, and nib files for Carbon
> implementations of the user interface.
>All new controls and other features will be based on HIView.
>If you want your application
On 4 Oct 2019, at 21.00, Jens Alfke wrote:
The people I hear complaining about this are those who, like you, didn't move
to Cocoa. Carbon was a _temporary_ transition API*. It was necessary when Mac
OS X shipped in March 2001, but even though it wasn't yet formally deprecated,
it was clear it
Hi,
I’m currently making a SpriteKit game in tvOS and am using the Play/Pause
button on the remote as my games secondary button. The code to make this work
is as follows:
let pushPlay = UITapGestureRecognizer(target: self, action:
#selector(pushedPlay))
pushPlay.allowedPressTyp
>> If you’re finding it difficult in the various transitions going on, how
about reaching out to another developer or group to get you over those
hurdles?
If only it were that simple. Cocoa wasn't just a few hurdles. More like a
constant slog of small and medium-sized problems, with insufficient
> On Oct 4, 2019, at 4:43 AM, Dragan Milić via Cocoa-dev
> wrote:
>
> Apple also strongly and clearly advised all new development should be done in
> Yellow Box/Cocoa. Sure it took Apple too quite some time to transition
> everything away from Carbon, but it was clear from the beginning that
> On 4 Oct 2019, at 11:43, Dragan Milić via Cocoa-dev
> wrote:
>
>> pet 04.10. 2019., at 11.51, Jeremy Hughes via Cocoa-dev wrote:
>>
>> It wasn’t clear to us (outside Apple) that Carbon was a temporary API until
>> 2007, when Apple suddenly abandoned 64-bit Carbon.
>
> I don’t agree.
Maybe
> pet 04.10. 2019., at 11.51, Jeremy Hughes via Cocoa-dev wrote:
>
> It wasn’t clear to us (outside Apple) that Carbon was a temporary API until
> 2007, when Apple suddenly abandoned 64-bit Carbon.
I don’t agree. The first version of macOS predecessor (Rhapsody) shipped only
with “Yellow Box” (
Hi Jens,
> On 3 Oct 2019, at 20:04, Jens Alfke via Cocoa-dev
> wrote:
>
> The people I hear complaining about this are those who, like you, didn't move
> to Cocoa. Carbon was a _temporary_ transition API*.
It wasn’t clear to us (outside Apple) that Carbon was a temporary API until
2007, whe
I stirred up some conflict on this list. It may be because of readership
differences.
If you work for Apple or a big corp, then technical answers is what you can
offer or desire.
The big picture is someone else's worry. When programming tools change,
it's just job security.
For a small developer
12 matches
Mail list logo
