Zope Subversion Repository

Zope: Sandbox/ccomb/z3c.form/trunk/CHANGES.txt

branch to work on an object widget

Add a hidden widget template for the ``ISelectWidget``.

- Bug: ``createId`` could not handle arbitrary unicode input. Thanks to
  Andreas Reuleaux for reporting the bug and a patch for it. (Added
  descriptive doctests for the function in the process.)

merged gocept-invariants branch from r80186 to HEAD

Get ready for release.

- Feature: Implemented ``ImageButton``, ``ImageAction``, 
  ``ImageWidget``, and ``ImageFieldWidget`` to support imge submit 
  buttons.

Turn bug into a new feature.

The AttributeField data manager wasn't honouring the field's interface
on the set method also.

Fix bug: When an error occurred during processing of the request the
widget ended up been security proxies and the system started
throwing `TraversalError's trying to access the `label' attribute of
the widget. Declared that the widgets require the `zope.Public'
permission in order to access these attributes.

Fixed bug: The `canAccess' and `canWrite' methods on the AttributeField
datamanager didn't check for the case when the field's interface was
not directly provided for by the context.

- Feature: Implemented single checkbox widget that can be used for boolean
  fields. They are not available by default but can be set using the
  ``widgetFactory`` attribute.

- Bug: When rendering a widget the ``style`` attribute was not honored. Thanks
  to Andreas Reuleaux for reporting.

- Bug: When an error occurred in the sub-form, the status message was not set
  correctly. Fixed the code and the incorrect test. Thanks to Markus
  Kemmerling for reporting.

Bug: Several interfaces had the ``self`` argument in the method
     signature. Thanks to Markus Kemmerling for reporting.

Get ready for 1.6.0 release.

- Feature: An event handler for ``ActionErrorOccurred`` events is registered
  to merge the action error into the form's error collectors, such as
  ``form.widgets.errors`` and ``form.widgets['name'].error`` (if
  applicable). It also sets the status of the form. (Thanks to Herman
  Himmelbauer, who requested the feature, for providing use cases.)

- Feature: Action can now raise ``ActionExecutionError`` exceptions that will
  be handled by the framework. These errors wrap the original error. If an
  error is specific to a widget, then the widget name is passed to a special
  ``WidgetActionExecutionError`` error. (Thanks to Herman Himmelbauer, who
  requested the feature, for providing use cases.)

- Feature: After an action handler has been executed, an action executed event
  is sent to the system. If the execution was successful, the event is
  ``ActionSuccessfull`` event is sent. If an action execution error was
  raised, the ``ActionErrorOccurred`` event is raised. (Thanks to Herman
  Himmelbauer, who requested the feature, for providing use cases.)

- Feature: The ``applyChanges()`` function now returns a dictionary of changes
  (grouped by interface) instead of a boolean. This allows us to generate a
  more detailed object-modified event. If no changes are applied, an empty
  dictionary is returned. The new behavior is compatible with the old one, so
  no changes to your code are required. (Thanks to Darryl Cousins for the
  request and implementation.)

- Bug (IE): In Internet Explorer, when a label for a radio input field is only
  placed around the text describing the choice, then only the text is
  surrounded by a dashed box. IE users reported this to be confusing, thus we
  now place the label around the text and the input element so that both are
  surrounded by the dashed border. In Firefox and KHTML (Safari) only the
  radio button is surrounded all the time.

Reporting invariant invalid errors was not working. Here is what was 
needed:

- Feature: A new ``InvalidErrorViewSnippet`` class provides an error view
  snippet for ``zope.interface.Invalid`` exceptions, which are frequently used
  for invariants.

- Bug: When extracting and validating data in the widget manager, invariant
  errors were not converted to error view snippets.

- Bug: When error view snippets were not widget-specific -- in other words,
  the ``widget`` attribute was ``None`` -- rendering the template would fail.

Better wording.

- Feature: When a widget is required, HTML-based widgets now declare a
  "required" class. Requested by Markus Leist.

- Restructuring: The widget specific class name was in camel-case. A
  converntion that later developed uses always dash-based naming of HTML/CSS
  related variables. So for example, the class name "textWidget" is now
  "text-widget". This change will most likely require some changes to your CSS
  declarations.

Add a comment about the work Aaron did on the text.

- Feature: The validation data wrapper now knows about the context of the
  validation, which provides a hook for invariants to access the environment.

Add some change notes from Roy's checkin yesterday.

Make changes notes about Roy's latest checkin.

- Feature: Exposed several attributes of the widget manager to the form for
  convenience. The attributes are: mode, ignoreContext, ignoreRequest,
  ignoreReadonly.

Make error messages for number parsing error more user-friendly.

Implemented a new feature putting a span around the value for a display 
widget. Also tested the button field widget someone better.

Remove mentioning of "hint" attribute.

Fix an ugly bug with buttons and the button manager.

Added widget events.

Fixed badness related to button actions. The API is much cleaner now.
 

Added button widget.

Get ready for beta release.

- 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

- Added all available HTML attributes.

Provide labels correctly for radio widgets.

Prepare 1.4.0 release.

Added prompt in select widget and updated interface.

- Feature: Allow "no value message" of select widgets to be dynamilcally
  changed using an attribute value adapter.

I spoke with Joachim Werner the other day on IRC and he mentioned to me 
that he was very annoyed that the widgets in Zope 3 (referring to the 
ones in zope.app.form) were not internationalized correctly and he would 
have to constantly write his own custom widgets to make them work for 
German input.

It occurred to me that the same problem holds true for z3c.form. So I 
had to change that! :-)

- 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.

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.

I have to escape the tests in the generated documentation now, since 
PyPI does not properly encode the long description. Sigh.

Get ready for 1.3.0.

- Move TODOS to project level. I think this means that they are picked 
  up in the release and we get a higher rating in the cheeseshop.

- Merged Roger's changes located in the code to the canonical location.

- Removed trailing whitespaces from util.

Note the changes of the previous checkin.

Record change and update setup.

Added change comment.

Add notes about recent changes.

Record recent changes.

Add changes comment for the last checkin.

* Implemented documentation corrections from Roy Mathew. Thanks!

* Implemented API extensions to select() and omit() in Fields as 
  suggested by Nikolay Kim. Thanks!

* Ignore buildout stuff.

Provide a better fix for the bug Roger fixed already. Also provided a 
comprehensive test for it.

Added ability to change button action title via an IValue adapter.

Update package information.

	Diffs between and
	Generate output suitable for use with a patch program
	Type of Diff should be a Colored Diff Long Colored Diff Unidiff Context Diff Side by Side

---

Sort log by: Not sorted Commit date Revision

---

webmaster@zope.org Powered by ViewCVS 1.0-dev

ViewCVS and CVS Help