Ian Bicking wrote: > David Bernard wrote: > >> I think it could be added to the instantiation of the plugin. So def > >> __init__(self, extra_vars_func=None, options=None, search_path=None): > > > > > > Why not define search_path as an options ? > > Options are use to set the configuration of the TemplatePlugin. > > Because I'd like this to be a standard thing that plugins should > support. I'm not quite clear how, say, the stan plugin works, and maybe > a search path wouldn't work there. But for most it should work, and I > consider it a very important feature so I'd like it to be consistent.
I think the plugin standard that we setup should stay as basic as possible. IMHO, the plugin should busy itself *only* with rendering output based on an already supplied path to a template and a dictionary of parameters. That's it. Anyone using the plugins can choose to implement search path behavior in their app/framework/whatever and then use the plugin to do the actual rendering. Thoughts? Christian http://www.dowski.com
