Hi Christophe,<br><br><div class="gmail_quote">2010/4/23 Christophe Combelles <span dir="ltr"><<a href="mailto:ccomb@free.fr" target="_blank">ccomb@free.fr</a>></span><br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
hi,<br>
<br>
what about bringing back zope.app.apidoc ? It is a very useful tool during<br>
development and it allows to dynamically add other namespaces such as z3c, zc,<br>
and even the project packages. There is probably a few changes to do in apidoc<br>
registrations. A very good thing would then be to move it to zope.apidoc later.<br>
</blockquote><div> <br>We need this, it is powerfull tool, and developer can include apidoc in any moment. But I think, developer needs these features mostly in _some_context_, i.e. to inspect components "on fly", not just to see docs. The more so the documentation should be moved out the doctests in future, yes? In this case displaying them via wsgi-server is not the best idea... there are editors, Sphinx, etc. Summary, lets' divide:<br>
<br>1) Need to see dynamic data - i.e. components, relations between them.<br>2) Need to see static documentation.<br><br>For dynamic data - inspect registry. Sometimes, we dive into exist zope3 project and <span><span style="background-color: rgb(255, 255, 255);" title="я чуствую, что где-то зарегистрирован адаптер, но где он, черт побери">"I am feeling that somewhere registered adapter, but where he, is the devil</span></span>...".<br>
<br></div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
There is a way to enable it only in devmode with zcml:condition="have devmode".<br>
I think we can provide at least two buildout files for this purpose, one for<br>
production, one for development using devmode and apidoc. It can be easily done<br>
with the templating system currently included.<br>
</blockquote><div><br>BlueBream is server-side software. When I create project, I need deploy this project on my sandbox and on server, in any case. So, I spend time for production-server-boilerplates, copy-past from older projects :)<br>
<br>Then we need decide:<br>1) We provide the simple and policy-free template<br>2) Or we provide powerful template for server-side projects. It can be relatively polcy-free, I think.<br><br></div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
</blockquote><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
If there is a way to do this without needing the templating, I would be +1 to<br>
remove the templating.<br>
<br></blockquote><div> </div><div>alternative - zcml in .cfg files - here is example: <a href="http://paste.lisp.org/+23S0" target="_blank">http://paste.lisp.org/+23S0</a><br><br>But it seems, templates is better... <span style="background-color: rgb(255, 255, 255);">I'm not sure exact...</span><span style="background-color: rgb(255, 255, 255);"></span> Personally for me, these big and mess buildout.cfg files is bad. And system administrators not liked this, I know (because we need provide instructions how to edit these files, remove or add bootstrap manager and etc.)<br>
<br></div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<br>
Same question for zope.app.onlinehelp and zope.app.preference ?<br>
_______________________________________________<br>
bluebream mailing list<br>
<a href="mailto:bluebream@zope.org" target="_blank">bluebream@zope.org</a><br>
<a href="https://mail.zope.org/mailman/listinfo/bluebream" target="_blank">https://mail.zope.org/mailman/listinfo/bluebream</a><br>
</blockquote></div><br><br clear="all"><br>-- <br>Ilshad R. Khabibullin<br><a href="http://astoon.zwiki.org" target="_blank">http://astoon.zwiki.org</a><br>+7 922 600 56 06<br>