On Thu, 2004-06-17 at 11:59, Adrian Howard wrote:
> On 17 Jun 2004, at 11:41, khemir nadim wrote:
> [snip]
> > OK. but a module without a readme with meaning ful content, a minimum
> > of
> > documentation is not "anything" it's "nothing" so I'd say it's OK to
> > not
> > allow "nothing" to get i
* Mark Stosberg <[EMAIL PROTECTED]> [2004-06-17 16:15]:
> So I think a good name might be JavaScript::Tooltip::HTML.
I put in another vote for this.
Regards,
--
Aristotle
"If you can't laugh at yourself, you don't take life seriously enough."
Well, I step into this thread because I _really_ think it's complicating
some (maybe) simple thing.
There can be many distinct actions:
1. search/browse CPAN for a module.
2. use (or require :) a module.
2.1 use it because I'm in a hurry or don't like to rewrite code.
2.2 use it because I don't
On 17 Jun 2004, at 11:41, khemir nadim wrote:
[snip]
OK. but a module without a readme with meaning ful content, a minimum
of
documentation is not "anything" it's "nothing" so I'd say it's OK to
not
allow "nothing" to get into CPAN.
[snip]
Tosh ;-)
If I removed the README file from one of my CPAN
On Thu, Jun 17, 2004 at 08:13:08AM -0500, Ken Williams wrote:
>
> Yeah, HTML::Tooltip and CGI::Tooltip seem like the obvious names. I
> don't think you need to put "Javascript" into the name, that's too much
> information.
Actually, I like JavaScript::Tooltip. If the the code is not
HTML-speci
On Wed, 16 Jun 2004, Fergal Daly wrote:
> On Wed, Jun 16, 2004 at 06:39:22PM -0300, SilvioCVdeAlmeida wrote:
> > Let's write it better:
> > 1. FORBID any module without a meaningful readme with all its (possibly
> > recursive) dependencies, its pod and any other relevant information
> > inside.
>
I'm 50/50 on this.
Just because a module name mentions "Javascript" doesn't mean it would
immediately be discounted by other developers. If people need something
to handle Tooltips, they'll use it, or at least read the pod
documentation.
Also, there are lots of other tooltip implementations out
On Jun 17, 2004, at 7:36 AM, darren chamberlain wrote:
* Becky Alcorn [2004/06/17 12:25]:
We're looking at releasing our new module CGI::Tooltip onto CPAN.
This
module provides a simple perl interface to Walter Zorn's elegant
Javascript
tooltip library (http://www.walterzorn.com/tooltip/tooltip
* Becky Alcorn [2004/06/17 12:25]:
> We're looking at releasing our new module CGI::Tooltip onto CPAN. This
> module provides a simple perl interface to Walter Zorn's elegant Javascript
> tooltip library (http://www.walterzorn.com/tooltip/tooltip_e.htm). This
> library provides a flexible way of
Le 17 juin 04, à 12:41, khemir nadim a écrit :
OK. but a module without a readme with meaning ful content, a minimum
of
documentation is not "anything" it's "nothing" so I'd say it's OK to
not
allow "nothing" to get into CPAN. We, of course, want to avoid
waisting our
time but I think all want t
Yeah, that makes sense to me.
>-Original Message-
>From: khemir nadim [mailto:[EMAIL PROTECTED]
>Sent: Thursday, June 17, 2004 11:52 AM
>To: [EMAIL PROTECTED]
>Subject: Re: New module: CGI::Tooltip
>
>
>OK that was the first part of my proposal (and I find your
>explication for its dismi
OK that was the first part of my proposal (and I find your explication for
its dismissa fine) but as was explained in the original posting, this module
needs a library to be installed. Wouldn't it be nice for the people browsing
around to get that information right away?
Would CGI::Tooltip::Whatev
"Eric Wilhelm" <[EMAIL PROTECTED]> wrote in message
news:[EMAIL PROTECTED]
> >FORBID any module without a meaningful readme with all its (possibly
> >recursive) dependencies, its pod and any other relevant information
> >inside.
> I don't think it is in the spirit of CPAN to "FORBID" anything.
O
I am not convinced of this. As I read it, the developer using CGI::Tooltip
needs no Javascript knowledge; I think I would see CGI::Javascript::Tooltip
and immediately exclude it as I have no knowledge of Javascript. It should
be made clear in the docs of the module that javascript is required at
I think it would be appropriate to further catalogue the module name under
"Java" or the name od the specific library you interface with.
"Becky Alcorn" <[EMAIL PROTECTED]> wrote in message
news:[EMAIL PROTECTED]
> We're looking at releasing our new module CGI::Tooltip onto CPAN. This
> module pr
"Fergal Daly" <[EMAIL PROTECTED]> wrote in message
news:[EMAIL PROTECTED]
> Hi all,
>
> One of my modules has a failure noted against it that was caused by the
> tester's wonky Perl installation. How can this be removed?
I don't have this problem but my modules sometimes fail on windows platform
Ken Williams sent the following bits through the ether:
> Dependencies are now listed in the META.yml file, which is human- and
> machine-readable.
Only in recent modules which use Module::Build. Whereas it's not that
hard[2] to get "good enough" dependencies for the rest. Now decide
who's going
We're looking at releasing our new module CGI::Tooltip onto CPAN. This
module provides a simple perl interface to Walter Zorn's elegant Javascript
tooltip library (http://www.walterzorn.com/tooltip/tooltip_e.htm). This
library provides a flexible way of adding good looking tooltips
(onmouseovers
18 matches
Mail list logo
