Hello,
I'm new to this list (and OS X programming in general) but it seemed
the place to start. I hope you can help.
My employer, a small 10 person company, has an application that was
ported from OS 9 CodeWarrior C++ to OS X Carbon Xcode. I've been
tasked to transition the app from the existing QuickDraw drawing
environment to Quartz. The Apple documentation describes the Quartz
environment well enough. The documents of interest appear to be:
"Upgrading to the Mac OS X HIToolbox" Upgrading_HIToolbox.pdf
"Quartz Primer" QuartzPrimer.pdf
"Transitioning to Quartz 2D"
"Quartz 2D Programming Guide" drawingwithquartz2d.pdf
Management believes that a simple one-to-one replacement of QuickDraw
calls with Quartz calls is sufficient. "Just encapsulate all the
QuickDraw calls in a class object, and then replace the QuickDraw calls
one at a time." However, the documentation suggests that this is not
only not desirable, but not even possible. Most of the documentation
assumes that one replaces the entire QuickDraw and Apple Event model,
with a nib-based Carbon Event model. However, management doesn't want
to take that big of a bite all at once.
0. Is this the right list to ask about transitioning from QuickDraw?
1. At what level of granularity does it make sense to replace
QuickDraw calls? Each window? Each control? Each region/path? The
need to obtain and release a CGContext suggests a larger granularity,
like a window.
2. Is there any recommended order in which to attack such a conversion?
3. Can Carbon event handlers coexist with QuickDraw WaitNextEvent
model?
Any suggestions would be greatly appreciated.
Scott Fraser
-----
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Quartz-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/quartz-dev/email@hidden
