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