Posts Categorized: Perl

The trick is simple: bundle all the files to be shared into a tarball called shared-files.tar.gz. As there is now only that one file, which name always remains the same, any new install is conveniently clobbering the old version.

To browse directories, I’m using the NERD Tree. But I also like to have a view where I can move files around in the listing, organize them in categories and hide a few of them. For that, there’s vim project. It’s cool, it’s nifty, it’s… almost what I want. Here’s the plan.

This experiment, I decided, would have the following goals: at its base it would have to be generic enough to be able to smoke any module, and provide the flexibility required to be easily extensible.

Today, I had some bit of fun and created a micro-web service as a one-liner. But then I thought that using almost 70 characters for a web service was awfully long-winded. Surely there was a way to make our Dancer more efficient. But how? How about… by getting a MC involved?

I’ll not try to bamboozle you: diving into Moose’s metaclass system is not easy because playing with classes that beget classes is heady, confusing stuff. It often feels like trying to type by looking at the keyboard in a mirror. But once that dragon is tamed, it can do truly wonderful, terrible things…

A while ago, I spotted TimelineJS, a JavaScript library to create gorgeous timelines, and earmarked it to a future app. Last week, I finally get to play with it by creating Yarnline, an itsy-bitsy mashup app that takes the projects of a Ravelry user and display them in a chronological manner, like so

One of the great joys of Perl and CPAN is how it allows you to stand on the shoulders of giants. By picking the right tools, applications that are not that trivial can be built in a matter of days, if not hours, and the goal of my little project of today is to demonstrate that very thing. So. Grab a helmet and put your mouth-piece on, for this time I aim at nothing else than to blow your mind to awestruck smithereens.

A couple of years back, I created WWW::Ohloh::API because it seemed to be a fun thing to do. And, trust me, it was. But now, since I’m not using that module personaly, I thought it would be a good idea to see if anyone would be willing to co-maintain it. Before I could do that, though, there was two little matters I had to deal with.