Issue 4332 in pharo: StartupUIManager is Morphic dependent

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
4 messages Options
Reply | Threaded
Open this post in threaded view
|

Issue 4332 in pharo: StartupUIManager is Morphic dependent

pharo
Status: FixProposed
Owner: pavel.krivanek

New issue 4332 by pavel.krivanek: StartupUIManager is Morphic dependent
http://code.google.com/p/pharo/issues/detail?id=4332

StartupUIManager uses WordState directly.
This patch makes safer use of deffered messages.

Attachments:
        StartupUIManager-inform.st  520 bytes


_______________________________________________
Pharo-bugtracker mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-bugtracker
Reply | Threaded
Open this post in threaded view
|

Re: Issue 4332 in pharo: StartupUIManager is Morphic dependent

pharo
Updates:
        Labels: Milestone-1.3

Comment #1 on issue 4332 by [hidden email]: StartupUIManager is  
Morphic dependent
http://code.google.com/p/pharo/issues/detail?id=4332

Tx pavel
Marcus I will tag these fix for 1.3 because this is good to make the  
production of small images easier.


_______________________________________________
Pharo-bugtracker mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-bugtracker
Reply | Threaded
Open this post in threaded view
|

Re: Issue 4332 in pharo: StartupUIManager is Morphic dependent

pharo

Comment #2 on issue 4332 by [hidden email]: StartupUIManager is Morphic  
dependent
http://code.google.com/p/pharo/issues/detail?id=4332

Thanks. Good catch. Startup should not assume that there are morphic loaded.

Now with this trick and with CommandLine manager, i more and more thinking  
about the need to have a separate "do this after startup" stage feature.

Because right now, the only thing which we have is #addDeferredUIMessage:
Maybe we should add a protocol to UI manager/Smalltalk to perform some  
action(s) after startup is done.
So, it may look as 2-stage startup, where on first stage you initializing  
critical parts of your system, which in case of failure leads to leaving  
from image to OS,
while in second stage, you are free to do anything (and can use UI, if it  
available).



_______________________________________________
Pharo-bugtracker mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-bugtracker
Reply | Threaded
Open this post in threaded view
|

Re: Issue 4332 in pharo: StartupUIManager is Morphic dependent

pharo
Updates:
        Status: Closed

Comment #3 on issue 4332 by [hidden email]: StartupUIManager is  
Morphic dependent
http://code.google.com/p/pharo/issues/detail?id=4332

Yes. I do not like to have code like that. I would prefer to have a nice  
infrastructure fixing the problem.
So I integrate the fix and open a new ticket.

In 13238


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