Lukas, I wondered about startup, and let's assume you are correct. Since the time hit for the scripts can be significant, it would be nice to wrap them with the display of the busy cursor. As it is, the machine winks out for a while, and the user is not notified that it's happening, and perhaps even more important, when it's over. Related to Sophie's "instability" perhaps? I can envision a frustrated user queuing a lot of input that later gets processed and causes trouble. More idealistically, this becomes an example of the beauty of Dolphin's session management. The VM knows when it is launched and tells the image, invoking startup (and conversely shutdown) behavior. These things happen when they should, and do not happen when they should not, as apparently is the case for Squeak/Pharo. Bill -----Original Message----- From: pharo-project-bounces@lists.gforge.inria.fr [mailto:pharo-project-bounces@lists.gforge.inria.fr] On Behalf Of Lukas Renggli Sent: Thursday, July 16, 2009 1:01 AM To: Pharo-project@lists.gforge.inria.fr Subject: Re: [Pharo-project] Save and quit vs. Save - a clue to performance???
I've noticed something that seems unusual to me. Â Choose save and quit, and the writing cursor appears, disappears, and the image is almost immediately gone after that happens. Â Choose save, and the cursor appears, sticks around for about the same amount of time as for save and quit (this part is a little bit of a stretch), and then the image becomes unresponsive for (depending) one or more seconds.
That's probably because startup scripts are run. In the first case this happens when the image comes up. Cheers, Lukas -- Lukas Renggli http://www.lukas-renggli.ch _______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project