[Filterproxy-devel] Re: e: : FilterProxy XSLT

[Bob M. <mce...@dr...>]

Mario Lang [la...@zi...] wrote:
> Bob McElrath <mce...@dr...> writes:
>=20
> > The point is there was no way to decide on the stylesheet.  None of the=
 web
> > forms show up, all I get is the "dump headers to file" checkbox.
> No, Not global. You have to choose a stylesheet for every siteconfig.
> Currently, there are no global options, I just left that there
> for me as example if I need some :-)... But I think I will
> remove the global section all together....

I was getting the headers checkbox for site config too...

My fault, I forgot to translate the variables.  I just checked in a bunch of
changes to your html file.  I also added an=20
    if(defined $SITECONFIG->{stylesheet})
so that it doesn't give form boxes for parameters when a stylesheet isn't
defined.  (was causing some perl errors)

So now it sorta works.  I see that the problem is that /usr/share/filterpro=
xy
is hardcoded into the xsl/xpath-filter.xsl file.  It looks like doing:
      <xsl:include href=3D"identity.xsl"/>
works, it seems to assume the same directory as the parent xsl file.  So as
long as all the xsl files are in one directory (or in a dir relative to xsl=
/),
we should be able to include them by specifying a relative path.

In the example you sent me, (for slashdot) I'm seeing black-on-black text. =
 Do
you get that too?

It's pretty fast too, on my machine that slashdot rule only takes 0.3s.  Ne=
ato.
;)  (the rewrite rules on slashdot take ~3s for me)

> Hmm, but lets see. Ill do a fresh install altogether, maybe
> I am getting something wrong here.

Ok, I got it sorta working.  I won't touch the xslt stuff for a while.  It's
all yours.

> > Sorry about that, I've been sitting on it too long... :(
> >=20
> > I hope the syntax is self-explanatory.  HTML::Mason is far more popular=
, so
> > there are many good references on the web too.
> It is also somehow more pleasant to read... Although <<EOT
> does have problems :)

Yeah, I had to fiddle with that a bit.  BTW if you use vim do:
    :set syntax=3Dmason

Problem is that errors/warnings generated by Mason don't have accurate line
numbers.  It has line numbers (two of 'em) but both of 'em are wrong.  The
<<EOF might even work.  I played with it for a while thinking that was the
error when the error was actually somewhere else.  *sigh*  I need to figure=
 out
how to get Mason to generate accurate line numbers, for my own sanity.

Ok, off to work now.  ;)

BTW, you should join the filterproxy-devel list, and we can continue
discussions there, so others can see what you've done!  ;)

Cheers,
-- Bob

Bob McElrath (rsm...@st...)=20
Univ. of Wisconsin at Madison, Department of Physics