Date: Mon, 16 Jun 1997 01:21:24 -0400 From: "Joel N. Weber II" <devnull@gnu.ai.mit.edu> To: hasty@rah.star-gate.com Cc: chat@FreeBSD.ORG Subject: Re: Plugin? (Re: Complaining at Warner Brothers? ) Message-ID: <199706160521.BAA16716@ethanol.gnu.ai.mit.edu> In-Reply-To: <199706160353.UAA08761@rah.star-gate.com> (message from Amancio Hasty on Sun, 15 Jun 1997 20:53:56 -0700)
next in thread | previous in thread | raw e-mail | index | archive | help
Date: Sun, 15 Jun 1997 20:53:56 -0700 From: Amancio Hasty <hasty@rah.star-gate.com> >From The Desk Of "Joel N. Weber II" : > Isn't it easy enough to include code in E-scape which knows about > timidy? Won't that solve the problem? The answer to that is no . If you like can can view E-scape as a platform from which you can launch applications as well as providing basic services. Another way to look at it is to dynamically reconfigure your package so as to keep the basic features to a minium . For instance, if I am not into midi why should I be inflicted by downloading the source code and recompiling e-scape to exclude the MIDI component. If E-scape ever does support plugins, you'll have to download the Linux and NetBSD and OpenBSD and Hurd and Solaris code which handles plugins, and I doubt it will ever be useful to you. I suspect there are a couple hundred lines of generic sound GUI code, and maybe a hundred lines or less to interact with Timidy. I think that any plugin API will be much bigger. (I'm assuming that about all this plugin really does is fork and exec timidy, and maybe provides some sort of stop/play/etc controls. Is that true?)
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199706160521.BAA16716>