Is there a clean way for a behavior, within some code implementing a
particular tag for that behavior, to access the ID of the text filter
which is in effect during the moment when the tag is processed?
At the moment, I'm overriding the private parse_object method, storing
object.filter_id in
I've just finished a first version of a simple news headline tag for
Radiant, incorporated into a 'News' behavior. It parses an RSS feed from
a given feed URL and generates an unordered list of headline items. The
number of headlines and whether or not a published date gets appended
can be
John W. Long wrote:
This is a great idea. Please submit a patch.
Agreed. I can now do the following to have a heading that is itself a
link to the parent page, in the manner of many Wiki engines:
h1
r:parentr:linkr:pager:title //r:page/r:link/r:parent
/h1
However, this breaks
So, given the above, if anyone wants to elaborate on the page just go
ahead. There's lots missing (e.g. better examples of tags and
Behavior-dependent tag descriptions).
It might be better to split it into a series of sub-section pages rather
than all collected together. At least as it stands
John W. Long wrote:
Please submit a ticket and associate it with the next release.
OK, done (I assume 0.6 is the next release...).
A cool future feature would allow by and status selectors on the
:first and :last tags, assuming they're not already supported.
Yah, a status attribute would
For my own Radiant installation I've extended all filters to include a
help method that returns a piece of text which gets inserted into the
relevant views to form a set of help links for filter types. They get
listed next to the pop-up filter menu. Ajaxian people might prefer to
have
In an effort to learn more about Radiant, I've just completed a first
draft of the Using Radiant page of the Handbook within the Radiant
Wiki at:
http://dev.radiantcms.org:9007/radiant/wiki/UsingRadiant
I'm planning on using Radiant as part of a wider site to enable a small
team to edit
Adrian Madrid wrote:
I'm getting started with Radiant and your summary helped me get
a btter look at it.
Great! Then it was worthwhile :-)
I've made various revisions now, including filling in the outstanding
TODO stuff. Writing the page gave me enough knowledge to start
experimenting with
Is it a bug or intentional that r:children:first and r:children:last
disagree with r:children:each about the first and last child by
default in Radiant 0.50?
The :first and :last tags appear to return the same thing shown in the
list of pages; that is, children sorted in alphabetical order by
