Of course we could always update whenever there is a change in the system,
but this would lead to a huge performance penalty, particular when loading
or fileing in code, so I didn't change that.
I think that is fairly simple:
SystemChangeNotifier uniqueInstance
notify: self "browser"
ofSystemChangesOfItem: #class
change: #Recategorize
using: #someClassChanged:.
In #someClassChanged: post a deferred message to update browser cache,
so it will be handled just after file-in will be complete.
Actually this is what we are doing now, we defer the update until World steps in. See
OBCodeBrowser #event:, #noteChanges and #stepAt:in:.
Or about what kind of deferring mechanism are you thinking?
David
_______________________________________________
Pharo-project mailing list
[email protected]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
