* On Sun, May 11 2008, Ashley wrote:
On May 10, 2008, at 7:18 PM, Kieren Diment wrote:
On 11 May 2008, at 10:56, Ashley wrote:
Two or more config examples is nice and kind to users and I think
it's a great best practice to include it (maybe someone would
attach a simple script to dump
On 11 May 2008, at 16:55, Jonathan Rockway wrote:
You seem upset that we're ditching YAML. Don't be. The defaults are
designed for people that don't know how to change the defaults. You
already know how to use YAML, so use it and forget what everyone else
thinks. Config::General is not
* On Sun, May 11 2008, Andrew wrote:
And I'm doing everything exactly as the book states except the config change
of putting the database path in the YAML file - it's still in the
AddressDB.pm file.
I looked in the DBIC.pm file which is generating the error message and the
method that is
* On Sun, May 11 2008, Andreas Marienborg wrote:
On May 11, 2008, at 7:14 AM, Andrew wrote:
And I'm doing everything exactly as the book states except the
config change of putting the database path in the YAML file - it's
still in the AddressDB.pm file.
I looked in the DBIC.pm file which is
Greetings all,
I am developing a program called CatalystX::Installer that will
simplify the installation and setup of Catalyst applications.
I was thinking about what the default options should be for
CatalystX::Installer and am wondering what people want. Basically, I
was thinking that they
On 10 May 2008, at 15:26, Aristotle Pagaltzis wrote:
* Tomas Doran [EMAIL PROTECTED] [2008-05-10 09:25]:
If I was to hack some code (and tests) up which supported my
originally suggested syntax ( Chained('sub1', 'sub2') for
joining chains), what would anyone feel about it?
You could no
* Tomas Doran [EMAIL PROTECTED] [2008-05-11 10:05]:
However, this does mean I now have 3 packages (a base class,
and two controllers), where before I had one file..
There’s nothing stopping you from putting them all in a single
file. :-)
(as, lets face it - splitting my code into 3 packages
Greetings all,
I am developing a program called CatalystX::Installer that will
simplify the installation and setup of Catalyst applications.
I was thinking about what the default options should be for
CatalystX::Installer and am wondering what people want. Basically, I
was thinking that they
2008/5/10 Daniel McBrearty [EMAIL PROTECTED]:
I'd like Leon's opinion on this. Forwarding to him again.
I understand many bits of it but have given up trying to get it
working. I would love a patch which passes tests on both old and new
lib-www-perls.
Leon
On 11 May 2008, at 15:18, Matt S Trout wrote:
On Sun, May 11, 2008 at 10:01:47AM +0100, Tomas Doran wrote:
Aha! I had a feeling the reason that someone didn't do that already
is that there was a compelling reason to not do so - I just hadn't
thought about it hard enough..
That's a
Hi Mitch,
You have some interesting ideas; thank you for your input.
CatalystX::Installer is mainly designed to help deploy an already
written project to a server for use. Here is a link to the full
description of my current plan:
* On Mon, May 12 2008, Mitch Jackson wrote:
Paul,
Is CatalystX::Installer going to be used to help initally create a
project, or help deploy a project that is already written to a server
for use? If it is for helping deploy a project to a server, there's a
few things I think would be
Found and solved an interesting little bug in someone else's application today.
Their unit tests ran fine, but the application itself always died instantly,
with an error from Class::C3::XS.. so they thought the bug was in DBIx::Class,
or rather their use of it, and we spent a lot of time hunting
13 matches
Mail list logo
