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

[Pharo-project] Issue 3996 in pharo: alt+k opens a StringHolder and not a workspace

by pharo＠googlecode.com

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'}.

April 12, 2011

[Pharo-project] [ANN] pre-build 1.3Core #13144

by Marcus Denker

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.

April 12, 2011

Re: [Pharo-project] Issue 3991 in pharo: use them instead of UITheme current

by pharo＠googlecode.com

Comment #1 on issue 3991 by fernando...(a)gmail.com: use them instead of UITheme current http://code.google.com/p/pharo/issues/detail?id=3991 I modified the refs, stil some remain, in some deprecated classes such as MenuIcons and some PolymorphSettings. I decided to add the method theme ^ UITheme current, whenver the object did not understand theme ( a non morph object), so we easily trace those by browsing implementors of #theme. Attachments: UIThemeRefsFix.2.cs 76.1 KB

April 12, 2011

[Pharo-project] [update 1.2] #12347

by Marcus Denker

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.

April 12, 2011

Re: [Pharo-project] Issue 3995 in pharo: alt+k when no window is open throws a debugger

by pharo＠googlecode.com

Updates: Labels: Milestone-1.3 Comment #2 on issue 3995 by marcus.d...(a)gmail.com: alt+k when no window is open throws a debugger http://code.google.com/p/pharo/issues/detail?id=3995 in 12347 TODO: check 1.3

April 12, 2011

Re: [Pharo-project] Issue 3980 in pharo: TestResource fails to makeAvailable an never recovers

by pharo＠googlecode.com

Updates: Status: Closed Comment #4 on issue 3980 by marcus.d...(a)gmail.com: TestResource fails to makeAvailable an never recovers http://code.google.com/p/pharo/issues/detail?id=3980 in 12347

April 12, 2011

[Pharo-project] [TODO 1.3] Things to do for 1.3

by Marcus Denker

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.

April 12, 2011

Re: [Pharo-project] Brussels Sprint: gathering number of attendes

by Andy Kellens

Hi, Could the people coming by car send me their license plate number? I would have to register you in the campus registration system such that you can enter. Kind regards, Andy On 11 Apr 2011, at 23:35, Camillo Bruni wrote: > I'll come as well ;) > > On 2011-04-11, at 17:39, Stefan Marr wrote: >> On 11 Apr 2011, at 17:33, Veronica Isabel Uquillas Gomez wrote: >>> On 11 Apr 2011, at 11:23, Johan Brichau wrote: >>>> - Steph >>>> - Marcus >>>> - Sven >>>> - Mariano >>>> - Craig Latta >>>> - Thomas Holzer >>>> - Andy >>>> - Johan >>> >>> -> Veronica >> -> Stefan > -> Camillo > >

April 12, 2011

[Pharo-project] Fix to be integrated

by Damien Cassou

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

April 12, 2011

Re: [Pharo-project] Issue 3995 in pharo: alt+k when no window is open throws a debugger

by pharo＠googlecode.com

Updates: Status: FixProposed Comment #1 on issue 3995 by damien.c...(a)gmail.com: alt+k when no window is open throws a debugger http://code.google.com/p/pharo/issues/detail?id=3995 Ok, it looks like the World #commandKeySelectors property is not properly initialized: (World valueOfProperty: #commandKeySelectors) at: $k ==> MessageSend (#open -> nil) and sending #open to nil is likely to open the debugger :-). This can easily be fixed by executing the dedicated initialize method: World initializeDesktopCommandKeySelectors. (World valueOfProperty: #commandKeySelectors) at: $k ==> MessageSend(#open -> StringHolder)

April 12, 2011