Hi!
On Mon, Jan 21, 2008 at 09:20:54PM -0800, Robert Krimen wrote:
On Jan 20, 2008 7:59 PM, Matt S Trout [EMAIL PROTECTED] wrote:
You seem to be using an 'assets' config key; please change this to
'Plugin::Assets' and deprecate the old one. We're currently moving the
'core'
plugins over
On Jan 31, 2008 11:24 AM, Thomas Klausner [EMAIL PROTECTED] wrote:
Hi!
Currently, Catalyst::Plugin::Assets is not available from CPAN anymore.
Is there a reason for this? Or is it some CPAN hickup?
It's still on BackPAN, BTW:
On Jan 20, 2008 7:59 PM, Matt S Trout [EMAIL PROTECTED] wrote:
You seem to be using an 'assets' config key; please change this to
'Plugin::Assets' and deprecate the old one. We're currently moving the 'core'
plugins over to this standard so you should make the change as soon as
possible to
On Sun, Jan 13, 2008 at 09:27:55PM -0800, Robert Krimen wrote:
Catalyst::Plugin::Assets
http://search.cpan.org/~rkrimen/Catalyst-Plugin-Assets-0.012/
You seem to be using an 'assets' config key; please change this to
'Plugin::Assets' and deprecate the old one. We're currently moving the 'core'
On Sun, Jan 13, 2008 at 09:27:55PM -0800, Robert Krimen wrote:
Catalyst::Plugin::Assets
http://search.cpan.org/~rkrimen/Catalyst-Plugin-Assets-0.012/
Managing .css and .js inclusions has been a recurring problem of mine;
I usually hack something together with Template Toolkit and call it
On Jan 14, 2008 6:35 AM, Bill Moseley [EMAIL PROTECTED] wrote:
I tend to specify the assets in the templates where they are used
instead of in the controller as it's a presentation issue. I don't
see why your Plugin could not do the same thing by using WRAPPERs.
You can certainly do this,
