Yes this is a good idea. May be the DummyUIManager should be by default in the system. Can you open a ticket? Stef
I think that maybe it is a good idea to use the DummyUIManager and the MorphicUIManager from Pavel MinimalImage.
We can put those classes in a repository called PharoMinimal or something similar. Then, you will be able to load both classes, run your image headless and before, evaluate something to set those classes as the current.
Just an idea...
On Tue, Feb 23, 2010 at 10:18 AM, Stéphane Ducasse <stephane.ducasse@inria.fr> wrote: this is a really good experiment please continue and let us know the results. Stef On Feb 22, 2010, at 8:21 PM, Esteban Lorenzano wrote:
I tried by starting pharo with a script:
Project uiProcess suspend. Smalltalk snapshot: true andQuit: true.
...and the processing stop working after the #suspend (no snapshot:andQuit: happens :( )
On 2010-02-22 13:43:05 -0300, Lukas Renggli <renggli@gmail.com> said:
Is that also necessary for a headless Pharo/Squeak?
No, it is not necessary. It saves a few CPU cycles because the event polling stops, the #step methods on the visible morphs are not called anymore, and the display is not updated any longer.
Programmatically you can still do everything (headless or non-headless). For example you can open morphs and move them around, you just won't see a change on the screen. Code that have some interaction with the GUI thread (like the debugger) might deadlock (or hang) the system.
Lukas
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project