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

[Leandro da Mota Damasceno]

That sounded like a Lego approach. :)

So the way I see it the GUI development should be in the most seemless way
for the user, right?

And we also have the problem between people who prefer a simple, leaner GUI
approach (the classic PD, for instance) against people who prefer a more
sofisticated, and sexy GUI. And I believe both groups would also like some
more knobs and stuff...

so basically, we should at least have two options of gui: simple (classic)
or sophisticated (sexy). But it would be cool to make it open enough to
anyone develop their own or come up with new and customized ones. that
would make PD way cooler than Max/MSP or anything else. So for that to work
(and now I must admit I really don't know the architecture behind this part
of PD, so maybe it is already this way), the comunication between the GUI
and the rest of PD should be kept simple, fast and modulated, working with
the leanest possible API. I also think this is a good approach considering
that most of these toolkits will stop getting support way before PD ceases
to exist. I have also thought about the possibility of skins, but then
loading a bunch of bitmaps would not help in terms of performance...


At the same time we pick a toolkit and focus on that one first. So we
should think of at least two teems, right? One at the GUI end and the other
at the core PD end...

What do you guys think?


On Mon, Jan 21, 2013 at 2:02 PM, Hans-Christoph Steiner <hans at at.or.at>wrote:

> On 01/21/2013 12:54 AM, Jonathan Wilkes wrote:
> > ----- Original Message -----
> >
> >> From: Billy Stiltner <billy.stiltner at gmail.com>
> >> To: IOhannes zmölnig <zmoelnig at iem.at>
> >> Cc: pd-list at iem.at
> >> Sent: Sunday, January 20, 2013 10:04 PM
> >> Subject: Re: [PD] GUI toolkits and custom GUIs WAS: Integra Live 1.5
> released
> >>
> >> haha , last month i tried to install juce to see about making an
> >> alternate graphics front end to my patches. there  was some weirdness
> >> in the way you compile it then run the introjucer or somethin to
> >> update it then after the update something didn't quite work right.
> >> then there are all the old projects that use the old steinberg vst sdk
> >> which you cant get from steinberg anymore so all that is just awful. i
> >> think that there should be a really nice updated version of juce
> >> either available now or in the near future.  its a tossup between
> >> fltk, qt , opengl ,juce, and processing.  i just want to be able to
> >> add my waveform data filenames to the presets with a fileopen dialog
> >> without using an external, string parsing like .scl files that have
> >> 100.00 or 3/2, and polyphonic patchcords would be nice.
> >
> > What about the -guicmd "cmd..." flag?  Could one write a pd-gui.html
> > that lives at localhost:1234, and have it talk to pd at its port on
> localhost?
> >
> > Then you could just write the interface with html5 canvas, svg,
> > javascript, or whatever.
> >
> > -Jonathan
>
>
> That sounds feasible to me.
>
> .hc
>
> _______________________________________________
> Pd-list at iem.at mailing list
> UNSUBSCRIBE and account-management ->
> http://lists.puredata.info/listinfo/pd-list
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.puredata.info/pipermail/pd-list/attachments/20130121/6fdf2063/attachment-0001.htm>