Yeah and afaiu this is exactly the job that HC just started (see his announcement below).<br>Yvan: in my simple understanding it goes like this: 1. getting rid of tcl-specific code in pd c core 2. minimizing the communication between the core and the gui (3. defining the api/protocol?) 4. anyone can go make all sorts of guis for pd... at this point or later on vanilla may or may not switch from tcl - imho it's to be decided when we're there<br>
<br>Andras<br><br><div class="gmail_quote">On Fri, Aug 26, 2011 at 01:39, Jonathan Wilkes <span dir="ltr"><<a href="mailto:jancsika@yahoo.com">jancsika@yahoo.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div><div style="color:#000;background-color:#fff;font-family:times new roman, new york, times, serif;font-size:12pt"><div>The pd/pd-gui divide is a little misleading-- there are lots of places in the c code where there are sys_gui and sys_vgui calls with tcl in them, plus c code that probably assumes tcl is being used on the gui side.</div>
<br>You'll either need to write a wrapper for those calls, or modify a lot of c code and basically make a fork (iemguis, canvas stuff, etc.)<span></span><br><br>But even if you write a wrapper, there are still issues that will need to be dealt with on the c side to minimize the number of messages passing back and forth between pd and gui. For example, there is one call per xlet to the gui when an object gets instantiated/vis'd, plus drawing the border and text, rather than one call per object (and letting the gui deal with where to draw xlets, box width, font,
etc.).<br><br>-Jonathan<br><div><blockquote style="border-left:2px solid rgb(16, 16, 255);margin-left:5px;padding-left:5px"><div style="font-family:times new roman, new york, times, serif;font-size:12pt"><div style="font-family:times new roman, new york, times, serif;font-size:12pt">
<font face="Arial" size="2"><hr size="1"><b><span style="font-weight:bold">From:</span></b> yvan volochine <<a href="mailto:yvan.pd@gmail.com" target="_blank">yvan.pd@gmail.com</a>><div class="im"><br><b><span style="font-weight:bold">To:</span></b> Hans-Christoph Steiner <<a href="mailto:hans@at.or.at" target="_blank">hans@at.or.at</a>><br>
</div><b><span style="font-weight:bold">Cc:</span></b> Jonathan Wilkes <<a href="mailto:jancsika@yahoo.com" target="_blank">jancsika@yahoo.com</a>>; pd-dev List <<a href="mailto:pd-dev@iem.at" target="_blank">pd-dev@iem.at</a>><br>
<b><span style="font-weight:bold">Sent:</span></b> Thursday, August 25, 2011 6:18 PM<br><b><span style="font-weight:bold">Subject:</span></b> Re: [PD-dev] tkwidgets<br></font><div class="im"><br>On 08/17/2011 08:54 PM, Hans-Christoph Steiner wrote:<br>
> I've started a private git branch of<br>> tkwidgets
that I intent to push once I get somewhere with it. The idea<br>> is to try out a new idea for how GUI objects can work. Basically, I<br>> think I can make it so that Tcl handles more of the interaction with the<br>
> user, minimizing on pd-gui <--> pd communications, and making it easier<br>> to write GUI objects. Its not trivial to do, but should be doable.<br><br>hiho<br><br>sorry for bumping in but what about giving up tcl-tk and go on with something more "modern" (à la Qt), with a decent OO interface ?<br>
<br>I might miss the obvious as I'm new here but what about rewriting pd GUI in Qt ?<br>wouldn't it make more sense than spending time hacking on and on tcl-tk code ?<br><br>my 0.001$<br>_y<br><br><br></div></div>
</div></blockquote></div></div></div><br>
</blockquote></div><br>