-
zope.publisher-4.3.2-1.lbn25.noarch
zope.publisher allows you to publish Python objects on the web. It
has support for plain HTTP/WebDAV clients, web browsers as well as
XML-RPC and FTP clients. Input and output streams are represented by
request and response objects which allow for easy client interaction
from Python. The behaviour of the publisher is geared towards WSGI
compatibility.
Located in
LBN
/
…
/
Plone and Zope
/
BastionLinux 19
-
zope.ramcache-1.0-2.lbn13.noarch
Zope RAM Cache
Located in
LBN
/
…
/
Plone and Zope
/
BastionLinux 13
-
zope.ramcache-2.2.0-1.lbn25.noarch
This package provides a RAM-based cache implementation for Zope.
Located in
LBN
/
…
/
Plone and Zope
/
BastionLinux 25
-
zope.ramcache-2.2.0-1.lbn25.noarch
This package provides a RAM-based cache implementation for Zope.
Located in
LBN
/
…
/
Plone and Zope
/
BastionLinux 19
-
zope.rdb-3.5.0-2.lbn13.noarch
Zope RDBMS transaction integration
Located in
LBN
/
…
/
Plone and Zope
/
BastionLinux 13
-
zope.rdb-3.5.0-2.lbn25.noarch
Zope RDBMS transaction integration
Located in
LBN
/
…
/
Plone and Zope
/
BastionLinux 25
-
zope.rdb-3.5.0-2.lbn25.noarch
Zope RDBMS transaction integration
Located in
LBN
/
…
/
Plone and Zope
/
BastionLinux 19
-
zope.schema-4.2.2-1.lbn13.noarch
==============
Zope 3 Schemas
==============
Introduction
------------
Schemas extend the notion of interfaces to detailed descriptions of Attributes
(but not methods). Every schema is an interface and specifies the public
fields of an object. A *field* roughly corresponds to an attribute of a
python object. But a Field provides space for at least a title and a
description. It can also constrain its value and provide a validation method.
Besides you can optionally specify characteristics such as its value being
read-only or not required.
Zope 3 schemas were born when Jim Fulton and Martijn Faassen thought
about Formulator for Zope 3 and PropertySets while at the Zope 3
sprint at the Zope BBQ in Berlin. They realized that if you strip
all view logic from forms then you have something similar to interfaces. And
thus schemas were born.
Located in
LBN
/
…
/
Plone and Zope
/
BastionLinux 13
-
zope.schema-4.9.3-1.lbn19.noarch
==============
Zope 3 Schemas
==============
Introduction
------------
Schemas extend the notion of interfaces to detailed descriptions of Attributes
(but not methods). Every schema is an interface and specifies the public
fields of an object. A *field* roughly corresponds to an attribute of a
python object. But a Field provides space for at least a title and a
description. It can also constrain its value and provide a validation method.
Besides you can optionally specify characteristics such as its value being
read-only or not required.
Zope 3 schemas were born when Jim Fulton and Martijn Faassen thought
about Formulator for Zope 3 and PropertySets while at the Zope 3
sprint at the Zope BBQ in Berlin. They realized that if you strip
all view logic from forms then you have something similar to interfaces. And
thus schemas were born.
Located in
LBN
/
…
/
Plone and Zope
/
BastionLinux 19
-
zope.schema-4.9.3-1.lbn25.noarch
==============
Zope 3 Schemas
==============
Introduction
------------
Schemas extend the notion of interfaces to detailed descriptions of Attributes
(but not methods). Every schema is an interface and specifies the public
fields of an object. A *field* roughly corresponds to an attribute of a
python object. But a Field provides space for at least a title and a
description. It can also constrain its value and provide a validation method.
Besides you can optionally specify characteristics such as its value being
read-only or not required.
Zope 3 schemas were born when Jim Fulton and Martijn Faassen thought
about Formulator for Zope 3 and PropertySets while at the Zope 3
sprint at the Zope BBQ in Berlin. They realized that if you strip
all view logic from forms then you have something similar to interfaces. And
thus schemas were born.
Located in
LBN
/
…
/
Plone and Zope
/
BastionLinux 25
