December 2010 - Pharo-dev - lists.pharo.org

Re: [Pharo-project] Issue 2247 in pharo: MessageNotUnderstood: NewInspector class>>openOn:withEvalPane:withLabel:

by pharo＠googlecode.com

Updates: Status: Duplicate Mergedinto: 3410 Comment #5 on issue 2247 by marcus.denker: MessageNotUnderstood: NewInspector class>>openOn:withEvalPane:withLabel: http://code.google.com/p/pharo/issues/detail?id=2247 (No comment was entered for this change.)

Dec. 20, 2010

Re: [Pharo-project] Issue 2705 in pharo: Collection enh for Cog

by pharo＠googlecode.com

Updates: Status: Closed Comment #6 on issue 2705 by marcus.denker: Collection enh for Cog http://code.google.com/p/pharo/issues/detail?id=2705 12283

Dec. 20, 2010

[Pharo-project] [update 1.2] #12283

by Marcus Denker

12283 ----- Issue 2690: dropping a cs file and cancelling the chooser raises and exception Issue 2705: Collection enh for Cog -- Marcus Denker -- http://www.marcusdenker.de INRIA Lille -- Nord Europe. Team RMoD.

Dec. 20, 2010

Re: [Pharo-project] Issue 2690 in pharo: dropping a cs file and cancelling the chooser raises and exception

by pharo＠googlecode.com

Updates: Status: Closed Comment #6 on issue 2690 by marcus.denker: dropping a cs file and cancelling the chooser raises and exception http://code.google.com/p/pharo/issues/detail?id=2690 12283

Dec. 20, 2010

[Pharo-project] Issue 3467 in pharo: Clean up ExternalDropHandler vs. DefaultExternalDropHandler?

by pharo＠googlecode.com

Status: Accepted Owner: marcus.denker New issue 3467 by marcus.denker: Clean up ExternalDropHandler vs. DefaultExternalDropHandler? http://code.google.com/p/pharo/issues/detail?id=3467 We fixed Issue 2690 by just fixing the nil check. But maybe we should clean up the dophandlers? Comment 1 by project member snoobabk(a)yahoo.ie, Aug 05, 2010 Error was happening because of incorrect nil check and it happens for any file dropped which has more than one service registered. Instead of fixing nil check, decided to rather remove class DefaultExternalDropHandler as it was doing same checks as ExternalDropHandler class. Because of this it would bring up the same chooser if the first chooser was cancelled. It also delegated to the same default behaviour i.e. fileStream edit. To add more handlers use ExternalDropHandler class>>registerHandler:. (see ExternalDropHandler class>>initialize see SLICE-Issue-2690-DropHandlerChooserCancelFix-CarloTeixeira.1

Dec. 20, 2010

Re: [Pharo-project] [squeak-dev] Re: Graph library in Smalltalk - Need for advices

by Alexandre Bergel

>> Couldn't we start developing something similar to Lemon (regarding "API", enitites, etc...) that would work for small scale project project in smalltalk ? > > It would be excellent. > Because now that you have a full time permanent position you can invest a bit and in 2 years you can get something really sexy.... > This is what we are doing all the time around pharo. Indeed, this is what we're doing.... Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

Dec. 20, 2010

Re: [Pharo-project] Issue 2705 in pharo: Collection enh for Cog

by pharo＠googlecode.com

Comment #5 on issue 2705 by marcus.denker: Collection enh for Cog http://code.google.com/p/pharo/issues/detail?id=2705 I will add just copyUpThrough:

Dec. 20, 2010

Re: [Pharo-project] Issue 2690 in pharo: dropping a cs file and cancelling the chooser raises and exception

by pharo＠googlecode.com

Comment #5 on issue 2690 by marcus.denker: dropping a cs file and cancelling the chooser raises and exception http://code.google.com/p/pharo/issues/detail?id=2690 For 1.2, I would just fix the nil check. I will add a new entry for cleaning up DefaultExternalDropHandler vs ExternalDropHandler Attachments: FixFor2690.1.cs 597 bytes

Dec. 20, 2010

Re: [Pharo-project] Issue 3462 in pharo: [Failing Test] SHParserST80Test.testNumbers

by pharo＠googlecode.com

Comment #2 on issue 3462 by guillermopolito: [Failing Test] SHParserST80Test.testNumbers http://code.google.com/p/pharo/issues/detail?id=3462 The failure is in here: s := 'x 1--1'. types := self tokenTypesIn: s. tokens := self tokensIn: s. self assert: types = #(patternUnary number binary #- number ). self assert: tokens = #('x' '1' '-' '-' '1'). Because it's recognizing the tokens: #('x' '1' '--' '1') whose types are #(#patternUnary #number #incompleteBinary #number)

Dec. 20, 2010

Re: [Pharo-project] Issue 3457 in pharo: Cannot show new CompiledMethod's asString

by pharo＠googlecode.com

Updates: Labels: -Milestone-1.2 Milestone-1.3 Comment #1 on issue 3457 by marcus.denker: Cannot show new CompiledMethod's asString http://code.google.com/p/pharo/issues/detail?id=3457 Question how to fix that, as a CompiledMethod new is very much undefined (no class, no source, no nothing). What should it do? return nil? I think it is not for 1.2

Dec. 20, 2010