Re: RFC - Test::Stupid module
A. Pagaltzis wrote: * Robert Rothenberg [EMAIL PROTECTED] [2005-08-21 13:40]: No matter what wiz-bang new module starter system somebody comes up with, there will be some kind of boilerplate text. Unless maybe it asks you to write the documentation before you write the module. Maybe the solution is to a) explicitly use placeholder marks and b) write the module starter tool in such a way that one can fill in placeholders after initially creating the module. That way the distro builder can find the placeholders without groping for known boilerplate, and the user can either remove the placeholders manually when editing, call the starter tool again later as guidance, or just use the its postponed fill-in as part of his personal modus operandi. Or have Module::Starter know how to include site-local boilerplate. I like addnig a fixed blurb on how to report bugs (and no doubt other stuff but that's what I can think of without looking). If M::S knew how to fetch that during a run it would save me from having to set up a local template such as brian d foy outlined earlier. David
RE: RFC - Test::Stupid module
Title: RE: RFC - Test::Stupid module there will be some kind of boilerplate text. Unless maybe it asks you to write the documentation before you write the module. (Fine for some developers, but not everyone.) Now that would be a cool tool. You simply write a bunch of .t files and it produces a stub module and documentation from it. :-) Yves
Re: RFC - Test::Stupid module
Selon David Landgren [EMAIL PROTECTED]: Or have Module::Starter know how to include site-local boilerplate. I like addnig a fixed blurb on how to report bugs (and no doubt other stuff but that's what I can think of without looking). If M::S knew how to fetch that during a run it would save me from having to set up a local template such as brian d foy outlined earlier. Module::Starter already allows you to create your own templates, see http://search.cpan.org/dist/Module-Starter/lib/Module/Starter/Plugin/Template.pm Then you can create distributions your way using the module-starter --plugin option. -- Sébastien Aperghis-Tramoni Close the world, txEn eht nepO.
Re: RFC - Test::Stupid module
* Robert Rothenberg [EMAIL PROTECTED] [2005-08-20T18:58:25] The problem is that authors use boilerplates. With Module::Starter there are lots of modules with abstracts The great new [modulename]. No matter what wiz-bang new module starter system somebody comes up with, there will be some kind of boilerplate text. Unless maybe it asks you to write the documentation before you write the module. (Fine for some developers, but not everyone.) What do you think about Module::Starter also building, by default, a test file that checks for the boilerplate text? -- rjbs pgpeew6qmBO0o.pgp Description: PGP signature
Re: RFC - Test::Stupid module
David Landgren wrote: Or have Module::Starter know how to include site-local boilerplate. I like addnig a fixed blurb on how to report bugs (and no doubt other stuff but that's what I can think of without looking). If M::S knew how to fetch that during a run it would save me from having to set up a local template such as brian d foy outlined earlier. We're working on something like this (but not there yet) for ExtUtils::ModuleMaker. jimk
Re: RFC - Test::Stupid module
On Mon, Aug 22, 2005 at 10:30:01AM +0200, David Landgren ([EMAIL PROTECTED]) wrote: Or have Module::Starter know how to include site-local boilerplate. I It does. Plugins. -- Andy Lester = [EMAIL PROTECTED] = www.petdance.com = AIM:petdance
Re: RFC - Test::Stupid module
On Aug 19, 2005, at 9:51 AM, Andy Lester wrote: On Fri, Aug 19, 2005 at 07:40:10AM -0700, David Baird ([EMAIL PROTECTED]) wrote: Sure, but the point remains, perhaps better stated as make it really easy for the really lazy, including me. I'm all in favour of modules that help *me* not make an ass of myself. We're all potential victims of our own stupidity. You can use Module::Starter. I tried to make sure it used much better defaults, including putting the name and email address in there for you. This kind of sanity-checking stuff would be appropriate in Module::Release. I've actually got a couple things like this in my custom subclasses that I use personally, such as checking that the Changes file has a data version, etc. -Ken
Re: RFC - Test::Stupid module
In article [EMAIL PROTECTED], A. Pagaltzis [EMAIL PROTECTED] wrote: * _brian_d_foy [EMAIL PROTECTED] [2005-08-20 23:15]: When you want to add something (like a standard test file), you just add it to the sample dist. When you want to change some boilerplate, you just change it in the sample dist. When you want to move files around, well, you get the idea. Using a tool from CPAN is not conceptually different from what youâre doing, but a good way for developers who havenât developed specific needs and wants (yet) to get a headstart on doing things properly. It is completely different. A tool from CPAN is somebody else's idea of what your module distro should look like. Mine, not being a module starter tool, is your own idea. It doesn't know anything about modules other than what you tell it. -- brian d foy, [EMAIL PROTECTED]
Re: RFC - Test::Stupid module
--- _brian_d_foy [EMAIL PROTECTED] wrote: In article [EMAIL PROTECTED], A. Pagaltzis [EMAIL PROTECTED] wrote: Using a tool from CPAN is not conceptually different from what youâre doing, but a good way for developers who havenât developed specific needs and wants (yet) to get a headstart on doing things properly. It is completely different. A tool from CPAN is somebody else's idea of what your module distro should look like. Mine, not being a module starter tool, is your own idea. It doesn't know anything about modules other than what you tell it. I have to agree with this. Long before module-starter came along, I wrote a bash script which, using Template Toolkit, would build the shell of a distribution for me. It also managed source control, various utilities that I enjoy, and set things up just the way I like 'em for my environment. It would be nearly useless for anyone else. Cheers, Ovid -- If this message is a response to a question on a mailing list, please send follow up questions to the list. Web Programming with Perl -- http://users.easystreet.com/ovid/cgi_course/
Re: RFC - Test::Stupid module
* _brian_d_foy [EMAIL PROTECTED] [2005-08-22 20:00]:
It is completely different. A tool from CPAN is somebody else's
idea of what your module distro should look like. Mine, not
being a module starter tool, is your own idea. It doesn't know
anything about modules other than what you tell it.
It’s the same thing insofar as both represent *someone*’s idea of
how the skeleton of a distro should be laid out. There’s valid
reason for both since some people aren’t as far along the curve
yet as to have their own ideas about that.
* Ovid [EMAIL PROTECTED] [2005-08-22 21:10]:
I have to agree with this. Long before module-starter came
along, I wrote a bash script which, using Template Toolkit,
would build the shell of a distribution for me. It also
managed source control, various utilities that I enjoy, and set
things up just the way I like 'em for my environment. It would
be nearly useless for anyone else.
Sure, but you and brian aren’t the kind of people who’d need h2xs
or module-starter or the like anyway. I find it kind of strange
to be telling people without enough experience to possibly roll
their own yet to do just that.
Regards,
--
#Aristotle
*AUTOLOAD=*_=sub{s/(.*)::(.*)/print$2,(,$\/, )[defined wantarray]/e;$1};
Just-another-Perl-hacker;
