in reply to Re^14: aXML vs TT2
in thread aXML vs TT2

So your response is: You can output "<d>", except when it's a recognized tag, and it commonly a recognized tag.

Was there any point to post?

You could also make it so that <db_select> takes an extra attribute argument to tell it what constitutes a delimiter within it's scope..

That doesn't help. First, suggesting I modify aXML's plugin for me to be able to use aXML is ridiculous.

Even if *you* add that feature to the plugin, it's still doesn't help: What if I want to output "<db_select>"?

Replies are listed 'Best First'.
Re^16: aXML vs TT2
by Logicus (Initiate) on Oct 23, 2011 at 03:40 UTC

    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.

[reply]

      I gave 3 methods on another post which would allow you to output absolutely anything using aXML, including fragments of aXML.

      I hadn't seen it yet. It wasn't even a reply to a post of mine.

      Are you deliberately missing the point or what?

      You finally get the point after ~20 posts, I miss the post where you got it, and you accuse me of missing the point?

[reply]

        It wasn't even a reply to a post of mine.

        Ok, sorry I thought it was. However now that you have found that post, do you still hold the same objection?

[reply]

      I gave 3 methods on another post which would allow you to output absolutely anything using aXML, including fragments of aXML.

      I hadn't seen it yet. It wasn't even a reply to a post of mine.

      Are you deliberately missing the point or what?

      You finally get the point after ~20 posts, I miss the post where you got it, and you accuse me of missing the point? 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.

      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.

      This was debunked in Re^3: aXML vs TT2.

[reply]

        No I didn't get your point, not because I failed to understand it, but because your wrong. It's not your fault and I can understand that it's tricky to make the leap from where your at to where I'm at without a decent set of documentation, but I am working hard to try and bridge that gap from this side and I only have one pair of hands!

        Your assertion that you cannot overload the subs is just completely wrong and I don't understand how you think you can justify that assertion.

        Take the <db_select> tag for instance, in the background it exists as:

        
  $plugins->{'db_select'} = sub { ... the code here ... };

        [download]

        The system allows for individual sites to have their own private subs and even for individual actions to have their own private subs, as defined by modules which you the end user build and which the system includes at compile time.

        If you don't like any given tag then in your private module you just write your own version and it automatically overloads the default version.

        
 my $plugins = {

       db_select => sub { ... your code here ... },
     some_other => sub { ... your code here ... }
  
   };

        [download]

        say for instance you want to extend the system so that you can use any given CPAN module, for instance Image::Resize

        
use Image::Resize;

my $plugins = {

     image_resize => sub {  ... interface code here ... }

   };

        [download]

        It really is as simple as that.

[reply]
[d/l]
[select]

In Section Meditations