On 10/21/05, Andy Wardley <[EMAIL PROTECTED]> wrote: > You could implement a method in the plugin objects that returns the filter > name.
This would be a change to Template::Plugin though, right? Either that, or a change to every third party plugin that the end user might install? > Alternately, you could have the plugin return a filter object rather > than installing it in the context filters. This is what > Template::Plugin::Filter does. Again, that would require changing third party modules. OK, so it looks as though each filter the user wants to run is going to require them to specify two things. First, the module the filter comes from, and second, the name of the filter within that module. That's OK, I can live with that. It's not quite as clean as I'd like, but it's a lot better than nothing. N _______________________________________________ templates mailing list [email protected] http://lists.template-toolkit.org/mailman/listinfo/templates
