Shortcodes (as seen in rah_beacon)

etc · 2017-04-21 13:07:55

jakob wrote #305433:

yield would be okay if you can use the name attribute, and the end user (admin writer) doesn’t have to use it (as totally non-intuitive for non-techs).

Sure, end users would just need to say

<txp::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" />

or simply

<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" />

Also important is the ability to define defaults for attributes at the beginning of one’s form.

Like this, rewritten if width attribute is set?

<txp:yield name="width">640</txp:yield>

And one thing I’ve found one need’s to watch out for is when using a variable of one’s own making inside a form, you need to to reset (or unset) it again at the end of the form or else it will carry over into the next instance. That problem may become less common with oleg’s forthcoming better evaluate options (i.e. obviating the need for using txp:variable to test for certain “has-this”, “is-that” cases), but I’ve yet to fully explore that.

Here I would like an example…

Re namespace again, I prefer short-tag <txp::some_form /> to potentially XML-clashing <output:some_form />. One of the reasons is also that namespacing implies some (small) performance penalty, and short tags (in 4.7) are optional.

etc · 2017-04-21 13:09:50

philwareham wrote #305430:

… this feature has some shared functionality with <txp:output_form />. Hmmm, decisions.

It is disguised <txp:output_form />, actually.

philwareham · 2017-04-21 13:14:07

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!

etc · 2017-04-21 13:46:53

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>

NicolasGraph · 2017-04-21 13:47:12

Interesting thread; would it be possible to add a value or default attribute to <txp:yield /> to provide a default value?

makss · 2017-04-21 13:49:32

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" />...

+1

…..

<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>

etc · 2017-04-21 13:57:21

NicolasGraph wrote #305439:

Interesting thread; would it be possible to add a value or default 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" />.

philwareham · 2017-04-21 14:02:30

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.

Bloke · 2017-04-21 14:45:30

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?

NicolasGraph · 2017-04-21 16:00:44

Bloke wrote #305443:

Nothing to stop us providing both […]

That would be nice and introduce some consistency with <txp:variable />.

Textpattern CMS

Textpattern CMS support forum

#11 2017-04-21 13:07:55

Re: Shortcodes (as seen in rah_beacon)

jakob wrote #305433:

#12 2017-04-21 13:09:50

Re: Shortcodes (as seen in rah_beacon)

philwareham wrote #305430:

#13 2017-04-21 13:14:07

Re: Shortcodes (as seen in rah_beacon)

#14 2017-04-21 13:46:53

Re: Shortcodes (as seen in rah_beacon)

#15 2017-04-21 13:47:12

Re: Shortcodes (as seen in rah_beacon)

#16 2017-04-21 13:49:32

Re: Shortcodes (as seen in rah_beacon)

etc wrote #305435:

#17 2017-04-21 13:57:21

Re: Shortcodes (as seen in rah_beacon)

NicolasGraph wrote #305439:

#18 2017-04-21 14:02:30

Re: Shortcodes (as seen in rah_beacon)

#19 2017-04-21 14:45:30

Re: Shortcodes (as seen in rah_beacon)

philwareham wrote #305442:

#20 2017-04-21 16:00:44

Re: Shortcodes (as seen in rah_beacon)

Bloke wrote #305443:

Board footer