[PD] GUI toolkits and custom GUIs WAS: Integra Live 1.5 released

[Lorenzo Sutton]

On 19/01/13 20:20, Hans-Christoph Steiner wrote:
> On 01/19/2013 01:56 PM, IOhannes m zmölnig wrote:
>> On 01/18/2013 22:31, Hans-Christoph Steiner wrote:
>>> I would love it if someone started this since it would greatly help with the
>>> goal of splitting the GUI from Pd itself.  And of course I'd help where I can.
>> i keep starting that project every now and then: moving all the drawing code
>> to pd-gui and only use FUDI (that is: not tcl code) to communicate between
>> pd->gui.
>>
>> unfortunately i always get distracted after a short time and i never get to a
>> really working prototype.
>>
>> gmsdr
>> IOhannes
> It can be done incrementally, which is likely the only way its going to get
> done.  It turns out that FUDI and tcl proc calls are very similar: space
> separated list of elements where the first one is the functionality.
>
> If the basics were done first, like object drawing, then someone could build a
> rough GUI with another toolkit to test out.
When you say 'FUDI' what exctly do you mean... what I mean is for me 
FUDI is actually [netsend] and/or [netreceive] interacting with 
'something else'... would this be something more clever? Is it still 
relying on sockets (have no strong feeling about that nor pro nor con 
just to have a clearer picture)

Would it make sense within this to think of some kind of 'patching' 
conventions, for example the fact that parameters are always 
set/modified by messages (and thus easily routable)? maybe some sort of 
'namespacing' lingo e.g. mypatch.freq mypatch.amplitude etc...

Or even some sort of semantics related to the GUI... 
mypatch.hslider.freq .. but this is probably going to far.

As you can see this topic is very thought provoking over here :)

Lorenzo.