not being able to use aXML to generate XML and aXMLThere is no problem with that at all since you have complete control over the plugins their names and definitions.
Ugh. So if I discover that I have to output (or worse, pass through and modify) XML that contains <d> elements, I have to review all my aXML code to make sure that I don't use any plugin named/responding to <d>? I'm still not convinced that this is a sound design choice. That you don't immediately spot this problem makes me think that you haven't encountered the problem ,but that is to be expected if all you are doing is generate web pages and work alone. That way, you have a good overview of the admissible names. This mechanism will horribly fail once one of these two parameters changes.
In reply to Re^31: aXML vs TT2
by Corion
in thread aXML vs TT2
by Logicus
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |