Nilson Santos Figueiredo Junior wrote:
Actually, I have no idea how Test::WWW::Mechanize tests manage to
crash perl under Windows on almost all test cases.
The comment on this bug report looks like it might provide a hint :)
http://rt.cpan.org/Public/Bug/Display.html?id=17954
Cheers, Dave
On 1/2/07, Joe Landman [EMAIL PROTECTED] wrote:
Daniel McBrearty wrote:
is there any way that this info can somehow find its way onto the
perldoc ? in big letters at the top ... ?
Might be a good thing to have an MODULES_CURRENT/MODULES_OBSOLETE list,
or ask the module authors to simply
Matthieu Codron wrote:
On 1/2/07, Joe Landman [EMAIL PROTECTED] wrote:
Might be a good thing to have an MODULES_CURRENT/MODULES_OBSOLETE list,
or ask the module authors to simply note the obsolescence in an updated
POD.
I think it is a terrific idea.
Catalyst is a lot about choice and
what happens if you need to deprecate it ... ?
(I'm only half joking ... )
On 1/3/07, Robert 'phaylon' Sedlacek [EMAIL PROTECTED] wrote:
Matthieu Codron wrote:
On 1/2/07, Joe Landman [EMAIL PROTECTED] wrote:
Might be a good thing to have an MODULES_CURRENT/MODULES_OBSOLETE list,
or ask the
another thing : doesn't that imply that you have to install the
deprecated plugin before the DepPlugins Plugin jumps up an says you
shouldn't ha' done that jimmy ... (presumably before breathing
alcohol at you and pissing in your flower pots).
All that is really needed is that instead of
Daniel McBrearty wrote:
another thing : doesn't that imply that you have to install the
deprecated plugin before the DepPlugins Plugin jumps up an says you
shouldn't ha' done that jimmy ... (presumably before breathing
alcohol at you and pissing in your flower pots).
What's that? I didn't
Daniel McBrearty wrote:
If I have this right, the plugin :
- looks at the list of installed stuff at runtime
- compares against %known_good_list or %black_list
- warns when it decides something is wrong ...
Rather: List of plugins loaded at runtime in the application, and only
warn if
I'd make that optional, per config or environment variable. Just loading
stuff off the net by default seems bad to me. Also, devs without
internet connection could get in trouble. IMO it also shouldn't update
itself, but rather just tell the user if there's a newer version.
yup, makes sense.
Daniel McBrearty wrote:
is there any way that this info can somehow find its way onto the
perldoc ? in big letters at the top ... ?
Might be a good thing to have an MODULES_CURRENT/MODULES_OBSOLETE list,
or ask the module authors to simply note the obsolescence in an updated POD.
--
Joseph
Matt S Trout wrote:
Call me a little confused, I am not sure that I properly grasp which one
to use for FormBuilder. For the moment, I am simply going to focus on
the plugin (C::P::FB).
Don't. The plugin's obsolete, undeveloped and has known interoperability
issues.
Incidentally, I wrote
Le 2 janv. 07 à 20:17, Jonathan Rockway a écrit :
Matt S Trout wrote:
Call me a little confused, I am not sure that I properly grasp
which one
to use for FormBuilder. For the moment, I am simply going to
focus on
the plugin (C::P::FB).
Don't. The plugin's obsolete, undeveloped and has
catalyst@lists.rawmode.org
Sent: Tuesday, January 02, 2007 7:47 PM
Subject: Re: [Catalyst] IMPORTANT: Catalyst::Plugin::FormBuilder obsoleted
by::Controller::FormBuilder
On 31 Dec 2006, at 03:29, Joe Landman wrote:
From my previous email on C::P::FormBuilder until now, I have been
reading
On 1/2/07, Octavian Rasnita [EMAIL PROTECTED] wrote:
Oh, too bad. I have tried installing it under Windows, but I couldn't.
It requires Test::WWW::Mechanize::Catalyst. I have installed this module
using ppm, but if I run it, it breaks with the error telling that
Test::WWW::Mechanize is required
On 1/2/07, Joe Landman [EMAIL PROTECTED] wrote:
Should we subclass C::C::FB, or put our forms within it? Curious as
to the way you recommend using it.
Create a base controller that sub-classes it and have your individual
controllers inherit from your base.
On 1/2/07, David Morel [EMAIL PROTECTED] wrote:
Le 3 janv. 07 à 00:29, Nilson Santos Figueiredo Junior a écrit :
On 1/2/07, Jonathan Rockway [EMAIL PROTECTED] wrote:
Incidentally, I wrote the chapter of my book on FormBuilder the day
before the Controller was released :) However, updating
15 matches
Mail list logo
