Eric Gorr wrote:
>For new apps, I don't believe this is an issue...anyone not using Obj-
>C/Cocoa in this case is being silly (imho)
...
>Am I wrong?
I have to disagree with this - there are situations where an API choice
is forced on you by politics (like CA requiring an NSView), but new code
should always look at the pros and cons of whatever is available.
A closed-source framework such as Cocoa is not without its downsides;
the "major changes require a paid-for OS update" model works well if
you're the platform vendor, but the choice isn't so easy for everyone
else.
E.g., if you buy into the programming-by-side-effect idea of properties,
then you need to wait for 10.5 to do it with Obj-C. Or you could grab an
existing property class for C++ (or roll your own), and work everywhere.
That's a language issue, but you can find similar points in Cocoa itself
where you'll need to wait for Apple to provide a fix (not being able to
hide views until 10.3, not being able to overlap sibling views, etc).
-dair
___________________________________________________
mailto:email@hiddenhttp://www.refnum.com/
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Carbon-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/carbon-dev/email@hidden
This email sent to email@hidden
