Zope-Announce June 2007

zope-announce@zope.dev

4 participants
5 discussions

z3c.form 1.4.0, z3c.formui 1.1.0, and z3c.formdemo 1.2.0 released!
by Stephan Richter 29 Jun '07

29 Jun '07

Hello everyone, again thanks to the great feedback we received -- especially from David Pratt, Roy Mathew, and Joachim Werner -- we were able to fine-tune our new form framework even more to make it as robust of a foundation as possible for your projects! New features include group support, fully internationalized widgets for number and calendar fields, a richer select widget, refined form templates, and of course a new demo! BTW, congratulations to Roger who became father for the third time last weekend! Again for the curious and impatient ... --------------------------------------- There is also a new demo, of course! The "Questionnaire" demo provides a form for filling out a simple questionaire about someones Zope community involvement and then provides a very simple results page. Technically this demo (available for the DIV- and Table-based layouts) demonstrates the usage of groups, a new feature of this release, as well as writing attribute value adapters. To run the demos do the following:: $ svn co svn://svn.zope.org/repos/main/z3c.formdemo/trunk formdemo $ cd formdemo $ python bootstrap.py $ ./bin/buildout -N $ ./bin/demo fg Now you can access the demo under: http://localhost:8080/ On the Javascript Front ----------------------- Paul has made some great progress recently and we have now two demos working, including a fully Javascript-driven calculator. I'll leave it up to Paul to decide whether he wants to make an announcement, but he will be definitely promoting his work at EuroPython! <secret>To see the demos: Replace "formdemo" with "formjsdemo" and follow the instructions above.</secret> Changes ------- z3c.form ~~~~~~~~ - Feature: The select widget grew a new ``prompt`` flag, which allows you to explicitely request a selection prompt as the first option in the selection (even for required fields). When set, the prompt message is shown. Such a prompt as option is common in Web-UIs. - Feature: Allow "no value message" of select widgets to be dynamically changed using an attribute value adapter. - Feature: Internationalized data conversion for date, time, date/time, integer, float and decimal. Now the locale data is used to format and parse those data types to provide the bridge to text-based widgets. While those features require the latest zope.i18n package, backward compatibility is provided. - Feature: All forms now have an optional label that can be used by the UI. - Feature: Implemented groups within forms. Groups allow you to combine a set of fields/widgets into a logical unit. They were designed with ease of use in mind. - Feature: Button Actions -- in other words, the widget for the button field -- can now be specified either as the "actionFactory" on the button field or as an adapter. - Bug: Recorded all public select-widget attributes in the interface. z3c.formui ~~~~~~~~~~ - Feature: Registered all defined macros for each form template. Also, added more slots to the templates providing more hooks for customization. - Feature: Added a macro/slot for the "required info", which explains how required fields are marked. - Feature: Added support for form labels. - Feature: Added support for groups to templates. z3c.formdemo ~~~~~~~~~~~~ - Feature: Added new field "promptChoiceField" to the "All Widgets" demo demonstrating the prompt message of the select widget. - Feature: Increased the integer default value of "All Widgets" demo to show off our new internationalized converter. - Feature: Made ``bytesField`` and ``passwordField`` non-required, since they do not show their default values prohibiting the form to successfully submit, which can be annoying when playing around. - Feature: New "Questionnaire" demo shows how to use groups effectively. It also demonstrates how the label of buttons and widgets can be changed using attribute value adapters. Enjoy! Regards, Stephan -- Stephan Richter CBU Physics & Chemistry (B.S.) / Tufts Physics (Ph.D. student) Web2k - Web Software Design, Development and Training

1 0

z3c.form 1.3.0, z3c.formui 1.0.1, and z3c.formdemo 1.1.0 released!
by Stephan Richter 22 Jun '07

22 Jun '07

