> Off the top of my head, why have your tags translate to
> my::default, wouldn't this be better to have:
>
> PerlSetVar XMLSubsDefault my::default
>
> then
>
> sub my::default {
> my($tag_name, $args, $html) = @_;
> ...
> }
>
> But, if you really want pre processing & post
> processing, we need something new, since the current
> XMLSubs model just handles post processing.
]- isn't the XMLSubs replace the tag with function-call before executing the
ASP code... ?!!
i.e.
<my:func/> become <% func() %> ... and then when the time comes it is
executed..
> Also for handling things like complex minilanguages,
> we really need a token parser that can create ASP on the
> fly to be parsed during the compilation phase
> that one could say something like:
>
> PerlSetVar XMLTagParse my:\w+
>
> then one could do ASP logic level tranformations
> on the fly like:
>
> <my:if eval="1+1">
> ...
> </my:if>
> <my:else>
> ...
> </my:else>
>
> # global.asa
> sub XMLTag_OnStart {
> my($token, $args) = @_;
> my $script = $Server->{ScriptData};
> if($token eq 'my:if') {
> $$script .= "<% if(".$args->{'eval'}." { %>";
> } elsif($token eq 'my:else') {
> $$script .= "<% } else { %>";
> }
> }
>
> sub XMLTab_OnEnd {} ...
]- Aha U mean XMLSubs happens at runtime not at compile time !?
> I think it would be with this kind of system that
> one could completely model most any other mini language
> like XSP or CFML.
>
> Rather, then go and build something that noone will use
> though, let us try to focus this conversation on what
> you are trying to do exactly...
]- Not very-clear idea yet :")... but I want first to try to remake my home
page with XMLSubs instead of AxKit... 'cause it is not worth it at the
moment to do full-blown AxKit.-installation... And that's why XMLSubs is the
right tool to use..
> BTW, I do like where you are going with this, but would
> like a complete solution for whereever this leads.
]- let me experiment a litle bit... and when I have a better idea i will
post again... but I generally think the for such "light-wave" tasks it the
perfect solution....
One other thing for which I would like to use it is to separate the design
from logic (the-template-way)... and this seems like a good way to do it...
/but if it is handled at compile-time, how it will be possible to pass info
from ASP script to this virtual-XML-template-system if it executed before
it.. may-be callbacks?! /
i.e.
ASP-object-model + logic-design separation + XML, XSLT transformation.
Thanx
=====
iVAN
[EMAIL PROTECTED]
=====
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
