Re: help for module name?

[Jerome Quelin]

On 07/05/27 21:27 +0200, A. Pagaltzis wrote:
> > well, i don't like the way to prereq sthg in pococm that i
> > won't really use - that is, the whole non-poe logic of
> > audio::mpd.
> 
> What whole non-POE logic? All the logic I can find is the
> as_string method. Are we talking about the same modules?

i was talking of adding in this helper dist the modules stats, status
and time (always in audio::mpd::) which are also just structs and are
shared between the poe and non-poe implementation.

thus, the dist audio::mpd::items would not be enough - unless i also
release separately audio::mpd::stats and... which is a bit silly imo.

therefore:
- audio::mpdhelper?
- audio::mpdcommon?


regards,
jérôme 
-- 
[EMAIL PROTECTED]

Re: taxonomy for data-structure modules?

[David Nicol]

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 user-applied keyword tagging scheme on CPAN (e.g.
search.cpan.org) would be very fruitful and would go a long way
toward solving a lot of the organization-related problems people
bring up on this list.

  -Ken


Does perlmonks have a wiki with a data structures section?  Wikipedia
has loads of data structures documents on it -- for instance,
http://en.wikipedia.org/wiki/Skiplist has links to SkipDB and an implementation
in C#.  Creating a norm of linking data structure modules from the wikipedia
article on the structure in question would do the trick using existing
infrastructure,
as would other proposals that do not demand tiers of new services appear from
nowhere.

US mirror of search.cpan *broken*

[Jonathan Rockway]

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 Rockway][$_].[split //,
";$;"]->[$_].q; ;for 1..4;$,=~s;^.;;;$,});$;->setup;


pgpeDQJtghopx.pgp
Description: PGP signature

Re: help for module name?

[A. Pagaltzis]

* 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 dependency and you’re done.
> 
> well, i don't like the way to prereq sthg in pococm that i
> won't really use - that is, the whole non-poe logic of
> audio::mpd.

What whole non-POE logic? All the logic I can find is the
as_string method. Are we talking about the same modules?

Regards,
-- 
Aristotle Pagaltzis // 

Re: help for module name?

[Jerome Quelin]

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 modules I see are just structs, and the only code in there is
> the formatter method in Audio::MPD::Item::Song. I does not seem
> to me that these things are very generically useful; you’d have
> to do a lot of work to make them interesting for other purposes.

they are indeed just structs, as i said.

> 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 dependency and you’re done.

well, i don't like the way to prereq sthg in pococm that i won't really
use - that is, the whole non-poe logic of audio::mpd. i'd really like to
have a small dist that could be used by the two. it would be way
cleaner imho.

after having sent this mail, i thought that i could as well add other
helper classes used by both audio::mpd and pococ::mpd...

==> maybe Audio::MPDHelper could do the trick?


jérôme 
-- 
[EMAIL PROTECTED]

Re: help for module name?

[A. Pagaltzis]

* 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 there is
the formatter method in Audio::MPD::Item::Song. I does not seem
to me that these things are very generically useful; you’d have
to do a lot of work to make them interesting for other purposes.

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 dependency and you’re done.

Regards,
-- 
Aristotle Pagaltzis // 

help for module name?

[Jerome Quelin]

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 by mpd. there are 3 subclasses item::song,
item::directory and item::playlist.

note that:
 - those items are just a bunch of accessors,
 - those items do not retrieve their information themselves from a file
   or whatever

my problem is that those classes are defined both:
 - in audio::mpd::item (with audio::mpd::item::* subclasses)
 - and poe::component::client::mpd::item (with pococm::item::*
   subclasses)

and the code is the same, with only the package name differing.

since code duplication is bad, and since i don't want to put a prereq
relationship between the 2 modules (in either direction), i'm going to
extract the item::* classes in their own module that's going to be
prereq by the others.

i haven't seen any such thing on cpan, it's always tied to a format
(mp3, or ogg vorbis, or...) and meant to extract meta-information from a
file.

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?


thanks for your help,
jérôme 
-- 
[EMAIL PROTECTED]