From 843784a799cf77e3fa31ff45e1baa4abd471ea6b Mon Sep 17 00:00:00 2001 From: Chris McDonough Date: Sat, 14 Nov 2009 03:51:22 +0000 Subject: Murg. --- docs/designdefense.rst | 21 ++++++++++----------- 1 file changed, 10 insertions(+), 11 deletions(-) (limited to 'docs') diff --git a/docs/designdefense.rst b/docs/designdefense.rst index ae3bf89e9..05ec7a29c 100644 --- a/docs/designdefense.rst +++ b/docs/designdefense.rst @@ -371,19 +371,18 @@ palatable for XML-haters. For example, the ``bfg_view`` decorator function allows you to replace ```` statements in a ZCML file with decorators attached to functions or methods. In the future, BFG will contain a mode that makes configuration completely imperative as -described in +described in :term:`zcml_encouragement`. In BFG 1.2, no +:mod:`repoze.bfg` developer will need to interact with ZCML/XML unless +they choose to. However, currently, there are times when a BFG application developer -will be required to interact with ZCML, and thus XML. Alas, it is -what it is. All configuration formats suck in one way or another; I -personally don't think any of our lives would be markedly better if -the format were YAML, JSON, or INI. It's all just plumbing that you -mostly cut and paste. - -As described in :term:`zcml_encouragement`, in BFG 1.2, there will be -mode of configuration which is completely imperative (completely -Python-driven). At this point, no :mod:`repoze.bfg` developer will -need to interact with ZCML/XML, they'll just be able to use Python. +will be required to interact with ZCML, and thus XML. Alas; it is +what it is. You might think some other configuration file format +would be better. But all configuration formats suck in one way or +another; I personally don't think any of our lives would be markedly +better if the format were YAML, JSON, or INI. It's all just plumbing +that you mostly cut and paste once you're past 20 minutes into a +project. .. _model_traversal_confusion: -- cgit v1.2.3