Re: Namespace question
On Mon, Feb 14, 2011 at 09:45:55AM -0800, Dennis Opacki wrote: > Aloha, > > I plan to contribute a perl module for interacting with Internap's ( > www.internap.com) new OpenStack-based storage architecture. Awesome. Please! > My intent is to name the module Net::XIPCloud after the Internap product > name. How sure are you that that's what your customers will be looking for when they're going to look for a module? Sort of wonder if Net::Internap::XIPCloud might be better and then make sure you've got OpenStack in the description in the =head1 NAME section. Or if the XIPCloud stuff is using standard protocols, Net::OpenStack::Something and mention the Internap part in NAME. Net::XIPCloud still seems fairly reasonable to me btw - just wondering if a more verbose name would be more findable. -- Matt S Trout - Shadowcat Systems - Perl consulting with a commit bit and a clue http://shadowcat.co.uk/blog/matt-s-trout/ http://twitter.com/shadowcat_mst/ Email me now on mst (at) shadowcat.co.uk and let's chat about how our Catalyst commercial support, training and consultancy packages could help your team.
Namespace question
Aloha, I plan to contribute a perl module for interacting with Internap's ( www.internap.com) new OpenStack-based storage architecture. My intent is to name the module Net::XIPCloud after the Internap product name. Sane? Thanks, -Dennis Opacki Systems Architect Internap Network Services, Inc dopa...@internap.com (c) 206-356-2996
Namespace question
Hi, I am writing a module to interface to the IBM LoadLeveler software. LoadLeveler is used for "dynamic workload management" on large AIX servers and MPP systems, very basically it is a batch scheduling system. I would like a namespace of LoadLeveler, is this appropriate ? Thanks for your time Mike -- Mike HawkinsBuilding E2 AWE PLC Aldermaston Email: [EMAIL PROTECTED] Reading Tel: (0118) 9827067 Fax: (0118) 9824820 Berkshire RG7 4PR -- ___ The information in this email and in any attachment(s) is commercial in confidence. If you are not the named addressee(s) or if you receive this email in error then any distribution, copying or use of this communication or the information in it is strictly prohibited. Please notify us immediately by email at [EMAIL PROTECTED], and then delete this message from your computer. While attachments are virus checked, AWE plc does not accept any liability in respect of any virus which is not detected.
Re: Namespace question
In article <[EMAIL PROTECTED]>, Hendrik Van Belleghem <[EMAIL PROTECTED]> wrote: > Someone on IRC suggested something in that direction as well. The big > question here is, what sub-category? Device::Camera:: ? Device::Webcam:: ? Camera would be fine, but not Webcam since you do not necessarily need to use it that way. -- brian d foy (one of many PAUSE admins), http://pause.perl.org please send all messages back to [EMAIL PROTECTED]
Re: Namespace question
On Sun, 5 Jan 2003 21:26:19 + Tim Bunce <[EMAIL PROTECTED]> wrote: > On Sat, Jan 04, 2003 at 10:27:23AM -0800, _brian_d_foy wrote: > > In article <[EMAIL PROTECTED]>, Hendrik Van > > Belleghem <[EMAIL PROTECTED]> wrote: > > > > > I' writing a module that basically access a Connectix/Logitech > > > QuickCam. I checked with rhizo's #perl and the perlmonks CB for a > > > good name for the module and came up with Device::QuikCam. Any > > > feedback would be helpfull :) > > > > i don't have any problem with that name. > > I don't either, much, except to wonder if there's a typo - QuikCam vs > QuickCam. > > But I wonder whether Device:: would end up becoming a bit of a mess > unless we consistently add more sub-categories. > > So far we have Device::ParallelPort::*, Device::ISDN::*, > Device::Modem::*. I think we should continue in that direction. Someone on IRC suggested something in that direction as well. The big question here is, what sub-category? Device::Camera:: ? Device::Webcam:: ? Ofcourse it's a parallel device (well mine is anyway), so Device::ParallelPort::Camera:: etc would also apply more or less. I'm open for ideas and have no problem with changing names if required (well, the module, not my own name ofcourse). To reply to that i vs R thing, yes indeed, altho I had some discussions on IRC and in CB about it prior to starting development :) and the time it took from start to current R wasn't that long. --- Greetz Hendrik ... Quidquid perl dictum sit, altum viditur.
Re: Namespace question
On Sat, Jan 04, 2003 at 10:27:23AM -0800, _brian_d_foy wrote: > In article <[EMAIL PROTECTED]>, Hendrik Van > Belleghem <[EMAIL PROTECTED]> wrote: > > > I' writing a module that basically access a Connectix/Logitech QuickCam. I > > checked with rhizo's #perl and the perlmonks CB for a good name for the > > module and came up with Device::QuikCam. Any feedback would be helpfull :) > > i don't have any problem with that name. I don't either, much, except to wonder if there's a typo - QuikCam vs QuickCam. But I wonder whether Device:: would end up becoming a bit of a mess unless we consistently add more sub-categories. So far we have Device::ParallelPort::*, Device::ISDN::*, Device::Modem::*. I think we should continue in that direction. Tim.
Re: Namespace question
In article <[EMAIL PROTECTED]>, Hendrik Van Belleghem <[EMAIL PROTECTED]> wrote: > I' writing a module that basically access a Connectix/Logitech QuickCam. I > checked with rhizo's #perl and the perlmonks CB for a good name for the > module and came up with Device::QuikCam. Any feedback would be helpfull :) i don't have any problem with that name. -- brian d foy (one of many PAUSE admins), http://pause.perl.org please send all messages back to [EMAIL PROTECTED]
Namespace question
Hi, I' writing a module that basically access a Connectix/Logitech QuickCam. I checked with rhizo's #perl and the perlmonks CB for a good name for the module and came up with Device::QuikCam. Any feedback would be helpfull :) --- Greetz Hendrik ... Quidquid perl dictum sit, altum viditur.
Namespace question
I've written a module for CPAN which translates between (United States) zip codes and city/state names. It seems like there are already some related modules in Geography:: so I was going to call it Geography::ZipCode . Any advice is most welcome. Thanks! -- Arie
Namespace question for caching autoloader
Hi everyone,
I already sent this message as a posting to clpm.modules but thought
here might also be the right place to ask:
I am currently writing on a little module implementing a cached
autoloading of methods as described by Mark Jason Dominus in
http://plover.perl.com/yak/tricks/slide073.html
Short example:
A little class:
package Test;
use base qw(Autoloader::Cache);
use Autoloader::Cache
method1 => q{
sub {
my ($self, $arg) = @_;
$self->{arg} = $arg;
}},
method2 => q{
sub {
return shift->{arg};
}};
sub new { bless { }, shift }
Program instantiating this class:
package main;
use Test;
my $obj = new Test;
# dynamically created via Autoloader::Cache::AUTOLOAD
# method is compiled and diddled into the caller's namespace
$obj->method1("argument");
print $obj->method2;
# second call to a method already previously called:
# quicker since no longer the need for the autoloader
print $obj->method2;
The above also works with an arbitrary number of classes inheriting from
this module, methods and classes aren't mixed up due to a mapping
between methods and classes inside Autoloader::Cache.
Now the question for the namespace: As it can be seen, I have named it
Autoloader::Cache as for yet. Is this appropriate? My main concern is
whether I can just put a module under the top-level namespace of
Autoloader since there is actually only one module of that name so I am
not even sure whether that's a valid top-level namespace.
Tassilo
--
$_=q!",}])(tsuJ[{@"tnirp}3..0}_$;//::niam/s~=)]3[))_$-3(rellac(=_$({
pam{rekcahbus;})(rekcah{lrePbus;})(lreP{rehtonabus;})(rehtona{tsuJbus!;
$_=reverse;s/sub/(reverse"bus").chr(32)/xge;tr~\n~~d;eval;
namespace question
Hi all, I have a module I would like to prepare for inclusion in CPAN. I've been struggling for a while about what to call it and would like some feedback. I guess the best way to do it is to tell you the name and what it does, sort of a pre-namespace-registration. The best name I've come up for it is Data::Grouper. This is a module I developed for use with HTML::Template, although it looks like it will work nicely with Template toolkit and Text::Template. Basically, it takes data, typically from a DBI source although this is a loose coupling, and does two things: 1. Creates an array ref / hash ref nested structure, arbitrarily deep, with breaks on whatever columns you need breaks on 2. Can compute aggregate functions, at every break level, of the data It has some other nifty features but that's the basics. This makes it much easier to create certain types of web pages summarizing and grouping data at multiple levels. The only thing similar I've found is Data::Reporter. It has a concept of breaks, but takes a different approach to output. This module is really meant to work with DBI and a templating module. Any comments on the name? Am I on the right track? I want to start cleaning it up for distribution but I'm going to wait until I'm reasonably sure what the name will ultimately be. Thanks, David Ferrance Principle, M3 Partners, Inc.
CPAN and namespace question
Howdy, I've written a module and I don't know if it is worth putting it in CPAN and what namespace to use. OK, I bought a Card from Conrad (German electronic stuff dealer) which has 8 Relais on it to control electronic circuits. It is connected to the serial port. So I wrote a Module which utilizes Device::SerialPort to control the card(s). Looking at the CPAn module list I don't have an glue about what namespace to use. It is indeed a kind of a hardware driver. It is also a device. In the cpan module list all the modules look very generic. Where to put a module for only one specific need? Before I will register at PAUSE I would like to hear some opinions. Please reply to my email address as I'm not subscribed to the module list. thanks in advance, Norbert
module namespace question
Dear, I'm currently working on a set of Perl modules that interface with a relational database model for the storage and retrieval of XML files. These modules include a broker that handles all database access, modules for XML entities (Document, Element, Attribute, ...) and a SAXDriver module to write files to the database. Currently I am using the namspace XML::DB. All modules reside under this namespace. The most important modules are: XML::DB::Broker XML::DB::Document XML::DB::Node XML::DB::Element XML::DB::Attribute XML::DB::Comment XML::DB::SAXHandler The project is far from complete so the module list can and probably will change over time. Do you approve of my namespace choice or do you have a suggestion for another one? Kind regards Steven Devijver
Re: module namespace question
In perl.modules, you wrote: >--=_NextPart_000_01B6_01C14446.9AE8EBC0 >Content-Type: text/plain; > charset="iso-8859-1" >Content-Transfer-Encoding: 7bit > >I've written some perl code to interface to a Davis Vantage Pro weather >station. I'd like to repackage it as a CPAN module with a proposed namespace >of: > >Device::VantagePro I'd recommend Weather::VantagePro, actually. The most interesting thing about the module is that it does weather stuff, not that it uses a specific device. K. -- Kirrily 'Skud' Robert - [EMAIL PROTECTED] - http://infotrope.net/ "Madi, yours is the one with Renee's lip prints on it." "Yes, and so's my Guinness." -- Sharkey, Madi (from the Netizen quotes file)
module namespace question
I've written some perl code to interface to a Davis Vantage Pro weather station. I'd like to repackage it as a CPAN module with a proposed namespace of: Device::VantagePro The methods in this module will Receive data from the datalogger (EEPROM device that stores data from the weather station until it is ready to be offloaded to the computer) Receive live data directly from the weather station Set the weather station's clock Set and clear alarms Turn the backlighting on and off (what the heck, it's easy) Erik Larsen [EMAIL PROTECTED]
Re: namespace question
> On Thu, 7 Jun 2001 02:04:35 -0700, "Jamie Krasnoo" <[EMAIL PROTECTED]> said: > Generally when one registers/asks for a namespace. When does it show up in > their account so that the Metadata can be edited? As soon as somebody goes over it and decides that the namespace be blessed. Please let us know if there is any urgency. Please note, that the blessings are NOT NEEDED in order to upload and distribute your work. -- andreas
namespace question
Generally when one registers/asks for a namespace. When does it show up in their account so that the Metadata can be edited? Jamie Krasnoo [EMAIL PROTECTED]
Namespace question
When I first registered as a developer I noted that I would be working on modules that could be used for various instrument building calculations - fret calculations, string gauge/diameter calculations, just intonation, numerical calculations of flute impedences and standing waves, length/bore calculations, note/frequecncy conversions and wavelength/frequency conversions, as well as misc music/physics calculations. The name spaces I requested were: Lutherie:: ::FretCalc cdpf Calculate stringed instrument fret locations Sound:: ::Wavelength cdpf Frequency/Wavelength conversions The question is, as most of these modules will be related, I wonder if I should put them in one top level namespace? Lutherie is specific to stringed instruments (plus, I'll be doing other Lutherie specific calculations besides fret placement), so maybe MusicMaker::Lutherie, MusicMaker::FretCalc or something of the sort would be better. In any case, none of the current top level namespaces seem to fit these modules. I'd like to get my first module up soon (currently Lutherie::FretCalc) and I'm open to suggestions before doing so. Thanks, doug sparling
Namespace question
Hi, I'm developing a module to easily support the `delegation' design pattern. How does Class::Delegate sound? Peace, * Kurt Starsinic ([EMAIL PROTECTED]) Senior Software Architect * | `People keep pretending they can make things deeply | |hierarchical, categorizable and sequential when they can't.| |Everything is deeply intertwingled.' -- Ted Nelson |
