[Zope3-dev] Allowing views to be registered for classes rather than interfaces.

[Stephan Richter]

On Thursday 17 July 2003 06:39, Steve Alexander wrote:
> > There will be not many UI designers working on the core components and
> > for products (where I would expect to see a lot of UI people working) t=
he
> > hierarchy looks anyway like::
> >
> > productX
> > productX/browser
> > productX/interfaces
> >
> > which brings me to another point. The zope.app hierarchy is different a=
nd
> > therefore inconsistent with all other base zope packages and third party
> > products.
>
> How is it different and inconsistent?
>
>
> We have
>
>
> =A0 =A0zope/app
>
> =A0 =A0zope/app/browser/...
>
> =A0 =A0zope/app/interfaces/...
>
>
> That seems to be the same as your productX example above.

Because I don't see zope.app as a product like package (I know some (most?)=
 of=20
you do, but I don't). I really see zope.app.workflow or zope.app.i18n as=20
packages like productX, since it contains a controlled feature. But again,=
=20
this might be just me. I just know that I get confused with this hierarchy=
=20
all the time. I counted on Tuesday how many times it bit me during=20
development and the count ended at 7 times. I was wondering why Emacs didn'=
t=20
find a file for me, before realizing I have to move 'interfaces' before=20
workflow for example.

Regards,
Stephan
=2D-=20
Stephan Richter
CBU Physics & Chemistry (B.S.) / Tufts Physics (Ph.D. student)
Web2k - Web Software Design, Development and Training