Philip,

> "As Jim described it, a plug-in would be required for base

functionality -

> - that's just wrong."
>
> Some of us might politely wish to take an alternate view: anything

that

> can be a plugin (even default functionality) should be.

Obviously, we disagree, which is our mutual right.

I just think of the average user trying to use the engine - How much
will they need to worry about?

In my model; Nothing. Just install the engine, no plug-ins to think
about and go.

In the alternate; They must be concerned with the installing and setting
up of the plug-ins.

From a support perspective, my solution will always be better -- it is
simpler. As we all know, it doesn't take much to confuse people.


Sean