Hi Matt, happy new year! I really liked the idea of widget opcodes
with parameters to specify the most common attributes such as colour,
size, position etc. It would mean that all csd's would be
interchangeable across frontends, plus it would do away with frontend
specific widgets syntax which in most cases is pretty ugly..

Rory.




2009/1/8 Matt Ingalls <ingalls@mills.edu>:
>
>> I strived for MacCsound compatibility primarily because it's the main
>> and most sucessful implementation of realltime widgets for Csound. I
>> wish Matt had used a more extensible and robust system like xml,
>
> i like Rory's lettuce/cabbage -- and had started talking to him about adding a few things so that everything MacCsound does could be specified in his spec..
> i also had a proposal of replacing the FLTK opcodes with a kind of system with widgets that would by fully dynamically changeable with a standardized system of attributes system sent with "outvalue" (or something similar) so you could do something like this at krate:
>
> outwidget iSliderChan, "Value", .56
> outwidget iSliderChan, "Label", "the new slider name"
>
>
> but never quite thought it all the way through and basically dropped the ball..
>
> Send bugs reports to this list.
> To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"