hi all,
pdp-0.11 is out. (it's the same as pdp-0.11-test8) get it at
http://zwizwa.fartit.com/pd/pdp/pdp-0.11.tar.gz
get the corresponding mac binary (which requires the x server (apple/fink) and libquicktime (fink unstable) at
http://zwizwa.fartit.com/pd/pdp/test/pdp.pd_darwin-0.11-test-8.tar.gz
you need pidip-0.11 with this because i broke the api again (this will probably happen again next time until i know what i'm doing..)
http://ydegoyon.free.fr/pidip-0.11.tar.gz
enjoy,
tom
---- from the changelog:
v0.11: 2003/04/08 updated pdp_trigger to behave like pd's trigger object added automatic philips web cam detection removed "zombie" packet passing and made pool manager thread safe (this required an api change: backward compat for pdp thread proc broken) added gem style object rendering & transformation objects (opengl lib) removed pdp_gradient binary module (it is now an abstraction) added pdp_loop (a packet array / loop sampler) added pdp_description added support for libquicktime on osx (thanks Jamie) added support for accumulation packets (dpd) (still experimental)
---- buzzwords for the road, things that are in the making:
* better type handling and automatic conversion (a usability meme sneaked in)
* a gem style opengl wrapper built on top of pdp, designed around a slightly different concept (disentangled "serial" drawing/transformation (dpd) and "parallel" image/texture processing code (pdp)), using accumulation packets. this is abusing pd to visualize context based serial control flow. or in other words: is there a point in explicitly giving up fanout for some packet types (i.e. drawing contexts), instead of providing invisible support for it? (what pdp does)