[PD] GrIPD: A new front-end GUI builder for PD

[Joseph A. Sarlo]

> Its GUI componet works and looks great!!!
> but i got an error in both Pd-0.31 and Pd-0.32.
>
> GrIPD: Bind Error: No error
> GrIPD: Attempting to re-bind
>
> when i try to connect GrIPD.

It sounds like somehow you're attempting to connect twice and the socket
is already bound.  I just noticed that this is really easy to do, just
send "connect" twice, or send "connect" then "open".  I'll have to fix
this so you can't (that's what v0.0.1 is all about I guess).  So if you're
doing that, then that's the problem. The usage directions might be a
little confusing: "connect" message is only used if you're going to open
the GrIPD GUI separately (like on a different machine).  If you're using
everything local, you don't need to send "connect" at all, just "open
<optional filename>".

> Also,
> Does gripd object always need to receive set_path and
> set_python_path messages in every patch?

If you have all the GrIPD python stuff (*.py files) in "c:\pd\gripd\" then
you don't need to use "set_path", similarly, if you have python installed
to "c:\program files\python\" then you don't need "set_python_path".
This is only so the GrIPD PD object can find stuff when you use "open".
You could always launch gripd.py separately, but I'd recommend wrapping
gripd and the set messages in a PD file with a little loadbang magic.

Let me know if this helps or not, I'm really want to iron out the kinks.


-- 
 ______________________________
|
| Joseph A. Sarlo
|
| jsarlo at mambo.peabody.jhu.edu
|______________________________



On Fri, 13 Jul 2001, uta wrote:

>
> I tested GrIPD on my windows98,
>
> Pd-0.31 and Pd-0.32 Patch1
> Python 2.1
> wxPython 2.3.0
>
> Its GUI componet works and looks great!!!
> but i got an error in both Pd-0.31 and Pd-0.32.
>
> GrIPD: Bind Error: No error
> GrIPD: Attempting to re-bind
>
> when i try to connect GrIPD.
>
> Also,
> Does gripd object always need to receive set_path and
> set_python_path messages in every patch?
>
>
> Respect!
> Uta.
>
>
> Johannes M Zmoelnig <zmoelnig at iem.kug.ac.at> wrote:
>
> > hi !
> >
> > how do you make it run ??
> >
> > on my debian system i have
> > gtk-1.2.10-1
> > python-1.5.2-16
> > wxgtk-2.2.6.1
> > wxgtk-python-2.2.6.1
> >
> > compilation went fine
> > i always get following error-message when trying to "open"
> > <snip>
> > GrIPD: Using port 3490
> > GrIPD: Waiting for a connection...
> > Traceback (innermost last):
> >   File "../gripd/gripd.py", line 23, in ?
> >     from gripdControls import *
> >   File "../gripd/gripdControls.py", line 179, in ?
> >     class mToggle(wxToggleButton, wxButton, mButton):
> > NameError: wxToggleButton
> > </snip>
> > obviously there is something missing ? looks like i need
> > wxgtk(-python)-2.3.x instead of 2.2.6 ??
> > ah, now i've seen the hint on your page
> > so debianized people will have to wait a little bit longer...
> >
> > mfg.ds.zhrt
> > IOhannes
> >
> > On Thu, 12 Jul 2001, Joseph A. Sarlo wrote:
> >
> > > GrIPD is an extension to PD that allows one to design custom graphical
> > > user interfaces for PD patches.  GrIPD is _not_ a replacement for the PD
> > > Tcl/Tk GUI, but instead is intended to allow one to create a front end to
> > > a PD patch.  The concept is to create your PD patch normally and then your
> > > GUI using GrIPD (similar to SuperCollider or Reaktor). You can then lauch
> > > PD using the -nogui command line argument (although this is certainly not
> > > necessary) so only your custom front end will be displayed.
> > >
> > > GrIPD is available for Windows and Linux.
> > >
> > > Check it out at:
> > > http://mambo.peabody.jhu.edu/~jsarlo/gripd/
> > >
> > > --
> > >  ______________________________
> > > |
> > > | Joseph A. Sarlo
> > > |
> > > | jsarlo at mambo.peabody.jhu.edu
> > > |______________________________
> > >
> > >
> > >
> > >
> > >
> > >
> >
> >
>
>