[Zope3-dev] Re: Bug 358/359, 367 fixed

Tom Hoffman tom.hoffman at gmail.com
Thu Mar 3 11:58:17 EST 2005


On Thu, 03 Mar 2005 14:52:19 +0000, Chris Withers
<chris at simplistix.co.uk> wrote:
> Hi Roger,
> 
> Roger Ineichen wrote:

> > It's Not a MUST, but you get a really bad situation if you implement
> > a totaly different concept on a enduser application level.
> 
> Indeed, this is why I said components from Z3MI should be usable in
> applications built using Z3. Think like MFC used to be for Windows
> programming, or Borland OWL if people look back further, or maybe
> WXWindows...
> 
> > If some
> > customers will deep into the roots of the application server, they have
> > to learn it again.
> 
> Not at all, if the customer is building a Z3 app, they should use Z3MI.
> If the customer is using a CMS built in Z3, that CMS should provide a
> complete interface of its own, even if it does re-use some bits of Z3MI...
> 
For reference, this is what we're doing with SchoolBell.  Most end
users will download a self-contained application and never see the ZMI
at all.  Or, you can add the schoolbell package to your Zope 3's path
and wire it in with ZCML, allowing you to add a whole SchoolBell
instance to your site via the ZMI.  Once you're "in" the SchoolBell
instance, the ZMI isn't supported.  You use SchoolBell's interface.

If you're curious, you can explore this further with our new release
candidate for SchoolBell 1.0:
http://www.schooltool.org/releases/schoolbell1.0/ ;-)

--Tom


More information about the Zope3-dev mailing list