Sylvain Thénault <sylvain.thenault@logilab.fr> [Wed, 20 Jan 2010 15:03:30 +0100] rev 4297
3.6 api update
Sylvain Thénault <sylvain.thenault@logilab.fr> [Wed, 20 Jan 2010 14:41:04 +0100] rev 4296
merge
Sylvain Thénault <sylvain.thenault@logilab.fr> [Wed, 20 Jan 2010 14:39:44 +0100] rev 4295
allow control of generic relations field display through display_fields
Sylvain Thénault <sylvain.thenault@logilab.fr> [Wed, 20 Jan 2010 14:39:10 +0100] rev 4294
no self._cw on widget objects while '_' is defined locally
Sylvain Thénault <sylvain.thenault@logilab.fr> [Wed, 20 Jan 2010 14:38:45 +0100] rev 4293
delete remaining stuff w/ handling of the generic relations
Sylvain Thénault <sylvain.thenault@logilab.fr> [Wed, 20 Jan 2010 14:34:06 +0100] rev 4292
test update
Adrien Di Mascio <Adrien.DiMascio@logilab.fr> [Wed, 20 Jan 2010 13:03:08 +0100] rev 4291
clear vreg's parent_classes cache to fix etype cache / auto-reloading bug
EtypeRegistry.parent_classes()'s is cached. When the registry is
reloaded, if the cache is not cleared, we might get the old list
of parent classes and that leads to strange bugs.
Typical scenario :
1/ start application in debug mode
2/ go to add/Bookmark -> everything's fine
3/ change the source
4/ reload add/Bookmark -> 'creation' not selectable because :
a/ cw detects a change in the source and reloads vreg
b/ cw tries to select 'creation' view for 'Bookmark'
- 'creation' view uses specified_etype_implements('Any')
- cw compares Bookmark.__bases__[0] (i.e. new version of
AnyEntity) with the old version of AnyEntity cached in
the vreg. They don't match => view is not applicable.
Sylvain Thénault <sylvain.thenault@logilab.fr> [Wed, 20 Jan 2010 11:31:38 +0100] rev 4290
merge