Issue 6033 in pharo: RPackageOrganizer should use the private announcer and not the public one.

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

Issue 6033 in pharo: RPackageOrganizer should use the private announcer and not the public one.

pharo
Status: FixToInclude
Owner: [hidden email]
Labels: Type-Bug Milestone-2.0

New issue 6033 by [hidden email]: RPackageOrganizer should use the  
private announcer and not the public one.
http://code.google.com/p/pharo/issues/detail?id=6033

RPackageOrganizer>>announcer
        "PRIVATE - Do not use this announcer to register to receive events. Use  
SystemAnnouncer instead"
        ^ SystemAnnouncer privateAnnouncer


_______________________________________________
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 6033 in pharo: RPackageOrganizer should use the private announcer and not the public one.

pharo

Comment #1 on issue 6033 by [hidden email]: RPackageOrganizer should  
use the private announcer and not the public one.
http://code.google.com/p/pharo/issues/detail?id=6033

RPackageWithDoTest>>announcer
        ^ SystemAnnouncer privateAnnouncer


_______________________________________________
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 6033 in pharo: RPackageOrganizer should use the private announcer and not the public one.

pharo

Comment #2 on issue 6033 by [hidden email]: RPackageOrganizer should  
use the private announcer and not the public one.
http://code.google.com/p/pharo/issues/detail?id=6033

Issue 6032 has been merged into this issue.


_______________________________________________
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 6033 in pharo: RPackageOrganizer should use the private announcer and not the public one.

pharo
Updates:
        Status: Workneeded

Comment #3 on issue 6033 by [hidden email]: RPackageOrganizer should  
use the private announcer and not the public one.
http://code.google.com/p/pharo/issues/detail?id=6033

there is no code :)


_______________________________________________
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 6033 in pharo: RPackageOrganizer should use the private announcer and not the public one.

pharo

Comment #4 on issue 6033 by [hidden email]: RPackageOrganizer should  
use the private announcer and not the public one.
http://code.google.com/p/pharo/issues/detail?id=6033

This is five times that I fix this problem and I do not understand why it  
still show up.
BTW about "there is no code" after a while this is not fun and just makes  
me lose time.



_______________________________________________
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 6033 in pharo: RPackageOrganizer should use the private announcer and not the public one.

pharo
Updates:
        Status: Integrated

Comment #5 on issue 6033 by [hidden email]: RPackageOrganizer should  
use the private announcer and not the public one.
http://code.google.com/p/pharo/issues/detail?id=6033

(No comment was entered for this change.)


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