[BlueBream] apidoc ? onlinehelp ? preference ?
ccomb at free.fr
Sun Apr 25 05:03:07 EDT 2010
Christophe Combelles a écrit :
> Baiju M a écrit :
>> The z.a.apidoc is there in KGS. But it is not configured in the
>> default project template. I think projects like ice.control can
>> configure it. Otherwise we can include a _new_ admin interface in the
>> next release by default.
> I agree.
> what I would like for BB 1.0 is just having the apidoc, without any admin interface.
>> IMO, the new admin interface should not depend on any community
>> packages, otherwise those packages should be added to core. Also the
>> admin interface should not register any view in the default layer.
> For the community packages I would like to add many of them in the community.cfg
> because I always end up using a lot of them, for instance:
I believe the community.cfg should even be included in the ZTK!
I'll ask zope-dev
>> Baiju M
>> On 4/23/10, Christophe Combelles <ccomb at free.fr> wrote:
>>> what about bringing back zope.app.apidoc ? It is a very useful tool during
>>> development and it allows to dynamically add other namespaces such as z3c,
>>> and even the project packages. There is probably a few changes to do in
>>> registrations. A very good thing would then be to move it to zope.apidoc
>>> There is a way to enable it only in devmode with zcml:condition="have
>>> I think we can provide at least two buildout files for this purpose, one for
>>> production, one for development using devmode and apidoc. It can be easily
>>> with the templating system currently included.
>>> If there is a way to do this without needing the templating, I would be +1
>>> remove the templating.
>>> Same question for zope.app.onlinehelp and zope.app.preference ?
>>> bluebream mailing list
>>> bluebream at zope.org
>> bluebream mailing list
>> bluebream at zope.org
> bluebream mailing list
> bluebream at zope.org
More information about the bluebream