- Pharo-dev - lists.pharo.org

[Pharo-project] Issue 3999 in pharo: Add More Explicit Error Classes for Collections
by pharo＠googlecode.com April 12, 2011

April 12, 2011

Status: New Owner: ---- New issue 3999 by camillob...(a)gmail.com: Add More Explicit Error Classes for Collections http://code.google.com/p/pharo/issues/detail?id=3999 Added OutOfBounds and some more explicit Error Messages Kernel-CamilloBruni.863 Collections-Sequenceable-CamilloBruni.87 Collections-Unordered-CamilloBruni.110

1 0

[Pharo-project] Issue 3393 in pharo: Better support of configuration dependencies in Monticello Browser
by pharo＠googlecode.com April 12, 2011

April 12, 2011

Status: Accepted Owner: alexandre.bergel CC: da...(a)teleport.com, stephane.ducasse Labels: Difficulty-Easy New issue 3393 by alexandre.bergel: Better support of configuration dependencies in Monticello Browser http://code.google.com/p/pharo/issues/detail?id=3393 Configurations are better handled now. If the configuration you're editing depends on another configuration, then it is correctly defined in the baseline. MonticelloGUI-AlexandreBergel.83 in the inbox

1 2

[Pharo-project] Fix to be included
by Damien Cassou April 12, 2011

April 12, 2011

http://code.google.com/p/pharo/issues/detail?id=3497 -- Damien Cassou http://damiencassou.seasidehosting.st "Lambdas are relegated to relative obscurity until Java makes them popular by not having them." James Iry

1 0

[Pharo-project] Issue 3996 in pharo: alt+k opens a StringHolder and not a workspace
by pharo＠googlecode.com April 12, 2011

April 12, 2011

Status: Started Owner: damien.c...(a)gmail.com Labels: Type-ReportDefect Milestone-1.2.2-DevImage Difficulty-Easy New issue 3996 by damien.c...(a)gmail.com: alt+k opens a StringHolder and not a workspace http://code.google.com/p/pharo/issues/detail?id=3996 alt+k shortcut is defined in PasteUpMorph>>defaultDesktopCommandKeyTriplets { $k. StringHolder. #open. 'Open a new, blank Workspace'}. Then, alt+k opens a StringHolder and not a plain Workspace. This prevents the user from accessing all features of workspaces (syntax highlighting, old content management, line ending handling...). It would be better to open a workspace. The correct way to do that is probably to ask the default ToolSet: ToolSet default openWorkspace However, the syntax of the table in #defaultDesktopCommandKeyTriplets prevents sending 2 messages to ToolSet. Doing { $k. ToolSet default. #openWorkspace. 'Open a new, blank Workspace'}. is fragile because it fixes the toolset upon initialization of the World. I propose to add #openWorkspace to the ToolSet class (along with a lot of other useful utilities) which would look like: ToolSet class>>openWorkspace ^ self default openWorkspace and then update #defaultDesktopCommandKeyTriplets: { $k. ToolSet. #openWorkspace. 'Open a new, blank Workspace'}.

1 2

[Pharo-project] Fix to be included
by Damien Cassou April 12, 2011

April 12, 2011

http://code.google.com/p/pharo/issues/detail?id=3996 -- Damien Cassou http://damiencassou.seasidehosting.st "Lambdas are relegated to relative obscurity until Java makes them popular by not having them." James Iry

1 0

[Pharo-project] [ANN] pre-build 1.3Core #13144
by Marcus Denker April 12, 2011

April 12, 2011

https://gforge.inria.fr/frs/download.php/28474/PharoCore-1.3-13144.zip to be linked as new unstable-core -- Marcus Denker -- http://www.marcusdenker.de INRIA Lille -- Nord Europe. Team RMoD.

1 0

[Pharo-project] [update 1.2] #12347
by Marcus Denker April 12, 2011

April 12, 2011

12347 ----- Issue 3980: TestResource fails to makeAvailable an never recovers Issue 3995: alt+k when no window is open throws a debugger -- Marcus Denker -- http://www.marcusdenker.de INRIA Lille -- Nord Europe. Team RMoD.

1 0

[Pharo-project] Issue 3980 in pharo: TestResource fails to makeAvailable an never recovers
by pharo＠googlecode.com April 12, 2011

April 12, 2011

Status: Accepted Owner: guillerm...(a)gmail.com New issue 3980 by guillerm...(a)gmail.com: TestResource fails to makeAvailable an never recovers http://code.google.com/p/pharo/issues/detail?id=3980 Using Pharo 1.2 TestResource>>makeAvailable "This method must be the _only_ way to set a notNil value for the unique instance (current). First, obtain a candidate instance and set current to a notNil placeholder (any notNil object not an instance of me would do; this version uses false). Next, check any subordinate resources needed by this resource. Lastly, setUp the candidate and put it in current if it is available, ensuring that it is torn down otherwise." | candidate | current := false. candidate := self new. .... And everywhere in the class, the check over the current var is done like current isNil ifTrue: .... So once that var is initialized, but the makeAvailable fails, it always fails...

1 4

[Pharo-project] [TODO 1.3] Things to do for 1.3
by Marcus Denker April 12, 2011

April 12, 2011

Core: - 38 Open Reports: http://code.google.com/p/pharo/issues/list?can=2&q=milestone=1.3 - Failing Tests: https://pharo-ic.lille.inria.fr/hudson/job/Pharo%20Core%201.3/lastCompleted… The most important thing for Core is to get all tests green. There are some *very* easy ones related to the headless mode... Full: - 4 Open Reports: http://code.google.com/p/pharo/issues/list?can=2&q=Milestone%3D1.3-DevImage - No tests running as build is broken (and nobody cares, I have to repeat) The most important thing for Full is to get the build to work. -- Marcus Denker -- http://www.marcusdenker.de INRIA Lille -- Nord Europe. Team RMoD.

1 0

[Pharo-project] Fix to be integrated
by Damien Cassou April 12, 2011

April 12, 2011

Issue 3995 in pharo: alt+k when no window is open throws a debugger http://code.google.com/p/pharo/issues/detail?id=3995 This is something to execute in the image, no new code involved -- Damien Cassou http://damiencassou.seasidehosting.st "Lambdas are relegated to relative obscurity until Java makes them popular by not having them." James Iry

1 0