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

[Pharo-project] Issue 3815 in pharo: Filing in Class comments raises an error
by pharo＠googlecode.com March 14, 2011

March 14, 2011

Status: Accepted Owner: ryd...(a)gmail.com Labels: Milestone-1.2 Milestone-1.3 New issue 3815 by ryd...(a)gmail.com: Filing in Class comments raises an error http://code.google.com/p/pharo/issues/detail?id=3815 Broken by SourceReference changes. ChangeRecord >> fileIn directly notifies deprecated RecentMessageSet. It seems to me like the #comment:stamp: call should correctly update RecentMessageList through the SystemChangeNotifier, and the calls could simply be removed. Need external confirmation of this though, as I have not beeen involved, and have no idea what the implications/consequences of RecentMessageSet deprecation really is. PS. We need tests for fileIns of different kinds, all tests passing for 1.2 without catching stuff like this is bad :)

1 14

[Pharo-project] Issue 3445 in pharo: [Repackage] "SUnit" should be well structured
by pharo＠googlecode.com March 14, 2011

March 14, 2011

Status: Accepted Owner: Torsten....(a)astares.de New issue 3445 by Torsten....(a)astares.de: [Repackage] "SUnit" should be well structured http://code.google.com/p/pharo/issues/detail?id=3445 Pharo 1.2beta 12280: I now reorganized the SUnit package: - introduce a SUnit-Core-X category instead of SUnit-X categories - rename SUnitGUI into SUnit-UI category - SUnit-Events becomes SUnit-Core-Announcements since announcements are used - rename ivar result in TestCaseAnnouncement into testResult since this is more consistent with ivar testCase and testSelector - method comments on TestCaseAnnouncement - class comment on TestCaseAnnouncement, TestCaseEnded and TestCaseStarted - a new "SUnit-Core" package => this has to be SAVED in Monticello - a new "SUnit-UI" package => this has to be SAVED in Monticello A help package/tutorial is in preparation ... Attachments: Repackage-SUnit-Reorganize.cs 3.8 KB

1 5

Re: [Pharo-project] Issue 3073 in pharo: A version of Compiler with support for methods with many arguments including external FFI calls - For inclusion in Pharo 1.2
by pharo＠googlecode.com March 14, 2011

March 14, 2011

Updates: Status: FixProposed Comment #3 on issue 3073 by marcus.d...(a)gmail.com: A version of Compiler with support for methods with many arguments including external FFI calls - For inclusion in Pharo 1.2 http://code.google.com/p/pharo/issues/detail?id=3073 (No comment was entered for this change.)

1 0

Re: [Pharo-project] Issue 1036 in pharo: Better interrupt handler registration
by pharo＠googlecode.com March 14, 2011

March 14, 2011

Updates: Status: FixProposed Comment #7 on issue 1036 by marcus.d...(a)gmail.com: Better interrupt handler registration http://code.google.com/p/pharo/issues/detail?id=1036 (No comment was entered for this change.)

1 0

[Pharo-project] [Bug Tracker] fixed vs. fixedProposed...
by Marcus Denker March 14, 2011

March 14, 2011

Hi, There was always the confusion of the meaning of "fixed", which actually had no clear meaning... I therefore added some weeks ago FixProposed --> this issue has a proposal of a fix, but there is no consensus that it's good FixToInclude ---> Please add to unstable ASAP This makes it clear what the status is. I now re-tagged all "fixed" issues as "FixProposed" and removed the "fixed" status. Next step: There are far too many items tagged "1.3". I think only a very select set of items should have that tag. -> FixToInclude -> Show stoppers ("If we release tomorrow, would this be a show stopper?") -> Failing tests -> Things people are actively working on. I will re-tag items... but I will turn off Email notification so that we don't get 130 mails. Marcus -- Marcus Denker -- http://www.marcusdenker.de INRIA Lille -- Nord Europe. Team RMoD.

1 0

Re: [Pharo-project] Issue 1575 in pharo: optimize WeakKeyDictionary and subclasses for messagesends
by pharo＠googlecode.com March 14, 2011

March 14, 2011

Updates: Status: Invalid Comment #3 on issue 1575 by marcus.d...(a)gmail.com: optimize WeakKeyDictionary and subclasses for messagesends http://code.google.com/p/pharo/issues/detail?id=1575 Weak* will be revisited soon. I close this.

1 0

[Pharo-project] Issue 3606 in pharo: [1.1.2] [Failing Test] Undeclared in package shout
by pharo＠googlecode.com March 14, 2011

March 14, 2011

Status: Accepted Owner: marcus.d...(a)gmail.com Labels: Milestone-1.1.2 New issue 3606 by marcus.d...(a)gmail.com: [1.1.2] [Failing Test] Undeclared in package shout http://code.google.com/p/pharo/issues/detail?id=3606 unstyledAcceptText styler hmm... these where not there before. Are we sure that 1.1 does *not* load the latest packages?

1 3

[Pharo-project] Issue 3734 in pharo: Build of 1.1 Full is broken...
by pharo＠googlecode.com March 14, 2011

March 14, 2011

Status: Accepted Owner: marcus.d...(a)gmail.com Labels: Milestone-1.1-DevImage Importance-High New issue 3734 by marcus.d...(a)gmail.com: Build of 1.1 Full is broken... http://code.google.com/p/pharo/issues/detail?id=3734 Somehow is loads different packages than in the past... THERE_BE_DRAGONS_HERE Error: Could not resolve: Collection-Arithmetic [Collection-Arithmetic] in /builds/workspace/Pharo 1.1/Pharo-1.1/package-cache http://www.squeaksource.com/PharoSound http://www.squeaksource.com/PharoNonCorePackages 19 February 2011 1:43:54 am VM: unix - i686 - linux - Squeak4.1 of 17 April 2010 [latest update: #9957] Image: Pharo1.1.1 [Latest update: #11420] SecurityManager state: Restricted: false FileAccess: true SocketAccess: true Working Dir /builds/workspace/Pharo 1.1/Pharo-1.1 Trusted Dir /builds/workspace/Pharo 1.1/Pharo-1.1/secure Untrusted Dir /builds/workspace/Pharo 1.1/Pharo-1.1/My Squeak MetacelloFetchingMCSpecLoader(Object)>>error: Receiver: a MetacelloFetchingMCSpecLoader(linear load : 2.0 [ConfigurationOfPharoSound] load : Soun...etc... Arguments and temporary variables: aString: 'Could not resolve: Collection-Arithmetic [Collection-Arithmetic] in /...etc... Receiver's instance variables: spec: a MetacelloMCVersionSpecLoader operator: #'>=' loaderPolicy: a MetacelloLoaderPolicy disablePackageCache: false

1 1

March 14, 2011

Hi guys since the esug discussion and request to take action, I kept that issue in my mind. Now I think that we should remove toolbuilder since it serves a purpose we do not need right now (developing tools to new ui framworks,...platform). Now if somebody uses it I suggest to maintain it. Stef

1 0

[Pharo-project] The current status of OSProcess
by nullPointer March 14, 2011

March 14, 2011

Please, I need know the actual status of OSProcess; what I can wit it and cannot: -Works in main platforms? Mac, Windows Linux? works of same way on all places? -I could execute external executable files? -I could execute commandline tools? -Which will be the next steps of development? -OsProcess will be integrated in Core? -Exists some place with deep doc? Thanks for the help. -- View this message in context: http://forum.world.st/The-current-status-of-OSProcess-tp3350744p3350744.html Sent from the Pharo Smalltalk mailing list archive at Nabble.com.

7 9