On Mon, Aug 24, 2009 at 3:51 PM, Matthias Dietrich mdietr...@cpan.orgwrote:
Hi Chris,
Am 24.08.2009 um 04:43 schrieb Chris:
Can you use catalyst::plugin::cache as the backend for the lexicon?
Then refreshing the texts involves clearing the cache, and updates are
transparent.
I took a
I am lobbying for the exclusive use of Catalyst as the development tool
of choice, and therefore Perl as the preferred language in our small
software company. Having researched Catalyst and having gone through
every tutorial I can get my hands on, I have a basic understanding of
the
Steve wrote:
I am lobbying for the exclusive use of Catalyst as the development tool
of choice, and therefore Perl as the preferred language in our small
software company. Having researched Catalyst and having gone through
every tutorial I can get my hands on, I have a basic understanding
Hi Wade,
Am 25.08.2009 um 13:48 schrieb Wade Stuart:
Why cant you just do a:
# ... incrementally add new lexicons
Locale::Maketext::Lexicon-import({
de = [Gettext = 'local/hello/de.po'],
})
... on change instead of reloading apache?
because this would only affect the current
Hi Chris,
Am 25.08.2009 um 00:48 schrieb Chris:
I wonder if you could force a reload using a SIG{USR1} handler and
avoid
a per-request check?
I think so, but I need to know the processes to send the signal to. I
guess $$ is only the current apache client process and a signal to
this
To be more specific, something like AutoCRUD, mixed in with some CSS
would be a huge plus, as the UI is the biggest obstacle. Business
logic, database design are strengths. In the past we have used a
PHP-based product called ATK which comes with 'themes'. I'm looking for
something similar,
For those of you who've had the pleasure of working with git you
may have come across gitweb, the web front end to a given set of git
repositories. It is bundled with the git source[1] as gitweb.perl and
gets munged into gitweb.cgi after make runs through it. With gitweb.cgi
you have one
Hi,
I've seen some Catalyst sample modules that use use base and some others
that use use parent.
I know that the recommendation could be to use Moose and extends..., but
if Moose is not needed, what's the difference between use parent and use
base?
When should be use parent be used and
I know that the recommendation could be to use Moose and extends..., but
if Moose is not needed, what's the difference between use parent and use
base?
per base.pm
Unless you are using the fields pragma, consider this module discouraged in
favor of the lighter-weight parent.
per
Thanks for posting this to the list, Dan. I have been thinking of the
same type of project recently. I am glad this is a Github project as
well. ;)
Best Regards,
Stephen Sykes
[http://catalystsites.org]
Dan Brook wrote:
For those of you who've had the pleasure of working with git you
may have
On Tue, Aug 25, 2009 at 11:55 AM, Evan Carroll li...@evancarroll.comwrote:
When should be use parent be used and not use base or it really
doesn't matter which one is used?
parent.pm when you can use cpan, base.pm when you can't.
If it's a Moose class should you always use extends over
Hello subscribers,
On some pages I need to re-check user password (to be more concrete -
each time when user change any settings on user settings page). I
can't compare passwords directly (something like: $form-{password} eq
$c-user-password()), because in DB I have only hashed passwords.
Seems
Oleg Kostyuk wrote:
Hello subscribers,
On some pages I need to re-check user password (to be more concrete -
each time when user change any settings on user settings page). I
can't compare passwords directly (something like: $form-{password} eq
$c-user-password()), because in DB I have only
Hello,
Problem:
Can't call method flatten on unblessed reference at
/nfs/local_perl/perllib/Catalyst/Helper/Model/DBIC/Schema.pm line 165.
Preamble:
I was following the catalyst tutorial in a Debian etch, and when tried
in tutorial_03 Create Static DBIx::Class Schema Files I had an error
with
ccing in -dev, as this is relevant there, and and contains a brain
dump :_)
If it's a Moose class should you always use extends over both?
Yep.
Hum, the CatalystAndMoose manual doesn't even show the application
base class inheriting:
Oleg Kostyuk wrote:
Hello subscribers,
On some pages I need to re-check user password (to be more concrete -
each time when user change any settings on user settings page). I
can't compare passwords directly (something like: $form-{password} eq
$c-user-password()), because in DB I have only
On 26 Aug 2009, at 00:58, pablo marin-garcia wrote:
Hello,
Problem:
Can't call method flatten on unblessed reference at
/nfs/local_perl/perllib/Catalyst/Helper/Model/DBIC/Schema.pm line 165.
Your Moose::Autobox, or autobox modules are busted. At a guess, the
latter, but it could be
On 25 Aug 2009, at 16:57, Matthias Dietrich wrote:
Hi Wade,
Am 25.08.2009 um 13:48 schrieb Wade Stuart:
Why cant you just do a:
# ... incrementally add new lexicons
Locale::Maketext::Lexicon-import({
de = [Gettext = 'local/hello/de.po'],
})
... on change instead of reloading
On 26 Aug 2009, at 00:50, Matt Whipple wrote:
Seems that I can try to authenticate user again, by calling
$c-authenticate(name=$c-user-name, pass=$form-{password}),
but I
concerned is this acceptable - calling authenticate, when user is
already authenticated. And what will be if provided
19 matches
Mail list logo