The humor of the idea of writing a plugin without a single line of code isn't lost on me, but there would is a valid use case for being able to make a qtz that would be setup sort of like a virtual patch, and then perhaps to drop it in an app that would turn the qtz into a plugin resource of some sort (an encrypted file or unix executable), setup inputs/outputs automatically, and build a qtz based plugin. There are some plugins where qtz's do a great deal of the heavy lifting already.
One could possibly even set something up like that so that multiple qtz's could represent separate subpatches. Even as is, if QC recognized qtz's that were manually renamed with a plugin file extension, in the sameway that a composition loader recognizes a qtz with an arbitrary extension, one could have a way of distributing qtz's that would provide patch like function yet also make underlying node structure not easily viewable or editable. It makes good sense for there to be a way to lock a qtz macro patch in stone, and load it in some encrypted non-qtz form. -George Toledo On May 21, 2010 9:49 AM, "kingLuma" <[email protected]> wrote: On May 21, 2010, at 7:11 AM, Alexander Zvyagin wrote: and think: "using the Quartz Composer without writing a single code line" in real mean the deep knowledge of OpenGL pixel formats and Carbon Programming I'm also awaiting the fulfillment of the "without a single line of code" promise : ) _______________________________________________ Do not post admin requests to the list. They will be ignored. Quartzcomposer-dev mailing list ([email protected]) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/quartzcomposer-dev/gtoledo3%40gmail.com This email sent to [email protected]
_______________________________________________ Do not post admin requests to the list. They will be ignored. Quartzcomposer-dev mailing list ([email protected]) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/quartzcomposer-dev/archive%40mail-archive.com This email sent to [email protected]
