- Zope-Announce - Zope lists

Zope 3 training in Oslo with Philipp von Weitershausen
by Andreas Johnsen 31 Jul '07

31 Jul '07

Bouvet is happy to announce Zope 3 training in Oslo with Philipp von Weitershausen, author of the best selling book «Web Component Development with Zope 3». The training is targeted at Zope 2 and Plone developers who want to step into the world of modern Zope development. - When: Monday 1. October - Thursday 4. October 2007 - Where: Oslo, Norway For agenda and more information, please visit http://www.bouvet.no/BouvetWEB/KursSeksjon.aspx?PageID=e1. -- Best regards, Andreas Rübner Johnsen www.bouvet.no

1 0

z3c.formjs-0.2 and z3c.formjsdemo-0.2 released!
by Paul Carduner 19 Jul '07

19 Jul '07

The 0.2 versions of z3c.formjs and z3c.formjsdemo have just been released! (for the blog version of this mail, see http://beta.carduner.net/wordpress/?p=20) For those who have not been following the development, z3c.formjs is a package that extends z3c.form (written by Stephan Richter and Roger Ineichen), adding JavaScript and AJAX functionality. More specifically, it allows you to control JavaScript and AJAX from within a presentation component like a form based view class. Alternatively ala Stephan Richter, This package is designed to provide a Python API to common Javascript features for forms written with the "z3c.form*" packages. While the reference backend-implementation is for the JQuery library, any other Javascript library can be hooked into the Python API. Here's what's new in the 0.2 release, taken straight from CHANGES.txt: z3c.formjs ------------- Version 0.2.0 (7/18/2007) * Feature: Registration of public AJAX server calls via a simple decorator. The calls are made available via a special ajax view on the original view. * Feature: Allow registering of JS subscriptions via a decorator within the presentation component. * Feature: Added a new CSS selector. * Feature: Implementation of AJAX-driven widget value validation. * Restructure: Completely overhauled the entire API to be most easy to use and have the most minimal implementation. * Bug: The package is now 100% tested. * Feature: Implementation of AJAX request handlers in forms. z3c.formjsdemo -------------------- Version 0.2.0 (7/18/2007) * Feature: The new chatroom demo implements a simple chat client in HTML and Javascript using the z3c.formjs package. * Feature: Validation demo showing off on the fly ajax field validation. * Restructure: Code updated to keep up with the changes in the API of z3c.formjs. Installation Instructions ------------------------------ To checkout the demo, perform the following commands: svn co svn://svn.zope.org/repos/main/z3c.formjsdemo/tags/0.2.0 z3c.formjsdemo cd z3c.formjsdemo python2.4 bootstrap.py ./bin/buildout -Nv ./bin/demo fg The demo will then be available at http://localhost:8080. Alternatively, checkout the live demo at http://demo.carduner.net:8080/ (please no slashdot posts) Cheese Shop ----------------- Both of these packages are available on the Python Cheese Shop at * http://cheeseshop.python.org/pypi/z3c.formjs/0.2.0 and * http://cheeseshop.python.org/pypi/z3c.formjsdemo/0.2.0 Want to help? ------------------ This is by no means a one (or two (or three ( … ) ) ) (wo)man project and I am very interested in what kinds of use cases other people have and would like to see implemented or demonstrated. I am also very interested in having other people join the fun and hack on some code. z3c.formjs is in theory JavaScript library agnostic, and I would love for that theory to be tested with a MochiKit rendering plugin or any other type of rendering plugin. So, please if you are interested, contact me at paulcarduner at gmail dot com or just make lots of noise on zope3-users, zope3-dev, or #zope3-dev and we can discuss further goals and tasks.

1 0

z3c.form 1.5.0 and z3c.formdemo 1.3.0 released!
by Stephan Richter 19 Jul '07

19 Jul '07

Hello everyone, I am pleased to announce new releases for z3c.form and z3c.formdemo. The latest changes were mainly driven by Paul Carduner's work on z3c.formjs and z3c.formjsdemo, but also by continued customer work. Again for the curious and impatient ... --------------------------------------- This time there is no new demo available, but the old ones still work as expected. 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 -v $ ./bin/demo fg Now you can access the demo under: http://localhost:8080/ We now also have functional tests that check all the demos: $ ./bin/test -vp1 On the Javascript Front ----------------------- A lot more progress has been made on this front. Look out for Paul's announcement! It will make up for the missing new demo in formdemo! Changes ------- z3c.form ~~~~~~~~ - Feature: Added a span around values for widgets in display mode. This allows for easier identification widget values in display mode. - Feature: Added the concept of widget events and implemented a particular "after widget update" event that is called right after a widget is updated. - Feature: Restructured the approach to customize button actions, by requiring the adapter to provide a new interface ``IButtonAction``. Also, an adapter is now provided by default, still allowing cusotmization using the usual methods though. - Feature: Added button widget. While it is not very useful without Javascript, it still belongs into this package for completion. - Feature: All ``IFieldWidget`` instances that are also HTML element widgets now declare an additional CSS class of the form "<fieldtype.lower()>-field". - Feature: Added ``addClass()`` method to HTML element widgets, so that adding a new CSS class is simpler. - Feature: Renamed "css" attribute of the widget to "klass", because the class of an HTML element is a classification, not a CSS marker. - Feature: Reviewed all widget attributes. Added all available HTML attributes to the widgets. - Documentation: Removed mentioning of widget's "hint" attribute, since it does not exist. - Optimization: The terms for a sequence widget were looked up multiple times among different components. The widget is now the canonical source for the terms and other components, such as the converter uses them. This avoids looking up the terms multiple times, which can be an expensive process for some applications. - Bug/Feature: Correctly create labels for radio button choices. - Bug: Buttons did not honor the name given by the schema, if created within one, because we were too anxious to give buttons a name. Now name assignment is delayed until the button is added to the button manager. - Bug: Button actions were never updated in the actions manager. - Bug: Added tests for textarea widget. z3c.formdemo ~~~~~~~~~~~~ - Feature: Created functional tests for the demos. - Feature: Moved all application ZCML declarations into a ZCML file called ``application.zcml``. 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] SmartPrintNG 0.1.0 released - PDF/ODT/DOCX/WML/RTF export for Plone
by Andreas Jung 13 Jul '07

13 Jul '07

I am pleased to announce the first release of SmartPrintNG 0.1.0. SmartPrintNG can convert the 'content' view of Plone documents into different formats: * PDF * RTF * ODT * WML * DOCX In addition SmartPrintNG provides a configurable pre- and post-processing pipline in order to give you full control over the conversion process. SmartPrintNG comes with filters to remove images, remove links or generate a link list at the end of the document, support for breaking a document into pages (e.g. for presentation handouts) and much more. To control the look & feel of the generated document you can configure custom templates and custom style-sheets. Requirements: * Zope 2.10.4 * Plone 3.0 * XFC converter (XMLMind) * XINC converter (Lunasil) * zopyx.convert V 0.4.5 for higher * Java 1.5 or higher Project homepage and download: http://smartprintng.zopyx.com 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

CMF 2.1.0-beta2 released
by Jens Vagelpohl 12 Jul '07

12 Jul '07

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 The CMF developer community is hereby announcing the release of CMF version 2.1.0-beta2. What is the CMF? The Zope Content Management Framework provides a set of services and content objects useful for building highly dynamic, content-oriented portal sites. The CMF provides the foundation for popular software packages such as Plone. It is intended to be easily customizable, in terms of both the types of content used and the policies and services it provides. Where do I get it? For release files, change logs, installation instructions and more please visit http://www.zope.org/Products/CMF/CMF-2.1.0-beta2. Roadmap and release information can be found at http://www.zope.org/Products/CMF/docs/roadmap. The CMF mailing list can be reached at the zope-cmf(a)zope.org address, to sign up please visit http://mail.zope.org/mailman/listinfo/zope- cmf. Please file bug reports, feature requests or suggestions in the CMF bug collector at http://www.zope.org/Collectors/CMF . What has changed since the last release? Please note: Please read the "Upgrading from versions earlier than 2.1.0-beta" section in the INSTALL.txt-document for upgrading hints. New Features - CMFCore.exportimport.skins: Added the ability to remove whole skin selections using a GS profile. (http://www.zope.org/Collectors/CMF/479) - Workflow definition instances now have a description field (http://www.zope.org/Collectors/CMF/480) Bug Fixes - UndoTool: Fixed 'listUndoableTransactionsFor'. The required 'object' argument is now respected. This doesn't change the behavior as long as 'object' is the site root object. - CMFCore.TypesTool: Corrected method signature of all_meta_types to have an interface keyword argument, as per the underlying OFS.ObjectManager interface declaration. - SkinnableObjectManager: Changed the way skins are set up. Acquisition wrapping no longer triggers 'setupCurrentSkin'. This is now done on publishing traversal after the BeforeTraverseEvent triggers 'setSite'. This fix replaces a temporary hack introduced in 2.1.0-beta, making sure ISkinsTool is looked up after setting the site. - CMFCore.CMFBTreeFolder: CMFBTreeFolders could not be used as the toplevel /Members container. (http://www.zope.org/Collectors/CMF/441) - Pass 'object' through to TypeInformation objects' 'listActions'. (http://www.zope.org/Collectors/CMF/482) - Removed extraneous "Cache" tab from FS-based skin objects. (http://www.zope.org/Collectors/CMF/343) - CMFCore.WorkflowTool: Using the '(Default)' keyword for a type's workflow chain will now reset any custom workflow chains for the type. (http://www.zope.org/Collectors/CMF/475) - Use the property API to get the member specific skin, because direct attribute access won't work with PAS based membership. (http://dev.plone.org/plone/ticket/5904) - Add POST-only protections to security critical methods. http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2007-0240) - Allow customization from DirectoryViews to be redirected into alternate folders, and use manually-built clones. (http://www.zope.org/Collectors/CMF/382) - Use a utility, registered for 'Products.CMFDefault.interfaces.IHTMLScrubber', to perform scrubbing of HTML; fall back to the old, hard-wired behavior. (http://www.zope.org/Collectors/CMF/452) - Remove antique usage of marker attributes in favor of interfaces, leaving BBB behind for places potentially affecting third- party code. (http://www.zope.org/Collectors/CMF/440) - Fixed DST-driven test breakage in CMFCalendar by adding an optional 'zone' argument to the DublineCore methods which return string rednitions of date metadata. (http://www.zope.org/Collectors/CMF/476) - Favorite: Fixed UID handling broken in 2.1.0-beta. - CMFDefault: Removed CMFUid dependency inadvertently added in 2.1.0-beta. - CMFActionIcons: Fixed interface declarations added in 2.1.0-beta. Other - The CMF now depends on Zope 2.10.4 or higher. - CMFDefault: Adjusted factory.py to new GenericSetup version. - CMFUid.UniqueIdAnnotationTool: Annotation handling has been switched from triggering it through old-style manage_*-methods to using events. UID assigning behavior has been made more flexible. Please review CMFUid/README.txt for information about the current behavior and the new features. (http://www.zope.org/Collectors/CMF/474) -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.7 (Darwin) iD8DBQFGlltDRAx5nvEhZLIRAjz+AJ91FGKJFbXBc0Qyr0kR70Grzh3sWwCeJBP2 wGHEuI+QbGm+Xe5VvzoQ69U= =6P48 -----END PGP SIGNATURE-----

1 0

Zope 3.4.0b1 released
by Christian Theune 06 Jul '07

06 Jul '07

July 5, 2007 - The Zope 3 development team announces the Zope 3.4.0b1 release This release is the first beta release for Zope 3.4.0. It was preceeded by an alpha release in April. Since the beta we finished repackaging of eggs, added three new features and fixed more than 12 bugs, please see the change log for details. Zope 3.4 introduces support for binary large objects in the ZODB, provides a new postprocessing hook for publishing results and makes all Zope packages available as Python eggs. Development release and feedback -------------------------------- This is a development release with beta quality. It is intended for developers to check their applications for compatibility with the new features. This release *is not intended to be used in production environments*. We would love to hear about any bugs you encounter. Please use our bug tracker, the mailing lists, and the IRC channel to contact us in case you encounter any problems. This beta release will be succeeded by a release candidate which is expected to be available by August 5, 2007. For status updates on our roadmap check: https://launchpad.net/zope3/3.4/+milestones What is Zope 3? --------------- Zope 3 is a web application server that continues to build on the heritage of Zope. It was rewritten from scratch based on the latest software design patterns and the experiences of Zope 2. The component architecture is the very core of Zope 3 that allows developers to create flexible and powerful web applications. Compatibility with Zope 2 -------------------------- We continue to work on the transition from Zope 2 to Zope 3 by making Zope 2 use more and more of the Zope 3 packages. But we're not there yet. **You can't run Zope 2 applications in Zope 3.** Downloads --------- Zope 3 can be downloaded from: http://zope.org/Products/Zope3 Installation instructions for both Windows and Un*x/Linux are now available in the top level README.txt file of the distribution. The binary installer is recommended for Windows. Zope 3.4 requires Python 2.4.3 to run. You must also have zlib installed on your system. Resources --------- - Zope 3 Development Web Site: http://wiki.zope.org/zope3 - Zope 3 Developers Mailing List: http://mail.zope.org/mailman/listinfo/zope3-dev - Zope 3 Users Mailing List: http://mail.zope.org/mailman/listinfo/zope3-users - Bug tracker at launchpad: https://launchpad.net/zope3 - IRC Channel: #zope3-dev at irc.freenode.net Acknowledgments --------------- Much thanks to everyone who contributed to this release: Jim Fulton, Dmitry Vasiliev, Martijn Faassen, Christian Theune, Wolfgang Schnerring, Fred Drake, Marius Gedminas, Baiju M, Brian Sutherland, Gary Poster

1 0

[ANN] Zope 2.10.4 and Zope 2.9.8 released
by Andreas Jung 05 Jul '07

05 Jul '07

The Zope developer community is pleased to announce two new Zope releases: 2.9.8 and 2.10.4 You can download the releases from: http://www.zope.org/Products/Zope/2.9.8/ http://www.zope.org/Products/Zope/2.10.4/ The release notes are available directly from the links above. All releases are bugfix releases and include the hotfix published some days ago: http://www.zope.org/Products/Zope/Hotfix-2007-03-20 - -- 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

Interest in a one-day business conference for Python, Zope and Plone companies ?
by eGenix Team: M.-A. Lemburg 02 Jul '07

02 Jul '07

Hello, eGenix is looking into organizing a one day conference specifically for companies doing business with Python, Zope and Plone. The conference will likely be held in or close to Düsseldorf, Germany, which is lively medium-sized city, with good airport connections world-wide and specifically to all major European cities, so it's easy getting there and ideal for a one day event. The focus of the conference is on networking, meeting people, exchanging experience and exploring ways of working together. We are aiming at having a small conference program with just a few talks. The main intent of the presentations should be to initiate discussions among the attendees. Since this will be a business-only event, we will likely get professional help from a conference organizer and also try to sign up with a hotel to do all the catering, conference room maintenance, etc. My questions to you: * Would there be interest in such a conference event ? * How many people from your company would likely attend ? * Would a weekday or weekend conference date be more attractive ? * Does the focus suit your needs ? We will be giving a short presentation of what we have in mind at EuroPython 2007 in Vilnius in the context of the Open Space sessions: http://wiki.python.org/moin/EuroPython2007OpenSpace If you're interested, please contact us. Thanks, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Jul 02 2007) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ 2007-07-09: EuroPython 2007, Vilnius, Lithuania 6 days to go :::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,MacOSX for free ! :::: eGenix.com Software, Skills and Services GmbH Pastor-Loeh-Str.48 D-40764 Langenfeld, Germany. CEO Dipl.-Math. Marc-Andre Lemburg Registered at Amtsgericht Duesseldorf: HRB 46611

1 0

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