It's totally illogical trying to compare aXML and TT2!. On the one hand yes aXML can be used for templating, but on the other hand it is not a templating system or even a language, it's just a simple set of rules on how to process a quasi-xml style document, from which great depth and complexity can be derived.
It doesn't even make sense to try and provide an example of the same thing as above done in aXML, since all you would need to do to replicate that output is write a little perl script like :
$result = ""; for (my $ctr=1;$ctr<4;$ctr++) { $result .= "recursion count: $ctr\n\n"; }
Save that as a plugin say "count.aXMLpi", and then add the tag "<count></count>", into any document that wants to use it. So when people ask for examples comparing TT2 and aXML, I'm stumped because the two are not equivalent paradigms.
Let me give you another quick example; one of the plugins I have written for aXML implements an Ajax powered chatroom. The code to output the javascript for the chatroom is written in perl, and if I want an Ajax chatroom on any page of any site I write, then all I have to do is add the plugin to that site's plugin folder (I don't keep it in the global plugin folder), and then add the following to the aXML file for that page :
<ajaxchat>ajaxresponder</ajaxchat>
Then I just make an action called ajaxresponder which loads the chat data either from a file or the database or whatever (programmers choice) and returns it when the browser is updating the chatwindow which was created by the plugin ajaxchat.
In reply to Re^2: H.O.P && aXML
by Logicus
in thread H.O.P && aXML
by Logicus
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |