hi,
just one idea comes to my mind as I'm looking at sub ParseXMLSubs{}...i.e.
Isn't it possible when we use XMLSubsMatch to have one additional option say
XMLSubsDef, what I have in mind :
PerlSetVar XMLSubsDef default
Later on in the ASP.pm (sub ParseXMLSubs{}) /everything on the fly so
excuse if there is errors / :
my($func,$args) = ($1,$2);
my $tagname;
#the new code
if ($self->{xml_subs_def}) {
$func =~ s/\:(.*?)/\:$self->{xml_subs_def}/s;
$tagname = $1;
}
$func =~ s/\:+/\:\:/g;
......
"<% $func({tagname => '$fname', $args}, '');%>"
...
similar several lines below...
What this gives me :
test.html
==========
<html>
....
<my:tag1 .../>
...html code... <my:tag2 />...etc..
my.pm
======
#any usage of tag in "my" namespace goes trought this function
sub default {
};
So what is the benefit :
Because the everything goes trought one function I can easily setup PRE and
POST tag processing, can attach/create a object on first invocation to
handle in a better way the tags, easly can store/cache common info...etc...
Also this way we can bundle easy TagLib modules... Apache::ASP::HomePage,
Apache::ASP::TT :"))
Can we handle in this way Template-loops easily...?
ok i'm giong to sleep...
=====
iVAN
[EMAIL PROTECTED]
=====
PS. I have a couple of XML files from my home page.. which I want to start
making again... but don't want to setup and install AxKit when I already
have and use ASP.pm :")
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
