[Radiant] [ANN] Variables & Conditionals Extension
Chris Parrish
chris at swank-i.com
Sat Oct 6 19:17:03 CDT 2007
Chris Parrish wrote:
>
> Sorry for my ignorance -- could someone give me some guidance here please?
>
Nevermind, I found it -- great minds, I guess. Wow, quit monitoring the
group for a few months and look what happens...
Anyway, my objectives are a bit different than back_door in that:
1.) There is NO WAY I want users to have full access to ruby. I wanted
something as benign as <r:if_parent> but more flexible. I wouldn't build a
site for a business and then hand the secretary or office staff that kind of
a weapon. I'm not even sure I'd trust myself if the site was important --
after all, there's no way to test whether your code breaks your live site
without breaking your live site (no real testing environment).
2.) I want something that designers and other non-coders could use. I
don't want them to have to learn ruby. My thoughts here are probably closer
to John's (can I say that?) when it comes to throwing in the kitchen sink --
just enough and no more... done elegantly (by the way that phrase is now
trademarked, John)
3.) I wanted to give the extension developer a way to easily expose values
from their creations and use them in conditionals -- yet also control what
can be freely accessed and what is protected. Again, flexibility with
security.
4.) I wanted something that was on a separate layer from the underlying
ruby code. That way if Radiant 4.2.5 changes the way page titles are
accessed, I only need to update my extension code -- not all my static pages
that now have Radiant-specific back_door code.
5.) On a different note, the 'vars' stuff I created is different (though
I'm sure that you could build that using back_door and Ruby code).
Please don't misunderstand me -- I LIKE having back_door available but the
needs driving this are very different (hey, that's why we have extensions).
So, yes, it does conflict with the <r:if> and <r:unless> tags that Aitor
created (I frankly love that he also used cond="" -- ha!) I suspect that
most developers would opt for one OR the other, though, based on their
security needs.
--
View this message in context: http://www.nabble.com/-ANN--Variables---Conditionals-Extension-tf4580441.html#a13078770
Sent from the Radiant - User mailing list archive at Nabble.com.
More information about the Radiant
mailing list