Re: Application framework namespaces
In article <[EMAIL PROTECTED]>, Mark Stosberg <[EMAIL PROTECTED]> wrote: > On Fri, May 14, 2004 at 03:17:50PM -0400, _brian_d_foy wrote: > > In article <[EMAIL PROTECTED]>, Michael A Nachbaur > > <[EMAIL PROTECTED]> wrote: > > I'd rather see top-level namespaces for complete applications. I don't > > think the App::* adds any information. :) > I would imagine that you meant to qualify this statement with an > assumption that the applications have decently unique names, i didn't really care to do that, but you would have to anyway to escape the wrath of the PAUSE and CPAN admins. -- brian d foy, [EMAIL PROTECTED]
Re: Application framework namespaces
On May 14, 2004 12:30 pm, Mark Stosberg wrote: > On Fri, May 14, 2004 at 03:17:50PM -0400, _brian_d_foy wrote: > > In article <[EMAIL PROTECTED]>, Michael A Nachbaur > > > > <[EMAIL PROTECTED]> wrote: > > > The thing is, these are free-standing applications, and for the most > > > part aren't developer tools. So, I was thinking an App:: namespace > > > would work well, (e.g.. App::WWW::NachoMusic, etc). > > > > I'd rather see top-level namespaces for complete applications. I don't > > think the App::* adds any information. :) > > I would imagine that you meant to qualify this statement with an > assumption that the applications have decently unique names, and not > generic ones that might look like an existing standard use of a > top-level domain (CGI, HTML, Data, WWW, etc). I agree to that. There can be many instances where you have non-intuitive names, or redundant names. Also, using different top-level namespaces can help to categorize the type of application, making it easier for someone to find what they're looking for. "Gee, I'd like a web-based MP3 player" (App::Media::WWW::), or "I need to provision cable modems using a barcode scanner." (App::Business::Internet::) -- Michael A. Nachbaur <[EMAIL PROTECTED]> http://nachbaur.com/pgpkey.asc
Re: Application framework namespaces
On Fri, May 14, 2004 at 03:17:50PM -0400, _brian_d_foy wrote: > In article <[EMAIL PROTECTED]>, Michael A Nachbaur > <[EMAIL PROTECTED]> wrote: > > > The thing is, these are free-standing applications, and for the most part > > aren't developer tools. So, I was thinking an App:: namespace would work > > well, (e.g.. App::WWW::NachoMusic, etc). > > I'd rather see top-level namespaces for complete applications. I don't > think the App::* adds any information. :) I would imagine that you meant to qualify this statement with an assumption that the applications have decently unique names, and not generic ones that might look like an existing standard use of a top-level domain (CGI, HTML, Data, WWW, etc). Mark
Re: Application framework namespaces
In article <[EMAIL PROTECTED]>, Michael A Nachbaur <[EMAIL PROTECTED]> wrote: > The thing is, these are free-standing applications, and for the most part > aren't developer tools. So, I was thinking an App:: namespace would work > well, (e.g.. App::WWW::NachoMusic, etc). I'd rather see top-level namespaces for complete applications. I don't think the App::* adds any information. :) -- brian d foy, [EMAIL PROTECTED]
Re: Application framework namespaces
Well, the thing is that I have several applications I would like to publish. One is a web-based calendaring app for online gaming, another is a CD store-like MP3 site, and so on. I'm working on a OO-based REST-compliant webmail system similar to SquirrelMail, but built on AxKit. The thing is, these are free-standing applications, and for the most part aren't developer tools. So, I was thinking an App:: namespace would work well, (e.g.. App::WWW::NachoMusic, etc). On May 14, 2004 04:11 am, khemir nadim wrote: > Without seein anything about your application, it's difficult (or nearly > impossible) to answer you but most work is welcome to CPAN if it is (IMO) > documented properly, (including stating clearly what it is good for (which > lack in too many CPAN modules)). > > Cheers, Nadim. > > > "Michael A Nachbaur" <[EMAIL PROTECTED]> wrote in message > news:[EMAIL PROTECTED] > > > I'm working on a web application that is almost 100% perl (the styling is > > handled in XSL). The entire application's test and installation > > procedure > > is > > > managed with a Makefile.PL, and the entire package is very CPAN-ish. I > > wanted to know if there was some place on CPAN that I can publish it so > > other > > > people can deploy my application if they choose? > > > > I'm using the namespace Nacho:: for my modules (Nacho being my > > IRC > > > nick), but if there was an App:: namespace that could be used, I'd > > be willing to upload this to CPAN when I'm finished. > > > > Does anyone see having this sort of code in CPAN as being useful? > > > > -- > > Michael A. Nachbaur <[EMAIL PROTECTED]> > > http://nachbaur.com/pgpkey.asc -- Michael A. Nachbaur <[EMAIL PROTECTED]> http://nachbaur.com/pgpkey.asc
Re: Application framework namespaces
Without seein anything about your application, it's difficult (or nearly impossible) to answer you but most work is welcome to CPAN if it is (IMO) documented properly, (including stating clearly what it is good for (which lack in too many CPAN modules)). Cheers, Nadim. "Michael A Nachbaur" <[EMAIL PROTECTED]> wrote in message news:[EMAIL PROTECTED] > I'm working on a web application that is almost 100% perl (the styling is > handled in XSL). The entire application's test and installation procedure is > managed with a Makefile.PL, and the entire package is very CPAN-ish. I > wanted to know if there was some place on CPAN that I can publish it so other > people can deploy my application if they choose? > > I'm using the namespace Nacho:: for my modules (Nacho being my IRC > nick), but if there was an App:: namespace that could be used, I'd be > willing to upload this to CPAN when I'm finished. > > Does anyone see having this sort of code in CPAN as being useful? > > -- > Michael A. Nachbaur <[EMAIL PROTECTED]> > http://nachbaur.com/pgpkey.asc
