Re: [Radiant] [ANN] SnS Minifier
On Mon, Jul 7, 2008 at 1:30 AM, Chris Parrish [EMAIL PROTECTED] wrote: You will need the Styles 'n Scripts extension installed for this to work and you will also probably need to change your project's environment.rb file to twiddle the load order (the SnS Extension must be loaded before this one). For example, you could use something like: config.extensions = [ :all, :sns_minifier ] I think extensions are loaded in alphabetical order unless otherwise specified by config.extensions. If you rename this extension to styles_n_scripts_minifier (or rename styles_n_scripts to sns), you won't need the change in environment.rb. I was poking around in the SVN repo last night and spotted these new extensions. They look great! -- Tim Gossett ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] [ANN] SnS Minifier
I got the following error for /admin/css/new: undefined method `minify' for #Stylesheet:0x2756ac8 (I'm on OS X 10.5, Rails 2.1, Radiant 0.6.7 using SQLite3) When I rake db:extensions:sns_minifier:migrate, the add_column never gets executed. I renamed sns_minifier/lib/tasks/minify_extension_tasks.rake to sns_minifier/lib/tasks/sns_minifier_extension_tasks.rake and remigrated (migrate VERSION=0 then migrate), and it was fixed. I am now enjoying SASS-filtered, minified stylesheets. Thanks a bunch, Chris! -- Tim Gossett ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] [ANN] SnS Minifier
New release! You can find v0.1.1 at: https://secure.svnrepository.com/s_swanki/open/radiant/extensions/sns_minifier/tags/latest Thanks to Tim who found this naming issue (see below). What can I say - it was getting late. -Chris Tim Gossett wrote: I got the following error for /admin/css/new: undefined method `minify' for #Stylesheet:0x2756ac8 (I'm on OS X 10.5, Rails 2.1, Radiant 0.6.7 using SQLite3) When I rake db:extensions:sns_minifier:migrate, the add_column never gets executed. I renamed sns_minifier/lib/tasks/minify_extension_tasks.rake to sns_minifier/lib/tasks/sns_minifier_extension_tasks.rake and remigrated (migrate VERSION=0 then migrate), and it was fixed. I am now enjoying SASS-filtered, minified stylesheets. Thanks a bunch, Chris! -- Tim Gossett ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] [ANN] SnS Minifier
Tim Gossett wrote: On Mon, Jul 7, 2008 at 1:30 AM, Chris Parrish [EMAIL PROTECTED] wrote: You will need the Styles 'n Scripts extension installed for this to work and you will also probably need to change your project's environment.rb file to twiddle the load order (the SnS Extension must be loaded before this one). For example, you could use something like: config.extensions = [ :all, :sns_minifier ] I think extensions are loaded in alphabetical order unless otherwise specified by config.extensions. If you rename this extension to styles_n_scripts_minifier (or rename styles_n_scripts to sns), you won't need the change in environment.rb. I was poking around in the SVN repo last night and spotted these new extensions. They look great! Tim, you're right about the load order thing. I had debated naming the new extensions styles_n_scripts_xxx but I've decided that carpal tunnel syndrome just is not for me. But I hadn't considered renaming the whole extension to sns though. I think I like that idea for several reasons. However, it would require users to physically change something on their servers -- not just update from svn. You would have to change from: /vendor/extensions/styles_n_scripts to: /vendor/extensions/sns Would anyone be opposed to my renaming the extension like this? -Chris P.S. Just to be clear, I'd only be renaming files and their related code. Oh, and rake tasks would now be rake radiant:extensions:sns But otherwise everything would be *identical* to your users (even the extension name in the Admin panel would still show Styles 'n Scripts). ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] [ANN] SnS Minifier
On Mon, Jul 7, 2008 at 11:02 AM, Chris Parrish [EMAIL PROTECTED] wrote: Tim, you're right about the load order thing. I had debated naming the new extensions styles_n_scripts_xxx but I've decided that carpal tunnel syndrome just is not for me. But I hadn't considered renaming the whole extension to sns though. I think I like that idea for several reasons. However, it would require users to physically change something on their servers -- not just update from svn. You would have to change from: /vendor/extensions/styles_n_scripts to: /vendor/extensions/sns Would anyone be opposed to my renaming the extension like this? -Chris P.S. Just to be clear, I'd only be renaming files and their related code. Oh, and rake tasks would now be rake radiant:extensions:sns But otherwise everything would be *identical* to your users (even the extension name in the Admin panel would still show Styles 'n Scripts). I think renaming the whole thing to SnS would be in-line with your preference against carpal tunnel syndrome :) None of the models would be renamed (right?), so users should be able to swap out the existing extension directory for a renamed one and get off without a hitch. If I had a few spare moments, I'd try it for myself right now... maybe there'd be a clash with the version number in the extension_meta table, and maybe there wouldn't because it's listed as Styles 'n Scripts. -- Tim Gossett ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] [ANN] SnS Minifier
Tim Gossett wrote: None of the models would be renamed (right?), so users should be able to swap out the existing extension directory for a renamed one and get off without a hitch. If I had a few spare moments, I'd try it for myself right now... maybe there'd be a clash with the version number in the extension_meta table, and maybe there wouldn't because it's listed as Styles 'n Scripts. No, I can keep the Styles 'n Scripts name in the meta table and in the Admin-Extensions page. So all that would be needed is for the user to update to the latest version of SnS and to change the styles_n_scripts folder name to sns. (Or change the /vendor/extensions folder's properties if using svn:externals). But for me it does require renaming all the rake tasks, the xx_extension.rb file, and probably something else I'm not thinking of. I'd also probably change StylesNScripts::Config to SnS::Config (and there would be a *bunch* of references to that that would need to change accordingly). Not strictly necessary but something I'd want. -Chris ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] Shared Layouts
Sean Cribbs wrote: Since there seems to be some confusion about how to use share_layouts lately, I'll break it down into steps for you and everyone. Thanks a lot, Sean for this post and the article on the wiki. I shall definitely try this in the next few days, and make modifications to the wiki, if needed. Best wishes Mohit. ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] apachecon running on radiant
On Mon, Jul 7, 2008 at 12:37 PM, J Aaron Farr [EMAIL PROTECTED] wrote: FWIW the new ApacheCon websites are now running on Radiant: http://us.apachecon.com The source code will be available under an Apache license Really Soon Now. We wrote up a custom extension for managing the conference schedule, sessions and speakers. A full Call For Papers submission system should be done by the end of the summer. Any chance I could get a look at that? As announced a couple of weeks ago, I'm working on something similar: http://gitorious.org/projects/ba http://lists.radiantcms.org/pipermail/radiant/2008-June/009288.html We'll be using it for a 500-attendees conference with about 100 lightning talks in october: http://smidig2008.no/ It would be great to join efforts on these extensions. Cheers, Aslak -- J Aaron Farr jadetower.com[US] +1 724-964-4515 馮傑仁 cubiclemuses.com [HK] +852 8123-7905 ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] apachecon running on radiant
aslak hellesoy [EMAIL PROTECTED] writes: On Mon, Jul 7, 2008 at 12:37 PM, J Aaron Farr [EMAIL PROTECTED] wrote: FWIW the new ApacheCon websites are now running on Radiant: http://us.apachecon.com The source code will be available under an Apache license Really Soon Now. We wrote up a custom extension for managing the conference schedule, sessions and speakers. A full Call For Papers submission system should be done by the end of the summer. Any chance I could get a look at that? As announced a couple of weeks ago, I'm working on something similar: I'm sorry I haven't been keeping up to date on the mailing list. Wish I had seen that earlier. It would be great to join efforts on these extensions. Absolutely. Give me about 24 hours or so and I'll have the code somewhere for you to look at. Ultimately I'd like to have it at Apache, but I have few steps to go before it will be there. Until then, I can get it in github or a svn repo. -- J Aaron Farr jadetower.com[US] +1 724-964-4515 馮傑仁 cubiclemuses.com [HK] +852 8123-7905 ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] if_content with inherit
On Mon, Jul 7, 2008 at 3:56 PM, Jim Gay [EMAIL PROTECTED] wrote: Is there any interest in adding the inherit attribute to the if_content tag? In some instances I'll find the need to output something like div id=extras r:content part=extras inherit=true / /div But I don't have a way to conditionally render the div id=extras bit. If the parent or current page has an extras part, then it will appear, but if it doesn't I'll have an empty div element. Is there a simple way to handle this or would r:if_content inherit=true be a clear and welcomed addition? -Jim I'm for it. -- Tim Gossett ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] if_content with inherit
There are few things that make me more grumpy that empty elements that server no useful purpose. I'd love it. On 7-Jul-08, at 12:56 PM, Jim Gay wrote: Is there any interest in adding the inherit attribute to the if_content tag? In some instances I'll find the need to output something like div id=extras r:content part=extras inherit=true / /div But I don't have a way to conditionally render the div id=extras bit. If the parent or current page has an extras part, then it will appear, but if it doesn't I'll have an empty div element. Is there a simple way to handle this or would r:if_content inherit=true be a clear and welcomed addition? -Jim ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
[Radiant] Re: page_attachments on non-normal page types
The solution turns out to be just editing environment.rb config.extensions = [ :page_attachments, :all ] or if you're still 0.6.7 config.extensions = [ :shards, :page_attachments, :all ] and restart of course. On 2008/07/01, at 21:38, john muhl wrote: Is there an easy way to get page_attachments working with other page types, like the File Not Found or Archive types? thanks ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
