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

[Pharo-project] Issue 3435 in pharo: Don't draw transparent fillStules
by pharo＠googlecode.com April 7, 2011

April 7, 2011

Status: FixedWaitingToBePharoed Owner: stephane.ducasse Labels: Milestone-1.3 New issue 3435 by stephane.ducasse: Don't draw transparent fillStules http://code.google.com/p/pharo/issues/detail?id=3435 don't draw transparent fillStyles. Needed by Tweak. Imported from OpenCobalt =============== Diff against Morphic-ul.490 =============== Item was changed: ----- Method: Canvas>>fillRectangle:fillStyle:borderStyle: (in category 'drawing-rectangles') ----- fillRectangle: aRectangle fillStyle: aFillStyle borderStyle: aBorderStyle "Fill the given rectangle." + aFillStyle isTransparent ifFalse:[ + self fillRectangle: (aRectangle insetBy: aBorderStyle width) fillStyle: aFillStyle]. + aBorderStyle ifNil:[^self]. + aBorderStyle width <= 0 ifTrue:[^self]. + aBorderStyle frameRectangle: aRectangle on: self + ! - self fillRectangle: (aRectangle insetBy: aBorderStyle width) fillStyle: aFillStyle. - aBorderStyle frameRectangle: aRectangle on: self!

1 1

[Pharo-project] Issue 3392 in pharo: Class finder should probably use a different editor
by pharo＠googlecode.com April 7, 2011

April 7, 2011

Status: Accepted Owner: rydier Labels: Milestone-1.3 New issue 3392 by rydier: Class finder should probably use a different editor http://code.google.com/p/pharo/issues/detail?id=3392 The editor used is a TextEditor, yet the class finder should be smalltalk aware (to f.ex. be able to use OCompletion without having a model accessor) See discussion at http://forum.world.st/Issue-3385-in-pharo-TextEditor-doest-not-understand-m… and the related resolution for 1.2 at http://code.google.com/p/pharo/issues/detail?id=3385

1 1

[Pharo-project] Issue 3766 in pharo: Lets fix this one (which is not broken)
by pharo＠googlecode.com April 7, 2011

April 7, 2011

Status: Accepted Owner: siguc...(a)gmail.com Labels: Milestone-1.3 New issue 3766 by siguc...(a)gmail.com: Lets fix this one (which is not broken) http://code.google.com/p/pharo/issues/detail?id=3766 PlugonMorph>>wantsSteps super wantsSteps ifTrue: [^true]. "For crawling ants effect of dashed line." borderDashSpec ifNil: [^false]. ^borderDashSpec size = 5 and: [(borderDashSpec fifth) > 0] it looks like that dash spec could carry information that its actually animated. And instead of asking directly, if it needs to be animated, like borderDashSpec isAnimated morph tries to do some mumbo-jumbo to determine this.

1 2

Re: [Pharo-project] Issue 3236 in pharo: Cuis DateAndTime Enhancement
by pharo＠googlecode.com April 7, 2011

April 7, 2011

Updates: Labels: Milestone-1.3 Comment #2 on issue 3236 by stephane...(a)gmail.com: Cuis DateAndTime Enhancement http://code.google.com/p/pharo/issues/detail?id=3236 (No comment was entered for this change.)

1 1

Re: [Pharo-project] Issue 2755 in pharo: Image Save loses Form's color [black becomes transparent]
by pharo＠googlecode.com April 7, 2011

April 7, 2011

Updates: Labels: -Milestone-1.2 Milestone-1.3 Comment #12 on issue 2755 by stephane.ducasse: Image Save loses Form's color [black becomes transparent] http://code.google.com/p/pharo/issues/detail?id=2755 (No comment was entered for this change.)

1 1

Re: [Pharo-project] Issue 2454 in pharo: decompiler fix
by pharo＠googlecode.com April 7, 2011

April 7, 2011

Comment #3 on issue 2454 by marcus.denker: decompiler fix http://code.google.com/p/pharo/issues/detail?id=2454 Next action: - take the code here and make a .cs or Slice out of it

1 4

Re: [Pharo-project] Issue 2374 in pharo: Dragging a .image in a Windows VM raises an error
by pharo＠googlecode.com April 7, 2011

April 7, 2011

Comment #5 on issue 2374 by DougEdmu...(a)gmail.com: Dragging a .image in a Windows VM raises an error http://code.google.com/p/pharo/issues/detail?id=2374 This works in XP. I no longer get the "Error:invalid utf8 input detected" 1. Delete the last two lines from pharo.ini ImageFile=Contents\Resources\pharo.image WindowTitle=Pharo Development 2. Set up a filetype association for .image files to pharo.exe (this allows double-clicking to open the image). Now when you click on pharo.exe (or a shortcut to it), it will ask you to select an image file. The first time, it needs some help finding the directory where they are located; the next time, it remembers that location. By deleting the WindowsTitle= line from the pharo.ini file, the title bar shows the name of the image file that you have opened.

