Re: [Catalyst] [ANNOUNCE] New plugin: Catalyst::Plugin::Assets
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 to this standard so you should make the change as soon as
possible to avoid getting live users with the wrong config key.
Okay, I've gone ahead and made this change. The new version, with new
config key preference and warning message, should be available on CPAN
shortly.
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:
http://backpan.cpan.org/authors/id/R/RK/RKRIMEN/Catalyst-Plugin-Assets-0.020.tar.gz
But if it won't be continued, I'd rather not use it :-)
--
#!/usr/bin/perl http://domm.plix.at
for(ref bless{},just'another'perl'hacker){s-:+-$-gprint$_.$/}
___
List: Catalyst@lists.scsys.co.uk
Listinfo: http://lists.scsys.co.uk/cgi-bin/mailman/listinfo/catalyst
Searchable archive: http://www.mail-archive.com/catalyst@lists.scsys.co.uk/
Dev site: http://dev.catalyst.perl.org/
Re: [Catalyst] [ANNOUNCE] New plugin: Catalyst::Plugin::Assets
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: http://backpan.cpan.org/authors/id/R/RK/RKRIMEN/Catalyst-Plugin-Assets-0.020.tar.gz But if it won't be continued, I'd rather not use it :-) Hi, 0.021 is being processed as this e-mail goes out. Yes, C::P::Assets will continue, I'm not exactly sure why it disappeared, but it's probably because an upload to PAUSE didn't take (for some reason). Thanks for pointing this out. Rob ___ List: Catalyst@lists.scsys.co.uk Listinfo: http://lists.scsys.co.uk/cgi-bin/mailman/listinfo/catalyst Searchable archive: http://www.mail-archive.com/catalyst@lists.scsys.co.uk/ Dev site: http://dev.catalyst.perl.org/
Re: [Catalyst] [ANNOUNCE] New plugin: Catalyst::Plugin::Assets
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 avoid getting live users with the wrong config key. Okay, I've gone ahead and made this change. The new version, with new config key preference and warning message, should be available on CPAN shortly. -- Rob ___ List: Catalyst@lists.scsys.co.uk Listinfo: http://lists.scsys.co.uk/cgi-bin/mailman/listinfo/catalyst Searchable archive: http://www.mail-archive.com/catalyst@lists.scsys.co.uk/ Dev site: http://dev.catalyst.perl.org/
Re: [Catalyst] [ANNOUNCE] New plugin: Catalyst::Plugin::Assets
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' plugins over to this standard so you should make the change as soon as possible to avoid getting live users with the wrong config key. -- Matt S Trout Need help with your Catalyst or DBIx::Class project? Technical Directorhttp://www.shadowcat.co.uk/catalyst/ Shadowcat Systems Ltd. Want a managed development or deployment platform? http://chainsawblues.vox.com/http://www.shadowcat.co.uk/servers/ ___ List: Catalyst@lists.scsys.co.uk Listinfo: http://lists.scsys.co.uk/cgi-bin/mailman/listinfo/catalyst Searchable archive: http://www.mail-archive.com/catalyst@lists.scsys.co.uk/ Dev site: http://dev.catalyst.perl.org/
Re: [Catalyst] [ANNOUNCE] New plugin: Catalyst::Plugin::Assets
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 day. Copying and pasting was becoming bothersome, though, so I decided to write up a utility to help. 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. Is it possible to define print, screen, etc. when specifying css? C::P::Assets also makes switching between minified and development versions of .css and .js files really quick and easy (with support for YUI compressor, JavaScript::Minifier, CSS::Minifier) Do you cache this? Another issue is that in development we might have many individual js files, but in production would want only a few minified files loaded from a different location. The thinking is that we will only have a few asset files for the entire application (front-loading the assets on the first request with very long expires). This is implemented via the application config which groups js into sections that are combined in production. Another approach is use a single js file in the application and in development have it point to a js file that loads all the other individual js files, and in production have it load a single minified version. -- Bill Moseley [EMAIL PROTECTED] ___ List: Catalyst@lists.scsys.co.uk Listinfo: http://lists.scsys.co.uk/cgi-bin/mailman/listinfo/catalyst Searchable archive: http://www.mail-archive.com/catalyst@lists.scsys.co.uk/ Dev site: http://dev.catalyst.perl.org/
Re: [Catalyst] [ANNOUNCE] New plugin: Catalyst::Plugin::Assets
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, and I do it as well. Right now I have an assets.tt that bundles the different assets into blocks (core web site, testing, ajax), and include the appropiate block depending on the page (and have a default in case none were specified). Is it possible to define print, screen, etc. when specifying css? Unfortunately not yet, although this is something I've been thinking about. Do you cache this? Yes, built/minified files are cached and not rebuilt unless the file mtime changes. -- Rob ___ List: Catalyst@lists.scsys.co.uk Listinfo: http://lists.scsys.co.uk/cgi-bin/mailman/listinfo/catalyst Searchable archive: http://www.mail-archive.com/catalyst@lists.scsys.co.uk/ Dev site: http://dev.catalyst.perl.org/
