| 1 | ||
|
Editor: antont
Time: 2004/10/07 07:33:04 GMT+0 |
||
| Note: | ||
changed: - the new PixelShox .. how is it? Discovering Quartz Composer New developer tool for Tiger 1) visual programming tool to render/process graphical data 2) integrates OpenGL, Quartz2D, CoreImage, CoreVideo, etc. Quartz composer core units called "patches" 1) analogous to base processing units 2) patches can have "input ports", and results to "output ports" 3) inputs/outputs can be files, values, or objects 4) patches can be aggregated and nested (into macro patches and hierarchical) Consumer Patches 1) render something 2) run every frame 3) execute in defined order 4) pull data Processor 1) run on demand and if inputs change 2) process data Provider 1) provide data from outside sources 2) run on demand Quartz Composer projects call compositions. To play compositions 1) Use QCView in IB 2) binding use QCPatchController (Cocoa bindings) 3) Use QCRenderer class (will have to write code, for example to integrate with existing OpenGL code. Building InteractiveComposition s 1) interact with external sources like mouse, [MIDI], videocams, [RSS] feeds, etc. 2) exportable to DV (but transparency not preserved at this time) Composer file format is private for now. There were requests to open it up, but no comment on making it public at this time. File sizes of compositions are reasonably small. Movie files are linked, not embedded. Most movie info is just descriptive info. With underlying changes made to support the Quartz Composer, the tool technology is not likely to be ported to Jaguar and Panther. If not using anything Tiger specific, then compositions should run fine on earlier systems.
the new PixelShox .. how is it?
Discovering Quartz Composer New developer tool for Tiger 1) visual programming tool to render/process graphical data 2) integrates OpenGL, Quartz2D, CoreImage?, CoreVideo, etc. Quartz composer core units called "patches" 1) analogous to base processing units 2) patches can have "input ports", and results to "output ports" 3) inputs/outputs can be files, values, or objects 4) patches can be aggregated and nested (into macro patches and hierarchical) Consumer Patches 1) render something 2) run every frame 3) execute in defined order 4) pull data Processor 1) run on demand and if inputs change 2) process data Provider 1) provide data from outside sources 2) run on demand Quartz Composer projects call compositions. To play compositions 1) Use QCView? in IB 2) binding use QCPatchController? (Cocoa bindings) 3) Use QCRenderer? class (will have to write code, for example to integrate with existing OpenGL code. Building InteractiveComposition s 1) interact with external sources like mouse, MIDI, videocams, [RSS]? feeds, etc. 2) exportable to DV (but transparency not preserved at this time) Composer file format is private for now. There were requests to open it up, but no comment on making it public at this time. File sizes of compositions are reasonably small. Movie files are linked, not embedded. Most movie info is just descriptive info. With underlying changes made to support the Quartz Composer, the tool technology is not likely to be ported to Jaguar and Panther. If not using anything Tiger specific, then compositions should run fine on earlier systems.