Hello everyone, Roger and I have received a great deal of feedback about the z3c.form* packages. Several people reported that they immediately started using it for their development. Thanks to those people, we were able to identify many bugs and determined new features. The result is a new round of releases! Again for the curious and impatient ... --------------------------------------- We have added two more demos: * An "Address Book" implements a non-trivial example of an address book, including multiple addresses and E-mails. It demonstrates the use of sub-forms, writing custom widgets and composite content. * An "SQL Message" demo reimplemnets the simple "Hello World!" demo only using queries to the Gadfly database. The example adds to the original demo by also providing a message overview screen, since the ZMI is not helpful for pure SQL data. To run the demos do the following:: $ svn co svn://svn.zope.org/repos/main/z3c.formdemo/trunk formdemo $ cd formdemo $ python bootstrap.py $ ./bin/buildout -N $ ./bin/demo fg Now you can access the demo under: http://localhost:8080/ Note: Python's Cheeseshop seems to be extremely slow today, so this might take a while. Alternatively, you can use Zope's distribution server: http://download.zope.org/distribution. On the Javascript Front ----------------------- Paul Carduner, as part of his GSOC project, is developing a super-cool extension to the z3c.form* packages that will make it very easy for the Python developer to write AJAX-driven applications. My hope is that Paul will have the first iteration and a demo done in a few weeks! So stay tuned... Changes ------- z3c.form ~~~~~~~~ - Feature: In an edit form applying the data and generating all necessary messages was all done within the "Apply" button handler. Now the actual task of storing is factored out into a new method called "applyChanges(data)", which returns whether the data has been changed. This is useful for forms not dealing with objects. - Feature: Added support for ``hidden`` fields. You can now use the ``hidden`` mode for widgets which should get rendered as ``<input type="hidden" />``. Note: Make sure you use the new formui templates which will avoid rendering labels for hidden widgets or adjust your custom form macros. - Feature: Added ``missing_value`` support to data/time converters - Feature: Added named vocabulary lookup in ``ChoiceTerms`` and ``CollectionTerms``. - Implemented support for ``FileUpload`` in ``FileWidget``. * Added helper for handling ``FileUpload`` widgets: + ``extractContentType(form, id) Extracts the content type if ``IBytes``/``IFileWidget`` was used. + ``extractFileName(form, id, cleanup=True, allowEmtpyPostFix=False)`` Extracts a filename if ``IBytes``/``IFileWidget`` was used. Uploads from win/IE need some cleanup because the filename includes also the path. The option ``cleanup=True`` will do this for you. The option ``allowEmtpyPostFix`` allows you to pass a filename without extensions. By default this option is set to ``False`` and will raise a ``ValueError`` if a filename doesn't contain an extension. * Created afile upload data converter registered for ``IBytes``/``IFileWidget`` ensuring that the converter will only be used for fiel widgets. The file widget is now the default for the bytes field. If you need to use a text area widget for ``IBytes``, you have to register a custom widget in the form using:: fields['foobar'].widgetFactory = TextWidget - Feature: Originally, when an attribute access failed in Unauthorized or ForbiddenAttribute exceptions, they were ignored as if the attribute would have no value. Now those errors are propagated and the system will fail providing the developer with more feedback. The datamanager also grew a new ``query()`` method that returns always a default and the ``get()`` method propagates any exceptions. - Feature: When writing to a field is forbidden due to insufficient priviledges, the resulting widget mode will be set to "display". This behavior can be overridden by explicitely specifying the mode on a field. - Feature: Added an add form implementation against ``IAdding``. While this is not an encouraged method of adding components, many people still use this API to extend the ZMI. - Feature: The ``IFields`` class' ``select()`` and ``omit()`` method now support two ketword arguments "prefix" and "interface" that allow the selection and omission of prefixed fields and still specify the short name. Thanks to Nikolay Kim for the idea. - Feature: HTML element ids containing dots are not very good, because then the "element#id" CSS selector does not work and at least in Firefox the attribute selector ("element[attr=value]") does not work for the id either. Converted the codebase to use dashes in ids instead. - Bug/Feature: The ``IWidgets`` component is now an adapter of the form content and not the form context. This guarantees that vocabulary factories receive a context that is actually useful. - Bug: The readonly flag within a field was never honored. When a field is readonly, it is displayed in "display" mode now. This can be overridden by the widget manager's "ignoreReadonly" flag, which is necessary for add forms. - Bug: The mode selection made during the field layout creation was not honored and the widget manager always overrode the options providing its value. Now the mode specified in the field is more important than the one from the widget manager. - Bug: It sometimes happens that the sequence widget has the no-value token as one element. This caused ``displayValue()`` to fail, since it tried to find a term for it. For now we simply ignore the no-value token. - Bug: Fixed the converter when the incoming value is an empty string. An empty string really means that we have no value and it is thus missing, returning the missing value. - Bug: Fix a slightly incorrect implementation. It did not cause any harm in real-world forms, but made unit testing much harder, since an API expectation was not met correctly. - Bug: When required selections where not selected in radio and checkbox widgets, then the conversion did not behave correctly. This also revealed some issues with the converter code that have been fixed now. - Bug: When fields only had a vocabulary name, the choice terms adaptation would fail, since the field was not bound. This has now been corrected. - Documentation: Integrated English language and content review improvements by Roy Mathew in ``form.txt``. z3c.formui ~~~~~~~~~~ - 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. z3c.formdemo ~~~~~~~~~~~~ - Feature: New "SQL Message" demo shows how ``z3c.form`` can be used with non-object data. Specificically, this small application demonstrates using a Gadfly database using pure SQL calls without any ORM. - Feature: New "Address Book" demo that demonstrates more complex use cases, such as subforms, composite widgets, and mappings/lists Enjoy! Regards, Stephan -- Stephan Richter CBU Physics & Chemistry (B.S.) / Tufts Physics (Ph.D. student) Web2k - Web Software Design, Development and Training

