Re: Module lists: defining the problem, restating the goals [was Re: OK, so we've decided...]
On Mon, Feb 16, 2004 at 10:43:13AM +, Tim Bunce wrote: Argues for more stats. I think useful *relative* download stats could be extracted from a sample of CPAN sites. Also search.cpan.org could provide relative page-*view* stats for modules. Agreed. There is the mirrors problem of course, but even having stats from one mirror could be really useful for ranking results. And also could provide a picture of what the Perl community is doing as a whole. I know about http://www.cpan.org/misc/cpan-faq.html#Plans_for_statistics and Mr. XXX Ginsparg's opinion, but times change don't they? I'm not suggesting that we make the statistics data available for download by TotalCTRL-wTerrorist Information Awareness cronies however... :) //Ed -- Ed Summers aim: inkdroid web: http://www.inkdroid.org Dealing with failure is easy: Work hard to improve. Success is also easy to handle: You've solved the wrong problem. Work hard to improve. [Alan Perlis]
Re: Smarty templates
On Mon, Feb 09, 2004 at 02:58:02AM -0600, david nicol wrote: Has anyone written a Perl parser for PHP's Smarty template language? I haven't, but it sure would be cool if TT3 [1] supported them. //Ed [1] http://tt3.template-toolkit.org/
Re: Mail::Outlook module
On Wed, Jan 21, 2004 at 02:00:40PM +, Barbie wrote: 1) Is this a distribution worth uploading to CPAN? Yes! There was a recent discussion at chicago.pm [1] at how to get at .pst files. 2) Is Mail::Outlook a suitable namespace or are there better suggestions? In an ideal world your module would plug into the Mail::Box framework somehow. But I'm not even sure if Outlook Express files are functionally different from vanilla Outlook files...exit stage left. //Ed [1] http://mail.pm.org/pipermail/chicago-talk/2004-January/000800.html
Re: New modules
On Wed, Nov 12, 2003 at 08:22:01PM +, Oliver White wrote: As a first step, I was considering adding a module to read GSHHS data [a binary format for coastline data] and give it a name something like Geo::GSHHS. More info at the site: http://www.soest.hawaii.edu/wessel/gshhs/gshhs.html Sounds like a good idea to me, considering that Geo::ShapeFile is already established. //Ed
