- Pharo-dev - lists.pharo.org

Re: [Pharo-project] Issue 3497 in pharo: Monticello Browser, +slice doesn't validate for not selecting any package

by pharo＠googlecode.com

Updates: Status: FixProposed Comment #4 on issue 3497 by damien.c...(a)gmail.com: Monticello Browser, +slice doesn't validate for not selecting any package http://code.google.com/p/pharo/issues/detail?id=3497 Name: SLICE-Issue-3497-Monticello-Browser-slice-doesnt-validate-for-not-selecting-any-package-DamienCassou.1 Author: DamienCassou Time: 12 April 2011, 11:31:32 am UUID: 17a71d3e-be65-4341-b60e-93370ed34b25 Ancestors: Dependencies: MonticelloGUI-DamienCassou.86 - Forces the user to select at least one package before being able to create a slice

April 12, 2011

[Pharo-project] Fix to be included

by Damien Cassou

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

April 12, 2011

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

by pharo＠googlecode.com

Comment #2 on 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 Use version 2 instead, as version 1 was an empty slice. Also requires to execute World initializeDesktopCommandKeySelectors to update the key strokes.

April 12, 2011

[Pharo-project] Fix to be included

by Damien Cassou

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

April 12, 2011

Re: [Pharo-project] Issue 3497 in pharo: Monticello Browser, +slice doesn't validate for not selecting any package

by pharo＠googlecode.com

Updates: Status: Started Cc: damien.c...(a)gmail.com Labels: Milestone-1.2.2 Type-RequestForEnhancement Difficulty-Easy Comment #3 on issue 3497 by damien.c...(a)gmail.com: Monticello Browser, +slice doesn't validate for not selecting any package http://code.google.com/p/pharo/issues/detail?id=3497 I agree, I've just did the same mistake

April 12, 2011

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

by pharo＠googlecode.com

Updates: Status: FixProposed Comment #1 on 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 Name: SLICE-Issue-3996-altk-opens-a-StringHolder-and-not-a-workspace-DamienCassou.1 Author: DamienCassou Time: 12 April 2011, 11:03:15 am UUID: 7f3fb192-6dab-405b-8a5f-00a8701fe323 Ancestors: - Updates PasteUpMorph>>defaultDesktopCommandKeyTriplets so that it uses the ToolSet to open a workspace - Adds ToolSet class>>openWorkspace

April 12, 2011

[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