emperor: (Default)

(no subject)

posted by [personal profile] emperor at 10:42am on 18/03/2005
Thanks for that comment (who are you, BTW? I prefer anonymous posters to give some idea of their identity); the problem with cocoa is it rather requires you to use objective-C (and again seems very nib-centric, documentation-wise).
[parent entry] [link] [parent] [reply]
 

(no subject)

posted by (anonymous) at 10:53am on 18/03/2005
You can still have you application logic/backend in C (since objc is a strict superset of C), and just use Cocoa for the glitzy UI stuff, or even mix and match Cocoa and Carbon in the same app. The nice thing about cocoa is that compared to Carbon, there is a lot of stuff (ie behaviour that has been accepted as standard by users) that you get for free, (this is coming from someone who has used Carbon for a while and the classic Mac toolbox before that). You do sort of have to get into the right mindset or you can spend a lot of time fighting Appkit without getting anywhere.

I don't believe you know me or that i know you, but I believe we both know Abi. I'm a friend of her's at Cambridge.
[link] [parent] [reply]

October

SunMonTueWedThuFriSat
      1
 
 2
 
 3
 
 4
 
5
 
 6
 
 7
 
 8
 
 9
 
 10
 
 11
 
12
 
 13
 
 14
 
 15
 
 16
 
 17
 
 18
 
19
 
 20
 
 21
 
 22
 
 23
 
 24
 
 25
1
26
 
 27
 
 28
 
 29
 
 30
 
 31