[Checkins] SVN: z3c.formui/trunk/ Get ready for release.
Stephan Richter
srichter at cosmos.phy.tufts.edu
Wed Jan 23 16:53:18 EST 2008
Log message for revision 83130:
Get ready for release.
Changed:
_U z3c.formui/trunk/
U z3c.formui/trunk/CHANGES.txt
U z3c.formui/trunk/setup.py
U z3c.formui/trunk/src/z3c/formui/README.txt
U z3c.formui/trunk/src/z3c/formui/form.py
U z3c.formui/trunk/src/z3c/formui/tests.py
-=-
Property changes on: z3c.formui/trunk
___________________________________________________________________
Name: svn:ignore
- build
develop-eggs
dist
eggs
bin
parts
.installed.cfg
+ build
coverage
develop-eggs
dist
eggs
bin
parts
.installed.cfg
Modified: z3c.formui/trunk/CHANGES.txt
===================================================================
--- z3c.formui/trunk/CHANGES.txt 2008-01-23 21:51:11 UTC (rev 83129)
+++ z3c.formui/trunk/CHANGES.txt 2008-01-23 21:53:18 UTC (rev 83130)
@@ -2,41 +2,41 @@
CHANGES
=======
-Version 1.4.1dev (unreleased)
-----------------------------
+Version 1.4.1 (2008-01-23)
+--------------------------
-- ...
+- Fixed up meta-data and the release.
-Version 1.4.0 (2007-01-21)
--------------------------
+Version 1.4.0 (2008-01-21)
+--------------------------
-- Bug: added missing display IContentTemplate, otherwise we can run into a
- recursion in some case
+- Feature: Added subform content and layout template. This allows you to
+ configure real sub forms which do not render the form tag.
-- Bug: rename table macro argument from ``form-required-info`` to
- ``required-info``. The macro ``form-required-info`` did not exist.
+- Feature: Improve layout implementation, support built-in layout templates.
-- Feature: Added subform content and layout template. This allows you to
- configure real sub forms which do not render the form tag for sub forms.
+- Feature: Use ``IContentTemplate`` instead of ``IPageTemplate`` in layout
+ base classes. This will help to prevent running into recursion errors if
+ there is a missing layout template.
-- Feature: Improve layout implementation, support built in layout templates
+- Feature: Added form module which offers built-in layout support.
-- Feature: Use IContentTemplate instead of IPageTemplate in layout base
- classes. This will help to prevent running into recursion errors if there
- is a missing layout template.
+- Bug: Added missing display ``IContentTemplate``, otherwise we can run into a
+ recursion in some cases.
-- Feature: Added form module which offers built in layout support.
+- Bug: Renamed table macro argument from ``form-required-info`` to
+ ``required-info``. The macro ``form-required-info`` did not exist.
-- Added unittests for layout support
+- Bug: Added unit tests for layout support.
-- Added tests for layout macros
+- Bug: Added tests for layout macros.
-- Added tests for layout templates
+- Bug: Added tests for layout templates.
-Version 1.3.0 (8/24/2007)
--------------------------
+Version 1.3.0 (2007-08-24)
+--------------------------
- Refactoring: Update CSS classes to reflect latest changes to the widget
classes in ``z3c.form``.
@@ -50,23 +50,23 @@
Leist for the report.
-Version 1.2.0 (7/18/2007)
--------------------------
+Version 1.2.0 (2007-07-18)
+--------------------------
- Feature: The row div element now also has an id of the form
"<widget-id>-row".
-Version 1.1.1 (7/4/2007)
--------------------------
+Version 1.1.1 (2007-07-04)
+--------------------------
- Refactoring: Split up registrations for simpler management of UI
components. This also makes it easier to see for developers how to create a
new template for forms.
-Version 1.1.0 (6/29/2007)
--------------------------
+Version 1.1.0 (2007-06-29)
+--------------------------
- Feature: Registered all defined macros for each form template. Also, added
more slots to the templates providing more hooks for customization.
@@ -79,15 +79,15 @@
- Feature: Added support for groups to templates.
-Version 1.0.1 (6/22/2007)
--------------------------
+Version 1.0.1 (2007-06-22)
+--------------------------
- Bug: Make sure we use the id for the "for" attribute of the "label"
element and not the name. This has worked until recently, because the
name and id were the same, but they are different now.
-Version 1.0.0 (5/24/2007)
--------------------------
+Version 1.0.0 (2007-05-24)
+--------------------------
- Initial Release
Modified: z3c.formui/trunk/setup.py
===================================================================
--- z3c.formui/trunk/setup.py 2008-01-23 21:51:11 UTC (rev 83129)
+++ z3c.formui/trunk/setup.py 2008-01-23 21:53:18 UTC (rev 83130)
@@ -23,9 +23,9 @@
setup (
name='z3c.formui',
- version='1.4.1dev',
+ version='1.4.1',
author = "Stephan Richter, Roger Ineichen and the Zope Community",
- author_email = "zope3-dev at zope.org",
+ author_email = "zope-dev at zope.org",
description = "A set of initial UI components for z3c.form.",
long_description=(
read('README.txt')
@@ -44,7 +44,7 @@
'Operating System :: OS Independent',
'Topic :: Internet :: WWW/HTTP',
'Framework :: Zope3'],
- url = 'http://cheeseshop.python.org/pypi/z3c.formui',
+ url = 'http://pypi.python.org/pypi/z3c.formui',
packages = find_packages('src'),
include_package_data = True,
package_dir = {'':'src'},
Modified: z3c.formui/trunk/src/z3c/formui/README.txt
===================================================================
--- z3c.formui/trunk/src/z3c/formui/README.txt 2008-01-23 21:51:11 UTC (rev 83129)
+++ z3c.formui/trunk/src/z3c/formui/README.txt 2008-01-23 21:53:18 UTC (rev 83130)
@@ -40,7 +40,7 @@
>>> from zope.schema.fieldproperty import FieldProperty
>>> class Person(object):
... zope.interface.implements(IPerson)
- ...
+ ...
... name = FieldProperty(IPerson['name'])
... age = FieldProperty(IPerson['age'])
...
@@ -83,7 +83,7 @@
>>> addForm = PersonAddForm(root, divRequest)
-Since we have not specified a template yet, we have to do this now. We use our
+Since we have not specified a template yet, we have to do this now. We use our
div based form template:
>>> import os
@@ -103,7 +103,7 @@
... (zope.interface.Interface, IDivFormLayer),
... IContentTemplate)
-And let's define a layout template which simply calls the render method. For a
+And let's define a layout template which simply calls the render method. For a
more adavanced content/layout render concept see z3c.pagelet.
>>> import tempfile
@@ -316,7 +316,7 @@
Form Macros
-----------
-Load the confguration, which will make sure that all macros get registered
+Load the confguration, which will make sure that all macros get registered
correctly.
>>> from zope.configuration import xmlconfig
@@ -338,26 +338,26 @@
Div IContentTemplate
--------------------
-Create some dummy form discriminators for calling div layout templates and
+Create some dummy form discriminators for calling div layout templates and
macros and check the div IContentTemplates:
>>> objects = (addForm, divRequest)
>>> zope.component.getMultiAdapter(objects, IContentTemplate).filename
'...div-form.pt'
- >>> objects = (form.DisplayForm(None, None), divRequest)
+ >>> objects = (form.DisplayForm(None, None), divRequest)
>>> zope.component.getMultiAdapter(objects, IContentTemplate, '').filename
'...div-form-display.pt'
We offer the following named IContentTemplate:
- >>> objects = (form.DisplayForm(None, None), divRequest)
- >>> zope.component.getMultiAdapter(objects, IContentTemplate,
+ >>> objects = (form.DisplayForm(None, None), divRequest)
+ >>> zope.component.getMultiAdapter(objects, IContentTemplate,
... 'display').filename
'...div-form-display.pt'
- >>> objects = (form.DisplayForm(None, None), divRequest)
- >>> zope.component.getMultiAdapter(objects, IContentTemplate,
+ >>> objects = (form.DisplayForm(None, None), divRequest)
+ >>> zope.component.getMultiAdapter(objects, IContentTemplate,
... 'subform').filename
'...subform.pt'
@@ -367,8 +367,8 @@
There is one generic layout template for build sub forms:
- >>> objects = (form.DisplayForm(None, None), divRequest)
- >>> zope.component.getMultiAdapter(objects, ILayoutTemplate,
+ >>> objects = (form.DisplayForm(None, None), divRequest)
+ >>> zope.component.getMultiAdapter(objects, ILayoutTemplate,
... 'subform').filename
'...subform-layout.pt'
@@ -430,26 +430,26 @@
Table IContentTemplate
----------------------
-Create some dummy form discriminators for calling table layout templates and
+Create some dummy form discriminators for calling table layout templates and
macros and check the div IContentTemplates:
>>> objects = (addForm, tableRequest)
>>> zope.component.getMultiAdapter(objects, IContentTemplate, '').filename
'...table-form.pt'
- >>> objects = (form.DisplayForm(None, None), tableRequest)
+ >>> objects = (form.DisplayForm(None, None), tableRequest)
>>> zope.component.getMultiAdapter(objects, IContentTemplate, '').filename
'...table-form-display.pt'
We offer the following named IContentTemplate:
- >>> objects = (form.DisplayForm(None, None), tableRequest)
- >>> zope.component.getMultiAdapter(objects, IContentTemplate,
+ >>> objects = (form.DisplayForm(None, None), tableRequest)
+ >>> zope.component.getMultiAdapter(objects, IContentTemplate,
... 'display').filename
'...table-form-display.pt'
- >>> objects = (form.DisplayForm(None, None), tableRequest)
- >>> zope.component.getMultiAdapter(objects, IContentTemplate,
+ >>> objects = (form.DisplayForm(None, None), tableRequest)
+ >>> zope.component.getMultiAdapter(objects, IContentTemplate,
... 'subform').filename
'...subform.pt'
@@ -460,8 +460,8 @@
There is one generic layout template for build sub forms:
- >>> objects = (form.DisplayForm(None, None), tableRequest)
- >>> zope.component.getMultiAdapter(objects, ILayoutTemplate,
+ >>> objects = (form.DisplayForm(None, None), tableRequest)
+ >>> zope.component.getMultiAdapter(objects, ILayoutTemplate,
... 'subform').filename
'...subform-layout.pt'
@@ -552,7 +552,7 @@
>>> metaconfigure.registerType('macro', tales.MacroExpression)
and at least we need a pagelet renderer. By default we use the provider called
-´´PageletRenderer´´ defined in the z3c.pagelet package. Bubt right now, we
+``PageletRenderer`` defined in the z3c.pagelet package. Bubt right now, we
don't have a dependency to this package. So let's implement a simple renderer
and use them as a IContentProvider:
@@ -560,16 +560,16 @@
... zope.component.adapts(zope.interface.Interface,
... zope.publisher.interfaces.browser.IBrowserRequest,
... zope.interface.Interface)
- ...
+ ...
... def __init__(self, context, request, pagelet):
... self.__updated = False
... self.__parent__ = pagelet
... self.context = context
... self.request = request
- ...
+ ...
... def update(self):
... pass
- ...
+ ...
... def render(self):
... return self.__parent__.render()
@@ -581,7 +581,7 @@
>>> class PersonEditForm(form.EditForm):
... """Edit form including layout support. See z3c.formui.form."""
- ...
+ ...
... template = getPageTemplate('subform')
... layout = getLayoutTemplate('subform')
...
Modified: z3c.formui/trunk/src/z3c/formui/form.py
===================================================================
--- z3c.formui/trunk/src/z3c/formui/form.py 2008-01-23 21:51:11 UTC (rev 83129)
+++ z3c.formui/trunk/src/z3c/formui/form.py 2008-01-23 21:53:18 UTC (rev 83130)
@@ -29,7 +29,7 @@
class ContentTemplateMixin(object):
"""Use IContentTemplate instead of IPageTemplate.
-
+
This prevents us running into a recusrion because of mess up layout and
content templates. This is the default template interface if you use the
z3c.template directive.
Modified: z3c.formui/trunk/src/z3c/formui/tests.py
===================================================================
--- z3c.formui/trunk/src/z3c/formui/tests.py 2008-01-23 21:51:11 UTC (rev 83129)
+++ z3c.formui/trunk/src/z3c/formui/tests.py 2008-01-23 21:53:18 UTC (rev 83130)
@@ -28,7 +28,3 @@
setUp=testing.setUp, tearDown=testing.tearDown,
optionflags=doctest.NORMALIZE_WHITESPACE|doctest.ELLIPSIS),
))
-
-
-if __name__ == '__main__':
- unittest.main(defaultTest='test_suite')
More information about the Checkins
mailing list