Re: Default Extension Proposal (was - Re: [Radiant] Re: Looking for something similar to summarize...)
On Mon, Jan 12, 2009 at 9:25 PM, Mohit Sindhwani t...@onghu.com wrote: Ben Morrow wrote: Mohit Sindhwani wrote: Actually, this method should be written up in the Radiant 2009 Documentation project as a good simple example of bringing in Rails methods into Radiant installs - it would help those entry level Rails programmers who wonder how to bridge the worlds of Rails and Radiant. Cheers, Mohit. 1/12/2009 | 9:28 PM. I wholeheartedly agree. The method seems simple enough, but I'm not sure how to implement it myself. Hi Everyone (especially developers), I have a proposal that Radiant should include a default extension called 'my_tags' or 'local' or something. [Rationale] There are quite a few suggestions on this list for doing something like the above 'truncate' tag. All it requires is to throw in some simple tag-related code and access it from the Admin UI. This is especially so for simple things that do not require complex logic in the background and do not need much else other than a few simple calculations. Examples are: * the above truncate method * a tag that spits out textile for a URL that is linked to itself * a tag that uses Javascript for encoding the mail address * something that checks if a New icon should be displayed next to the title of an article depending on its age ...and so on. For good reason, a lot of these are simple things and are typically 'local' things that get customized for the specific installation and needs. I was wondering if it would be a good idea for Radiant to include an empty 'local' extension into which such code could be dumped. This would have the effect of: a) Having a common place where people can add their own tags (or tags taken from this list) b) Less tech-savvy developers being able to modify things without necessarily having to create an extension, a task that sounds very demanding and daunting. What do you think? +1 ~Nate ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: Default Extension Proposal (was - Re: [Radiant] Re: Looking for something similar to summarize...)
Nate Turnage said the following on 01/13/2009 10:01 AM: b) Less tech-savvy developers being able to modify things without necessarily having to create an extension, a task that sounds very demanding and daunting. Sounds like me ;-) What do you think? +1 +256 -- December 32, 1999: We're pleased to report no Y2K failures! ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Default Extension Proposal (was - Re: [Radiant] Re: Looking for something similar to summarize...)
Ben Morrow wrote: Mohit Sindhwani wrote: Actually, this method should be written up in the Radiant 2009 Documentation project as a good simple example of bringing in Rails methods into Radiant installs - it would help those entry level Rails programmers who wonder how to bridge the worlds of Rails and Radiant. Cheers, Mohit. 1/12/2009 | 9:28 PM. I wholeheartedly agree. The method seems simple enough, but I'm not sure how to implement it myself. Hi Everyone (especially developers), I have a proposal that Radiant should include a default extension called 'my_tags' or 'local' or something. [Rationale] There are quite a few suggestions on this list for doing something like the above 'truncate' tag. All it requires is to throw in some simple tag-related code and access it from the Admin UI. This is especially so for simple things that do not require complex logic in the background and do not need much else other than a few simple calculations. Examples are: * the above truncate method * a tag that spits out textile for a URL that is linked to itself * a tag that uses Javascript for encoding the mail address * something that checks if a New icon should be displayed next to the title of an article depending on its age ...and so on. For good reason, a lot of these are simple things and are typically 'local' things that get customized for the specific installation and needs. I was wondering if it would be a good idea for Radiant to include an empty 'local' extension into which such code could be dumped. This would have the effect of: a) Having a common place where people can add their own tags (or tags taken from this list) b) Less tech-savvy developers being able to modify things without necessarily having to create an extension, a task that sounds very demanding and daunting. What do you think? Cheers, Mohit. 1/13/2009 | 11:25 AM. ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
