[[ This message was both posted and mailed: see the "To," "Cc," and "Newsgroups" headers for details. ]]
In article <aanlkti=tc5xsrkivefdgnem6ecrgx4c=5=gnzdxqv...@mail.gmail.com>, Stephen Rollyson <srolly...@cpan.org> wrote: > I've just joined PAUSE and have begun working on a module whose > purpose is to fill a directory based on pluggable criteria and > fetching methods. My inclination is to call this module > Directory::Fill, with an abstract Directory::Fill::Criteria class and > an abstract Directory::Fill:Fetcher class. An example usage of this > module would be to fill an MP3 player up with random MP3s. Does the directory portion really matter in this case? That is, once you figure out which files to select, does putting them in a directory actually matter as a fundamental part of the problem? I see two parts here. There's the pluggable criteria portion to select items, and there's the part that post processes that list of items. It sounds like your module is mostly the picking part, and it would be much more flexible to having the picking portion apart from the directory portion. I thought there would already be some modules in the Algorithm::* section that would do that sort of thing. I haven't looked to see if any do exactly what you need though. -- brian d foy (one of many PAUSE admins), http://pause.perl.org PAUSE instructions: http://pause.perl.org/pause/query?ACTION=pause_04about Archives: http://www.xray.mpe.mpg.de/mailing-lists/modules Please send all messages back to modules@perl.org with no CC to me.
