[Radiant] Extensions are for...?

[Sean Cribbs]

> 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.
>
>   
The LDAP extension was developed from scratch. It has its own 
controllers, models, views, and even a quasi-model that integrates with 
the ruby-ldap library.  It creates global tags that are available on any 
page.

Essentially an extension is, as we say, a "vertical slice".  In other 
words, it's a miniature Rails application that runs inside Radiant.  
What this means is that pretty much anything you can do with Rails, you 
can do with an extension, plus the facilities that Radiant provides like 
Radius tags, admin tabs, etc.  So, part of the reason it is vague is 
that you can do _whatever you want_!  The sky's the limit.

Sean