On Mon, Jul 04, 2005 at 12:19:59PM +1000, Stuart Bishop wrote:
| Sidnei da Silva wrote:
|
| > Right, seems that's my only choice for the time being.
| >
|
| We currently do this in our 'start Z3' script before any of the Zope imports
| are done:
|
| # Disgusting hack to use our extended config
Sidnei da Silva wrote:
> Right, seems that's my only choice for the time being.
>
We currently do this in our 'start Z3' script before any of the Zope imports
are done:
# Disgusting hack to use our extended config file schema rather than the
# Z3 one. TODO: Add command line options or other to
On 7/1/05, Jens Vagelpohl <[EMAIL PROTECTED]> wrote:
> That just has the disadvantage that you're increasing the number of
> configuration files to maintain in an instance. If it's imported and
> used in zope.conf at leaast there's just one file to deal with...
This is true. Is that really import
On Thu, Jun 30, 2005 at 11:58:08PM -0400, Fred Drake wrote:
| On 6/30/05, Sidnei da Silva <[EMAIL PROTECTED]> wrote:
| > Gosh, that looks too nice to be true. I will try that out tomorrow and
| > write out a how-to on zope.org if it works out.
|
| It is too good to be true; sorry.
|
| Well, it is
On Fri, Jul 01, 2005 at 08:27:02AM -0400, Fred Drake wrote:
| On 7/1/05, Chris McDonough <[EMAIL PROTECTED]> wrote:
| > FWIW, I don't know if it helps at all, but there's a concrete example of
| > allowing a 3rd-party product to add a section to zope.conf via %import
| > in the ClockServer product
On Fri, 2005-07-01 at 10:54 -0300, Sidnei da Silva wrote:
> | The general case of being able to add a section (or anything else)
> | isn't covered by the current implementation.
>
> That is right. I've just learnt that the hard way *wink*.
Oh. ;-)
- C
___
On 7/1/05, Chris McDonough <[EMAIL PROTECTED]> wrote:
> FWIW, I don't know if it helps at all, but there's a concrete example of
> allowing a 3rd-party product to add a section to zope.conf via %import
> in the ClockServer product at
> http://www.plope.com/software/ClockServer/ . It sounds from yo
FWIW, I don't know if it helps at all, but there's a concrete example of
allowing a 3rd-party product to add a section to zope.conf via %import
in the ClockServer product at
http://www.plope.com/software/ClockServer/ . It sounds from your
description exactly like what you want to do, although it a
On 1 Jul 2005, at 04:58, Fred Drake wrote:
Since using an additional configuration file is possible (and quite
easy in Zope 2, since the location of the instance is so easy to
discern, I'm not convinced it's actually important to support
embedding the configuration for 3rd-party components into
On 6/30/05, Sidnei da Silva <[EMAIL PROTECTED]> wrote:
> Gosh, that looks too nice to be true. I will try that out tomorrow and
> write out a how-to on zope.org if it works out.
It is too good to be true; sorry.
Well, it is true, but it's not what you're looking for. You can't use
it to extend t
On Thu, Jun 30, 2005 at 10:21:40PM -0400, Andrew Langmead wrote:
| The config file syntax has a "%import" directive that allows you to
| add another package to handle certain config directive.
| That package than can contain a an XML file that describes your new
| configuration directives and t
I'm looking back and forth between the Zope and ZConfig sources and
documentation to see if I can figure out how to have a Product (or a
python package) to extend Zope's ZConfig schema
(a.k.a. Zope/Startup/zopeschema.xml) without having to reach into the
guts of ZConfig.
The config file syntax
Hello,
I've been hitting my head against the wall for a few hours already, so
I thought it would be a good time to ask before the house falls apart
*wink*.
I'm looking back and forth between the Zope and ZConfig sources and
documentation to see if I can figure out how to have a Product (or a
pyth
13 matches
Mail list logo
