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' example I posted), I put them in the site specific extension.
I think it is an excellent suggestion that each Radiant app would contain a local_extension. Although it is quite easy to create new extensions using the packaged generator, the process is not one that I have memorised. I usually have to check the wiki, or refer to one of my older extensions to remember how to do it, what goes where etc. When it comes to giving advice on the mailing list, I certainly coudn't reel the instructions off the top of my head. If there were a local_extension, it would be far more straightforward to just say, 'try this code in this file'. +1 Drew On Tue, Jan 13, 2009 at 3:25 AM, Mohit Sindhwani <[email protected]> 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? > > Cheers, > Mohit. > 1/13/2009 | 11:25 AM. > > > > _______________________________________________ > Radiant mailing list > Post: [email protected] > Search: http://radiantcms.org/mailing-list/search/ > Site: http://lists.radiantcms.org/mailman/listinfo/radiant > _______________________________________________ Radiant mailing list Post: [email protected] Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
