[BlueBream] ftesting.zcml

Ilshad Khabibullin astoon.net at gmail.com
Tue Sep 21 04:33:53 EDT 2010


+1 for good notes.

2010/9/21 Baiju M <baiju.m.mail at gmail.com>

> On Mon, Sep 20, 2010 at 2:42 PM, Christophe Combelles <ccomb at free.fr>
> wrote:
> > Le 20/09/2010 00:04, Ilshad Khabibullin a écrit :
> >> (I wrote about .zcml files)
> >>
> >> 2010/9/20 Ilshad Khabibullin <astoon.net <http://astoon.net>@gmail.com
> >> <http://gmail.com>>
> >>
> >>     Now we have (in trunk) dublication in etc/ - two absolutely
> >>     identical files. Let's discuss about it.
> >>
> >>     When I described how I doing, really, I'm doing two different files,
> >>     and it helps me to do not create too complex zcml with many
> >>     "conditions". This just conveniently.
> >>
> >>     For example, it can be more these files (3 instead of 2) when we
> >>     need fully tested staging site, and etc. Also, "manager" principal
> >>     turned on, often, in deploy mode to setup site in first time. Also,
> >>     deploy and debug modes have different ports, usually. And all this -
> >>     under version control systems, let's do not forget about this.
> >>
> >>     But I do not insist that it must be in the standard template. Maybe
> >>     it's not everyone like that. And in any case we should not allow
> >>     dublication in this very important package, because dublication
> >>     looks ugly anyway...
> >
> > we have several options:
> >
> > - <include deploy.zcml> from debug.zcml to avoid duplication
> > - or add a note in the debug.zcml saying this file can be customized for
> debug
> > (and maybe a minimal customization)
> > - or both
> > - or remove the debug file and keep just a site.zcml
> >
> > btw, for point 2, we could remove the admin manager from the deploy.zcml,
> and
> > just keep it in debug. I don't like having the manager password for
> deployment
> > in a versionned file because people can forget to remove it.
> > That would mean we could authenticate as global manager only in
> development mode.
>
> +1 for second approach (add a note in the debug.zcml saying this file
> can be customized for debug)
>
> +0 for removing global manager principal from deploy.zcml
>
> The basic idea for two ZCML files is to show the best practice so that
> a beginner can
> organize their code in a better way.  So, even if the content is same,
> that's fine.
> But adding a comment in each file would help the user to understand
> the reasoning.
>
> Regards,
> Baiju M
> _______________________________________________
> bluebream mailing list
> bluebream at zope.org
> https://mail.zope.org/mailman/listinfo/bluebream
>



-- 
Ilshad R. Khabibullin
http://astoon.zwiki.org
+7 922 600 56 06
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mail.zope.org/pipermail/bluebream/attachments/20100921/7c2a6bef/attachment.html 


More information about the bluebream mailing list