David Pratt wrote:
Hi Carlo.
As a workaround to get objects into the db you can comment out the
following lines in checkName like this:
def checkName(self, name, container):
if isinstance(name, str):
name = unicode(name)
elif not isinstance(name, unicode):
Hi Jeff. Your approach is very interesting. There is lots room in Zope
for differences in the way applications are tackled to deliver on
requirements. My feeling is that explicit object metadata and some of
the content-management-esque concepts in Zope fit prominently into the
future of the web
Hi Jeff. Good points. I can really add anything more to this other than
I believe there are great possibilities working with Zope 3 in something
that is more tightly bound or not. Zope 3's architecture will be become
as flexible as python itself and it future packaging choices will only
undersc
Hi Roger. This is really interesting. It would be good to see a very
small demo of these nice packages you have been contributing - something
that would put together the minimal layer, menu package, and a few
basic viewlets just to give folks a basic idea of what can be acheived
'minimally'. A
Hi David
[...]
> Hi Roger. This is really interesting. It would be good to see
> a very small demo of these nice packages you have been
> contributing - something
> that would put together the minimal layer, menu package,
> and a few basic viewlets just to give folks a basic idea of
> what c
Jeff,
Before everything else, thank you very much for sharing your thoughts
and experience: as a newcomer, I found them very valuable.
Hm. It seems like a NameChooser should *somehow* be giving you a
usable name. That pair::
container[name] = content
return container[name]
seems redun
On Monday 14 August 2006 05:08, Carlo Cardelli wrote:
> > I think that my company's recent experiences with Zope and SQLAlchemy
>
> > show that the fundamentals of Zope can be terrific toolkit for rich
> > object oriented RDBMS / Business Object backed applications that have
> > nothing to do with
Roger Ineichen wrote:
Hi David
[...]
Hi Roger. This is really interesting. It would be good to see
a very small demo of these nice packages you have been
contributing - something
that would put together the minimal layer, menu package,
and a few basic viewlets just to give folks a basic ide
On 8/10/06, Carlo Cardelli <[EMAIL PROTECTED]> wrote:
Once skipped this, the process halted while adding the 'blank' object to
the db: in zope.app.container.browser.adding, in the method add(), the
following lines failed:
container[name] = content
... one ininfluent-for-this-p
On 8/12/06, David Pratt <[EMAIL PROTECTED]> wrote:
Hi Jeff. Your approach is very interesting. There is lots room in Zope
for differences in the way applications are tackled to deliver on
requirements. My feeling is that explicit object metadata and some of
the content-management-esque concepts i
Hi Jeff
[...]
> With the ZMI, I end up asking "is this the UI I want to
> deliver to my customer?" And the answer is rarely "yes!" I
> feel like I have to arm wrestle a lot more to turn off and
> hide features. I still don't really understand how the 'Add'
> menu works.
Did you see the layer
On 8/14/06, Carlo Cardelli <[EMAIL PROTECTED]> wrote:
> I think that my company's recent experiences with Zope and SQLAlchemy
> show that the fundamentals of Zope can be terrific toolkit for rich
> object oriented RDBMS / Business Object backed applications that have
> nothing to do with content
12 matches
Mail list logo
