I've just pushed the latest changes to GitHub
(http://github.com/SwankInnovations/radiant-conditional-tags-extension/tree/master)
-- and there are quite a few changes:
* Radically improved the way other extensions can create their own
evaluators (look for a new extension from me later t
Chris Parrish wrote:
This is interesting. I'll have to think about this. Essentially what
you're going for here is the removal of the attributes (something I
agree with). I bet my extension would be more comfortable if only you
could write:
I haven't thought this through, but what abo
Sorry. I didn't want to come across so preachy. I agree with you. It
bugs me too.
If, however, I ask myself whether it would bother a non-techy -- someone
who not only doesn't know xml but who's never even heard of it -- then
I'd bet nearly all would prefer something like:
to
But the
Ok, you're right.
For me, would not feel right, though.
Manuel
On Sat, Oct 25, 2008 at 8:35 PM, Chris Parrish
<[EMAIL PROTECTED]> wrote:
> Manuel Meurer wrote:
I think that there is a place for these tags and I'd love it if there
was
an easy way to use this to create both if_
Manuel Meurer wrote:
I think that there is a place for these tags and I'd love it if there was
an easy way to use this to create both if_ and unless_ tags. Something like:
conditional_tags "my_tag" do |tag|
#return a boolean
false
end
which would then create if_my_tag and unless_my_tag tags.
>> I think that there is a place for these tags and I'd love it if there was
>> an easy way to use this to create both if_ and unless_ tags. Something like:
>>
>> conditional_tags "my_tag" do |tag|
>> #return a boolean
>> false
>> end
>>
>> which would then create if_my_tag and unless_my_tag tags
Adam van den Hoven wrote:
Sure that works except that it is entirely too late IMHO. It
should be raised when you install the extension (say in the update or
migrate tasks) since that is when you are dealing with extensions. If
you were to do that for a live site running passenger then sudde
I just released v0.2 of the extension. Changes include:
* Jeff's request for a "status" evaluator. The term "status" gets
evaluated into a string ("draft", "reviewed", "published", or
"hidden"). Keep these requests coming.
* And I beefed up (fixed) the mechanism for other exten
On 23-Oct-08, at 9:46 PM, Chris Parrish wrote:
Adam van den Hoven wrote:
What I mean is:
1) I decide to use your tag instead of creating my own special
purpose if_ and unless tags. I document it in my README
2) Like some existing extensions do, I inject a page or a snippet
or a layout into
Adam van den Hoven wrote:
What I mean is:
1) I decide to use your tag instead of creating my own special purpose
if_ and unless tags. I document it in my README
2) Like some existing extensions do, I inject a page or a snippet or a
layout into the database that uses my extension and yours
3) A
On 23-Oct-08, at 3:35 PM, Chris Parrish wrote:
Adam,
Thank you so much for your feedback. I like your thinking. I do
have some questions and comments for you and the rest of the gang.
See below...
While the proliferation of tags can be bad for users, Radiant lacks
any mechanism for
Adam,
Thank you so much for your feedback. I like your thinking. I do have
some questions and comments for you and the rest of the gang. See below...
While the proliferation of tags can be bad for users, Radiant lacks
any mechanism for ensuring dependancies are installed making using
thi
Hello all. I'm finally releasing an extension that I've mentioned over
the last year on the list. I think that it has a lot of power and
potential but I could use some input from the Radiant clan.
The Conditional Tags Extension
(http://github.com/SwankInnovations/radiant-conditional-tags-ext
Chris,
I love the idea you've got going here. I haven't had a chance to try
it but I have a few thoughts:
While the proliferation of tags can be bad for users, Radiant lacks
any mechanism for ensuring dependancies are installed making using
this extension within my own potentially destabi
That's an easy one. It's because I didn't implement an evaluator for
"status. Doh!
I am working on a v0.2 right now and will add that. I think I'll
implement "status" and have it return a string ("published", "draft", etc.)
So to be more clear to everyone, in v0.1 I've implemented the foll
Ok, upon first use I am running into a few problems (Naturally since I
said this would be useful for development-minded people and have
therefore excluded myself as murphy's law dictates).
I am trying to use the page status as the condition and have:
...
However this results in an error on
Eeexcellent
While I can see the advantage of a small set of standard tags
to make things easier for normal users the flexibility provided by
these tags will come in useful for the more development-minded.
Jeff
Quoting Chris Parrish <[EMAIL PROTECTED]>:
Hello all. I'm finally
Hello all. I'm finally releasing an extension that I've mentioned over
the last year on the list. I think that it has a lot of power and
potential but I could use some input from the Radiant clan.
The Conditional Tags Extension
(http://github.com/SwankInnovations/radiant-conditional-tags-ext
18 matches
Mail list logo
