Le 30/06/2014 09:09, Nicolai Hess a écrit :
Yes, we had quite some bugs with this package tree update in the past.
What I don't understand is, why
is the whole tree removed and rebuild, maybe this is a common strategy
in Morphic, update a list ore tree
will always rebuild the whole morph structure? But it happens even if
the structure is the same and
just this little package/dirty package icon is updated.
I let you as an exercise write the necessary code to do a partial update
of the displayed tree :) Don't forget to remember which nodes were
expanded and which were not.
Another issue is this "selected package/package selection". The tree
(and for example the
category list and/or method list" as well), stores the selection on
multiple ways, in the model (PackageTreeNautilus), the
UI (PackageTreeNautilusUi) and the treelist morph. Once as a
SelectedTreeNode, a Package from Nautilus Model and
once as a PackgeTreeSelection/PackageTreeTagSelection.
I find it pretty confusing.
This is the Nautilus approach. You don't have to do it that way.
BTW, I still can not reproduce this memory leak behavior. I tried this:
[ Gofer new smalltalkhubUser: 'ObjectProfile'
project: 'Roassal2';
package: 'ConfigurationOfRoassal2';
load.
(Smalltalk at: #ConfigurationOfRoassal2) load ] timeToRun.
with and without an open SystemBrowser. But the load time and
memory consumption is the same.
Select a package in Nautilus first.
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
