On Monday 13 February 2006 10:05, Tres Seaver wrote:
> - I don't want to encourage people to do configuration in Python:
> we have moved away from that *on purpose* in Zope, and I don't see
> a reason to go back. Directives which make it possible to change
> policy decisions without touching software are a Good Thing. I think
> that letting people who spend their days up to the elbows in the
> software make choices here skews the picture: we *want* people to
> be able to change the behavior of the system in controlled ways
> without having to modify software; I would prefer to hear feedback
> from non-core-developers before going further with the "ZCML delenda
> est" thread.
> - The "application vs plugin" discussion is probably germane to this
> issue, as well: a user who is deploying a single application is
> acutally *more* likely to define and use convenience directives
> which reduce the amount of effort required to change policy than
> the generic appserver-with-plugins configuraiton. Removing the
> ability to create such convenience declarations makes it harder
> for those developers.
> - Many of the objected-to directives exist precisely because people
> did not want to type the much more verbose equivalents which were
> the original, "cleaner" spellings.
Mmmh, I had totally forgotten about this design goal/use case. Thanks a lot
for pointing this out. I will not change my vote on the other proposal, but I
think we have to keep this in mind when talking about ZCML simplification.
CBU Physics & Chemistry (B.S.) / Tufts Physics (Ph.D. student)
Web2k - Web Software Design, Development and Training
Zope3-dev mailing list