April 2011 - Pharo-dev - lists.pharo.org

Re: [Pharo-project] Please update Help> Announcements tutorial
by Marcus Denker April 17, 2011

April 17, 2011

I added a tracker entry: http://code.google.com/p/pharo/issues/list?thanks=4036 On Apr 15, 2011, at 6:50 PM, DougEdmunds wrote: > 1. Not understanding how announcements work, I tried the tutorial information > found under > World menu > Help> Help Browser > Announcements framework > > 2. Under Tutorial - Step 3, there is this line: > > "Transcript open." That crashes, because apparently Transcript no longer > understands 'open'. How do you open a Transcript from a workspace under > 1.3? > > 3. I created a category 'Sandbox', and a class 'MyStuff'. I put the code > from Tutorial -Step 3 into a method called anno1 > > Object subclass: #MyStuff > instanceVariableNames: '' > classVariableNames: '' > poolDictionaries: '' > category: 'Sandbox'! > > !MyStuff methodsFor: 'as yet unclassified' stamp: 'DougEdmunds 4/14/2011 > 16:27'! > anno1 > | announcer | > World announcer > on: WindowOpened > send: #value > to: [ Transcript show: 'A new window was opened';cr].! ! > > I ran "MyStuff new anno1." in a workspace. > Now every time I open a window, the Transcript shows. "A new window was > opened." > > 4. I removed the MyStuff class. But every time I open a window, the > Transcript still shows "A new window was opened." > > I return to the Announcements Tutorial, and there is NO EXPLANATION how to > get rid of this 'announcement' or whatever I should call the line that > appears in the Transcript. > > 6. So, please whoever wrote the Tutorial, update it. > > 7. And the more immediate question: how do I stop automatically printing 'A > new window was opened' in the Transcript every time I open a window? > > -- > View this message in context: http://forum.world.st/Please-update-Help-Announcements-tutorial-tp3452524p3… > Sent from the Pharo Smalltalk mailing list archive at Nabble.com. > -- Marcus Denker -- http://www.marcusdenker.de INRIA Lille -- Nord Europe. Team RMoD.

1 0

[Pharo-project] Issue 3572 in pharo: Failing test on Hudson: MCInitializationTest.testWorkingCopy
by pharo＠googlecode.com April 17, 2011

April 17, 2011

Status: Accepted Owner: marcus.d...(a)gmail.com Labels: Milestone-1.2 Milestone-1.3 New issue 3572 by marcus.d...(a)gmail.com: Failing test on Hudson: MCInitializationTest.testWorkingCopy http://code.google.com/p/pharo/issues/detail?id=3572 MCInitializationTest.testWorkingCopy strange.

1 6

Re: [Pharo-project] Issue 2294 in pharo: Fix unreliable Monticello test.
by pharo＠googlecode.com April 17, 2011

April 17, 2011

Updates: Status: Duplicate Mergedinto: 3572 Comment #6 on issue 2294 by marcus.d...(a)gmail.com: Fix unreliable Monticello test. http://code.google.com/p/pharo/issues/detail?id=2294 (No comment was entered for this change.)

1 0

[Pharo-project] Issue 4034 in pharo: Deprecate TranslucentProgressMorrph + some dead code removal
by pharo＠googlecode.com April 17, 2011

April 17, 2011

Status: FixProposed Owner: marcus.d...(a)gmail.com Labels: Milestone-1.3 New issue 4034 by marcus.d...(a)gmail.com: Deprecate TranslucentProgressMorrph + some dead code removal http://code.google.com/p/pharo/issues/detail?id=4034 TranslucentProgessMorph --> Deprecated13 and - remove methods related to Tiles, Futures + dead code in AST - clean some unsent messages in WorldState - random cleans VariableNode removeSelector: #currentValueIn:! VariableNode removeSelector: #variableGetterBlockIn:! ParseNode removeSelector: #currentValueIn:! ParseNode removeSelector: #isFutureNode! ParseNode removeSelector: #notYetImplemented! WorldState removeSelector: #worldMenuPragmaKeyword! WorldState removeSelector: #worldMenuTitle! NewParagraph removeSelector: #asParagraphForPostscript! ReadWriteStream removeSelector: #fileOutChanges! ReadWriteStream removeSelector: #fileOutClass:andObject:blocking:! WeakSubscriptionBuilder removeSelector: #requiresEphemeronsSupport! Attachments: Deprecated.1.cs 826 bytes

