I'm going to start looking into what it will take to move our
window/control code from Carbon to Cocoa.
I should also mention that our app is still using WaitNextEvent for
the main event loop. Work has been done to move to
RunApplicationEventLoop, but is not quite done. Our Mac framework
loads proprietary resources to create windows and controls. It was
written long before Carbon, then Carbonized, then moved to using real
controls where possible or custom HIView subclasses where needed. But
there is still a lot of our own window handling code in place, which
causes problems when I try using RAEL and/or compositing windows.
It's sounding more and more like Carbon *will* die in the future, and
as much as I can't stand Obj-C, and Apple's development goals seem to
be driven by the NeXT politics, etc etc. So, I guess I need to get
started now - 100 windows, palettes, and dialogs aren't gonna convert
themselves.
_______________________________________________
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