1 1

Re: [Pharo-project] Issue 1907 in pharo: Set with nil
by pharo＠googlecode.com April 7, 2011

April 7, 2011

Updates: Cc: -niko.schwarz -oscar.nierstrasz Labels: Milestone-1.3 Comment #21 on issue 1907 by stephane.ducasse: Set with nil http://code.google.com/p/pharo/issues/detail?id=1907 (No comment was entered for this change.)

1 2

[Pharo-project] Issue 3345 in pharo: findBinary: from Cuis as integrated in Squeak
by pharo＠googlecode.com April 5, 2011

April 5, 2011

Status: FixedWaitingToBePharoed Owner: stephane.ducasse Labels: Milestone-1.3 Difficulty-Easy New issue 3345 by stephane.ducasse: findBinary: from Cuis as integrated in Squeak http://code.google.com/p/pharo/issues/detail?id=3345 It would be nice to have a look at that and write some tests Levente Uzonyi uploaded a new version of Collections to project The Trunk: http://source.squeak.org/trunk/Collections-ul.408.mcz ==================== Summary ==================== Name: Collections-ul.408 Author: ul Time: 17 November 2010, 12:25:59.364 pm UUID: 1520a654-9c34-734d-ae16-a600d1a2b948 Ancestors: Collections-ul.407 - findBinary* enhancements from Cuis. =============== Diff against Collections-ul.407 =============== Item was changed: ----- Method: SequenceableCollection>>findBinary: (in category 'enumerating') ----- findBinary: aBlock "Search for an element in the receiver using binary search. The argument aBlock is a one-element block returning 0 - if the element is the one searched for <0 - if the search should continue in the first half >0 - if the search should continue in the second half If no matching element is found, raise an error. Examples: + #(1 3 5 7 11 15 23) findBinary: [ :arg | 11 - arg ] - #(1 3 5 7 11 15 23) findBinary:[:arg| 11 - arg] " + ^self findBinary: aBlock do: [ :found | found ] ifNone: [ self errorNotFound: aBlock ]! - ^self findBinary: aBlock ifNone: [self errorNotFound: aBlock]! Item was added: + ----- Method: SequenceableCollection>>findBinary:do:ifNone: (in category 'enumerating') ----- + findBinary: aBlock do: actionBlock ifNone: exceptionBlock + "Search for an element in the receiver using binary search. + The argument aBlock is a one-element block returning + 0 - if the element is the one searched for + <0 - if the search should continue in the first half + >0 - if the search should continue in the second half + If found, evaluate actionBlock with the found element as argument + If no matching element is found, evaluate exceptionBlock, + with the 'bounding' elements (or nil) as optional arguments. + Examples: + #(1 3 5 7 11 15 23) + findBinary: [ :arg | 11 - arg ] + do: [ :found | found ] + ifNone: [ :a :b | ('between: ', {a. b} printString) ] + #(1 3 5 7 11 15 23) + findBinary: [ :arg | 12 - arg ] + do: [ :found | found ] + ifNone: [ :a :b | ('between: ', {a. b} printString) ] + #(1 3 5 7 11 15 23) + findBinary: [ :arg | 0.5 - arg ] + do: [ :found | found ] + ifNone: [ :a :b | ('between: ', {a. b} printString) ] + #(1 3 5 7 11 15 23) + findBinary: [ :arg | 25 - arg ] + do: [ :found | found ] + ifNone: [ :a :b | ('between: ',{a. b} printString) ] + " + ^self + findBinaryIndex: aBlock + do: [ :foundIndex | actionBlock value: (self at: foundIndex) ] + ifNone: [ :prevIndex :nextIndex | + exceptionBlock + cull: (prevIndex > 0 ifTrue: [ self at: prevIndex ]) + cull: (nextIndex <= self size ifTrue: [ self at: nextIndex ]) ]! Item was changed: ----- Method: SequenceableCollection>>findBinary:ifNone: (in category 'enumerating') ----- findBinary: aBlock ifNone: exceptionBlock "Search for an element in the receiver using binary search. The argument aBlock is a one-element block returning 0 - if the element is the one searched for <0 - if the search should continue in the first half >0 - if the search should continue in the second half + If no matching element is found, evaluate exceptionBlock, + with the 'bounding' elements (or nil) as optional arguments." + + ^self findBinary: aBlock do: [ :found | found ] ifNone: exceptionBlock! - If no matching element is found, evaluate exceptionBlock." - | index low high test item | - low := 1. - high := self size. - [index := high + low // 2. - low > high] whileFalse:[ - test := aBlock value: (item := self at: index). - test = 0 - ifTrue:[^item] - ifFalse:[test > 0 - ifTrue: [low := index + 1] - ifFalse: [high := index - 1]]]. - ^exceptionBlock value! Item was changed: ----- Method: SequenceableCollection>>findBinaryIndex: (in category 'enumerating') ----- findBinaryIndex: aBlock "Search for an element in the receiver using binary search. The argument aBlock is a one-element block returning 0 - if the element is the one searched for <0 - if the search should continue in the first half >0 - if the search should continue in the second half If no matching element is found, raise an error. Examples: + #(1 3 5 7 11 15 23) findBinaryIndex: [ :arg | 11 - arg ] - #(1 3 5 7 11 15 23) findBinaryIndex:[:arg| 11 - arg] " + ^self findBinaryIndex: aBlock do: [ :found | found ] ifNone: [ self errorNotFound: aBlock]! - ^self findBinaryIndex: aBlock ifNone: [self errorNotFound: aBlock]! Item was added: + ----- Method: SequenceableCollection>>findBinaryIndex:do:ifNone: (in category 'enumerating') ----- + findBinaryIndex: aBlock do: actionBlock ifNone: exceptionBlock + "Search for an element in the receiver using binary search. + The argument aBlock is a one-element block returning + 0 - if the element is the one searched for + <0 - if the search should continue in the first half + >0 - if the search should continue in the second half + If found, evaluate actionBlock with the index as argument + If no matching element is found, evaluate exceptionBlock, + with the indexes of the 'bounding' elements as optional + arguments. Warning: Might give invalid indexes, see + examples below. + Examples: + #(1 3 5 7 11 15 23) + findBinaryIndex: [ :arg | 11 - arg ] + do: [ :found | found ] + ifNone: [ :a :b | ('between: ', {a. b} printString)] + #(1 3 5 7 11 15 23) + findBinaryIndex: [ :arg | 12 - arg ] + do: [ :found | found ] + ifNone: [ :a :b | ('between: ', {a. b} printString) ] + #(1 3 5 7 11 15 23) d + findBinaryIndex: [ :arg | 0.5 - arg ] + do: [ :found | found ] + ifNone: [ :a :b | ('between: ', {a. b} printString) ] + #(1 3 5 7 11 15 23) + findBinaryIndex: [ :arg | 25 - arg ] + do: [ :found | found ] + ifNone: [ :a :b | ('between: ',{a. b} printString) ] + " + | index low high | + low := 1. + high := self size. + [ + index := high + low // 2. + low > high ] whileFalse: [ + | test | + test := aBlock value: (self at: index). + test = 0 + ifTrue: [ ^actionBlock value: index ] + ifFalse: [ test > 0 + ifTrue: [ low := index + 1 ] + ifFalse: [ high := index - 1 ] ] ]. + ^exceptionBlock cull: high cull: low! Item was changed: ----- Method: SequenceableCollection>>findBinaryIndex:ifNone: (in category 'enumerating') ----- findBinaryIndex: aBlock ifNone: exceptionBlock "Search for an element in the receiver using binary search. The argument aBlock is a one-element block returning 0 - if the element is the one searched for <0 - if the search should continue in the first half >0 - if the search should continue in the second half + If no matching element is found, evaluate exceptionBlock, + with the indexes of the 'bounding' elements as optional + arguments. Warning: Might give invalid indexes." + + ^self findBinaryIndex: aBlock do: [ :found | found ] ifNone: exceptionBlock! - If no matching element is found, evaluate exceptionBlock." - | index low high test | - low := 1. - high := self size. - [index := high + low // 2. - low > high] whileFalse:[ - test := aBlock value: (self at: index). - test = 0 - ifTrue:[^index] - ifFalse:[test > 0 - ifTrue: [low := index + 1] - ifFalse: [high := index - 1]]]. - ^exceptionBlock value!

1 1

[Pharo-project] Issue 3645 in pharo: Update Hudson One-Click build files for 1.2
by pharo＠googlecode.com April 3, 2011

April 3, 2011

Status: Accepted Owner: marcus.d...(a)gmail.com Labels: Milestone-1.2-DevImage New issue 3645 by marcus.d...(a)gmail.com: Update Hudson One-Click build files for 1.2 http://code.google.com/p/pharo/issues/detail?id=3645 -> current VM Please list everything else...

1 5