Daniel Waite wrote: > What it boils down to is I'd like to see an example of an extension in > use that wasn't ported over from a behavior. Ideally the extensions > makes full use of itself, including the controllers, models, views, > extra Radius tags, etc. As it stands now I have no idea how an extension > actually works or can be used. >
Well, to just answer the question in your original subject: Extensions are for developers of Radiant, to extend Radiant. If you are not a developer wanting to extend Radiant, then Extensions as an architecture are not for you. They can be used by the deploying person to achieve, whatever that particular extension promises. And for the end user of the site, they help to adress the specific problem, that the extension was developed for. So, if you dont want or cant extend Radiant, then extensions (as a framwork) are not for you. But if you find a specific extension, which adresses your need, then that extension might be for you. (Its like asking: what is Ruby on Rails for? If you are not a developer of web applications, then it is not for you. ) _______________________________________________ Radiant mailing list Post: [email protected] Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
