Textpattern CMS support forum
You are not logged in. Register | Login | Help
- Topics: Active | Unanswered
Re: Shortcodes (as seen in rah_beacon)
Hi Oleg – I’m happy with your explanations. If this could be coded as an extension of output_form (and also using your short-tag) then I’d be super happy!
Offline
Re: Shortcodes (as seen in rah_beacon)
Ok, they have landed in dev branch, without short tags and smart yield unsetting atm. This should work, please test:
<!-- create a form called "my_link" -->
<a href="<txp:yield name="href" />" class="<txp:yield name="class">default</txp:yield>"><txp:yield /></a>
<!-- call -->
<txp:output_form form="my_link" href="#">Click me!</txp:output_form>
<!-- should output -->
<a href="#" class="default">Click me!</a>
Offline
Offline
Re: Shortcodes (as seen in rah_beacon)
etc wrote #305435:
<txp:output_form form="media_video" width="640" height="480" ratio="0.5625" mp4-url="/video/video.mp4" webm-url="/video/video.webm" poster-url="/img/poster.png" duration-seconds="20" />...
…..
<txp:output_form form="someform" anyname1="somevariable" anyname2="qwerty" />
someform:
...define defaults <txp:yield_default anyname1="11" anyname2="22" /> . ...set/override yield <txp:yield name="anyname1" value="33" /> or <txp:yield name="anyname1">33</txp:yield> . ...use yield <txp:yield name="anyname1" /> <txp:yield name="anyname2" /> . ...if <txp:if_yield name="anyname1"> .. <txp:else /> .. </txp:if_yield> <txp:if_yield name="anyname2" value="qwerty"> .. </txp:if_yield>
aks_cron : Cron inside Textpattern | aks_article : extended article_custom tag
aks_cache : cache for TxP | aks_dragdrop : Drag&Drop categories (article, link, image, file)
Offline
Re: Shortcodes (as seen in rah_beacon)
NicolasGraph wrote #305439:
Interesting thread; would it be possible to add a
value
ordefault
attribute to<txp:yield />
to provide a default value?
Yes, currently it’s the content:
<txp:yield name="test">default value</txp:yield>
I also like makss idea: <txp:yield name="test" value="default value" />
.
Offline
Re: Shortcodes (as seen in rah_beacon)
Again, as long as the default values of yield can be within the form itself, I’m super happy! Probably favouring Makss idea of yield syntax – although does a container tag provide more options for content? Dunno.
Offline
Re: Shortcodes (as seen in rah_beacon)
philwareham wrote #305442:
Probably favouring Makss idea of yield syntax – although does a container tag provide more options for content?
Nothing to stop us providing both, like we do with the form
attribute in other tags at present. Container overrides value
, probably, in the same way as container overrides form
in other tags?
The smd plugin menagerie — for when you need one more gribble of power from Textpattern. Bleeding-edge code available on GitHub.
Txp Builders – finely-crafted code, design and Txp
Offline
Offline
Re: Shortcodes (as seen in rah_beacon)
Ok, let have both. Also, should <txp:output_form form="some_form" wraptag="p" />
consider wraptag
as global attribute, or as <txp:yield name="wraptag" />
(current case)?
Offline
Re: Shortcodes (as seen in rah_beacon)
etc wrote #305445:
Ok, let have both.
I love this feature. After reviewing a tonne of off-the-shelf software out there for delivering topic-based documentation, I’ve tentatively started using (a plugin-customised) Txp for it instead, and this feature is fabulous for parameterizing reusable Forms.
should
<txp:output_form form="some_form" wraptag="p" />
considerwraptag
as global attribute, or as<txp:yield name="wraptag" />
(current case)?
Whichever offers the user the fewest surprises. I would be tempted to say that it should wrap the entire content, in the same way that any other wraptag/class combo does in Txp. If someone wants a different wraptag
for the yield, they should add the attribute to that tag. Unless I’ve missed some subtle nuance here.
The smd plugin menagerie — for when you need one more gribble of power from Textpattern. Bleeding-edge code available on GitHub.
Txp Builders – finely-crafted code, design and Txp
Offline
Re: Shortcodes (as seen in rah_beacon)
Bloke wrote #305587:
I would be tempted to say that it should wrap the entire content, in the same way that any other wraptag/class combo does in Txp. If someone wants a different
wraptag
for the yield, they should add the attribute to that tag. Unless I’ve missed some subtle nuance here.
No, it’s only semantics. A yield called class
looks more natural than my_class
.
Edit: also, global attributes set being plugin-extensible, a form yield attribute can inadvertently become global.
Offline
Re: Shortcodes (as seen in rah_beacon)
etc wrote #305616:
A yield called
class
looks more natural thanmy_class
.
Ah yes, allowing arbitrary attributes for the output_form tag opens the possiblity of clashes with global attributes. Hadn’t thought of that. Hmmm…
The smd plugin menagerie — for when you need one more gribble of power from Textpattern. Bleeding-edge code available on GitHub.
Txp Builders – finely-crafted code, design and Txp
Offline