Hi,

you do not need only the DummyUIManager but some modifications to
MorphicUIManager from Pharo-Kernel.

You should start with the scripts:
DummyUIManager.st
MorphicUIManager.st
patch.st
unload.st - here the UIProcess is stopped

There's updated version of Pharo-Kernel here:
http://gforge.inria.fr/frs/download.php/26462/PharoKernel-1.1-11229-UNSTABLE.zip
However it's still very dirty and a lot of things will change soon.

Cheers,
-- Pavel


On Thu, Feb 25, 2010 at 1:49 PM, Esteban Lorenzano <[email protected]> wrote:
> Ok, I tried passing a .st by command line:
>
> UIManager default: DummyUIManager new.
>
> Project uiProcess terminate.
>
> SmalltalkImage current snapshot: true andQuit: true.
>
> but I fail miserably :'(
> (it stops do anything after "Project uiProcess terminate"... and the
> same using "Project uiProcess suspend")
>
> Any idea of how can I proceed from here? (I confess: I'm totally lost here)
>
> Cheers,
> Esteban
>
>
> On 2010-02-23 06:44:18 -0300, Mariano Martinez Peck
> <[email protected]> said:
>
>>
>>
>> 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=E9phane Ducasse <
>> [email protected]> 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
>>>> <[email protected]> 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
>>>> [email protected]
>>>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
>>>
>>>
>>> _______________________________________________
>>> Pharo-project mailing list
>>> [email protected]
>>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
>>>
>>
>>
>> I think that maybe it is a good idea to use the DummyUIManager and the Morp=
>> hicUIManager=A0 from Pavel MinimalImage.<br><br>We can put those classes in=
>>  a repository called PharoMinimal or something similar. Then, you will be a=
>> ble to load both classes, run your image headless and before, evaluate some=
>> thing to set those classes as the current.<br>
>> <br>Just an idea...<br><br><div class=3D"gmail_quote">On Tue, Feb 23, 2010 =
>> at 10:18 AM, St=E9phane Ducasse <span dir=3D"ltr">&lt;<a href=3D"mailto:ste=
>> [email protected]">[email protected]</a>&gt;</span>
>> wrote:<br>=
>> <blockquote class=3D"gmail_quote" style=3D"border-left: 1px solid rgb(204, =
>> 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
>> this is a really good experiment<br>
>> please continue<br>
>> and let us know the results.<br>
>> Stef<br>
>> <div><div></div><div class=3D"h5">On Feb 22, 2010, at 8:21 PM, Esteban Lore=
>> nzano wrote:<br>
>> <br>
>> &gt; I tried by starting pharo with a script:<br>
>> &gt;<br>
>> &gt; Project uiProcess suspend.<br>
>> &gt; Smalltalk<br>
>> &gt; =A0 =A0 =A0 snapshot: true<br>
>> &gt; =A0 =A0 =A0 andQuit: true.<br>
>> &gt;<br>
>> &gt; ...and the processing stop working after the #suspend (no<br>
>> &gt; snapshot:andQuit: happens :( )<br>
>> &gt;<br>
>> &gt; On 2010-02-22 13:43:05 -0300, Lukas Renggli<br>
>> &gt; &lt;<a
>> href=3D"mailto:[email protected]";>[email protected]</a>&gt;
>> sai=
>> d:<br>
>> &gt;<br>
>> &gt;&gt;&gt; Is that also necessary for a headless Pharo/Squeak?<br>
>> &gt;&gt;<br>
>> &gt;&gt; No, it is not necessary. It saves a few CPU cycles because the eve=
>> nt<br>
>> &gt;&gt; polling stops, the #step methods on the visible morphs are not cal=
>> led<br>
>> &gt;&gt; anymore, and the display is not updated any longer.<br>
>> &gt;&gt;<br>
>> &gt;&gt; Programmatically you can still do everything (headless or<br>
>> &gt;&gt; non-headless). For example you can open morphs and move them aroun=
>> d,<br>
>> &gt;&gt; you just won&#39;t see a change on the screen. Code that have some=
>> <br>
>> &gt;&gt; interaction with the GUI thread (like the debugger) might deadlock=
>>  (or<br>
>> &gt;&gt; hang) the system.<br>
>> &gt;&gt;<br>
>> &gt;&gt; Lukas<br>
>> &gt;<br>
>> &gt;<br>
>> &gt;<br>
>> &gt;<br>
>> &gt; _______________________________________________<br>
>> &gt; Pharo-project mailing list<br>
>> &gt; <a
>> href=3D"mailto:[email protected]";>pharo-proj...@l=
> ists.gforge.inria.fr</a><br>
> &gt;
>>
>> <a href=3D"http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo=
>> -project" target=3D"_blank">http://lists.gforge.inria.fr/cgi-bin/mailman/li=
>> stinfo/pharo-project</a><br>
>> <br>
>> <br>
>> _______________________________________________<br>
>> Pharo-project mailing list<br>
>> <a
>> href=3D"mailto:[email protected]";>pharo-proj...@lists.=
> gforge.inria.fr</a><br>
> <a
>>
>> href=3D"http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-proj=
>> ect" target=3D"_blank">http://lists.gforge.inria.fr/cgi-bin/mailman/listinf=
>> o/pharo-project</a><br>
>> </div></div></blockquote></div><br>
>>
>>
>>
>>
>> _______________________________________________
>> Pharo-project mailing list
>> [email protected]
>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
>
>
>
>
> _______________________________________________
> Pharo-project mailing list
> [email protected]
> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
>

_______________________________________________
Pharo-project mailing list
[email protected]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Reply via email to