- People are sticking with PP because it's too much trouble to change
- Most people prefer to roll their own, and now we're all fragmented
because PP had no clear successor
- People are using Cocoa instead
- People are using plain Carbon calls instead; Carbon does a lot more
than it used to, so there's less need for frameworks like PP
- People don't like my approach, and/or I'm just bad at marketing :)
Don't bother - it just isn't worth the pain. I wouldn't go so far as
to say that PowerPlant is (now) a false economy - but it is very close.
In the long run you'll simply spend more and more of your time
updating PP (or whatever) for new features in the OS that Apple is
already giving you support for in Cocoa. Plus, most classes in Cocoa
are much better designed than their MacApp/TCL/PP cousins ever were.
There is a huge productivity gain to be made if you take advantage of
this.
Keep your C++ engine code and wrap it with a Cocoa GUI. Take a look
at the source for webkit if you don't believe this model works. C++/
KHTML under the hood and ObjC/Cocoa on the top. If there is something
in Cocoa that isn't up to par sprinkle some Carbon, CoreFoundation or
POSIX code into the mix.
Yes, yes, I know, it's a huge time consuming job, but the long term
advantages outweigh the short term pain.
After fifteen years of Carbon/TCL/PowerPlant I know the job you face
but making the switch is easily -easily- worth it.
Ross
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/xcode-users/email@hidden
