Yah rly.

aXML (the grammar definition) + a set of definition plugins (the syntax) = a language.

It's not logical to compare aXML and TT2, any more than it is to compare Perl and TT2, however for the purposes of illustration a comparison of them does help a bit in explaining the rules of aXML in a way that is accessible to users of TT2.

aXML is not a replacement to TT2, infact, you could if you so desired, replace the standard set of aXML plugins with ones which output TT2 template code. Then aXML could generate TT2 templates for you, or catalyst apps, or mojolicious programs... whatever really.

aXML is more concerned with controlling server behaviour in a declaritive manner than browser behaviour, but having said that it's perfectly capable of doing both, and unless there is a really good reason for using TT2 then there is no need as aXML is more than adequetly capable of replicating the html/xml output templating functions of TT2.

What your looking at is the emergence of a new paradigm, still in its infancy yes, but a clearly different way of doing things which has various strong advantages over older methods (at the expense of processor time).

If you actually do want to understand what it is, instead of just wanting to be difficult, then I suggest that when PerlNights opens in the near future, you click on the "Castle Blueprints" section and download the full source code, which with any luck will be sufficient for most people to understand just what it is about aXML that drives me to continue pursuing it at the expense of my whole career.

Programmers, especially perl programmers earn upwards of £30,000 p/a, which conservatively speaking means I have currently invested around £150,000 of my time into the project so far. And I'm giving it away for free to a bunch of people who don't like me and call me a delusional arrogant troll.

I must be flipping mental...

In reply to Re^26: Is an aXML compiler possible? by Logicus
in thread Is an aXML compiler possible? by Logicus

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.