PG Suggestion Series: Carbon-Cocoa Distinction Dissolution
PG Suggestion Series: Carbon-Cocoa Distinction Dissolution
- Subject: PG Suggestion Series: Carbon-Cocoa Distinction Dissolution
- From: Perry Gregg <email@hidden>
- Date: Wed, 8 Jan 2003 06:57:49 -0800
Can we get rid of the Carbon-Cocoa distinction in app
building? Is anyone else seeing that you pretty much
want to use both. I've met a few regular Apple UI
people that come out to the client sites and tell them what
Apple would like to see, and how to do what. They
push Cocoa and the Cocoa look. Right now to be
competitive with Windows and even Linux in a product
category you need access to every bit on the screen.
In porting this fairly well known digital movie app from
Windows, Cocoa is great, and makes sense to use for
things like the getting file panels and stuff where the
particular app is not doing a lot of value-added. But
functions in your app that are part of the core purpose,
chances are you've gone beyond and done custom
things, that means control of every bit in your window, or at
least in sections of it.
Merge the 2 logically and get rid of the distinction by WWDC.
Maybe I can get a free pass to WWDC for making
the suggestion. Cocoa apps should by default (MVC system)
include the Carbon framework and place the Carbon include
header in your files.
Look at Safari. It is close, but could benefit in places (main dialog)
by being able to get at every bit and maybe having
XML controls or things like that in places. They should be able
to use libpng if it gets them something cool. You can do that in
a Cocoa app by including Carbon as many folks on these lists
know.
And someone at the top of Apple has to override the
legacy idea that platform software is great if between packages
we have common themes and the users get one metaphor
and that makes them more productive. Hooey. That is true, but
on the priority list, not more important than individuality.
Great software is distinct like people and movies are distinct.
Let the creators be free to win and fail using their own judgment.
As the bits roll in the dialogs of your apps, free some of them from
corporate. Let them be yours baby.
Bring me back to Apple Software Engineering Management,
--Perry Gregg
01 (530) 400-5692
P.S. Not to mention it'll be cheaper going forward internally to combine
departments (if there is any Carbon staff left doing anything like
fixing bugs). The Developer message will be cost effective
if you put them on one path that is the real one where they can win
at the highest level. Developers will deliver you to the promised
land. And these lists can merge.
_______________________________________________
cocoa-dev mailing list | email@hidden
Help/Unsubscribe/Archives:
http://www.lists.apple.com/mailman/listinfo/cocoa-dev
Do not post admin requests to the list. They will be ignored.