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:
r:if content exists?
I haven't thought this
Ok, you're right.
For me, r:if content exists? 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
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:
r:if x = 0
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
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 extensions to
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
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
Mr. Burns Eeexcellent /Mr. Burns
While I can see the advantage of a small set of standard if_xxx 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]:
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
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
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
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
12 matches
Mail list logo
