Hi all,
Is BjornT about?
I have been working with photo and photoslide packages
- got them working now with 3.3 branch
- made resizeUtility schema field a vocabaulary choice
Other features I'm beginning on:
- make displayIds sizes editable
- offer filesystem storage as alternative to zodb
-
On Thu, Sep 14, 2006 at 02:41:28PM +0700, Darryl Cousins wrote:
Hi all,
Is BjornT about?
Yes, I'm here.
I have been working with photo and photoslide packages
- got them working now with 3.3 branch
- made resizeUtility schema field a vocabaulary choice
Other features I'm beginning
Hi,
I'm starting to have lots of schemas around. They are mostly for
view/add/edit forms, based on the entity (content object's) schema.
That means they mostly have the same fields with mostly the same
properties.
Adding field to a schema is piece of cake. Subclass the original,
add
the
I see that zope.app.introspector Will be gone in 3.3. [sic].
To help on this, I would like to commit a patch on `trunk` to remove dependency
of API doc on this deprecated package; see below.
If someone want to keep backward compatibility on this permission, I can do
something more complex. If
On Thursday 14 September 2006 05:05, Florent Xicluna wrote:
To help on this, I would like to commit a patch on `trunk` to remove
dependency of API doc on this deprecated package; see below.
If someone want to keep backward compatibility on this permission, I can do
something more complex. If
Florent Xicluna wrote:
I see that zope.app.introspector Will be gone in 3.3. [sic].
:(
We should remove it from the trunk.
To help on this, I would like to commit a patch on `trunk` to remove dependency
of API doc on this deprecated package; see below.
If someone want to keep backward
Hi Darryl
On 14.09.2006, at 09:41, Darryl Cousins wrote:
Hi all,
Is BjornT about?
I have been working with photo and photoslide packages
- got them working now with 3.3 branch
- made resizeUtility schema field a vocabaulary choice
Other features I'm beginning on:
- make displayIds sizes
Philipp von Weitershausen philipp at weitershausen.de writes:
We should remove it from the trunk.
OK
For backward compatibility, I suggest we redefine
zope.app.introspector.Introspect to zope.app.apidoc.UseAPIDoc via
meta:redefinePermission.
Good point. I did not know this directive.
On Sep 14, 2006, at 5:00 AM, adamg wrote:
I'm starting to have lots of schemas around. They are mostly for
view/add/edit forms, based on the entity (content object's) schema.
That means they mostly have the same fields with mostly the same
properties.
Adding field to a schema is piece of
See me response to your earlier mail.
On Sep 14, 2006, at 5:10 AM, Adam Groszer wrote:
Hi,
I'm starting to have lots of schemas around. They are mostly for
view/add/edit forms, based on the entity (content object's) schema.
That means they mostly have the same fields with mostly the same
Dear Zope3-dev community,
As you know, the Open Source Software (OSS) phenomenon is gaining
momentum and is increasingly viewed as an alternative to traditional
software development. Indeed, OSS projects have generated some of the
most sophisticated development in computer technology (Such as
Cheers Bernd,
Yeah. I spent a couple of hours today to build an extimage object using
z3c.extfile. Tests work very nicely.
Thanks for the pointer to z3c.image. I'll co the package now.
Sincere regards,
Darryl
On Thu, 2006-09-14 at 11:38 +0200, Bernd Dorn wrote:
- offer filesystem storage as
12 matches
Mail list logo