Hi, list,
I am just trying to migrate a existing application from Zope2 to
Zope3, and had to feel around for my ways to do things correctly.
I have following view.pt snippet:
span tal:replace=context/item_nameItem Name/span
pspecification: span tal:replace=context/specification //p
pPrice: span
Hi, everyone,
This must be novice question:
Is there a package providing relational database based authentication
service for zope 3 already lying around somewhere or do I have write
one?
And how does one connect a login form with the authentication service?
In Zope 2 one can have lots products
On Fri, Aug 24, 2007 at 09:45:57PM +0800, Yuan HOng wrote:
Hi, list,
I am just trying to migrate a existing application from Zope2 to
Zope3, and had to feel around for my ways to do things correctly.
I have following view.pt snippet:
span tal:replace=context/item_nameItem Name/span
There's a pluggable system ... Look in:
zope/app/authentication/README.txt
Or online:
http://svn.zope.org/*checkout*/zope.app.authentication/trunk/src/zope/app/authentication/README.txt?rev=77044
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Yuan
I'm new to zope3 and have been writing an application backed by a
relational database. I wanted to created a IContainer implementation
which essential provides a view of items in the database, but there is
no need for to make the container instances manageable through the ZMI
or persistent in
I'm trying to make a skin for my program, but am having trouble getting the
input forms converted over. I have a skin created by a graphic artist, my
problem now is figuring out how to change the cssClass attribute for all my
widgets.
Currently my forms are registered like this:
Drew Smathers a écrit :
I'm new to zope3 and have been writing an application backed by a
relational database. I wanted to created a IContainer implementation
which essential provides a view of items in the database, but there is
no need for to make the container instances manageable through
On 8/24/07, Christophe Combelles [EMAIL PROTECTED] wrote:
My advice would be to use a simple persistent object and store some stuffs in
it
(sql query?), so you can easily traverse to it and to its view.
As long as the object doesn't store any data in the ZODB, there's no
reason to store it
You don't really need to implement a container, you could just write a non
persistent object (not derived from Persistent), and create a view on it.
But the next problem is to be able to traverse to this object, since traversal
starts from the root of the zodb.
I thought a Container was a
