an attribute named "empty"

maniqui · 2008-06-08 20:28:21

Beware: this nasty plastic mannequin strikes again with an idea he got during a sunday satori (probably, to be rejected, as happened with many of his satoris, hehehe).

I’ve been thinking about some kind of tag attribute similar to what chh_if_data does.
This attribute (let’s call it empty) will return something if the tag itself doesn’t return anything.
In other words, if tag returns empty, it really returns the value attribute empty.

Some examples:

<li>Favorite food: <txp:tag name="food" empty="-" /></li> returns <li>Favorite food: - </li> if txp:tag returns empty.

<txp:tag1 empty='<txp:tag2 />' /> (an example using the new parser)

ruud · 2008-06-08 22:08:54

In cases where you need that, use that plugin. No point in adding such code to each and everytag. That just increases code side and makes it slower.

els · 2008-06-08 22:25:32

In that case, can we have <txp:if_data>? ;) (Not that I’d want to include each and every plugin in the core, but my impression is that almost everyone is using this one anyway.)

redbot · 2008-06-08 22:42:02

Els wrote:

In that case, can we have <txp:if_data>? ;) (Not that I’d want to include each and every plugin in the core, but my impression is that almost everyone is using this one anyway.)

+1

colak · 2008-06-09 06:47:51

I agree with Els. I would also take it a step further and speculate that a lot of “if” tags could be replaced with a more generic tag.

examples could include txp:if_comments, txp:if:excerpt, etc ~~but not txp:if_custom_field as that tag provides flexibility such as:~~

~~<txp:if_custom_field name=“url”>~~
~~<a href=”<txp:custom_field name=“url” />”><txp:custom_field name=“image” /></a>~~
~~</txp:if_custom_field>~~

>EDIT: Rethinking about it:)

All if tags could eventually be deprecated if the if_data tag becomes a container tag which could be used like <txp:if_data field="any-field">anything goes here</txp:if_data>

Last edited by colak (2008-06-09 07:03:16)

wet · 2008-06-09 09:51:36

<txp:variable name="honeybunny" value='<txp:custom_field name="redridinghood" />' />
<txp:if_variable name="honeybunny">anything goes here</txp:if_variable>

colak · 2008-06-09 12:32:51

hi Robert,

that looks very handy. will the new txp:variable and if_variable tags allow for tags in tags?

wet · 2008-06-09 12:37:48

Sure. Tags as attributes are tag-independent, as this capability is part of the the new tag parser which handles absolutely every tag, be it built-in or provided by a plugin. You could even use <txp:php>...</txp:php> to generate some really complex attribute values, in case the situation requires some math or complex logic.

uli · 2008-06-09 12:46:01

Aah, a bright future lies ahead, Honey Bunny! :)

maniqui · 2008-06-27 15:10:23

hi!

wet wrote:

<txp:variable name="honeybunny" value='<txp:custom_field name="redridinghood" />' />
<txp:if_variable name="honeybunny">anything goes here</txp:if_variable>

colak wrote:

that looks very handy. will the new txp:variable and if_variable tags allow for tags in tags?

I know wet’s code is just an example, but isn’t this exactly the same as this?

<txp:if_custom_field name="honeybunny">anything goes here</txp:if_custom_field>

I mean, I can’t see anything “very handy” through that example. Any other example that will make me drop my jaw? :o——[]

Last edited by maniqui (2008-06-27 15:10:39)

wet · 2008-06-27 15:15:58

May it’s not about “jaw dropping effects”, but flexibility

<ul id="nav">
<txp:section_list sections="contact,support,library,products" include_default="1" default_title="Home" wraptag="" break="" form="nav2" />
</ul>

nav2

<txp:if_section name='<txp:section />'>
  <txp:variable name="navactive" value="strong" />
<txp:else />
  <txp:variable name="navactive" value="" />
</txp:if_section>
<li>
<txp:section title="1" link="1" wraptag='<txp:variable name="navactive" />' />
<txp:variable name="sec" value='<txp:section />' />
<txp:if_variable name="sec" value="products">
  <txp:category_list section="products" categories="a,b,c" wraptag="ul" break="li" form="nav3" />
</txp:if_variable>
<txp:if_variable name="sec" value="d">
  <txp:section_list sections="library" wraptag="ul" break="li" />
</txp:if_variable>
</li>

nav3

<txp:category link="1" title="1" />
<txp:article_custom section='<txp:section />' category='<txp:category />' sort="Title asc" limit="999" wraptag="ul" break="li">
  <txp:wet_link><txp:custom_field name="menutitle" default='<txp:title />' /></txp:wet_link>
</txp:article_custom>

maniqui · 2008-06-27 16:36:14

Thanks, wet!
Your example both made me drop my jaw and made it flexible at the same time (it was like a cross to my mandible). I’m still trying to recover…

Lets try to dissect this one too:

<txp:if_variable name="sec" value="products">
<txp:category_list section="products" categories="a,b,c" ... />
</txp:if_variable>

connected with this
<txp:article_custom section='<txp:section />' category='<txp:category />' ...>
means necessarily that section='<txp:section />' returns section='products' ^{(brain overheating)}
and being that category='<txp:category /> is context sensitive… ^{(brain about to explode)}
mmmm if it returns something different than a, b or c… ^{(sticky chunks of brain all over the walls)}

OK, I can’t connect categories="a,b,c" with category='<txp:category />
Care to explain, please? :D
——

Let’s go on:

<txp:if_variable name="sec" value="d">
<txp:section_list sections="library" wraptag="ul" break="li" />
</txp:if_variable>

I think I didn’t get this one either.
If there is a section named “d”, the condition will be true and then… it will output a txp:section_list but just with the section “library”?
And, at the same time, this section_list is inside the other section_list?
——

Finally: <txp:custom_field name="menutitle" default='<txp:title />' />
Ooooh! I didn’t know about the default attribute for txp:custom_field!
It’s similar to (or exactly) what I’ve asked when I started this thread (an attribute named “empty”)
Just to be sure:
<txp:custom_field name="menutitle" default='<txp:title />' /> is equal to
<txp:if_custom_field name="menutitle"><txp:custom_field name="menutitle"><txp:else /><txp:title /></txp:if_custom_field />
Right?

Last edited by maniqui (2008-06-27 19:07:57)

Textpattern CMS

Textpattern CMS support forum

#1 2008-06-08 20:28:21