I'd like to make a screensaver that is roughly similar to Apple's
iTunes Artwork screensaver in that I will have a grid of images, and
will perform some 3D transitions to each image.
I had originally planned on delving into OpenGL and doing it all
programmatically, but I've being playing around with Quartz Composer,
and have discovered that I can make a macro in a Quartz composition
extremely easily that will handle the work of doing whatever
transitions I want on a given input image.
Provided that I'm not worried about supporting lower-end systems and
anything before Tiger, would it be a bad approach to load a Quartz
composition multiple times on the screen and getting each instance to
do all of the transition work, or would it be considerably better
(from a memory and processor usage point of view) to do everything
programmatically using OpenGL calls to load the images onto planes on
which the transitions will occur?
Thanks,
Patrick
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Quartzcomposer-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/quartzcomposer-dev/email@hidden
This email sent to email@hidden