1 0

[Pharo-project] Issue 3655 in pharo: Tools->Configuration browser fails with DNU in Pharo1.3
by pharo＠googlecode.com April 17, 2011

April 17, 2011

Status: Accepted Owner: marcus.d...(a)gmail.com New issue 3655 by marcus.d...(a)gmail.com: Tools->Configuration browser fails with DNU in Pharo1.3 http://code.google.com/p/pharo/issues/detail?id=3655 Tools->Configuration browser fails with DNU in Pharo1.3

1 1

[Pharo-project] [1.3 core] new pre-build Core #13159
by Marcus Denker April 17, 2011

April 17, 2011

https://gforge.inria.fr/frs/download.php/28486/PharoCore-1.3-13159.zip -- Marcus Denker -- http://www.marcusdenker.de INRIA Lille -- Nord Europe. Team RMoD.

1 0

[Pharo-project] Issue 3984 in pharo: Announcements announced when a test is runned
by pharo＠googlecode.com April 17, 2011

April 17, 2011

Status: FixProposed Owner: Benjamin...(a)gmail.com Labels: Milestone-1.3 Nautilus New issue 3984 by Benjamin...(a)gmail.com: Announcements announced when a test is runned http://code.google.com/p/pharo/issues/detail?id=3984 More precisely, when the history of the test case is updated Attachments: AnnouncementsInTestCase.1.cs 2.8 KB

1 7

[Pharo-project] Issue 3967 in pharo: Announcement enhancement
by pharo＠googlecode.com April 17, 2011

April 17, 2011

Status: Accepted Owner: stephane...(a)gmail.com New issue 3967 by stephane...(a)gmail.com: Announcement enhancement http://code.google.com/p/pharo/issues/detail?id=3967 Both solutions lead to remaining subscribers being notified when an error occurs. So which is decided upon, depends on which of their respective benefits are valued more. For that, it'd be nice if more than 2 people chimed in on. :) Short summary (not guaranteed to be 100% objective) Curtailing -> - Your image may crash in some cases, more specifically if you: 1) have errors in subscribers to announcements made in system-critical processes, as they will be suspended while debugging. 2) deliver announcements in a separate thread from where they're announced, and the announcing thread does so regularily. + Easy to debug. Entire call-chain available, no modification to state caused by subsequent subscribers. Restart should always lead in bug being reproduceable. The remove-from-subscriptions part of Error-handling and ifCurtailed could be combined as well, in which case #2 no longer applies. Error handling -> - Hard/impossible to debug because: 1) If your error was in ordering, debugger will step through flawlessly if restarted. 2) You start at the context of the subscriptions action, no idea where it came from. + More robust, none of the cases mentioned in Curtailing will crash your image. With the different pros/cons mentioned above in mind, here are .cs with example implementations for what both Igor / I would like. (minus remove-from-subscriptions for ifCurtailed: ) Attachments: AnnouncementErrorHandling.zip 1.7 KB

1 2

[Pharo-project] Issue 3937 in pharo: Breaking Announcement system
by pharo＠googlecode.com April 17, 2011

April 17, 2011

Status: Accepted Owner: Benjamin...(a)gmail.com Labels: Milestone-1.3 New issue 3937 by Benjamin...(a)gmail.com: Breaking Announcement system http://code.google.com/p/pharo/issues/detail?id=3937 If an error occur during the propagation of an Announcement, then the further receiver will not be informed ... It can break the system easily because it breaks the synchronicity

1 3

[Pharo-project] Issue 4029 in pharo: DomainError and NaNException
by pharo＠googlecode.com April 17, 2011

April 17, 2011

Status: New Owner: ---- New issue 4029 by sven.van...(a)gmail.com: DomainError and NaNException http://code.google.com/p/pharo/issues/detail?id=4029 PharoCore 1.3 Name: Kernel-SvenVanCaekenberghe.867 Author: SvenVanCaekenberghe Time: 15 April 2011, 5:02:31 pm UUID: 476ee577-2508-4d70-bba1-91ffd1d63592 Ancestors: Kernel-SvenCamillo.866 added DomainError and NaNException added signaler instance variable to Exception with initialization in signal refactored Exception method categories

1 1