Le 15/04/2013 11:29, Hilaire Fernandes a écrit :
Le 15/04/2013 11:23, Goubier Thierry a écrit :
You can...
Have one colum with a two levels tree in it, and an editing pane to edit
the values (it's a quite common approach in other GUI worlds).
Or a two-column morph with a two level tree like the settings manager;
in the right colum you have the editing morph or nothing or a read-only
morph.
Would you be OK with the Settings browser approach?
I think no, as it may consume too much place. You can imagine the second
column of the settings browser to be a canvas view in my case. The tree
view is a hierarchical view of the canvas to browse and to edit items
displayed in the canvas.
Ok, so you would like the node morph in the tree to be editable in
place, but only for the attributes? Single column MorphTreeMorph with
nodes that you can edit?
I found that if you set an editable morph as the node in a tree, then
you can really edit it in the tree :)
In that case, you may just need to change the nodeStringGetter: when you
initialize your MorphTreeMorph. It will call asMorph on the result of
calling that selector on your item; if you happen to build a morph as a
reply then it should return it as it is. Just then, for your attributes,
return a Morph containing a label and a text field well linked to your item.
This should be cool to use :) I'll keep it in my good-ideas-to-try
notebook :)
Thierry
--
Thierry Goubier
CEA list
Laboratoire des Fondations des Systèmes Temps Réel Embarqués
91191 Gif sur Yvette Cedex
France
Phone/Fax: +33 (0) 1 69 08 32 92 / 83 95
