hi phil, > But, [messagespewer] and [guiconfiguration] are mutually independent, so > really this is maybe just the way it works by default. No one is under > any obligation to use either of these objects in just this way, and > since the interface between them is just messages, which many other > things can input or output, there are nearly uncountable ways to use > either of these objects.
having an approach like this, why use the nova interpreter? if we think of the other way around ... the gui changes a preset, notifies the guiconfiguration object, which send a bunch of messages to the | messagefilewriter| object, to save the configuration file... so again, the message will to through 3 different threads before it is actually saved :/ > It would have been really handy if I could have > rigged up some number boxes in a patch to twiddle the colors without > restarting the GUI each time. I suspect users that don't like the colors > I picked will appreciate this ability, too. well, but that is a completely different point ... number boxes, like all other gui objects, should have a gui-configuration inlet, which can be used to set properties for this instance from the nova language ... it would also make sense to implement a popup menu like in pd or max, where the user can simply edit the properties ... i would say, let us first try to work on a properties mechanism, and then on the way, how to load the properties :) cheers, tim -- [EMAIL PROTECTED] ICQ: 96771783 http://tim.klingt.org Linux is like a wigwam: no windows, no gates, apache inside, stable.
signature.asc
Description: This is a digitally signed message part
_______________________________________________ nova-dev mailing list [email protected] http://klingt.org/cgi-bin/mailman/listinfo/nova-dev http://tim.klingt.org/nova
