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

pharo at googlecode.com pharo at googlecode.com
Tue Apr 12 11:01:45 CEST 2011


Status: Started
Owner: damien.c... at gmail.com
Labels: Type-ReportDefect Milestone-1.2.2-DevImage Difficulty-Easy

New issue 3996 by damien.c... at 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'}.




More information about the Pharo-project mailing list