>You are obviously far from convinced that template plugins could offer
>advantages, or you are very reluctant to change one of the core features
>of WebGUI. And you will probably have good reasons for that.
I am reluctant, but not because I don't like change. Instead, because I like to weigh
the advantage gained versus the work involved, the ease of use achieved, and the speed
>I find Macros perfect when performing small, straightforward tasks, that
>doesn't need you to provide it with a bunch of (opaque) parameters. But
>in some cases, you need to pass a bunch to get the job done. I thought
>that template plugins could enhance template writing and reading and
>prevent obfuscated code. But you are right, it also has its
>disadvantages (we didnt even speak about development of these plugins,
>which will probably be a lot harder than programming Macros), and is
>somewhat redundant when macros are available.
I will admit that the Macro/Template combo is not perfect, but it is the best thing I've
seen to date to keep the content seperated from the logic. If these plug-ins that you're
talking about would make the world better, then I want to explore them. I require hard
evidence, and that is what I'm pushing you for.
>I'll drop the discussion.
I don't want you to drop the discussion unless you want to. Don't drop it just because
I'm pushing back on you. When I don't understand something (or don't believe it) I
always push back because I don't believe in jumping on every idea just because someone
conceived it. I need to know that we're going down a path of massive benefit. There is
so much that can be done with WebGUI, but there is very little time (even with the
support of the open source community) so I've got to pick the battles that get the big
JT ~ Plain Black
Create like a god, command like a king, work like a slave.