Hi, I'd need a zope.schema field for blobs. Should this go directly to zope.schema or some third party package? Something like bla = zope.schema.Blob(title=...) would be nice to have. -- Christian Zagrodnick gocept gmbh & co. kg · forsterstrasse 29 · 06112 halle/saale www.gocept.com · fon. +49 345 12298894 · fax. +49 345 12298891
Hi there, Christian Zagrodnick wrote:
I'd need a zope.schema field for blobs. Should this go directly to zope.schema or some third party package?
Something like
bla = zope.schema.Blob(title=...)
would be nice to have.
If you mean using blobs for file storage, see megrok.form, which in turn uses collective.namedblobfile for the actual field and widget. Regards, Martijn
Hi Christian Regards Roger Ineichen _____________________________ END OF MESSAGE
-----Ursprüngliche Nachricht----- Von: zope-dev-bounces+dev=projekt01.ch@zope.org [mailto:zope-dev-bounces+dev=projekt01.ch@zope.org] Im Auftrag von Nikolay Kim Gesendet: Dienstag, 15. April 2008 22:29 An: zope-dev@zope.org Betreff: Re: [Zope-dev] Field for blobs?
On Tue, 2008-04-15 at 16:14 +0200, Christian Zagrodnick wrote:
Hi,
I'd need a zope.schema field for blobs. Should this go directly to zope.schema or some third party package?
there is z3c.schema package for various third party packages
If this widget doesn't depend on ZODB it's a good choice. If it depends on ZODB and other things it's pobably bad for someone who likes this widgets but does not use ZODB at all. Right now all widgets included in the z3c.widget depend only on: import re import zope.schema import zope.interfaces import z3c.i18n I think this is a very good choice and it whould be bad to depend on more components then that. The other option whould be to split every widget into it's own package and use z3c.widget as namespace package. What do you think? Regards Roger Ineichen
_______________________________________________ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
On Tue, 2008-04-15 at 17:37 +0200, Roger Ineichen wrote:
The other option whould be to split every widget into it's own package and use z3c.widget as namespace package.
What do you think?
i think we should split z3c.schema and z3c.widget to separate packages, so we can have one namespace for all third party fields and widgets
On 2008-04-16 10:01:30 +0200, Nikolay Kim <fafhrd@datacom.kz> said:
On Tue, 2008-04-15 at 17:37 +0200, Roger Ineichen wrote:
The other option whould be to split every widget into it's own package and use z3c.widget as namespace package.
What do you think?
i think we should split z3c.schema and z3c.widget to separate packages, so we can have one namespace for all third party fields and widgets
actually, when the __init__.py of z3c.schema would be a namespace __init__.py one could just add new packages w/o the need to split the z3c.schema up. Even though this might be a bit confusing. -- Christian Zagrodnick gocept gmbh & co. kg · forsterstrasse 29 · 06112 halle/saale www.gocept.com · fon. +49 345 12298894 · fax. +49 345 12298891
participants (4)
-
Christian Zagrodnick -
Martijn Faassen -
Nikolay Kim -
Roger Ineichen