Re^5: RFC : Abstraction Markup

I think you misunderstood my question. From what I can tell, this is supposed to be completely generic, being able to attach handlers to any "tag" (or have it pass through verbatim if there is no handler), with each handler receiving its children as content and returning a rendered version. With <> tags, child content has already been processed, but handling of () tags is supposed to take precedence over their children; does that mean the contents of a () tag aren't subject to any handlers? Or that upon return of the () tag handler, any tags in the return are handled? Other?

Comment on Re^5: RFC : Abstraction Markup Select or Download Code

Replies are listed 'Best First'.

Re^6: RFC : Abstraction Markup
by Anonymous Monk on Jul 13, 2011 at 19:25 UTC

I think you misunderstood my question

I don't think I did :) I explained how the given template example unravels in both perl and tt2 terms

does that mean the contents of a () tag aren't subject to any handlers?

I don't understand what you're asking :)

Based on his actual proof of concept (both old, new) "(DB)" "DB" is the name of plugin, its perl code, either ...DB.aXMLpl or ...DB.pm

Since (DB) has no () children, it is processed first, as a complete unit

Its responsible for processing all tags contained within as a template

Or that upon return of the () tag handler, any tags in the return are handled? Other?

Lets try another , shorter example

(Foo)
 <Fruit>Apples</Fruit>
 (Bar)
   <pants>red</pants><d>varyable</d>
 (/Bar)
(/Foo)
[download]

return $Foo->(
 '<Fruit>Apples</Fruit>'
 .$Bar->('<pants>red</pants><d>varyable</d>')
);
[download]

Like chromatic said, its basically scheme

Am I closer now?

[reply]
[d/l]
[select]


Pathologically Eclectic Rubbish Lister
	PerlMonks