Re: Could it be possible to support configuring with *.cfg instead of *.zcml?
Domen Kožar <[email protected]>
| Newsgroups | gmane.comp.web.zope.plone.devel |
|---|---|
| Message-ID | <CAMvcdZS9T82Xubaj5-qVOJT8Or2f77xHnr6MrpYSLx5t3C0okg@mail.gmail.com> |
Introducing another configuration style to Plone core doesn't make anything easier. However, I would argue that using venusian as declarative style configuration to replace grok is a step forward. For new projects, those who favour declarative style configuration could use venusian as a replacement of zcml and when the community grows, the debate can go further. One very big good plus of this experiment is that Plone will converge with Pyramid stack, at least easing adoption of Python 3. On Fri, Nov 29, 2013 at 10:59 AM, Martin Aspeli <[email protected]> wrote: > For what it's worth the pyramid "scan" approach is inspired by and quite > similar to the Martian/grokcore approach. The main difference is that > pyramid kicks it all off in Python as you create a config state machine > imperatively. > Venusian is a simplification of Martian: decorators are deferred: information is later collected during "scan" phase and configured appropriately. And most importantly - it's very well documented. ------------------------------------------------------------------------------ Rapidly troubleshoot problems before they affect your business. Most IT organizations don't have a clear picture of how application performance affects their revenue. With AppDynamics, you get 100% visibility into your Java,.NET, & PHP application. Start your 15-day FREE TRIAL of AppDynamics Pro! http://pubads.g.doubleclick.net/gampad/clk?id=84349351&iu=/4140/ostg.clktrk _______________________________________________ Plone-developers mailing list Plone-developers-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org https://lists.sourceforge.net/lists/listinfo/plone-developers