[Zope3-dev] Flexibility

[Chris Withers]

Jim Fulton wrote:
> 
> I think that users of Zope have given pretty clear guidence that that
> level of flexibility is pretty much always needed. Extensability is
> critical to Zope 3 specifically because people want to change things,
> especially the views. But people often want to add other functionality.
> Furthermore, it's extremely hard to predict what parts people are
> going to want to replace. A system that makes it easy to add, remove,
> and delete components is really important.

Yes, BUT, the only reason that this was demanded is because Zope 2 got the first
part of this stuff very very right: It should be dead simple to build small
slightly dynamic websites.

The Zope 2 paradigm of knocking up a python script or two, some ZPT's and using
something like DTML Docs as content objects meant people could get going damn
quick and with minimal effort.

If they have to write several config files and interfaces, understand XML, some
Zope specific XML dialect, the Zope configuration model, AND python AND ZPT and
write their app then Zope 3 is gonna have a tough time appealing to new users,
which given it's current place in the market and it's aim of growing 10x this
year, seems to still be the main group to keep happy.

For me, the key is to solve the problem of letting people make simple apps more
complex in a sane way rather than only letting people write complex apps, which
is where Zope 3 appears to be now.

cheers,

Chris