1 0

[ANN] SQLAlchemyDA 0.3.0 released - a generic database adapter for Zope 2
by Andreas Jung 16 Jun '07

16 Jun '07

I am pleased to announce the first public release of SQLAlchemyDA V 0.3.0 Download: --------- <http://opensource.zopyx.com/software/sqlalchemyda/releases/0.3.0> What is SQLAlchemyDA? --------------------- SQLAlchemyDA is generic database adapter for ZSQL methods. Since it is based on SQLAlchemy, SQLAlchemyDA supports all databases out-of-the box that are supported by SQLAlchemy (Postgres, MySQL, Oracle, SQLite, MS-SQL, Firebird, Informix). Changes in 0.3.0: - fixed some security assertions - added "Test" tab for executing SQL queries directly - better error handling for ZMI screens - no longer depending on a pre-registered SQLAlchemy wrapper. SQLAlchemyDA now accepts (as any other DA) a DSN as property 'dsn' - DSN can be passed through the add form - redirect directly to "Info" tab after creating an instance through the ZMI - catching some low-level exceptions from the sqlite interface in order to make it work with SQLite - new properties 'transactional' and 'quoting_style' - improved support for Oracle and MySQL - SQLAlchemyDA no longer provides access to mapper related functionalities. It now acts as a DA for executing SQL statements *only*. - fixed unregistration code for a wrapper (hopefully works with Zope 2.8 or higher) - updated documentation Requirements: ------------- - Zope 2.8+, Zope 3.3+ - SQLAlchemy 0.3.X - z3c.sqlalchemy 1.0.5 + License ======= SQLAlchemyDA is licensed under the Zope Public License 2.1. See LICENSE.txt. This release has been funded by Renovis, SF, USA. Andreas Jung -- ZOPYX Ltd. & Co. KG - Charlottenstr. 37/1 - 72070 Tübingen - Germany Web: www.zopyx.com - Email: info(a)zopyx.com - Phone +49 - 7071 - 793376 Registergericht: Amtsgericht Stuttgart, Handelsregister A 381535 Geschäftsführer/Gesellschafter: ZOPYX Limited, Birmingham, UK ------------------------------------------------------------------------ E-Publishing, Python, Zope & Plone development, Consulting

1 0

Zope Foundation and DZUG boards meet
by Martijn Faassen 11 Jun '07

11 Jun '07

Zope Foundation and DZUG boards meet Potsdam, June 5, 2007 - the boards of the Zope Foundation and the DZUG (German speaking Zope User Group) met in Potsdam, Germany. The meeting took place after the close of the successful Zope-Tagung, a conference on Zope that that DZUG organizes annually. Topics discussed were wide-ranging, and included closer cooperation between DZUG and the Zope Foundation as well as a reaching out to other regional user groups. Recognizing DZUG as one of the oldest and most successful of regional Zope user groups, the Zope Foundation is interested in tapping DZUG's experience and resources for the wider international Zope community. In order to foster closer cooperation between DZUG and the Zope Foundation, the Zope Foundation has invited DZUG to participate in Zope Foundation board meetings on an observer basis. In addition, a DZUG representative will join the Zope Founadtion committee in charge of revising the Zope web presence.

1 0

[Ann] DMHistorical -- access historical state in a ZODB
by Dieter Maurer 07 Jun '07

07 Jun '07

"DMHistorical" is a set of tools to access the historical state of a ZODB. Such tools may be helpful to analyse why unwanted or unexpected changes happened and/or to selectively go back to a previous state. This implementation resolves not only the main object but also all (direct or indirect) persistent references from this object at the given time. Zope's 'History' facility on the other hand can show the state of an object at a given time but would resolve persistent references with respect to the current time. This implementation will not work for ZODB 3.2 or earlier. It has been tested with ZODB 3.4. It may (or may not) work for ZODB 3.6 or above. Download via <http://www.dieter.handshake.de/pyprojects/zope#DMHistorical> -- Dieter

1 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

2001

2000

1999

Zope-Announce June 2007