well, FYI in Jitter you do [jit.someobject @color r g b a] (for example), or can use a message named color.
Ive never seen or used [jit.someobject @red r @green g @blue b @alpha a] and jitter also has just about every colorspace conversion possible, that I have ever seen or dealt with professionally, and many I have not heard of or ever had to use: http://cycling74.com/documentation/jit.colorspace Not meant as flame bait (sorry, I still feel like an ass for yesterday Mathieu!), but more for compare/contrast. I quite like the attribute system jitter has, and think it could be imported with some sort of syntax highlighting for objects where attribute names are one color and their set values another. It would (may?) help visually grokking the text within the patcher object On Dec 6, 2007, at 2:16 PM, Mathieu Bouchard wrote: > On Thu, 6 Dec 2007, marius schebella wrote: > >> the most obvious and useful things are the tons of @arguments that >> each >> objects accepts. > > Having tons of @arguments is not necessarily a blessing. Wherever > Jitter has four @arguments named red,green,blue,alpha, GridFlow has > only one, which is a list of the four colour components after a > [#pack]. It makes GridFlow more structured than Jitter in this case, > and that makes some objects more open to different colour spaces > than Jitter's, in addition to yielding a better features-per- > @arguments ratio. > > _ _ __ ___ _____ ________ _____________ _____________________ ... > | Mathieu Bouchard - tél:+1.514.383.3801, Montréal QC > Canada_______________________________________________ > [email protected] mailing list > UNSUBSCRIBE and account-management -> > http://lists.puredata.info/listinfo/pd-list _______________________________________________ [email protected] mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list
