Matt and I are getting ramped up for the coding, still designing right now.
We're thinking about starting it as a sourceforge project, or should we code it in the PD CVS?
Its called LME, and it will have the following functions (on OSX, Linux and Windows):
* Turn on and off flags * Add flag options * Add Lib(s) * Remove Lib(s) * Configure (edit conf file) [ where is PD, where to scan for libs, etc.. ] * Load Config Set [ Config sets will be executable without the manager! sh scripts in Linux, .commands in OSX, and shortcuts in Windows ] * Save Config Set * Launch PD with Open Set * Quit * About
Feedback? Those interested in collaboration please drop me a line.
Ben
Hallo, bbogart@ryerson.ca hat gesagt: // bbogart@ryerson.ca wrote:
We're thinking about starting it as a sourceforge project, or should we code it in the PD CVS?
I'd prefer it, if it was in the pd-cvs, because of simpler packaging later and the advantage of "having all in one place".
ciao
Wouldn't it be the best thing to have such a thing as part of pd (Accessable from the menu) ?
This would be possible on the CVS. Of course this would limit the implementation to tcl/tk and C, but it would be another step into building a pd developer community.
Guenter
On Fri, 30 May 2003 bbogart@ryerson.ca wrote:
Matt and I are getting ramped up for the coding, still designing right now.
We're thinking about starting it as a sourceforge project, or should we code it in the PD CVS?
Its called LME, and it will have the following functions (on OSX, Linux and Windows):
- Turn on and off flags
- Add flag options
- Add Lib(s)
- Remove Lib(s)
- Configure (edit conf file) [ where is PD, where to scan for libs, etc.. ]
- Load Config Set [ Config sets will be executable without the manager! sh scripts in Linux, .commands in OSX, and shortcuts in Windows ]
- Save Config Set
- Launch PD with Open Set
- Quit
- About
Feedback? Those interested in collaboration please drop me a line.
Ben
PD-dev mailing list PD-dev@iem.kug.ac.at http://iem.kug.ac.at/cgi-bin/mailman/listinfo/pd-dev