Oops,
Of course the pdp_ objects start with pdp_ so my suggestion is illogical.
Do the objects only deal with pixel data? If so then pix_pdpin pix_pdpout may work...
Ok thats enough of me.
B.
since it's really only 'get' and 'set' (just about exchainging data with a gem render chain) i think this should be clear in the name.
the object qualify as 'gem chain objects' not pdp objects. so [pdp_xxx] seems confusing.
true. still i think that "pdp" should be in the name too, as [gem_set] wouldn't necessarily have something to do with pdp packages. so probably [gem_pdpout} and [gem_pdpin] would be more apropriate ? (or [gem_pdp.out] and [gem_pdp.in])
...
so the templates are almost done; just want to settle the name before i check them in
[gem_pdp.out] and [gem_pdp.in] seem ok to me
or even
[out_pdp] and [in_pdp] to keep them shorter, since most gem objects don't have a gem_ prefix.
yeah, politics!
GEM-dev mailing list GEM-dev@iem.at http://iem.at/cgi-bin/mailman/listinfo/gem-dev