[Zope3-dev] separation of view hierarchy

[Casey Duncan]

On Thursday 12 December 2002 12:37 pm, Florent Guillaume wrote:
> Martijn Faassen  <faassen@vet.uu.nl> wrote:
> > I've just posted some general directory hierarchy proposals. A specia=
l=20
aspect
> > of these change is the separation of the view hierarchy from=20
> > the implementation hierarchy. If you want to discuss this, then pleas=
e
> > also review the earlier proposal which has motivation:
> >=20
> >=20
http://dev.zope.org/Wikis/DevSite/Projects/ComponentArchitecture/ViewDire=
ctoryHi
> > erarchyReorganization
> >=20
> > I'd like to repeat here that the view developer target
> > audience will not contain people with names like 'Stephan Richter' an=
d=20
> > 'Guido van Rossum'. :) My argument is that the requirements for
> > view developers are different from those developing other zope 3=20
> > components.=20
>=20
> My big problem at the moment with ProposedDirectoryHierarchy is the
> removal of the View package. If we only have zope.app.browser instead o=
f
> zope.app.view.browser, there's absolutely no way to factor out code
> that's specif to views but not specific to browsers. For instance
> sorting of folder contents, helper formatting functions, and so on.

Sure, just create a zope.app.view module for the general view code shared=
 by=20
browser et al.

-Casey