Re: [PD-dev] naming loaders: pdlua, tclpd, etc.
Claude Heiland-Allen wrote: > Yes, a simple one: there is a function typedef (for the loader hook > functionality) and a function to add a hook to the list. I forget the > exact names, they're in m_pd.h if you have a new enough Pd. You mean this? (From your Lua external.) /* defined in pd/src/s_loader.c but not in any header file... */ typedef int (*loader_t)(t_canvas *, char *); void sys_register_loader(loader_t loader); This looks like it may be useful for Pd/Q, too. I guess I'll have to dive into the sources to see how it works, or is it documented somewhere? > In my experience trying to use Haskell in Pd didn't work so well, partly > because it was compiled. Lua, being interpreted, worked much better. Yeah, the nice thing about interpreted languages is that they allow you to change the code on the fly which is great for live coding. Pd/Q does that, too. It's still work in progress, but all the basic functionality for processing Pd messages is already there and seems to work quite well. (In fact you could see it in action in Julius' Faust guitar demo at LAC08, where it did all the table-driven MIDI-to-Faust controller mapping behind the scenes.) Thanks, Albert -- Dr. Albert Gr"af Dept. of Music-Informatics, University of Mainz, Germany Email: [EMAIL PROTECTED], [EMAIL PROTECTED] WWW:http://www.musikinformatik.uni-mainz.de/ag ___ PD-dev mailing list PD-dev@iem.at http://lists.puredata.info/listinfo/pd-dev
Re: [PD-dev] naming loaders: pdlua, tclpd, etc.
Albert Graef wrote: > Frank Barknecht wrote: >> May I throw in another one: As loaders are a bit different than >> externals, > > Uhm, did I miss anything? In which way is a "loader" different from an > external? A loader-external adds a hook into Pd's loader (the bit that searches for files to load when an object of unknown class is instantiated). This hook can do anything, but most commonly it adds support for classes written in languages other than (already compiled) C or .pd text patches. A "loader" is a subset of an external, any compiled code loaded by Pd is an external, but some externals can use the loader API. > In that it loads another interpreter? Is there a special new > API for this kind of things? Yes, a simple one: there is a function typedef (for the loader hook functionality) and a function to add a hook to the list. I forget the exact names, they're in m_pd.h if you have a new enough Pd. > I just want to know as I'm maintaining the > Pd-Faust and -Q interfaces, and I'm always looking for ways to make them > work better... In my experience trying to use Haskell in Pd didn't work so well, partly because it was compiled. Lua, being interpreted, worked much better. > Albert Hope this helps, Claude -- http://claudiusmaximus.goto10.org ___ PD-dev mailing list PD-dev@iem.at http://lists.puredata.info/listinfo/pd-dev
Re: [PD-dev] naming loaders: pdlua, tclpd, etc.
Frank Barknecht wrote: > May I throw in another one: As loaders are a bit different than > externals, Uhm, did I miss anything? In which way is a "loader" different from an external? In that it loads another interpreter? Is there a special new API for this kind of things? I just want to know as I'm maintaining the Pd-Faust and -Q interfaces, and I'm always looking for ways to make them work better... Albert -- Dr. Albert Gr"af Dept. of Music-Informatics, University of Mainz, Germany Email: [EMAIL PROTECTED], [EMAIL PROTECTED] WWW:http://www.musikinformatik.uni-mainz.de/ag ___ PD-dev mailing list PD-dev@iem.at http://lists.puredata.info/listinfo/pd-dev
Re: [PD-dev] naming loaders: pdlua, tclpd, etc.
what exactly *is* the lua loader? is it a wrapper? or a library? I was confused in the beginning bcause I thought the "thing" was named pdlua, but the "thing" was loaded with lib- lua (so I thought it *is* a library, but named like lua, the language itself? hmm..) marius. Frank Barknecht wrote: > Hallo, > Hans-Christoph Steiner hat gesagt: // Hans-Christoph Steiner wrote: > >> Any perferred name? I don't think I have a strong preference of any >> name, but I do think there should be a simple, standard naming scheme. > > May I throw in another one: As loaders are a bit different than > externals, maybe a "loader" pre- or suffix would be good, like > lua_loader.pd_linux or loader_lua.pd_linux. That way, [lua] would > still be possible. > > I also don't have a strong preference for any of the suggestions, but > I agree that consistent naming can be useful. > > Ciao ___ PD-dev mailing list PD-dev@iem.at http://lists.puredata.info/listinfo/pd-dev
Re: [PD-dev] naming loaders: pdlua, tclpd, etc.
Hallo, Hans-Christoph Steiner hat gesagt: // Hans-Christoph Steiner wrote: > Any perferred name? I don't think I have a strong preference of any > name, but I do think there should be a simple, standard naming scheme. May I throw in another one: As loaders are a bit different than externals, maybe a "loader" pre- or suffix would be good, like lua_loader.pd_linux or loader_lua.pd_linux. That way, [lua] would still be possible. I also don't have a strong preference for any of the suggestions, but I agree that consistent naming can be useful. Ciao -- Frank Barknecht _ __footils.org__ ___ PD-dev mailing list PD-dev@iem.at http://lists.puredata.info/listinfo/pd-dev
Re: [PD-dev] naming loaders: pdlua, tclpd, etc.
Hans-Christoph Steiner ha scritto: > Hey, > > Now that we have a number of loaders, I'd like to figure out a > standard way of naming the libraries so that they are easy to > organize and load. Currently, there are these arrangments: > > pdXXX > - > pdlua.pd_linux > pdtcl.pd_linux > pdhaskell.pd_linux > [import pdtcl] > > > XXXpd > - > luapd.pd_linux > tclpd.pd_linux > haskellpd.pd_linux > [import tclpd] > > > XXX > --- > lua.pd_linux > tcl.pd_linux > haskell.pd_linux > [import tcl] > > for me it's ok either "tclpd" or "pdtcl". I believe calling it just "tcl" would lead to confusion, since Tcl is already a library used by Pd. if you happen to rename tclpd to pdtcl, please rename also the occurrences of tclpd inside the source code to pdtcl. -- Federico Ferri ___ PD-dev mailing list PD-dev@iem.at http://lists.puredata.info/listinfo/pd-dev
Re: [PD-dev] naming loaders: pdlua, tclpd, etc.
So I agree this is good: -lib lua [import lua] Then it seems that it would be nice if the projects were either: pdlua pdtcl pdhaskell or: luapd tclpd haskellpd How about the first one? .hc On Mar 13, 2008, at 2:39 PM, Claude Heiland-Allen wrote: > Hans-Christoph Steiner wrote: >> XXX >> --- >> lua.pd_linux > > ^^ this is what I use. The project as a whole is called 'pdlua' > but the external for Pd is called 'lua', like '-lib lua' and [lua]. > >> tcl.pd_linux >> haskell.pd_linux > > ^^ this is probably what I will use if I ever resume work on my > Haskell external, or maybe 'ghc.pd_linux' if it depends on that > Haskell implementation. > > The extra 'pd' in the other alternative are redundant. > >> Any perferred name? I don't think I have a strong preference of >> any name, but I do think there should be a simple, standard >> naming scheme. > > Remove redundant 'pd's. > > > Claude Access to computers should be unlimited and total. - the hacker ethic ___ PD-dev mailing list PD-dev@iem.at http://lists.puredata.info/listinfo/pd-dev
Re: [PD-dev] naming loaders: pdlua, tclpd, etc.
Hans-Christoph Steiner wrote: > XXX > --- > lua.pd_linux ^^ this is what I use. The project as a whole is called 'pdlua' but the external for Pd is called 'lua', like '-lib lua' and [lua]. > tcl.pd_linux > haskell.pd_linux ^^ this is probably what I will use if I ever resume work on my Haskell external, or maybe 'ghc.pd_linux' if it depends on that Haskell implementation. The extra 'pd' in the other alternative are redundant. > Any perferred name? I don't think I have a strong preference of any > name, but I do think there should be a simple, standard naming scheme. Remove redundant 'pd's. Claude ___ PD-dev mailing list PD-dev@iem.at http://lists.puredata.info/listinfo/pd-dev
[PD-dev] naming loaders: pdlua, tclpd, etc.
Hey, Now that we have a number of loaders, I'd like to figure out a standard way of naming the libraries so that they are easy to organize and load. Currently, there are these arrangments: pdXXX - pdlua.pd_linux pdtcl.pd_linux pdhaskell.pd_linux [import pdtcl] XXXpd - luapd.pd_linux tclpd.pd_linux haskellpd.pd_linux [import tclpd] XXX --- lua.pd_linux tcl.pd_linux haskell.pd_linux [import tcl] Any perferred name? I don't think I have a strong preference of any name, but I do think there should be a simple, standard naming scheme. .hc Mistrust authority - promote decentralization. - the hacker ethic ___ PD-dev mailing list PD-dev@iem.at http://lists.puredata.info/listinfo/pd-dev
[PD-dev] [Fwd: Re: finding debian-dependencies of a binary]
Original Message From: Hans-Christoph Steiner <[EMAIL PROTECTED]> That sounds quite useful, I should have guessed. Could you send this to pd-dev? Georg is mostly doing this work. .hc On Mar 13, 2008, at 10:36 AM, IOhannes m zmoelnig wrote: > hi hans. > > i knew that there was a dpkg helpertool to get the package- > dependencies of a binary. it's "dpkg-shlibdeps" > > for whatever[*] reasons it needs debian/control > > % mkdir debian && touch debian/control > % dpkg-shlibdeps -O Gem.pd_linux > > mfg.sr > IOhannes > > [*] well, obviously this helper is meant to be used when building > debian-packages when you have the full debian/ infrastructure; you > usually call it as "dh_shlibdeps" in the debian/rules ___ PD-dev mailing list PD-dev@iem.at http://lists.puredata.info/listinfo/pd-dev
