It would be super userful to have an easy way to make the various loaders auto-load (Lua, Tcl, libdir, etc). For the 0.43 GUI plugins, currently, it will autoload any file called *-plugin.tcl anywhere in the path, so to install a 0.43 GUI plugin, you just drop the file into the Pd path and restart.
I was thinking we could do the same with with loaders. So *- loader.pd_linux (or maybe *-loader.so) anywhere in the Pd path would be loaded at startup.
I'd really like to see more people using the pdlua, tclpd, libdir, etc. and I think making them really easy to install on all platforms would go a long way towards making that happen.
.hc
----------------------------------------------------------------------------
"[W]e have invented the technology to eliminate scarcity, but we are deliberately throwing it away to benefit those who profit from scarcity." -John Gilmore
On Mon, 16 Nov 2009, Hans-Christoph Steiner wrote:
It would be super userful to have an easy way to make the various loaders auto-load (Lua, Tcl, libdir, etc).
I think it would be even more userful to have hexloader work for abstractions.
I was thinking we could do the same with with loaders. So *-loader.pd_linux (or maybe *-loader.so) anywhere in the Pd path would be loaded at startup.
You just have to put every loader in the -lib section of your pdsettings or pdrc. That's all.
I'd really like to see more people using the pdlua, tclpd,
Yeah, one thing that always annoyed me was that although it's extremely nice to have this support for a bunch of extra languages, there's scarcely anything significant that has been released for pd, that uses those languages. I mean, there are not many of those language libs that appear to have any more users than the author himself. It may be a sign of how those libs are used though: I suppose that they are more often used for project-specific code than otherwise. But generally, I think that they are underused.
_ _ __ ___ _____ ________ _____________ _____________________ ... | Mathieu Bouchard, Montréal, Québec. téléphone: +1.514.383.3801
On Nov 17, 2009, at 12:40 AM, Mathieu Bouchard wrote:
On Mon, 16 Nov 2009, Hans-Christoph Steiner wrote:
It would be super userful to have an easy way to make the various loaders auto-load (Lua, Tcl, libdir, etc).
I think it would be even more userful to have hexloader work for abstractions.
I was thinking we could do the same with with loaders. So *- loader.pd_linux (or maybe *-loader.so) anywhere in the Pd path would be loaded at startup.
You just have to put every loader in the -lib section of your pdsettings or pdrc. That's all.
Its an extra step that doesn't seem necessary. And we are getting to drag-n-drop installation of libraries, plus the preferences in Pd are a mess.
I'd really like to see more people using the pdlua, tclpd,
Yeah, one thing that always annoyed me was that although it's extremely nice to have this support for a bunch of extra languages, there's scarcely anything significant that has been released for pd, that uses those languages. I mean, there are not many of those language libs that appear to have any more users than the author himself. It may be a sign of how those libs are used though: I suppose that they are more often used for project-specific code than otherwise. But generally, I think that they are underused.
Personally, I think they are underused because they are difficult to install and use. That's why I want to make it trivially easy to install.
.hc
----------------------------------------------------------------------------
As we enjoy great advantages from inventions of others, we should be glad of an opportunity to serve others by any invention of ours; and this we should do freely and generously. - Benjamin Franklin
On Tue, Nov 17, 2009 at 3:22 AM, Hans-Christoph Steiner hans@at.or.atwrote:
It would be super userful to have an easy way to make the various loaders auto-load (Lua, Tcl, libdir, etc). For the 0.43 GUI plugins, currently, it will autoload any file called *-plugin.tcl anywhere in the path, so to install a 0.43 GUI plugin, you just drop the file into the Pd path and restart.
I still don't understand why is it better to have plugins all around the patch than having them in one plugin directory. Do we expect libs and abstractions having plugins bundled with them? Or is it for being able to administer them from the same place as path dirs?
Andras
On Nov 17, 2009, at 5:29 PM, András Murányi wrote:
On Tue, Nov 17, 2009 at 3:22 AM, Hans-Christoph Steiner hans@at.or.at wrote:
It would be super userful to have an easy way to make the various loaders auto-load (Lua, Tcl, libdir, etc). For the 0.43 GUI plugins, currently, it will autoload any file called *-plugin.tcl anywhere in the path, so to install a 0.43 GUI plugin, you just drop the file into the Pd path and restart.
I still don't understand why is it better to have plugins all around the patch than having them in one plugin directory. Do we expect libs and abstractions having plugins bundled with them? Or is it for being able to administer them from the same place as path dirs?
In Debian-speak: /usr/lib/pd/startup - plugins included with a package /usr/lib/pd-externals - plugins in a separate package ~/pd-externals - user-installed plugins
In Mac OS X speak: Pd.app/Contents/Resources/startup - plugins included with a package /Library/Pd - admin-installed plugins ~/Library/Pd - user-installed plugins
.hc
----------------------------------------------------------------------------
There is no way to peace, peace is the way. -A.J. Muste
2009/11/17 Hans-Christoph Steiner hans@at.or.at
On Nov 17, 2009, at 5:29 PM, András Murányi wrote:
On Tue, Nov 17, 2009 at 3:22 AM, Hans-Christoph Steiner hans@at.or.atwrote:
It would be super userful to have an easy way to make the various loaders auto-load (Lua, Tcl, libdir, etc). For the 0.43 GUI plugins, currently, it will autoload any file called *-plugin.tcl anywhere in the path, so to install a 0.43 GUI plugin, you just drop the file into the Pd path and restart.
I still don't understand why is it better to have plugins all around the patch than having them in one plugin directory. Do we expect libs and abstractions having plugins bundled with them? Or is it for being able to administer them from the same place as path dirs?
In Debian-speak: /usr/lib/pd/startup - plugins included with a package /usr/lib/pd-externals - plugins in a separate package ~/pd-externals - user-installed plugins
In Mac OS X speak: Pd.app/Contents/Resources/startup - plugins included with a package /Library/Pd - admin-installed plugins ~/Library/Pd - user-installed plugin
Rings a bell ;o)
Andras
-
András Murányi -
Hans-Christoph Steiner -
Mathieu Bouchard