Wed, 27 Jan 2010 11:15:32 +0100 must check for relation inlined in main form type
Sylvain Thénault <sylvain.thenault@logilab.fr> [Wed, 27 Jan 2010 11:15:32 +0100] rev 4400
must check for relation inlined in main form type
Wed, 27 Jan 2010 11:14:57 +0100 skip final relations at this point
Sylvain Thénault <sylvain.thenault@logilab.fr> [Wed, 27 Jan 2010 11:14:57 +0100] rev 4399
skip final relations at this point
Wed, 27 Jan 2010 11:26:57 +0100 add missing errno import in etwist/server.py stable
Adrien Di Mascio <Adrien.DiMascio@logilab.fr> [Wed, 27 Jan 2010 11:26:57 +0100] rev 4398
add missing errno import in etwist/server.py
Wed, 27 Jan 2010 10:17:27 +0100 should not raise KeyError if key's missing
Sylvain Thénault <sylvain.thenault@logilab.fr> [Wed, 27 Jan 2010 10:17:27 +0100] rev 4397
should not raise KeyError if key's missing
Wed, 27 Jan 2010 10:00:58 +0100 choices function should now take the field as argument
Sylvain Thénault <sylvain.thenault@logilab.fr> [Wed, 27 Jan 2010 10:00:58 +0100] rev 4396
choices function should now take the field as argument
Wed, 27 Jan 2010 10:00:35 +0100 cleanup
Sylvain Thénault <sylvain.thenault@logilab.fr> [Wed, 27 Jan 2010 10:00:35 +0100] rev 4395
cleanup
Wed, 27 Jan 2010 10:00:19 +0100 missing import
Sylvain Thénault <sylvain.thenault@logilab.fr> [Wed, 27 Jan 2010 10:00:19 +0100] rev 4394
missing import
Wed, 27 Jan 2010 09:59:55 +0100 systematically call bool on BooleanField values
Sylvain Thénault <sylvain.thenault@logilab.fr> [Wed, 27 Jan 2010 09:59:55 +0100] rev 4393
systematically call bool on BooleanField values
Wed, 27 Jan 2010 09:59:13 +0100 by default this is not the widget responsability to turn empty string into None,
Sylvain Thénault <sylvain.thenault@logilab.fr> [Wed, 27 Jan 2010 09:59:13 +0100] rev 4392
by default this is not the widget responsability to turn empty string into None, move this behaviour to the field.
Wed, 27 Jan 2010 09:57:53 +0100 ensure we get a correct key
Sylvain Thénault <sylvain.thenault@logilab.fr> [Wed, 27 Jan 2010 09:57:53 +0100] rev 4391
ensure we get a correct key
Wed, 27 Jan 2010 09:57:16 +0100 test fixes
Sylvain Thénault <sylvain.thenault@logilab.fr> [Wed, 27 Jan 2010 09:57:16 +0100] rev 4390
test fixes
Wed, 27 Jan 2010 09:56:58 +0100 useless, same as test_nonregr_eetype_etype_editing
Sylvain Thénault <sylvain.thenault@logilab.fr> [Wed, 27 Jan 2010 09:56:58 +0100] rev 4389
useless, same as test_nonregr_eetype_etype_editing
Wed, 27 Jan 2010 09:56:16 +0100 [forms] propagate aguments given to .vocabulary to .choices if it's a callable.
Sylvain Thénault <sylvain.thenault@logilab.fr> [Wed, 27 Jan 2010 09:56:16 +0100] rev 4388
[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.
Wed, 27 Jan 2010 09:53:48 +0100 reorganize code:
Sylvain Thénault <sylvain.thenault@logilab.fr> [Wed, 27 Jan 2010 09:53:48 +0100] rev 4387
reorganize code: move everything related to inlined forms and generic relation from editviews/editforms where there are used, eg in autoforms
Wed, 27 Jan 2010 09:25:40 +0100 [forms] fix backward compat for field.choices arguments
Sylvain Thénault <sylvain.thenault@logilab.fr> [Wed, 27 Jan 2010 09:25:40 +0100] rev 4386
[forms] fix backward compat for field.choices arguments
(0) -3000 -1000 -300 -100 -15 +15 +100 +300 +1000 +3000 tip