SubscribeI’ve been thinking more about state storing and logic processing in Quartz Composer based on some comments made by Vade. Currently the options are very limited and seemingly that’s a deliberate design decision on Apple’s part, you’re not supposed to store state in a Quartz Composer composition. So what’s the options? Hack up stores based on counter or stop watch or code your logic processing in objective c, but wait, what about Core Data?
Has anyone tried to make a Core Data application tied into a Quartz Composer composition yet? Or is there any tutorials demonstrating how to do this?
From what I understand it should be possible to use Core Data to manage all your data you want saved without any actual programming. Eg in Quartonian or Quartonian VSM I could define a managed object to hold all the assigned video loops and still images and I’d get save/load and other goodies like multiple levels of undo “for free”.
What are the implications of Apple writing a node like Signal and then deliberately disabling it even though it’s already working and there? The obvious answer is they really don’t want you doing logic processing or storing state inside quartz composer. You’re “supposed” to use objective c or core data for this.
Many people have hacked state storing nodes based upon the counter object, see the custom macros on the quartzcompositions wiki.
I’m interested in what people think, should we do things the “right way” and store state outside Quartz Composer compositions or should users ask Apple to reimplement and reenable all the logic processing and state storing nodes that PixelShox had? (Don’t even ask about what MAX/MSP can do…)
Quartz Composer
