Re: Default Extension Proposal (was - Re: [Radiant] Re: Looking for something similar to summarize...)

2009-01-13 Thread Anton Aylward
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

Re: Default Extension Proposal (was - Re: [Radiant] Re: Looking for something similar to summarize...)

2009-01-13 Thread Nate Turnage
On Mon, Jan 12, 2009 at 9:25 PM, Mohit Sindhwani 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 hel

Re: Default Extension Proposal (was - Re: [Radiant] Re: Looking for something similar to summarize...)

2009-01-13 Thread Andrew Neil
I have a convention of my own, which is to create an extension named after each project that I am working on. So if I have Radiant sites called "wpbf" and "lilly", each will have it's own extension: wpbf_extension and lilly_extension. When I need to add miscellaneous tags (such as the 'truncate' ex

Default Extension Proposal (was - Re: [Radiant] Re: Looking for something similar to summarize...)

2009-01-12 Thread Mohit Sindhwani
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 o