<txp:if_yield>

mrdale · 2012-12-18 17:46:04

Cool.

backward compatible?
would plugins need to be rewritten to take advantage, ie <rah:replace> vs <txp:rah_replace>
so basically a whole load of existing functionality specific to certain tags is now allowed to exist in any tag via attributes with a “txp:” prefix? (what retooling is required to make this real?)
<mrd:pony txp:request="can haz?" />

Gocom · 2012-12-18 18:05:17

Considering you can’t have colons in attribute names and it doesn’t change existing behavior, it’s majorly not compatible.
I harvested some fairies last time I visited the Tingle Winkle Forest. No kidding. They will travel around the world, posses our old plugin authors and make them update the existing code. So, sure yes. No. Needs at least registering the tag. Changeable namespaces could be option, but causes collision with that thing. What was it called? Umm, something like XML and those other things. Sooo, kinda inclined against having customizable namespaces even that they would be cool. Ruud brought it up first time few years ago, after which it has been in my mind.
Parser feature. All parser. Some new stuff. I write it here and there. Ready in 2089, around 20 years after I’m gone. Requires like gazillion (some type of horse?) lines of code.

els · 2012-12-18 19:40:47

Gocom wrote:

Ready in 2089, around 20 years after I’m gone.

Like the Sagrada Família. You will be famous, Jukka ;)

tye · 2012-12-18 23:34:36

Els wrote:

Gocom wrote:

Ready in 2089, around 20 years after I’m gone.

Like the Sagrada Família. You will be famous, Jukka ;)

Remembered as a coffee machine – the great Jukka5000

gomedia · 2014-11-16 22:01:40

Textpattern CMS