I thhink just dropping zmi is ploblematical
without a management ui alternative. How would you propose managing
things like per instance pluggable auth components. zcml is not enough
and nor is any other static config. You need per instance persistent
configuration and I am assuming grok and anything using zope 3
(traiditional server) would need to do this.  So anyone buidling a
instance based manageble tool would want to ship it with a management
ui that would work on multiple zope toolkit based


On Wed, Apr 15, 2009 at 1:20 AM, Martijn Faassen <faas...@startifact.com> wrote:
> Hey,
> Fabio Tranchitella wrote:
> [snip]
>> If the question was "who is interested in zope3, the application server,
>> and willing to maintain it", I'd answer "me".
> Thanks for speaking up!
> Do you use the Zope 3 ZMI a lot?
> The Zope Toolkit right now is most of the Zope 3 libraries. The main
> thing we're getting rid of is the ZMI right now and cleaning up the
> dependency structure. After that there are various other avenues for
> innovation.
> We're not out to break people's code. The Zope Toolkit project is very
> much about supporting this code better, allowing it to evolve and stay
> relevant. I'm a huge user of the existing codebase itself and I'm not
> about to rewrite all my stuff.
> Regards,
> Martijn
> _______________________________________________
> Zope-Dev maillist  -  zope-...@zope.org
> http://mail.zope.org/mailman/listinfo/zope-dev
> **  No cross posts or HTML encoding!  **
> (Related lists -
>  http://mail.zope.org/mailman/listinfo/zope-announce
>  http://mail.zope.org/mailman/listinfo/zope )
Zope-Dev maillist  -  Zope-Dev@zope.org
**  No cross posts or HTML encoding!  **
(Related lists - 
 http://mail.zope.org/mailman/listinfo/zope )

Reply via email to