On 12/1/05, Chris Withers <[EMAIL PROTECTED]> wrote:
> In this case, I think zopeschema.xml should be documentation enough,
> especially as any product author wanting to use this feature is going to
> have to write a component.xml at least ;-)
Actually, a product author isn't required to write a c
Fred Drake wrote:
I don't know that there's any real documentation for this. Feel free
to add some.
In this case, I think zopeschema.xml should be documentation enough,
especially as any product author wanting to use this feature is going to
have to write a component.xml at least ;-)
chee
On Wed, Nov 30, 2005 at 04:27:11PM -0500, Fred Drake wrote:
| On 11/30/05, Sidnei da Silva <[EMAIL PROTECTED]> wrote:
| > I haven't seen this being checked in at all, maybe it's in Tres
| > laptop?
|
| These were committed to the trunk before the 2.9 branch was created:
|
| --
On 11/30/05, Sidnei da Silva <[EMAIL PROTECTED]> wrote:
> I haven't seen this being checked in at all, maybe it's in Tres
> laptop?
These were committed to the trunk before the 2.9 branch was created:
r39652 | tseaver | 2005
On Wed, Nov 30, 2005 at 03:55:22PM -0500, Fred Drake wrote:
| On 11/30/05, Sidnei da Silva <[EMAIL PROTECTED]> wrote:
| > I have some product that would greatly benefit from being able to be
| > configured from within zope.conf. I don't want a separate
| > configuration file. Period.
|
| Tres Seav
On 11/30/05, Sidnei da Silva <[EMAIL PROTECTED]> wrote:
> I have some product that would greatly benefit from being able to be
> configured from within zope.conf. I don't want a separate
> configuration file. Period.
Tres Seaver and I implemented this during the Goldegg sprint in
Fredericksburg, w
This might be the third time I hit this issue, and I've always given
up before. I hope this is the last time.
I have some product that would greatly benefit from being able to be
configured from within zope.conf. I don't want a separate
configuration file. Period.
Why? Apache doesn't have separat
