hi there,
i'm working on a module to interface with music player daemon (mpd).
i've released:
- audio::mpd, a traditional oo interface
- poe::component::client::mpd, a poe-aware interface
they're both under development.
for each of them, i've defined an item class to map the items
manipulated
* Jerome Quelin [EMAIL PROTECTED] [2007-05-27 09:50]:
so here's my question: how should i name this new module?
- audio::item= isn't it too vague?
- audio::mpditem = isn't it too specific? (would it be used by others?)
- other?
The modules I see are just structs, and the only code in
On 07/05/27 17:31 +0200, A. Pagaltzis wrote:
* Jerome Quelin [EMAIL PROTECTED] [2007-05-27 09:50]:
so here's my question: how should i name this new module?
- audio::item= isn't it too vague?
- audio::mpditem = isn't it too specific? (would it be used by others?)
- other?
The
* Jerome Quelin [EMAIL PROTECTED] [2007-05-27 18:05]:
On 07/05/27 17:31 +0200, A. Pagaltzis wrote:
I’d suggest Audio::MPD::Item as the distro name, since you’ve
already organised them as a hierarchy in there. As a bonus
you won’t even need to change any of the Audio::MPD code,
just add
The bizrate search.cpan is broken. The most recent module (judging by the
recent tab) is from 5 days ago, 23 May.
I'm told that the UK mirror (digitalcraftsmen) is running fine.
--
package JAPH;use Catalyst qw/-Debug/;($;=JAPH)-config(name = do {
$,.=reverse qw[Jonathan tsu rehton lre rekca
On 5/26/07, Ken Williams [EMAIL PROTECTED] wrote:
I think that's part of it. But another problem is that many people
don't know the official names for the data structures they're
thinking of, e.g. trie or skiplist or whatever, so they can't
search very effectively for it.
It does seem like a
