Michael Graham wrote:
>>I agree. Maybe this isn't so dangerous cause the plugin author would
>>describe what template engine is supported 'out of box' and just use
>>load_tmpl(). If the author's load_tmpl does something different than the
>>plugin wants, it's up to the user to port the templates and put them
>>where he wants them.
>
>
> Hmmm... I see what you're saying. But there are also a lot of cases
> where a plugin uses HTML::Template and I don't particularly care that it
> does, even though I personally use Template::Toolkit for my own apps.
> I might convert them, but I might not bother. But if the plugin uses
> load_tmpl(), then I'm pretty well forced to re-write all of its
> templates before I use the plugin (even just to try it out).
>
> From a user's point of view I think it would make more sense to let the
> plugin use whatever templates it wants to use, independently of my own
> template choices. Then if the boss decides to make me convert all the
> templates to the corporate standard I can do so, but until then I can be
> lazy and just mix and match templates.
That makes complete sense too. So I guess it's up to the plugin authors
to play nicely and use named configs where it makes sense.
--
Michael Peters
Developer
Plus Three, LP
---------------------------------------------------------------------
Web Archive: http://www.mail-archive.com/suppressed/
http://marc.theaimsgroup.com/?l=cgiapp&r=1&w=2
To unsubscribe, e-mail: suppressed
For additional commands, e-mail: suppressed
Mail converted by mhonarc 2.6.15
This archive provided courtesy of JSW4.NET, Internet Hosting Services for Small Business.