|
Hi,
in a project at hand we have the constraint of backing a bjsf:tree by a Swing JTree and providing a bi-directional synchronisation in terms of selection/expansion state and tree model.
Along the way I found that the 'open' attribute is not synched back to the server. This can be worked around by way of custom actions, however it is somewhat irritating since the 'selected' attribute is synched.
Also, it would be useful to have the 'empty' attribute available on the server side. This would eliminate the need to use bjsf:treeItem for leaf nodes. Instead, a bjsf:tree with empty='true' could be used, which makes certain frameworks easier to implement.
Finally, I was unable to select multiple tree nodes. Would it be possible to expose the 'selectType' attribute on the server side? I suppose the issue is that BJSF lacks the notion of a tree (as opposed to tree nodes) to which this attribute can be applied.
Cheers,
Dirk.
Id on UIBackbaseTreeItem - unexpected behaviour
1 July, 2008 - 15:46 — Dirk WeiseHi,
further to the above, the TreeItemRenderer will derive a TreeItem's id from its value or label, even if the id is explicitly provided. The only way to prevent the renderer from doing that is to set userDefinedId to true. The same applies to MenuItem, but none of the other components seem to override an explicitly set id.
Dirk.
Our fixes
18 July, 2008 - 20:17 — jstockallTo make the open attribute sync with the server, modify UIBackbaseTree so that the open ComponentField is created with clientSync=true
We've also replaced the renderer to allow us to use a specified ID instead of one generated from the label/value