New module HTML::FormTemplate
The next version of the Module List will list the following module: modid: HTML::FormTemplate DSLI:adpO description: Store definition, make persist forms, report userid: DUNCAND (Darren Duncan) chapterid: 15 (World_Wide_Web_HTML_HTTP_CGI) enteredby: JV (Johan Vromans) enteredon: Sat Jan 6 10:34:39 2001 GMT The resulting entry will be: HTML:: ::FormTemplateadpO Store definition, make persist forms, report DUNCAND Please allow a few days until the entry will appear in the published module list. Parts of the data listed above can be edited interactively on the PAUSE. See https://pause.kbx.de/pause/authenquery?ACTION=edit_mod Thanks for registering, The Pause Team
Re: forwarded message from Brian Ingerson
[Quoting Andreas J. Koenig, on January 6 2001, 07:16, in "Re: forwarded messag"] > > On Thu, 4 Jan 2001 21:55:04 +0100, Johan Vromans <[EMAIL PROTECTED]> said: > > > Fellow modulars, > > What do you think? > > An option that goes around in my head is championizing the module > list. We could say, just as Doug is champion of the Apache namespace, > Brian I could be the champion of the Inline namespace. Sounds like a good idea. > This could be implemented in terms of permissions. The form to > register a new module that all admins can use without restriction > could be changed so that userid XXX can add modules in the YYY > namespace. Then I could grant Brian the permission to add modules to > the Inline namespace. I think this is a slight oversimplification. People will apply to the mailing list to register a module. That means that we (modulars) must know what namespaces are championized, and who is their champion. Would it be possible to have a user-mode "Register a Module" form, that just sends the request to the mailing list, and --if appropriate-- to the champion? -- Johan
Re: forwarded message from Brian Ingerson
> On Sat, 6 Jan 2001 11:34:04 +0100, [EMAIL PROTECTED] (Johan Vromans) said: > I think this is a slight oversimplification. People will apply to the > mailing list to register a module. That means that we (modulars) must > know what namespaces are championized, and who is their champion. > Would it be possible to have a user-mode "Register a Module" form, > that just sends the request to the mailing list, and --if > appropriate-- to the champion? Sounds good. I'll see how fast I can do it. -- andreas
[RFC] Audio::SoundFile - Perl interface to libsndfile library
Hi. I've written a Perl module that handles audio stream using external libsndfile library and is now ready to upload it to CPAN. But before doing so, I'd like to ask for a comment on module naming. I'm planning to use following namespace: Audio::SoundFile Audio::SoundFile::Header Audio::SoundFile::Reader Audio::SoundFile::Writer Basically, this module provides common read/write interface for various sound formats supported by libsndfile (includes .au and .wav). Also, in addition to standard I/O interface, I have added direct PDL (Perl Data Language) interface, so data can be read/ manipulated/written efficiently, without copying to Perl's native scalar/array. I considered PDL::IO::SoundFile:: SoundFile:: Audio::LibSoundFile:: Audio::SoundFile:: and Audio::SoundFile:: seems fairly clear and appropriate. Anyone has comments/agreement/disagreement on this naming? -- Taisuke Yamada <[EMAIL PROTECTED]> PGP fingerprint = 6B 57 1B ED 65 4C 7D AE 57 1B 49 A7 F7 C8 23 46
Re: [RFC] Audio::SoundFile - Perl interface to libsndfile library
> On Sun, 7 Jan 2001 04:44:16 +0900, Taisuke Yamada <[EMAIL PROTECTED]> said: > and Audio::SoundFile:: seems fairly clear and appropriate. > Anyone has comments/agreement/disagreement on this naming? Sounds good:-) -- andreas
