> That's basically why I think inventing Yet Another, Although Much > Cooler Looking GUI Toolkit would be worth the effort, if it could > help cutting GUI development time without dropping chrome and/or > features. (Whether or not it's possibly is another issue. Guess I'll > > just have to try it...) >
Actually, Instead of writing another GUI toolkit i think the best is to write widgets that would go well for audio programs in some existing widget set such as GTK. > > > > >We do have very powerful tools, but i have to admit that for most > > > of them we have to learn some script programming. > > > > Some people think this is a good thing because the tools are > > ultimately more capable and less limiting. Others disagree. > > I'd like both... Fiddle knobs and draw curves until you get the > basic sound, and then, if required, unscrew the chrome panels to > hack same more complex logic and/or math in. :-) > > Doesn't make things easier, does it? > Personally I'd rather move knobs than trying values. I write my apps usually in the userfriendly way becuse of this. Juan Linietsky
