----- Original Message -----
> From: yvan volochine <yvan...@gmail.com>
> To: pd-list <pd-list@iem.at>
> Cc:
> Sent: Saturday, May 12, 2012 8:17 PM
> Subject: Re: [PD] variable receive objects?
>
> On 05/12/2012 10:29 PM, Jonathan Wilkes wrote:
>> However, there comes a point when making a serious user interface that
>> wires start to get in the way, esp. on some of the more complex interfaces
> people
>> have made in Pd for sequencing, real-time performance, etc. I'd say at
> the level
>> where the author is designing for user's who don't necessarily need
> to know the ins
>> and outs of Pd's dataflow paradigm, wires become a hindrance.
>>
>> Of course that doesn't mean one can't do normal Pd patching using
> only GUI objects.
>
> just to add my 2 cents..
> if a patch needs a GUI, I really like when its top-level canvas contain only
> the
> GUI and only patchers (read: *no wires* when opening the patch)
>
> using GUI send|receive instead of wires is a very good idea.
> it also encourage putting things where they should be, i.e. separate the
> logic
> from the GUI (à la maxmsp 'presentation mode').
>
> then somewhere in your subpatches:
> [s GUI-to-vol] [r GUI-from-vol] [s GUI-to-mute] etc..
>
> much cleaner IMHO
>
> or even better, only:
> [pd init]
> [pd audio]
> [pd GUI]
> on the top-level and some key triggers opening [pd GUI]
>
> BTW I'd _love_ to be able to do that:
> [hslider sendSymbol receiveSymbol]
Supercollider-style any-order keyword args would be nice.
-Jonathan
>
> now that would save some time :)
>
> cheers,
> y
>
> --
> yvan.voloch...@gmail.com
> http://yvanvolochine.com
>
> _______________________________________________
> Pd-list@iem.at mailing list
> UNSUBSCRIBE and account-management ->
> http://lists.puredata.info/listinfo/pd-list
>
_______________________________________________
Pd-list@iem.at mailing list
UNSUBSCRIBE and account-management ->
http://lists.puredata.info/listinfo/pd-list