We could just go down the separation path. I'm just worried it's going
to be a PITA to require the various classes. It also doesn't give us a
centralized bootstrap if we require it down the road (I don't
expect all
to use the MVC).
I would have asked the same questions Rob already has but I wondered;
couldn't you just formalise an example bootstrap (or two) as being
part of the framework? As I mentioned before it is really the first
point of contact with the framework and is essentially the starting
point for any further action. This bootstrap file could be the
inclusion point for any required classes. It would also make getting
the framework up and running a lot faster.
Several people have mentioned that ZF is not attempting to be a PEAR
like pick and mix selection and I can see that Zend.php somewhat
reinforces that fact. Something however doesn't feel/smell right with
it as it stands or as you propose when compared to the rest of the
framework. Of course I'm looking at it from the necessarily narrow
perspective of my own use and would be interested to hear the use
cases inferred by "require it down the road"
Nick
