Re: [Radiant] Re: Re: [Radiant-Dev] [ANN] Styles 'n Scripts Extension
Sean Cribbs wrote: Chris, We might be able to make a rake task that loads the environment with no extensions installed. In fact, it should be as easy as something like this: task :minimal_environment do Radiant::Initializer.run do |config| config.extensions = [] end end Then we could make db:bootstrap and anything else that needs to prevent extensions from loading depend on that instead of the default :environment task. Sean I tried the idea above (added it to my extension -- not Radiant) and set up my extension's tasks like: task :migrate = :minimal_environment do ... I got an error that the constant StylesNScripts wasn't defined (at least that's what I remembered). I probably just did something wrong here but I wanted to post the result as an FYI. -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] Re: Re: [Radiant-Dev] [ANN] Styles 'n Scripts Extension
For anyone (now or in the future) following this thread, I've identified the issue nurullah mentioned here. It is indeed a bug with the SnS extension and will be resolved in the upcoming 0.5 release. For those interested, it's caused by the interplay between the way SnS extension stores its settings, and the way Radiant rake tasks are performed. SnS creates its default settings and then overwrites those with any custom settings during initialize. Well, it turns out that extensions are initialized during any Rake task -- including 'rake db:bootstrap' So, if you're including SnS in a *brand new* installation of Radiant (not already bootstrapped), when you try to create the database, the SnS extension gets initialized and tries to store some settings in the not-yet-created config table. Doh! Those adding SnS to an existing Radiant install will never see this issue. -Chris nurullah wrote: although all installation steps fail it adds tabs on panels and some columns on config table 5|stylesheet_mime_type|text/css 6|response_cache_directory|text_asset_cache 7|javascript_mime_type|text/javascript 8|javascript_directory|js 9|stylesheet_directory|css but you are right production.log says it cannot find text_assets table and right there is no such table on db file On 5/19/08, Chris Parrish [EMAIL PROTECTED] wrote: The Styles 'n Scripts extension makes use of Radiant's built-in Radiant::Config settings (which get stored in the config table). So this sound like a Radiant setup issue. (The only table my extension adds is text_assets). Remove my extension (all extensions, really) and make sure that your plain-vanilla Radiant extension has this table created (should have been created when you ran: rake db:bootstrap (or rake production db:bootstrap if running in production mode). -Chris Arik Jones wrote: I think this is a fault of Radiant. Could be wrong. nurullah wrote: I could get it run on a clean install (0.6.7) tho, with sqlite3 and no other extension installed it gives Could not find table 'config' error On 5/18/08, Chris Parrish [EMAIL PROTECTED] ___ 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 mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] Re: Re: [Radiant-Dev] [ANN] Styles 'n Scripts Extension
What was the fix for SnS? I saw the same problem with RBAC Base on a clean install (which I must not have tried when we created it) and haven't had time to look into it. -Jim On Jun 15, 2008, at 9:19 AM, Chris Parrish wrote: For anyone (now or in the future) following this thread, I've identified the issue nurullah mentioned here. It is indeed a bug with the SnS extension and will be resolved in the upcoming 0.5 release. For those interested, it's caused by the interplay between the way SnS extension stores its settings, and the way Radiant rake tasks are performed. SnS creates its default settings and then overwrites those with any custom settings during initialize. Well, it turns out that extensions are initialized during any Rake task -- including 'rake db:bootstrap' So, if you're including SnS in a *brand new* installation of Radiant (not already bootstrapped), when you try to create the database, the SnS extension gets initialized and tries to store some settings in the not-yet-created config table. Doh! Those adding SnS to an existing Radiant install will never see this issue. -Chris nurullah wrote: although all installation steps fail it adds tabs on panels and some columns on config table 5|stylesheet_mime_type|text/css 6|response_cache_directory|text_asset_cache 7|javascript_mime_type|text/javascript 8|javascript_directory|js 9|stylesheet_directory|css but you are right production.log says it cannot find text_assets table and right there is no such table on db file On 5/19/08, Chris Parrish [EMAIL PROTECTED] wrote: The Styles 'n Scripts extension makes use of Radiant's built-in Radiant::Config settings (which get stored in the config table). So this sound like a Radiant setup issue. (The only table my extension adds is text_assets). Remove my extension (all extensions, really) and make sure that your plain-vanilla Radiant extension has this table created (should have been created when you ran: rake db:bootstrap (or rake production db:bootstrap if running in production mode). -Chris Arik Jones wrote: I think this is a fault of Radiant. Could be wrong. nurullah wrote: I could get it run on a clean install (0.6.7) tho, with sqlite3 and no other extension installed it gives Could not find table 'config' error On 5/18/08, Chris Parrish [EMAIL PROTECTED] ___ 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 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] Re: Re: [Radiant-Dev] [ANN] Styles 'n Scripts Extension
Chris, We might be able to make a rake task that loads the environment with no extensions installed. In fact, it should be as easy as something like this: task :minimal_environment do Radiant::Initializer.run do |config| config.extensions = [] end end Then we could make db:bootstrap and anything else that needs to prevent extensions from loading depend on that instead of the default :environment task. Sean Chris Parrish wrote: For anyone (now or in the future) following this thread, I've identified the issue nurullah mentioned here. It is indeed a bug with the SnS extension and will be resolved in the upcoming 0.5 release. For those interested, it's caused by the interplay between the way SnS extension stores its settings, and the way Radiant rake tasks are performed. SnS creates its default settings and then overwrites those with any custom settings during initialize. Well, it turns out that extensions are initialized during any Rake task -- including 'rake db:bootstrap' So, if you're including SnS in a *brand new* installation of Radiant (not already bootstrapped), when you try to create the database, the SnS extension gets initialized and tries to store some settings in the not-yet-created config table. Doh! Those adding SnS to an existing Radiant install will never see this issue. -Chris nurullah wrote: although all installation steps fail it adds tabs on panels and some columns on config table 5|stylesheet_mime_type|text/css 6|response_cache_directory|text_asset_cache 7|javascript_mime_type|text/javascript 8|javascript_directory|js 9|stylesheet_directory|css but you are right production.log says it cannot find text_assets table and right there is no such table on db file On 5/19/08, Chris Parrish [EMAIL PROTECTED] wrote: The Styles 'n Scripts extension makes use of Radiant's built-in Radiant::Config settings (which get stored in the config table). So this sound like a Radiant setup issue. (The only table my extension adds is text_assets). Remove my extension (all extensions, really) and make sure that your plain-vanilla Radiant extension has this table created (should have been created when you ran: rake db:bootstrap (or rake production db:bootstrap if running in production mode). -Chris Arik Jones wrote: I think this is a fault of Radiant. Could be wrong. nurullah wrote: I could get it run on a clean install (0.6.7) tho, with sqlite3 and no other extension installed it gives Could not find table 'config' error On 5/18/08, Chris Parrish [EMAIL PROTECTED] ___ 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 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] Re: Re: [Radiant-Dev] [ANN] Styles 'n Scripts Extension
I'm not opposed to your solution in anyway. I think it'd be helpful. I just think that the right solution for my extension would be to: * have my extension's default settings installed via the initial migrate task * offer a rake task to allow administrators (server admins) to change the css/js settings on the fly. This need only be run once manually (after bootstrap) and not at every init. I'd probably throw in a restore_defaults task too. I designed the StylesNScripts::Config bit with the future UI designs of Radiant in mind -- for the day when we'll have a settings/configuration admin panel where extensions can add into the Radiant UI (instead of sticking settings in some tab or hard coded and loaded at init). My problem is that I broke this rule and made the settings load during init just for now and shot myself in the foot. If I do what I've outlined above, it'll be trivial to hook into Radiant's shiny new settings UI when it arrives -Chris Sean Cribbs wrote: Chris, We might be able to make a rake task that loads the environment with no extensions installed. In fact, it should be as easy as something like this: task :minimal_environment do Radiant::Initializer.run do |config| config.extensions = [] end end Then we could make db:bootstrap and anything else that needs to prevent extensions from loading depend on that instead of the default :environment task. Sean Chris Parrish wrote: For anyone (now or in the future) following this thread, I've identified the issue nurullah mentioned here. It is indeed a bug with the SnS extension and will be resolved in the upcoming 0.5 release. For those interested, it's caused by the interplay between the way SnS extension stores its settings, and the way Radiant rake tasks are performed. SnS creates its default settings and then overwrites those with any custom settings during initialize. Well, it turns out that extensions are initialized during any Rake task -- including 'rake db:bootstrap' So, if you're including SnS in a *brand new* installation of Radiant (not already bootstrapped), when you try to create the database, the SnS extension gets initialized and tries to store some settings in the not-yet-created config table. Doh! Those adding SnS to an existing Radiant install will never see this issue. -Chris nurullah wrote: although all installation steps fail it adds tabs on panels and some columns on config table 5|stylesheet_mime_type|text/css 6|response_cache_directory|text_asset_cache 7|javascript_mime_type|text/javascript 8|javascript_directory|js 9|stylesheet_directory|css but you are right production.log says it cannot find text_assets table and right there is no such table on db file On 5/19/08, Chris Parrish [EMAIL PROTECTED] wrote: The Styles 'n Scripts extension makes use of Radiant's built-in Radiant::Config settings (which get stored in the config table). So this sound like a Radiant setup issue. (The only table my extension adds is text_assets). Remove my extension (all extensions, really) and make sure that your plain-vanilla Radiant extension has this table created (should have been created when you ran: rake db:bootstrap (or rake production db:bootstrap if running in production mode). -Chris Arik Jones wrote: I think this is a fault of Radiant. Could be wrong. nurullah wrote: I could get it run on a clean install (0.6.7) tho, with sqlite3 and no other extension installed it gives Could not find table 'config' error On 5/18/08, Chris Parrish [EMAIL PROTECTED] ___ 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 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 mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] Re: Re: [Radiant-Dev] [ANN] Styles 'n Scripts Extension
I just outlined the fix in a reply to Sean's post. It's a little more elaborate (though I think more elegant) than I'd post here. If you're trying to get it to just work for now you can simply comment out the following line from the styles_n_scripts_extension.rb file: include CustomSettings Run your rake db:bootstrap to create the database, then un-comment that line back in. -Chris Jim Gay wrote: What was the fix for SnS? I saw the same problem with RBAC Base on a clean install (which I must not have tried when we created it) and haven't had time to look into it. -Jim ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] Re: Re: [Radiant-Dev] [ANN] Styles 'n Scripts Extension
Anton Aylward wrote: My gripe is about the packaging. I unpacked v0.3 into /vendor/extensions/styles_n_scripts/ and got: Could not load extension from file: v0.3_extension. #NameError: V0.3Extension is not a valid constant name! As far as I could make out, v0.3 wanted to be installed in /vendor/extensions/v0.3 Hmm, that sounds like something didn't unpack to the right location (I'd guess an SVN thing, actually). Once you checkout the project, make sure that inside your /radiant_project/vendor/extensions folder you have the following: /styles_n_scripts /app /config /db /lib /public /spec CHANGELOG custom_settings.rb LICENSE Rakefile README styles_n_scripts_extension Also, if you're using Radiant 0.6.7, I've released a v0.3.1 yesterday with some minor tweaks. Let me know if you're still having issues with this. I certainly welcome any ideas/suggestions here. Its a fairly straightforward design but nothing's set in stone. Are you going to subsume attachments ? I think, long term, John would like an application that has a built-in solution for images, css, and js. In the meantime, I don't think I have that kind of authority to overthrow other extensions... Wrings hands... And after this one falls, boys, we're going to conquer and assimilate the CopyMove extension, mwaa haa ha! -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] Re: Re: [Radiant-Dev] [ANN] Styles 'n Scripts Extension
good work, i appreciate your effort. i dont know pitfalls.. but it would be better if we could throw csses and javascripts between head tags no matter where they are called from.. secondly, looks like there is almost no difference between inline and other way.. in inline mode it adds html comment tags other way just include the way i write it if i dont add script / tags it just dumps everything to the page. it must wrap codes if there is no header tag On 5/28/08, Steven Southard [EMAIL PROTECTED] wrote: I must admit that assets that don't happen to include images is a bit long. I kind of like text assets. That kind of opens it up to include other types of files that people may want to put there like .xml or maybe even a .as file. One thing that would be nice about putting them together is that you could then make use of a file type combo box. That would fill out the page a bit and give a person a little more to do. Also those lovely icons would have a chance to help you sort out your file types. -Steven On May 27, 2008, at 8:50 PM, Chris Parrish wrote: Thanks for the feedback Steven. I'm really interested in making this a usable extension for all. I always used pages for my js and css files too and, like you, never had more than a handful of each -- it wasn't much of a bother to do. So, when John first mentioned the idea to me I really only saw one or two valid reasons for such an extension (for instance, I found it difficult to explain to users why they had to create a blank layout for a stylesheet just to set the content-type). Now that I've been working on it, I see *many* good reasons to go this route (my current favorite is the server and browser caching benefits -- I *love* the idea of not having to expire and reserve all stylesheets and javascripts every 5 minutes). As to the multiple tabs, yeah, I'm with you. Originally I think John envisioned something like an Assets tab where CSS, JS and image files could all reside but Radiant hasn't settled on an image asset approach just yet. And without images, what do you call the tab -- Text Assets? CSS JS? Assets-That-Don't-Happen-To-Include-Images? Actually, my original mock-up for this extension had one tab (called Files) but I still kind of choked on that vague name. Anyway, for now, John just suggested keeping two tabs and waiting to see how things progressed. In the interest of minimizing tab space, I did choose to name them CSS and JS instead of Stylesheets and Javascripts. Plus, your standard-level users never see the tabs anyway so it looks clean to them. I certainly welcome any ideas/suggestions here. Its a fairly straightforward design but nothing's set in stone. -Chris Steven Southard wrote: I just tried out your extension. Nice idea. I've always liked how the css file was exposed under pages but I really hadn't thought of it having it's own section either. Also, I've always wondered where to put my js files. I usually just tucked them in the javascript folder and referenced them. This gives them a proper place. I mostly only use one stylesheet per website so it seems a bit overkill. Not to be stingy with my tabs, but I think I'd like it better if the css and js pages were both under one tab. I'm looking forward to seeing what becomes of this extension. Thanks, Steven On May 27, 2008, at 1:28 PM, Chris Parrish wrote: nurilized wrote: is there any way to call js/css files from anywhere of the page/layout? suppose, i use one template and many subpages? but i use different/extra css/js files on subpages (and also common), for example i will use accordion script on a subpage and putting this on template or on header snippet is nonsense so i am looking for a way to call these files from inside page/layout I just released version 0.3 of this extension and you will now find tags to do just this. For instance: r:stylesheet name=my_stylesheet / produces: your stylesheet content Or, if you want to be more fancy, try: r:stylesheet name=my_stylesheet as=inline / and get: style type=text/css !-- your stylesheet content -- /style The same works with the r:javascript tag. -Chris ___ 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 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
Re: [Radiant] Re: Re: [Radiant-Dev] [ANN] Styles 'n Scripts Extension
Not sure I follow you. What do you mean by no matter where they are called from? i called r:javascript name=xyz.js / from the content form and it dumped everything in the place where i called it (inside body tag) but i say it would be better if it is placed between head tags (but there could be some pitfalls to do this tho) also why not add a feature that will give just the src link for js/css files am i missing something? ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] Re: Re: [Radiant-Dev] [ANN] Styles 'n Scripts Extension
thank you that was helpful. ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] Re: Re: [Radiant-Dev] [ANN] Styles 'n Scripts Extension
why dont you git? On 5/28/08, Chris Parrish [EMAIL PROTECTED] wrote: I've just checked in a version (trunk -- not tagged) that adds r:javascript name=xyz.js as=link / (same for stylesheet) which renders a link to the external javascript or stylesheet. Stick a bunch of those in your page parts and reference the part from your layout. I'll roll the whole thing into a 0.3.1 release some time tomorrow. -Chris nurilized wrote: thank you that was helpful. ___ 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 mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] Re: Re: [Radiant-Dev] [ANN] Styles 'n Scripts Extension
I've just checked in a version (trunk -- not tagged) that adds r:javascript name=xyz.js as=link / (same for stylesheet) which renders a link to the external javascript or stylesheet. Stick a bunch of those in your page parts and reference the part from your layout. I'll roll the whole thing into a 0.3.1 release some time tomorrow. -Chris nurilized wrote: thank you that was helpful. ___ 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] Re: Re: [Radiant-Dev] [ANN] Styles 'n Scripts Extension
On May 28, 2008, at 1:15 PM, Chris Parrish wrote: nurilized wrote: why dont you git? You guys are killing me. John's pushing me there today too ;-) For the record, I use Windows and Eclipse (Aptana's RadRails) to do my development. I'm used to, and like both very much. Right now, I can do all my source code control right in my IDE wonderfully -- visually see which files have changed, apply properties, commit, update, etc. Unfortunately git support is weak for Windows and weaker still for Eclipse. So I'm going to have to figure out a new workflow to use my IDE and git as an external tool in order to make the switch. It'll probably happen eventually but I've got enough irons in the fire already for now. The killer thing about git in my mind is Github. It makes it super easy to push changes back and forth on projects. I'd highly recommend sitting through the Peep Code screencast if you haven't already. -- John Long http://wiseheartdesign.com ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] Re: Re: [Radiant-Dev] [ANN] Styles 'n Scripts Extension
nurilized wrote: is there any way to call js/css files from anywhere of the page/layout? suppose, i use one template and many subpages? but i use different/extra css/js files on subpages (and also common), for example i will use accordion script on a subpage and putting this on template or on header snippet is nonsense so i am looking for a way to call these files from inside page/layout I just released version 0.3 of this extension and you will now find tags to do just this. For instance: r:stylesheet name=my_stylesheet / produces: your stylesheet content Or, if you want to be more fancy, try: r:stylesheet name=my_stylesheet as=inline / and get: style type=text/css !-- your stylesheet content -- /style The same works with the r:javascript tag. -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] Re: Re: [Radiant-Dev] [ANN] Styles 'n Scripts Extension
I just tried out your extension. Nice idea. I've always liked how the css file was exposed under pages but I really hadn't thought of it having it's own section either. Also, I've always wondered where to put my js files. I usually just tucked them in the javascript folder and referenced them. This gives them a proper place. I mostly only use one stylesheet per website so it seems a bit overkill. Not to be stingy with my tabs, but I think I'd like it better if the css and js pages were both under one tab. I'm looking forward to seeing what becomes of this extension. Thanks, Steven On May 27, 2008, at 1:28 PM, Chris Parrish wrote: nurilized wrote: is there any way to call js/css files from anywhere of the page/ layout? suppose, i use one template and many subpages? but i use different/extra css/js files on subpages (and also common), for example i will use accordion script on a subpage and putting this on template or on header snippet is nonsense so i am looking for a way to call these files from inside page/layout I just released version 0.3 of this extension and you will now find tags to do just this. For instance: r:stylesheet name=my_stylesheet / produces: your stylesheet content Or, if you want to be more fancy, try: r:stylesheet name=my_stylesheet as=inline / and get: style type=text/css !-- your stylesheet content -- /style The same works with the r:javascript tag. -Chris ___ 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] Re: Re: [Radiant-Dev] [ANN] Styles 'n Scripts Extension
Thanks for the feedback Steven. I'm really interested in making this a usable extension for all. I always used pages for my js and css files too and, like you, never had more than a handful of each -- it wasn't much of a bother to do. So, when John first mentioned the idea to me I really only saw one or two valid reasons for such an extension (for instance, I found it difficult to explain to users why they had to create a blank layout for a stylesheet just to set the content-type). Now that I've been working on it, I see *many* good reasons to go this route (my current favorite is the server and browser caching benefits -- I *love* the idea of not having to expire and reserve all stylesheets and javascripts every 5 minutes). As to the multiple tabs, yeah, I'm with you. Originally I think John envisioned something like an Assets tab where CSS, JS and image files could all reside but Radiant hasn't settled on an image asset approach just yet. And without images, what do you call the tab -- Text Assets? CSS JS? Assets-That-Don't-Happen-To-Include-Images? Actually, my original mock-up for this extension had one tab (called Files) but I still kind of choked on that vague name. Anyway, for now, John just suggested keeping two tabs and waiting to see how things progressed. In the interest of minimizing tab space, I did choose to name them CSS and JS instead of Stylesheets and Javascripts. Plus, your standard-level users never see the tabs anyway so it looks clean to them. I certainly welcome any ideas/suggestions here. Its a fairly straightforward design but nothing's set in stone. -Chris Steven Southard wrote: I just tried out your extension. Nice idea. I've always liked how the css file was exposed under pages but I really hadn't thought of it having it's own section either. Also, I've always wondered where to put my js files. I usually just tucked them in the javascript folder and referenced them. This gives them a proper place. I mostly only use one stylesheet per website so it seems a bit overkill. Not to be stingy with my tabs, but I think I'd like it better if the css and js pages were both under one tab. I'm looking forward to seeing what becomes of this extension. Thanks, Steven On May 27, 2008, at 1:28 PM, Chris Parrish wrote: nurilized wrote: is there any way to call js/css files from anywhere of the page/layout? suppose, i use one template and many subpages? but i use different/extra css/js files on subpages (and also common), for example i will use accordion script on a subpage and putting this on template or on header snippet is nonsense so i am looking for a way to call these files from inside page/layout I just released version 0.3 of this extension and you will now find tags to do just this. For instance: r:stylesheet name=my_stylesheet / produces: your stylesheet content Or, if you want to be more fancy, try: r:stylesheet name=my_stylesheet as=inline / and get: style type=text/css !-- your stylesheet content -- /style The same works with the r:javascript tag. -Chris ___ 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 mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] Re: Re: [Radiant-Dev] [ANN] Styles 'n Scripts Extension
I must admit that assets that don't happen to include images is a bit long. I kind of like text assets. That kind of opens it up to include other types of files that people may want to put there like .xml or maybe even a .as file. One thing that would be nice about putting them together is that you could then make use of a file type combo box. That would fill out the page a bit and give a person a little more to do. Also those lovely icons would have a chance to help you sort out your file types. -Steven On May 27, 2008, at 8:50 PM, Chris Parrish wrote: Thanks for the feedback Steven. I'm really interested in making this a usable extension for all. I always used pages for my js and css files too and, like you, never had more than a handful of each -- it wasn't much of a bother to do. So, when John first mentioned the idea to me I really only saw one or two valid reasons for such an extension (for instance, I found it difficult to explain to users why they had to create a blank layout for a stylesheet just to set the content-type). Now that I've been working on it, I see *many* good reasons to go this route (my current favorite is the server and browser caching benefits -- I *love* the idea of not having to expire and reserve all stylesheets and javascripts every 5 minutes). As to the multiple tabs, yeah, I'm with you. Originally I think John envisioned something like an Assets tab where CSS, JS and image files could all reside but Radiant hasn't settled on an image asset approach just yet. And without images, what do you call the tab -- Text Assets? CSS JS? Assets-That-Don't-Happen-To-Include- Images? Actually, my original mock-up for this extension had one tab (called Files) but I still kind of choked on that vague name. Anyway, for now, John just suggested keeping two tabs and waiting to see how things progressed. In the interest of minimizing tab space, I did choose to name them CSS and JS instead of Stylesheets and Javascripts. Plus, your standard-level users never see the tabs anyway so it looks clean to them. I certainly welcome any ideas/suggestions here. Its a fairly straightforward design but nothing's set in stone. -Chris Steven Southard wrote: I just tried out your extension. Nice idea. I've always liked how the css file was exposed under pages but I really hadn't thought of it having it's own section either. Also, I've always wondered where to put my js files. I usually just tucked them in the javascript folder and referenced them. This gives them a proper place. I mostly only use one stylesheet per website so it seems a bit overkill. Not to be stingy with my tabs, but I think I'd like it better if the css and js pages were both under one tab. I'm looking forward to seeing what becomes of this extension. Thanks, Steven On May 27, 2008, at 1:28 PM, Chris Parrish wrote: nurilized wrote: is there any way to call js/css files from anywhere of the page/ layout? suppose, i use one template and many subpages? but i use different/extra css/js files on subpages (and also common), for example i will use accordion script on a subpage and putting this on template or on header snippet is nonsense so i am looking for a way to call these files from inside page/ layout I just released version 0.3 of this extension and you will now find tags to do just this. For instance: r:stylesheet name=my_stylesheet / produces: your stylesheet content Or, if you want to be more fancy, try: r:stylesheet name=my_stylesheet as=inline / and get: style type=text/css !-- your stylesheet content -- /style The same works with the r:javascript tag. -Chris ___ 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 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] Re: Re: [Radiant-Dev] [ANN] Styles 'n Scripts Extension
is there any way to call js/css files from anywhere of the page/layout? suppose, i use one template and many subpages? but i use different/extra css/js files on subpages (and also common), for example i will use accordion script on a subpage and putting this on template or on header snippet is nonsense so i am looking for a way to call these files from inside page/layout The way I usually do this is to put a content part in my layout's header called head-meta that appears in the header, e.g. !DOCTYPE html PUBLIC -//W3C//DTD XHTML 1.0 Transitional//EN http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd; html xmlns=http://www.w3.org/1999/xhtml; xml:lang=en lang=en head ...other header stuff ... r:content part=head-meta / /head Then you can just add a part to the page called (what else) head-meta and add whatever page-specific Javascript, CSS, meta tags, etc. you might want. Hope this helps! Rufo ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] Re: Re: [Radiant-Dev] [ANN] Styles 'n Scripts Extension
hmm, thats nice but it can be good to inject css/js files from body part inside head thank you On 5/20/08, Rufo Sanchez [EMAIL PROTECTED] wrote: is there any way to call js/css files from anywhere of the page/layout? suppose, i use one template and many subpages? but i use different/extra css/js files on subpages (and also common), for example i will use accordion script on a subpage and putting this on template or on header snippet is nonsense so i am looking for a way to call these files from inside page/layout The way I usually do this is to put a content part in my layout's header called head-meta that appears in the header, e.g. !DOCTYPE html PUBLIC -//W3C//DTD XHTML 1.0 Transitional//EN http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd; html xmlns=http://www.w3.org/1999/xhtml; xml:lang=en lang=en head ...other header stuff ... r:content part=head-meta / /head Then you can just add a part to the page called (what else) head-meta and add whatever page-specific Javascript, CSS, meta tags, etc. you might want. Hope this helps! Rufo ___ 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] Re: Re: [Radiant-Dev] [ANN] Styles 'n Scripts Extension
I played around with the idea of creating an r:stylesheet and r:javascript tag or even enhancing the r:content tag to let you add stylesheet/javascript content in addition to page part content. The problem is that in either case you have to specify which file you want (either explicitly or by first setting up a context to that item) so why not just manually type it and save the noise of yet another radius tag. This case, however, has me thinking the other way. (Plus the other benefit that your users only need to know the name of the script or stylesheet and not their full path -- my tag would build that). I'm going to be putting out a new rev shortly -- it would be simple to add a r:stylesheet and r:javascript tag. I'd certainly welcome other ideas as well. -Chris nurilized wrote: hmm, thats nice but it can be good to inject css/js files from body part inside head thank you On 5/20/08, Rufo Sanchez [EMAIL PROTECTED] wrote: is there any way to call js/css files from anywhere of the page/layout? suppose, i use one template and many subpages? but i use different/extra css/js files on subpages (and also common), for example i will use accordion script on a subpage and putting this on template or on header snippet is nonsense so i am looking for a way to call these files from inside page/layout The way I usually do this is to put a content part in my layout's header called head-meta that appears in the header, e.g. !DOCTYPE html PUBLIC -//W3C//DTD XHTML 1.0 Transitional//EN http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd; html xmlns=http://www.w3.org/1999/xhtml; xml:lang=en lang=en head ...other header stuff ... r:content part=head-meta / /head Then you can just add a part to the page called (what else) head-meta and add whatever page-specific Javascript, CSS, meta tags, etc. you might want. Hope this helps! Rufo ___ 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 mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] Re: Re: [Radiant-Dev] [ANN] Styles 'n Scripts Extension
Ok, so now that you have a running Radiant app, you now should do the following to install the extension: 1. Copy the Styles 'n Scripts Extension to the following path: radiant_app/vendor/extensions/styles_n_scripts You can find the latest version of the extension here: https://secure.svnrepository.com/s_swanki/open/radiant/extensions/styles_n_scripts/tags/v0.2.2 2. From your radiant_app directory, migrate the extension's db changes (adding the text_assets table). Run: rake radiant:extensions:styles_n_scripts:migrate If you have any problems, run the rake task with the '--trace' option to show the details (and post them here). 3. Finally, copy the images used by the extension. Again, from your radiant_app directory, run: rake radiant:extensions:styles_n_scripts:update This doesn't sound like where your problem lies but, if you should have any problems here, run rake with the --trace option again. Good luck and let us know how it goes and post any specific error messages here. -Chris nurullah wrote: although all installation steps fail it adds tabs on panels and some columns on config table 5|stylesheet_mime_type|text/css 6|response_cache_directory|text_asset_cache 7|javascript_mime_type|text/javascript 8|javascript_directory|js 9|stylesheet_directory|css but you are right production.log says it cannot find text_assets table and right there is no such table on db file On 5/19/08, Chris Parrish [EMAIL PROTECTED] wrote: The Styles 'n Scripts extension makes use of Radiant's built-in Radiant::Config settings (which get stored in the config table). So this sound like a Radiant setup issue. (The only table my extension adds is text_assets). Remove my extension (all extensions, really) and make sure that your plain-vanilla Radiant extension has this table created (should have been created when you ran: rake db:bootstrap (or rake production db:bootstrap if running in production mode). -Chris Arik Jones wrote: I think this is a fault of Radiant. Could be wrong. nurullah wrote: I could get it run on a clean install (0.6.7) tho, with sqlite3 and no other extension installed it gives Could not find table 'config' error On 5/18/08, Chris Parrish [EMAIL PROTECTED] ___ 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 mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
