Appologies if some of these questions seem naive, I'm just beginning to more 
thoroughly delve into zope3 - of which I've been very impressed so far.

However - is it just me, or does zope3 seem to require a rather massive amount 
of configuration?

Is that specifically an artifact of Component Architectures in general?  Or is 
this by design?

Are "site administrators" really supposed to understand all that zcml in the 
configure.zcml files, or are they more realistically the domain of component 
developers? It seems to me that the configure.zcml looks almost as if it 
would basically be considered "hands off", once the application/component was 
coded and installed. 

Generally how much of any particular configure.zcml could - practically 
speaking - be modified in a usefull manner?

Even for relatively smallish apps, such as the buddydemo and zwiki, the 
configure.zcml file seem quite large; I hate to imagine what a more involved 
and complex app would do.

Am I just looking at it wrong? Perhaps the basic idea is small amounts of 
code, and large amounts of configuration/meta-programming via zcml?

Many thanks, and again sorry if I'm judging things prematurely based on my 
limited experience with zope3.


Cheers,

Corey





_______________________________________________
Zope3-users mailing list
Zope3-users@zope.org
http://mail.zope.org/mailman/listinfo/zope3-users

Reply via email to