Re: [Radiant] SnS Requests Anyone?
Adam van den Hoven wrote:
Things I would like:
something like a separate field for copyright notices so that you can
minimize the JS/CSS without loosing (someone else's) copyright notice.
You can accomplish this today by bundling multiple assets. For instance:
--- JS file #1: prototype.js (not minified) ---
/* Prototype JavaScript framework, version 1.6.0
* (c) 2005-2007 Sam Stephenson
*
* Prototype is freely distributable under the terms of an MIT-style license.
* For details, see the Prototype web site: http://www.prototypejs.org/
*
*--*/
--- JS file #2: prototype.js.content (this has 'minify?' checked) ---
... the rest of the prototype lib goes in here ...
That would serve up the prototype library just as you requested as
'prototype.js'
support for external libraries
I really just want 1 tag to use for all these assets
they can be always "as link"
If you really want to be cool, "know" ahead of time all the important
libraries and their versions (kinda like how the google Ajax Libraries
API works -- http://code.google.com/apis/ajaxlibs/) so I can do
But also just http://scriptsite.com/somelibrary"; />
Sounds neat -- though I'm *positive* you don't want me anywhere near any
project that requires constant maintenance to keep up-to-date with the
latest libraries.
Couple of questions, though:
* If you know the url, what's the benefit of using the tag? I mean sure, it renders the link for you but that's not
so bad to type manually.
* How would it be helpful for SnS to have it's own list of libraries
when the Google api you offered already does this?
I'm really not trying to beat the "you can already do this" drum, but
why not just type:
http://www.google.com/jsapi";>
google.load("prototype", "1.6");
google.load("scriptaculous", "1.8.1");
Or, if you want to keep your list of google.load's in their own
javascript file (named, say, "google.loads"), you could just:
http://www.google.com/jsapi";>
I want to make sure I'm understanding your ideas. (Thanks for the tip
on google, BTW. I've never used that and think that it'd be a nice
addition -- looks like they even minify stuff for us).
___
Radiant mailing list
Post: Radiant@radiantcms.org
Search: http://radiantcms.org/mailing-list/search/
Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] Articles extension
Be very careful about this before you go down this road. You may put in more effort than you get put of it. That being said, I'd look at the archive extension. This is probably the route you want to take: modifying the behaviour of a page. This should "play well" with pages. Adam On 13-Nov-08, at 5:21 PM, Philip Arndt <[EMAIL PROTECTED]> wrote: Hi everyone, I'm working on a site at the moment where the next thing I'll need to build is an extension to have "articles" These are pretty much the same as pages but need to have different groupings etc. Does anybody know of any existing extension that will do this or most of this and could be added to? Otherwise, once I'm done, I'll see if I can make what I get done public. But it'd be nice if somebody has already done that! Cheers Phil ___ 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] Articles extension
Philip Arndt wrote: Hi everyone, I'm working on a site at the moment where the next thing I'll need to build is an extension to have "articles" These are pretty much the same as pages but need to have different groupings etc. I'd have thought that if each article belongs to 1 category, then it's a regular hierarchical page - just create the parent and add children under it. On the other hand, if an article belongs to multiple categories, you could use something like the tagging extension. More detail about how to tag with Radiant is in the Summer Reboot article about Using radiant as a blog. http://wiki.radiantcms.org/Using_Radiant_as_a_Blog Cheers, Mohit. 11/14/2008 | 9:32 AM. ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
[Radiant] Articles extension
Hi everyone, I'm working on a site at the moment where the next thing I'll need to build is an extension to have "articles" These are pretty much the same as pages but need to have different groupings etc. Does anybody know of any existing extension that will do this or most of this and could be added to? Otherwise, once I'm done, I'll see if I can make what I get done public. But it'd be nice if somebody has already done that! Cheers Phil ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] Comment extension
Luiz Biagi wrote: Hi I'm trying to use the Extension for comments: http://github.com/artofmission/radiant-comments/tree/master I want to view the commentaries and the comment insertion frame only when i'm in the article visualization, I mean, when I'm in the article link, not the articles (main page), but I'm having some problems, the " " are apearing in the main page, please help me! Sounds like you have refered to the comments snippet somehow. I'm not sure what you've done, but a few things might be: 1. You refer to the comments snippet in the layout and both pages (articles and the main page) use the same layout. So, comments show in both pages. Fix: Create a different layout for the articles. 2. Your main page does something that includes the body of the article and the body of the article has the comments in it. If this doesn't help, we'll need to see what your main page's content area looks like and how you refer to the comments. Cheers, Mohit. 11/14/2008 | 9:00 AM. ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] Importing & Exporting
Anton Aylward wrote: Hi Anton, Mohit Sindhwani said the following on 11/13/2008 02:01 PM: So far, I'm using SQLite, so I just move the database between my PC and the demo site. How lucky you are! I tried that, moving from my laptop to my ISP and it didn't work. Probably because my laptop runs a 32-bit processor and my ISP runs a 64-bit. Or possibly an OS clash. Or ... That is very strange! SQLite is supposed to be binary compatible - sure it wasn't a problem with extensions? No dump-restore is the way to go! I notice that you have a version management plugin for Radiant. What are you using? Cheers, Mohit. 11/14/2008 | 8:55 AM. ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] SnS Requests Anyone?
Things I would like: something like a separate field for copyright notices so that you can minimize the JS/CSS without loosing (someone else's) copyright notice. support for external libraries I really just want 1 tag to use for all these assets they can be always "as link" If you really want to be cool, "know" ahead of time all the important libraries and their versions (kinda like how the google Ajax Libraries API works -- http://code.google.com/apis/ajaxlibs/) so I can do But also just http://scriptsite.com/somelibrary"; /> Adam On 13-Nov-08, at 3:31 PM, Andrew Neil wrote: I'm getting ready to roll out a new SnS version this weekend with some bug fixes and a column name change (requested and implemented by Andrew Neil to help it work with his file_system extension). As Chris says, I have been working on integrating file_system functionality into SnS. The column name change was simply to avoid a naming conflict between the two extensions, but it shouldn't cause any perceptible change in the behaviour of SnS. My file_system/SnS integration is not ready for release yet, but I shall announce it here when it is. Since I'm doing that, are there any other issues/feature requests out there? Now would be a good time to entertain those. I was going to suggest asset packaging... but then I had another look at the README and saw that it was already there! Cheers, Drew ___ 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] SnS Requests Anyone?
I'm getting ready to roll out a new SnS version this weekend with some bug fixes and a column name change (requested and implemented by Andrew Neil to help it work with his file_system extension). As Chris says, I have been working on integrating file_system functionality into SnS. The column name change was simply to avoid a naming conflict between the two extensions, but it shouldn't cause any perceptible change in the behaviour of SnS. My file_system/SnS integration is not ready for release yet, but I shall announce it here when it is. Since I'm doing that, are there any other issues/feature requests out there? Now would be a good time to entertain those. I was going to suggest asset packaging... but then I had another look at the README and saw that it was already there! Cheers, Drew ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] Importing & Exporting
On 13-Nov-08, at 2:00 PM, Chris Parrish wrote: * It's simple (read: non-technical users love it) * It's db-independent so if my local development environment is Sqlite3 but my server is MySQL or PostgreSQL (or I want to change databases/servers some day) it's no sweat to move content around. * It's collects all of the content (this means styles and scripts ala SnS, and whatever fun extensions I choose to add in the future). * My site's content can be fully restored via import. * Ideally it's in a human readable format so if it's kept in an scm, diff tools can identify changes. * Bonus points for packaging all the files up nicely (like a zip or tarball for download). * Bonus points for managing asset files such as images images (though I'm not holding my breath here). It seems to me that you want to keep a copy of everything in an svn repo so why not simply symlink your assets directory from the repository directory and symlink db/export from the SAME repository. Paperclipped (or what ever) will store all its changes in the symlink and the super_export (which is the only one of the two that will work for this) will put its files there too. Now you simply have to svn add and svn commit and you're laughing. Adam ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
[Radiant] Comment extension
Hi I'm trying to use the Extension for comments: http://github.com/artofmission/radiant-comments/tree/master I want to view the commentaries and the comment insertion frame only when i'm in the article visualization, I mean, when I'm in the article link, not the articles (main page), but I'm having some problems, the " " are apearing in the main page, please help me! Thank you guys ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] Importing & Exporting
On 2008/11/13, at 15:00, Chris Parrish wrote: * Bonus points for managing asset files such as images images (though I'm not holding my breath here). I've found page attachments using Amazon S3 as the storage backend alleviates all of the issues I had surrounding tracking static assets. ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] Importing & Exporting
Chris, The import_export extension[1] captures every model in the database within one big yaml file. By default this is saved as db/export.yml. Pros: * very portable Cons: * if you want to edit the records captured in the yaml, they can be quite difficult to find The super_export extension[2] captures every model in the database in its own file. The file format is like this: /db/export/:model_name/:id.yml Pros: * it is easier to locate individual records, should you want to edit them Cons: * less portable export format than a single yaml file There is no harm in installing both extensions, playing around with them and deciding which you prefer. They can both co-exist happily. Of course, things could get confusing if you keep a stale db copy in one format... If your assets are stored on the filesystem, then neither of these extensions will be able to assist in backing them up. I don't know how they would fare if you were storing your assets in the db... I hope that helps. Cheers, Drew [1]: http://github.com/radiant/radiant-import-export-extension/tree/master [2]: http://github.com/Aissac/radiant-super-export-extension/tree/master On 13 Nov 2008, at 22:00, Chris Parrish wrote: One of the problems with Radiant being so extensible is that it attracts a lot of software geek-types. ;-) It's no issue for me to do a db dump/restore but I couldn't give that job to my assistant. Plus I'm not sure that that's a friendly format for, say, version controlling a site's content. Anyway, sorry for not being more clear. My goals here are: * It's simple (read: non-technical users love it) * It's db-independent so if my local development environment is Sqlite3 but my server is MySQL or PostgreSQL (or I want to change databases/servers some day) it's no sweat to move content around. * It's collects all of the content (this means styles and scripts ala SnS, and whatever fun extensions I choose to add in the future). * My site's content can be fully restored via import. * Ideally it's in a human readable format so if it's kept in an scm, diff tools can identify changes. * Bonus points for packaging all the files up nicely (like a zip or tarball for download). * Bonus points for managing asset files such as images images (though I'm not holding my breath here). And I'd really *love* it if someone could tell me the difference between import_export and super_export (which I think does import too). -Chris Mohit Sindhwani wrote: Chris Parrish wrote: I'm looking for a good way to backup/restore all of my content for a Radiant App. I'm want something that collects all the data (including extension models). I'm aware of Import-Export and Super Import-Export but I can't seem to find anything that clearly spells out the differences. Is anyone familiar with both solutions (or any other ones you'd recommend)? I could use some tips. Would a database dump not help? So far, I'm using SQLite, so I just move the database between my PC and the demo site. But, I would have thought that a database dump would manage 'almost' everything. The only thing that gets left behind, unfortunately, is the stuff in public... and I don't know how Page Attachments / Gallery would work across database dumps and restores. I need to think about this not too far in the future... in a way, it's good that you're ahead! Cheers, Mohit. 11/14/2008 | 2:58 AM. ___ 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] Importing & Exporting
One of the problems with Radiant being so extensible is that it attracts a lot of software geek-types. ;-) It's no issue for me to do a db dump/restore but I couldn't give that job to my assistant. Plus I'm not sure that that's a friendly format for, say, version controlling a site's content. Anyway, sorry for not being more clear. My goals here are: * It's simple (read: non-technical users love it) * It's db-independent so if my local development environment is Sqlite3 but my server is MySQL or PostgreSQL (or I want to change databases/servers some day) it's no sweat to move content around. * It's collects all of the content (this means styles and scripts ala SnS, and whatever fun extensions I choose to add in the future). * My site's content can be fully restored via import. * Ideally it's in a human readable format so if it's kept in an scm, diff tools can identify changes. * Bonus points for packaging all the files up nicely (like a zip or tarball for download). * Bonus points for managing asset files such as images images (though I'm not holding my breath here). And I'd really *love* it if someone could tell me the difference between import_export and super_export (which I think does import too). -Chris Mohit Sindhwani wrote: Chris Parrish wrote: I'm looking for a good way to backup/restore all of my content for a Radiant App. I'm want something that collects all the data (including extension models). I'm aware of Import-Export and Super Import-Export but I can't seem to find anything that clearly spells out the differences. Is anyone familiar with both solutions (or any other ones you'd recommend)? I could use some tips. Would a database dump not help? So far, I'm using SQLite, so I just move the database between my PC and the demo site. But, I would have thought that a database dump would manage 'almost' everything. The only thing that gets left behind, unfortunately, is the stuff in public... and I don't know how Page Attachments / Gallery would work across database dumps and restores. I need to think about this not too far in the future... in a way, it's good that you're ahead! Cheers, Mohit. 11/14/2008 | 2:58 AM. ___ 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] Importing & Exporting
Mohit Sindhwani said the following on 11/13/2008 02:01 PM: > So far, I'm using SQLite, so I just > move the database between my PC and the demo site. How lucky you are! I tried that, moving from my laptop to my ISP and it didn't work. Probably because my laptop runs a 32-bit processor and my ISP runs a 64-bit. Or possibly an OS clash. Or ... No dump-restore is the way to go! -- Listen, thou love-child of Methuselah, for you will be thrown into a den of hyperactive lions! ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] Importing & Exporting
Chris Parrish wrote: I'm looking for a good way to backup/restore all of my content for a Radiant App. I'm want something that collects all the data (including extension models). I'm aware of Import-Export and Super Import-Export but I can't seem to find anything that clearly spells out the differences. Is anyone familiar with both solutions (or any other ones you'd recommend)? I could use some tips. Would a database dump not help? So far, I'm using SQLite, so I just move the database between my PC and the demo site. But, I would have thought that a database dump would manage 'almost' everything. The only thing that gets left behind, unfortunately, is the stuff in public... and I don't know how Page Attachments / Gallery would work across database dumps and restores. I need to think about this not too far in the future... in a way, it's good that you're ahead! Cheers, Mohit. 11/14/2008 | 2:58 AM. ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
[Radiant] Importing & Exporting
I'm looking for a good way to backup/restore all of my content for a Radiant App. I'm want something that collects all the data (including extension models). I'm aware of Import-Export and Super Import-Export but I can't seem to find anything that clearly spells out the differences. Is anyone familiar with both solutions (or any other ones you'd recommend)? I could use some tips. -Chris ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
[Radiant] [Fwd: [Radiant-Dev] Re: Conditional Tags Tutorial?]
Adam Asked this on the Radiant-Dev list but I thought it might be more applicable here... Fair enough. Anyone with any other votes? Or questions you'd like answered in a tutorial? -Chris Adam van den Hoven wrote: Chris, One of the things that is missing from your recent two extensions (both Conditional Tags and Variables) is a tutorial. While gawking at your code is not a /bad/ way to figure out how to do it, I'd like to have more information about the reasons why you would expose something through the evaluator and so on. So I'd like to make the following (cheeky?) suggestion. Take an existing, non trivial extension (my vote is for paperclipped) and write a tutorial showing step by step what one would do to create a separate extension to add conditional evaluators to it. I would include things like "What is the best way to write tests/specs for each evaluator" as i suspect its not /entirely / clear. This should give us enough information to start using Conditional Tags in our own extensions. Adam! > --~--~-~--~~~---~--~~ Radiant CMS Dev Mailing List Post:[EMAIL PROTECTED] Unsubscribe: [EMAIL PROTECTED] Group Site: http://groups.google.com/group/radiantcms-dev/ -~--~~~~--~~--~--~--- ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] Radiant Template Contest Extended
Hi Sean Sean Cribbs wrote: I have decided to extend the Template Contest deadline to January 1, 2009. Sadly, we received no entries by the October 31 deadline. In order to spark your imagination, here are some suggestions for templates you might make: * Corporate brochure-ware * Artist portfolio * Blog or 'zine * Podcast (with in-page media player?) * Tutorials or documentation If you have started working on one, please finish and submit it. If you haven't started, here's your chance! That is a great idea. I've been inching along on a small simple corporate (SME) website kind of thing (in fact, to be honest, I was working on it when your mail came in) and have been hoping to send it in to you. It won't be flashy, but it will work. Cheers, Mohit. 11/14/2008 | 12:16 AM. ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
[Radiant] Radiant Template Contest Extended
I have decided to extend the Template Contest deadline to January 1, 2009. Sadly, we received no entries by the October 31 deadline. In order to spark your imagination, here are some suggestions for templates you might make: * Corporate brochure-ware * Artist portfolio * Blog or 'zine * Podcast (with in-page media player?) * Tutorials or documentation If you have started working on one, please finish and submit it. If you haven't started, here's your chance! Cheers, Sean ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
[Radiant] How to use the -tag?
Hi! I tried to figure out how to use the -tag, but couldn't find any effect no matter where I put it in the form template... and no matter what I used as a redirect_to (I also tried without one and having the form page as the redirect_to page). I used it like this: Thanks! Another thing that I noticed is that there's no real explanation to how you call variables in the email templates: http://github.com/radiant/radiant-mailer-extension/tree/master ...apart from showing up in the list of tags that can be used in the form, which isn't really accurate. However I figured this one out by looking in the comments in the code, as the handbook recommends. :) cheers, Simon ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] Tags extension: move to latest edge breaks db migration
> The task rake db:migration breaks on a file of the Tags extensions if I > move to latest edge. http://pastie.org/312887 > > > /simon Hi Simon, Quite sure that this is caused by a change in rails; rails 2.1.1 moved module Dependencies to ActiveSupport::Dependencies I'm swamped as ever at the moment, and not working with edge anytime soon.. Could you try this and let me know if it worked? Or even better fork and send a pull request on github; The patch would be to update vendor/extensions/tags/vendor/plugins/has_many_polymorphs/lib/has_many_polymorphs/dependencies.rb so that the first line module Dependencies reads module ActiveSupport::Dependencies Not sure how to make this backwards-compatible though.. Regards, Benny Degezelle Gorilla webdesign www.gorilla-webdesign.be ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
