Thank you.
Unfortunately, it'll have to be a bit more complicated than that because i want to screen attributes and their values as well as tags, but I've got most of it done.
But there are two things I don't quite understand, and the docs are every bit as opaque as you suggested. I hope you can help:
update: both issues fixed by subclassing properly. All working now. Thanks for your help.
1. Should $filter and $want_it really be class variables? It feels like they should be tied to the $parser, at the very least, or better passed back directly from the methods. But i think i haven't quite grasped the event-driven model :(
2. Just clarification: HTML::Parser modifies text in place, it seems. Is there some way to stop it from printing upon eof? There must be, but i can't find it...
I'm trying to fold this into an existing system that uses TT2 and a subclass of Class::DBI, so I really need it to cooperate with TT's lovely lazy method calls, you see.
When it's done, should i post it here, or is this a rite of passage that everyone else has already passed through?
In reply to Re: Re: Tag filtering: a standard mechanism?
by thpfft
in thread Tag filtering: a standard mechanism?
by thpfft
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |