Re: I think we can just scrap CPAN Ratings altogether

2006-05-26 Thread Mark Stosberg
On Fri, May 26, 2006 at 12:32:48PM -0500, Ken Williams wrote:
 
 I think the real value that most people find in the ratings is not  
 the quantitative data but the qualitative written reviews.  Making  
 that more integrated with various other search/browse sites might be  
 cool, but even then it might help turn CPAN from a collaborative  
 sharing space into a competitive, bashing, NIH space, which would be  
 too bad.

Perhaps at least the number of reviews could be factored into searches,
or the at least the presence of /any/ reviews. I always find it easier
to evaluate a module when I can see what others think about it as well.

Mark


ISO8601 Module: Would this be worth writing?

2006-05-26 Thread Ron Blaschke
Dear Module Authors,

I'm thinking about writing an ISO 8601 module, and would like to know if
you guys would consider it useful.  I have the following in mind:

- It should parse and format ISO 8601

- It should be simple (no fancy date arithmetics, ..), and have minimal
dependencies

- There should be an API similar to [local|gm]time and
Time::Local::time[local|gm]

- For example:
perl -MTime::ISO8601 -e print scalar iso8601time
2006-05-26T20:42:16+02:00

- Probably called Time::ISO8601 ?

Any comment is greatly appreciated, even if you think the idea is silly.

Ron


Module naming advice

2006-05-26 Thread Jeff Lavallee
Hi all, before I upload a new module, I thought I'd make sure the
namespace I intend to use makes sense.  I've been working on a set of
modules to make interacting with the next generation of Yahoo's
marketing web services easier.  The modules insulate the user from a lot
of the SOAP::Lite details.  Currently, I'm planning on calling it
Yahoo::Marketing.  Yahoo::Marketing.pm itself would just serve as a
place holder (with POD) for the time being, with all the meat under that
namespace (for example, Yahoo::Marketing::AccountService,
Yahoo::Marketing::Account, etc).  The POD-in-progress for
Yahoo::Marketing is below.

Any thoughts/comments/suggestions about the intended namespace would be
greatly appreciated.

Thanks,

Jeff





NAME
   Yahoo::Marketing - an interface for Yahoo! Search Marketing's Web
   Services.

VERSION
   Version 0.01

SYNOPSIS
   This collection of modules makes interacting with Yahoo! Search
   Marketing's Web Services as easy as possible.

   Sample Usage:

   use Yahoo::Marketing::Keyword;
   use Yahoo::Marketing::KeywordService;

   my $service =
Yahoo::Marketing::KeywordService-new-parse_config;

   my $keyword = Yahoo::Marketing::Keyword-new
  -adGroupID(
$ad_group_id )
  -text( 'some text' )
  -alternateText( 'some
alternate text' )

-sponsoredSearchMaxBid( 1.00 )
  -status( 'On' )
  -advancedMatchON(
'true' )
  -url(
'http://www.someurl.com' )
 ;

   my $added_keyword = $service-addKeyword(
 keyword = $keyword
 );
   ...

EXPORT
   No exported functions

METHODS
   No methods.

   See Yahoo::Marketing::Service

   for service use

   And

   See Yahoo::Marketing::ComplexTypes

   for Complex Type documentation


Re: ISO8601 Module: Would this be worth writing?

2006-05-26 Thread A. Pagaltzis
Hi Ron,

* Ron Blaschke [EMAIL PROTECTED] [2006-05-26 22:00]:
 I'm thinking about writing an ISO 8601 module, and would like
 to know if you guys would consider it useful.

see HTTP::Date.

The fact that it’s burried inside libwww-perl has annoyed me more
than once, though.

Regards,
-- 
Aristotle Pagaltzis // http://plasmasturm.org/


Re: Module naming advice

2006-05-26 Thread David Landgren

Jeff Lavallee wrote:

Hi all, before I upload a new module, I thought I'd make sure the
namespace I intend to use makes sense.  I've been working on a set of
modules to make interacting with the next generation of Yahoo's
marketing web services easier.  The modules insulate the user from a lot
of the SOAP::Lite details.  Currently, I'm planning on calling it
Yahoo::Marketing.  Yahoo::Marketing.pm itself would just serve as a
place holder (with POD) for the time being, with all the meat under that
namespace (for example, Yahoo::Marketing::AccountService,
Yahoo::Marketing::Account, etc).  The POD-in-progress for
Yahoo::Marketing is below.

Any thoughts/comments/suggestions about the intended namespace would be
greatly appreciated.


There is already at least one module in WWW::Yahoo::*. I would suggest 
slotting your modules in at that level as well.


David

--
hope still, a little resistance always maybe stubborn tiny lights vs. 
clustering darkness forever ok?