should take arbitrary arguments

i18nupdate

calling unicode instead of gettext...

[entity] small optimization: once an entity has been completed, don't redo it (for nothing)

[treeview] ensure items are ordered according to their dc_title, we can't rely on an ordered rset * is_last has to be computed on the caller now, not possible in the callee * rely on b3f61c38526b to use entity.view() with vid in *view*'s arguments

[entity] rename vid argument of .view(...) into __vid to avoid potential conflicts with kwargs

eschema view is gone away

remove misnamed argument

add version number to deprecation warning

[entities] fix CWUser.is_in_group implementation use self.groups property instead of self._groups which might not be initialized.

missing import

must check for relation inlined in main form type

skip final relations at this point

add missing errno import in etwist/server.py

should not raise KeyError if key's missing

choices function should now take the field as argument

cleanup

missing import

systematically call bool on BooleanField values

by default this is not the widget responsability to turn empty string into None, move this behaviour to the field.

ensure we get a correct key

test fixes

useless, same as test_nonregr_eetype_etype_editing

[forms] propagate aguments given to .vocabulary to .choices if it's a callable. So we can properly uses vocabulary(limit=xxx) in places where we used to call .choices(limit), since field.choices is not meant to be accessed directly. Also, document expected behaviour for custom choices method for relation fields.

reorganize code: move everything related to inlined forms and generic relation from editviews/editforms where there are used, eg in autoforms

[forms] fix backward compat for field.choices arguments

use field.vocabulary instead of field.choices, skip already related eids. Also consider vocabulary when no etype specified

[primary view] activate toolbox

it seems that prefixiter is expected to return child *folder* but was relying on a specific .children implementation, fix this

3.6 api update, cleanup

[forms] let the autoform specify the generic relation field label, no need for a custom fieldset, may be handled as for other fields by the renderer.

simplify messages used for inlined forms

should have been in previous commit (moved below in the module)

[forms] the last touch: handle inlined relation forms as fields by introducing a simple InlinedRelationField. This makese things more flexible while removing a lost of overriding necessary.

fix label handling: when label is explicitly set to None, don't try to guess it

surrounding div necessary for proper error localization

cleanup base class

by default use new jquery widgets for Time/Date/DateTime fields

new jquery based widgets for Time/Date/DateTime, backported from crm

introduce a default render implementation on the base widget, which add_media and then call the newly introduced method _render(form, field, formrenderer), abstract of the base widget class. This allow a litle code factorisation and avoid to forget the call to add_media in subclasses.

[forms] new optional suffix attribute on widget objects, used to generage input name / dom id. Ease reuse of widgets from another widget. Also move base values computing to a separated values(form, field) method.

introduce new _ensure_correctly_typed method on fields, responsible to ensure the value return by the widget is suitable for that kind of field. Also factorize date and time fields.

fix typed_value implementation w/ eidparam field which are actual entity's relation and have .value set for their initial value

cleanup module namespace but only importing the formwidgets module

fix deprecation warnings

fif inlined relation forms pb w/ new ajax forms. We've to ensure the varmaker is properly initialized when generating a form where we may add new subentities, which will use ajax call to generate the subform while this subform expect a varmaker to be set.

now that we are property initializing autoform_section for the 'inlined' form type, use it...

[uicfg] fix autoform_section rtags initialization 1. when a relation is marked as inlined in the 'main' form type, we want its opposite (eg when one the other side of the relation) to be marked as hidden in the 'inlined' form type 2. when no section is specified for the 'inlined' form type, use the same as in the 'main' form type to do this properly, we need two initialization stages. The first one to handle 1., the second to handle what was done before and 2. We can't do this in a single stage because we've to know the bare value of the "opposite" tag.