Linking the inspector with nautilus is not a good idea to me. Because at the end we can joke the old squeak by saying that it was monolithic but we are building the same.
So now I cannot unload Nautilus because when I remove it, it removes NavigationHistory that is used by the inspector and I do not understand why something is failing -> debugger -> fialure of debugger. Stef > Ok > I will check now I do not even understand why and how it is related. > > Stef > >> it's the inspector, not nautilus. >> >> => InspectorNavigator >> pushHistory: >> >> On 2013-10-02, at 19:20, Stéphane Ducasse <[email protected]> wrote: >> >>> When I try >>> >>> (MCWorkingCopy forPackage: (MCPackage named: 'NautilusRefactoring')) unload >>> >>> NautilusUI allInstances do: [ :inst | >>> SystemAnnouncer uniqueInstance unsubscribe: inst]. >>> Smalltalk garbageCollect. >>> >>> (MCWorkingCopy forPackage: (MCPackage named: 'NautilusCommon')) unload. >>> (MCWorkingCopy forPackage: (MCPackage named: 'Nautilus')) unload >>> >>> I get the attached system. I do not understand why SpecDebugger has >>> something to do with navigationHistory. >>> >>> Any idea? >>> I also think that we are not good at making sure what we load can be >>> cleanly unloaded. Without that discipline we will never have >>> a modular system. >>> >>> Stef >>> >>> >>> <Screen Shot 2013-10-02 at 7.04.02 PM.pdf> >> > >
