PrePAN

Sign in to PrePAN

PrePAN provides a place
to discuss your modules.

CLOSE

Requests for Reviews Feed

Marathon Perl bindings for the Marathon REST API

geidies@github 0 comments

Catalyst::Model::DBI ADD Option set_names_utf8

Hello all,

I' ve added a option set_names_uft8 in the Config-Hash. This set the SQL-Order "Set names 'utf8' on connect. What you think?

FlorianBogel@twitter 0 comments

WebService::ILS Unified web interface to internet library services APIs

Focused on the e-book distributors, but there's no reason why it cannot be used with the providers of other media that expose API It provides both unified and native interfaces to service providers. It is planned to provide interface for consolidated parallel search with multiple providers in the near future.

srdjan-catalyst@github 0 comments

MemcacheDB::Dump MemcacheDB strage dumper

  • MemcacheDB (http://memcachedb.org/) is a KVS designed for persistent.
  • MemcacheDB::Dump is a dumper for the MemcacheDB's backend strage file.

ajiyoshi-vg@github 0 comments

WWW::PagerDuty This is a perl wrapper of the PagerDuty client API

Currently, there is no publicly available simple pager duty client wrapper for Perl. This is an attempt to wrap LWP::UserAgent to provide access to their services. The key used in the above example is the key used in their public documents.

rnovak1988@github 0 comments

DTrace::Consumer A DTrace Consumer Implemented as a Perl XS module

This module likely only builds, tests, and runs on Solaris 10 and higher, for SPARC/x86 at the moment.

Its purpose is to provide a DTrace Consumer that emits output as raw Perl data structures (scalars, arefs, hrefs), rather than the usual dtrace(1M) consumer program, whose output would have to subsequently be parsed into such data structures.

Such data can be much more efficiently parsed into JSON and the like for further processing and visualization.

It should be relatively straightforward to add support for other platforms that have DTrace, such as MacOS X.

gmarler@github 0 comments

Time::Ago Convert duration, in seconds, to approximation in words

Given a duration, in seconds, returns a readable approximation.

This is a port of Rails' time_ago_in_words date helper method.

Package name suggestions welcome.

   From Rails' docs:

     0  29 secs
       less than a minute

     30 secs  1 min, 29 secs
       1 minute

     1 min, 30 secs  44 mins, 29 secs
       [2..44] minutes

     44 mins, 30 secs  89 mins, 29 secs
       about 1 hour

     89 mins, 30 secs  23 hrs, 59 mins, 29 secs
       about [2..24] hours

     23 hrs, 59 mins, 30 secs  41 hrs, 59 mins, 29 secs
       1 day

     41 hrs, 59 mins, 30 secs  29 days, 23 hrs, 59 mins, 29 secs
       [2..29] days

     29 days, 23 hrs, 59 mins, 30 secs  44 days, 23 hrs, 59 mins, 29 secs
       about 1 month

     44 days, 23 hrs, 59 mins, 30 secs  59 days, 23 hrs, 59 mins, 29 secs
       about 2 months

     59 days, 23 hrs, 59 mins, 30 secs  1 yr minus 1 sec
       [2..12] months

     1 yr  1 yr, 3 months
       about 1 year

     1 yr, 3 months  1 yr, 9 months
       over 1 year

     1 yr, 9 months  2 yr minus 1 sec
       almost 2 years

     2 yrs  max time or date
       (same rules as 1 yr)

mla@github 17 comments

Mojo::RabbitMQ::Client This is a rewrite of great module AnyEvent::RabbitMQ to work on top of Mojo::IOLoop

This module is based on AnyEvent::RabbitMQ. But unlike it, it runs on Mojo::IOLoop and implements Mojo::EventEmitter instead of AE callbacks.

SPodjasek@github 0 comments

CMS::Drupal Perl interface to the Drupal CMS

Just a simple interface to Drupal, to provide a connector for other CMS::Drupal::Module::* modules.

A database handle is returned by the $drupal->dbh() method call.

There's a CMS::Drupal::Types submodule for type-checking.

1nickt@github 0 comments

ArangoDB ArangoDB 2.x HTTP API interface

ArangoDB implements the ArangoDB 2.x HTTP API interface (mostly) and uses Furl HTTP client as it's faster than LWP. My plan is to continue this, so it will at the end implement full HTTP API.

Now, I have a problem about namespace as there is already two other ArangoDB API. One named ArangoDB (implements 1.01 API) and another one ArangoDB2 (implements 2.x API).

Reason why I created new one, was that documentation of ArangoDB2 module in that time was quite poor and I didn't have time to figure out how to use it. So, I created new one more faster.

So what should I do with my version? How to name it or not release it all?

Cheers, Jari

bissei@github 1 comment