Could it be possible to support configuring with *.cfg instead of *.zcml?

Asko Soukka <[email protected]>
Newsgroups gmane.comp.web.zope.plone.devel
Message-ID <[email protected]>
Hi,

TL;DR

Could it be possible and would it make sense (in the long run) to 
support also ini-configuration (cfg-files) instead of current 
xml-configuration (zcml-files)? This must have been discussed before, so 
maybe someone could give me pointers to old discussions or repeat the 
known issues.

-

I've understood that we try hard to make Plone development more 
"pythonic". One known barrier for new developers is ZCML, mainly for two 
reasons: 1) configuration is separate from code 2) it's in xml.

Grok tried to solve both of the issues above, but it never got complete 
feature parity with zcml (at least not in five.grok) and there is still 
no consensus on whether problem 1) is really a problem at all (the more 
I work with Plone, the more I like explicit configuration files to give 
overview for the code).

Could it be possible (optionally) to use cfg instead of zcml? AFAIK, 
nothing in zope.configuration (except xmlconfig-module) depends on xml.

The benefit would be that add-on developer could write configure.cfg:

[browser:page:uniquepostfix]
name = hello-world
for = *
class = .view.FooBar
permission = zope2.View

instead of configure.zcml



- configure.cfg instead of configure.zcml


I made a very naive experiment:

https://github.com/datakurre/collective.cfgconfig

Cheers,
Asko

------------------------------------------------------------------------------
Shape the Mobile Experience: Free Subscription
Software experts and developers: Be at the forefront of tech innovation.
Intel(R) Software Adrenaline delivers strategic insight and game-changing 
conversations that shape the rapidly evolving mobile landscape. Sign up now. 
http://pubads.g.doubleclick.net/gampad/clk?id=63431311&iu=/4140/ostg.clktrk
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.