Are you deliberately missing the point or what?
I gave 3 methods on another post which would allow you to output absolutely anything using aXML, including fragments of aXML.
If you don't like the function of a plugin, you can just overload it, nothing is set in stone except for the rules of tag process precedence.
I know it might be difficult to understand the functioning of a completely flexible softcoded dynamic declarative language when your used to working with rigid inflexible limited imperitive document macro languages, but I assure you I'm not attempting to mislead you in anyway and I am not so stupid as to have been unable to notice such glaring faults as the ones your wrongly perceiving to exist within aXML.
In reply to Re^16: aXML vs TT2
by Logicus
in thread aXML vs TT2
by Logicus
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |