I'll be speaking about using (and abusing) the MetaCPAN API on day 2 of YAPC::NA. If you think you might be attending (or even if you're not), I thought I'd post some links to some helpful info. No, you don't need to do any prep for this talk, but for those who are interested, this is just some background info that will help you get your head around MetaCPAN.
This talk will touch on and expand on some of the points I discussed last year, so you could have a quick look at last year's slides. Read More...
I'm happy to announce that iCPAN 2.0.0 is now in the app store. If you're not familiar with it, iCPAN is a free iOS app which allows you to browse CPAN Pod on your iPhone/iPod/iPad. The previous version of iCPAN was released in November of 2010, so this has been a long time in coming.
If only CPAN had a web service...
Originally, my hope was to release frequent iCPAN updates with new Pod, bug fixes and improvements. Read More...
iCPAN hit the app store about a year ago. I didn't really expect there would be a lot of downloads, but the reality is that there was far more interest than I had expected, which is good. After the original app was released, I was able to release a couple of subsequent versions with updated Pod, but it soon became clear that some problems were not being solved.
The first issue was that it was taking a very long time to put a build together, because I had to parse all of minicpan with each run. Read More...
Lots of great stuff is happening with MetaCPAN. Here's a quick (and incomplete) list.
First off, Yanick Champoux has been doing some excellent work to add module up and downvoting to the MetaCPAN API. His work is on Github He has also created a Greasemonkey script to allow module voting to begin on search.cpan.org. We plan on incorporating it into the cpan-mangler as well, so that you can vote on search. Read More...
Since we've been porting CPAN to the iPhone via iCPAN, we've had the chance to re-imagine the CPAN a little bit. We've been thinking, what would we change about search.cpan.org if we were able? We've added the bookmarking, we save searches of recently viewed modules and now we've got syntax highlighting.
A lot of us see our code highlighted in our editors. That's how we're accustomed to viewing code. So why not view it that way in our module documentation? Read More...
