[PD-dev] Pdplay?
Ben Bogart - FMPM/F1999
bbogart at ryerson.ca
Wed Oct 2 22:58:11 CEST 2002
you could package your own distro of PD and your patches with a
fancy installed and a nice shortcut/link/alias to open PD with the
proper options and your patch. Another possibility.
somwhat related, there is something called tclkit which is a
self-contained single exe tcl/tk distro. Maybe something like that
for PD? Would make the above a bit easier... (does it have to be
multiplatform?)
Ben
On Wed, 2 Oct 2002, Nicola Bernardini wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Il 01/10/02 alle 22:28, Joseph A. Sarlo scrisse:
>
> > This is actually where I'm hoping to take GrIPD. It can be done manually
> > now. Just use the PD '-nogui' command line (don't forget to put a netreceive
> > object in your patch, something I need to look into) and use a loadbang
> > connected to an 'open_locked <filepath>' message to the gripd object (the
> > _locked will disable any GrIPD gui editing). Keep in mind that the filepath
> > for 'open' and 'open_locked' are relative to the PD executable file. To
> > close when the GrIPD gui closes, just use the outlet of the gripd object
> > with the ';pd quit' message. You can then just bundle everything together
> > (your patches, PD, and GrIPD) into a single distribution and have it launch
> > with some script. The only problem might be other command line args such as
> > selecting the audio and MIDI devices, etc. I've been thinking of creating
> > some kind of distribution compiler that would do all this automagically. I'm
> > also considering making some 'setup' app for PD (probably with wxPython)
> > that the end user (the user getting your distro) would run once to generate
> > the command line args. I think this would be a nice thing for people wanting
> > to create seemingly stand alone apps with PD or for
> > installation/demo/educational types of situations. There's also the
> > possibility of working up a stripped down version of PD without any editing
> > features at all, to further prevent editing of PD patches by expeditious
> > users, but I personally don't think this is such a good idea.
>
> Thank you Joe for your quick reply (and also for griPD obviously!:)
>
> My current problem is not so much patch editing but rather the idea that
> users that would like to see some application of some sort would *have*
> to have the whole shabang installed into their machine. Thank you for
> all the suggestions, I'll do some hacking and see if I'll explain myself
> better with that.
>
> However, your suggestions were *extremely* useful. Thank you.
>
> nicb
>
> +--------------------------------------------------------------------+
> |Nicola Bernardini |
> |E-mail: nicb at centrotemporeale.it |
> |GPG Fingerprint = 6AE6 AF21 E160 D9B3 396E EBAC 906C CFAE 4D65 D910|
> |Neither MS-Word nor MS-PowerPoint attachments please: |
> |http://www.fsf.org/philosophy/no-word-attachments.html |
> +--------------------------------------------------------------------+
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.2.0 (GNU/Linux)
> Comment: Made with pgp4pine 1.75-6
>
> iD8DBQE9mrC1kGzPrk1l2RARAg50AJ42ybzTtgPE+sgc4Azn6mRfCXIuwwCg1O3n
> n9P0nXT4Y9wMdwprKRnWKb0=
> =8ZLB
> -----END PGP SIGNATURE-----
>
>
>
> _______________________________________________
> PD-dev mailing list
> PD-dev at iem.kug.ac.at
> http://iem.kug.ac.at/cgi-bin/mailman/listinfo/pd-dev
>
B. Bogart
---------
More information about the Pd-dev
mailing list