Re: Issue 1817 in pharo: [etoy] Should remove project

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

Re: Issue 1817 in pharo: [etoy] Should remove project

pharo
Updates:
        Labels: -Milestone-1.3

Comment #3 on issue 1817 by [hidden email]: [etoy] Should remove  
project
http://code.google.com/p/pharo/issues/detail?id=1817

Not a show stopper for 1.3


_______________________________________________
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 1817 in pharo: [etoy] Should remove project

pharo
Updates:
        Status: ReviewNeeded
        Cc: [hidden email]

Comment #4 on issue 1817 by [hidden email]: [etoy] Should remove project
http://code.google.com/p/pharo/issues/detail?id=1817

Done
SLICE-Issue-1817-Should-remove-project-AlainPlantec.7
The ui process is now an instance variable of MorphicUIManager.
Project is moved to Deprecated13 package

Igor, could you check, especially
NonInteractiveUIManager>>uiProcess
and
MorphicUIManager class >> uiProcess

Thanks




_______________________________________________
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 1817 in pharo: [etoy] Should remove project

pharo
Updates:
        Labels: Milestone-1.3

Comment #5 on issue 1817 by [hidden email]: [etoy] Should remove  
project
http://code.google.com/p/pharo/issues/detail?id=1817

(No comment was entered for this change.)


_______________________________________________
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 1817 in pharo: [etoy] Should remove project

pharo
Updates:
        Status: Closed

Comment #6 on issue 1817 by [hidden email]: [etoy] Should remove  
project
http://code.google.com/p/pharo/issues/detail?id=1817

in 13215


_______________________________________________
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 1817 in pharo: [etoy] Should remove project

pharo
Updates:
        Status: Comment

Comment #7 on issue 1817 by [hidden email]: [etoy] Should remove  
project
http://code.google.com/p/pharo/issues/detail?id=1817

No, this is not loadable with monticello using the process.

The simplest thing would be to use a Changeset instead.


_______________________________________________
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 1817 in pharo: [etoy] Should remove project

pharo

Comment #8 on issue 1817 by [hidden email]: [etoy] Should remove  
project
http://code.google.com/p/pharo/issues/detail?id=1817

Strangely enough, these changes appeared again in 13216.
(making it broken the same way).




_______________________________________________
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 1817 in pharo: [etoy] Should remove project

pharo

Comment #9 on issue 1817 by [hidden email]: [etoy] Should remove  
project
http://code.google.com/p/pharo/issues/detail?id=1817

****WARNING****

For the update process, this code can not be merged with MC. Merging just  
stops, leaving the system in a strange state.

We need to do a changeset to load this.

Loading this code in the normal way already broke two times the updates  
13215 (fixed by redo it without) and 13216 (broken now)


_______________________________________________
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 1817 in pharo: [etoy] Should remove project

pharo
Updates:
        Status: FixProposed

Comment #10 on issue 1817 by [hidden email]: [etoy] Should remove  
project
http://code.google.com/p/pharo/issues/detail?id=1817

here is a cs

Attachments:
        PrjRemoval.1.cs  13.6 KB


_______________________________________________
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 1817 in pharo: [etoy] Should remove project

pharo

Comment #11 on issue 1817 by [hidden email]: [etoy] Should remove  
project
http://code.google.com/p/pharo/issues/detail?id=1817

It sounds reasonable that MorphicUIManager
holds an instance of UI process.

But be aware that it is only for MorphicUIManager.

So, using expression like:
UIManager default uiProcess
may fail if UI manager is not morphic.

So, we need a better review of this code.
We want to make sure that if we strip image from morphic, there should be  
no code
with bogus #spawnNewProcessIfThisIsUI:

I think all this logic around spawning/suspending ui process could be  
encapsulated by UI manager itself, without providing any control outside:

- a request to debug a process comes through UI manager! Therefore UI  
manager could handle this by itself, without delegating this responsibility  
to Debugger or anything else.





_______________________________________________
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 1817 in pharo: [etoy] Should remove project

pharo
Updates:
        Labels: -Milestone-1.3

Comment #12 on issue 1817 by [hidden email]: [etoy] Should remove  
project
http://code.google.com/p/pharo/issues/detail?id=1817

Let's move this to 1.4


_______________________________________________
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 1817 in pharo: [etoy] Should remove project

pharo
Updates:
        Labels: Milestone-1.4

Comment #13 on issue 1817 by [hidden email]: [etoy] Should remove  
project
http://code.google.com/p/pharo/issues/detail?id=1817

(No comment was entered for this change.)


_______________________________________________
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 1817 in pharo: [etoy] Should remove project

pharo
Updates:
        Status: Comment

Comment #14 on issue 1817 by [hidden email]: [etoy] Should remove  
project
http://code.google.com/p/pharo/issues/detail?id=1817

(No comment was entered for this change.)


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