- Pharo-dev - lists.pharo.org

[Pharo-project] Fwd: [update 1.1] #11120
by StÃ©phane Ducasse Dec. 29, 2009

Dec. 29, 2009

> 11120 > ----- > > - Cleaning some tests. > #testSort, #testRestoreDefaultFonts > - Issue 1691: Adding some tests for formalParameterAt: from nicolas > - Moved FixedIdentitySet to Collections-Unordered > - Better comments. > - Better shuffledBy: > - Issue 1713: Clean Duplication in widthOfString:from:to: > > >

1 0

[Pharo-project] Fwd: [update 1.1] #11119
by StÃ©phane Ducasse Dec. 29, 2009

Dec. 29, 2009

11119 ----- - Issue 1711: Cleaning host menu Mike can you confirm that everybody is ok. Tx Stef

1 0

Re: [Pharo-project] Pharo-project Digest, Vol 20, Issue 286
by Colin Putney Dec. 29, 2009

Dec. 29, 2009

On 2009-12-29, at 2:15 AM, pharo-project-request(a)lists.gforge.inria.fr wrote: > >> Good point. When I have a fix for OB under pharo. What is the preferred >> ?process. So far I posted them on the bug tracker, is that okay? > > OB has its bug tracker at <http://code.google.com/p/omnibrowser/>. > > In the past people have been committing fixes to > http://source.wiresong.ca/ob. The problem with this approach was that > there is no control over what got integrated. People submitted changes > to wrong packages, untested changes, changes that broke the tests, > changes that broke the meta-model, or changes that simply broke some > browsers. Then people merged random branches and it was not clear what > to load, what worked and what didn't. I don't know what the take on > this is from Colin? Yes, we definitely need a little more process around this. I'm thinking of having a separate inbox repository where contributions can be made. Once a contribution had been tested, it would be promoted to the main repository. Ultimately, I'd like to have a robot do at least part of that - run the tests and either report test failures or promote the changes - but for now we can do it manually. Thoughts? Colin

2 2

[Pharo-project] pharo images - Win32 Installer
by Torsten Bergmann Dec. 29, 2009

Dec. 29, 2009

>We have been discussing this and we want to be sure people understand that >1.1 is unstable and very yet in development. Yes, but I name them similar to the images they were built from (the ones Damien provides). You have to ask him to rename them first. At least I've updated the download page to: Windows Installer 1.0-10502-rc1dev09.12.2 (Pharo 1.0 RC1) Windows Installer 1.1-11112-alphadev09.12.2 (Pharo 1.1 unstable Alpha) Bye Torsten -- Jetzt kostenlos herunterladen: Internet Explorer 8 und Mozilla Firefox 3.5 - sicherer, schneller und einfacher! http://portal.gmx.net/de/go/atbrowser

1 0

Re: [Pharo-project] Tests of OmniBrowser
by Colin Putney Dec. 29, 2009

Dec. 29, 2009

On Mon, 28 Dec 2009, Lukas Renggli wrote: > >>> There are more related to the packages we are including? >> >> No. Only the core bits of OB are tested. There aren't any tests for the refactoring code or Shout. > > The refactoring code is quite well tested with the tests of the > refactoring engine. The thing that is not tested is the RB integration > in OB: hounders of new commands and a couple of extra browsers. I am > sorry, I was too lazy to write these tests. > > Lukas Oh, of course, I should have mentioned this in my reply to Mariano. If you're running a test suite to ensure that OB is working, it should include all the Refactory tests. BTW, no disrespect intended. I'm very glad to have refactoring integration in OB, tests or no tests! Colin

1 0

[Pharo-project] pharo images - Win32 Installer
by Torsten Bergmann Dec. 29, 2009

Dec. 29, 2009

setup_pharo1.0-10502-rc1dev09.12.2.exe and setup_pharo1.1-11112-alphadev09.12.2.exe are up on the download page Bye T. -- GRATIS fÃ¼r alle GMX-Mitglieder: Die maxdome Movie-FLAT! Jetzt freischalten unter http://portal.gmx.net/de/go/maxdome01

2 1

[Pharo-project] How to execute code before and after a package is load?
by Adrian Kuhn Dec. 29, 2009

Dec. 29, 2009

It need to turn off system notifications for TestCase while gofer updates SUnit. One way I see would be to execute some code snippet before and after loading. However the Script button in Monticello seems to be broken. I cannot add scripts to the package. What can I do? So the current way to load akuhn SUnit is [SystemChangeNotifier uniqueInstance noMoreNotificationsFor: TestCase. Gofer it displabePackageCache; squeaksource: 'akuhn'; package: 'SUnit'; package: 'SUnitGUI'; load ] ensure: [ TestCase initialize ]. which is well ... quite ugly for a Gofer script. --AA

4 4

[Pharo-project] Tests of OmniBrowser
by Mariano Martinez Peck Dec. 29, 2009

Dec. 29, 2009

Hi Colin! I saw you were committing in the OmniBrowser tests. I am interested in loading these tests in Pharo (optionally). But I am not sure which packages to include and their state. Right now, in our Pharo images we are loading the following packages from http://source.wiresong.ca/ob package: 'OmniBrowser'; package: 'OB-Morphic'; package: 'OB-Standard'; package: 'OB-Refactory'; package: 'OB-Regex'; package: 'OB-SUnitIntegration'; package: 'OB-Shout'; I saw the following tests packages: OB-Tests-Core OB-Tests-Morphic OB-Tests-Standard There are more related to the packages we are including? should these test be all green? Thank you very much. Mariano

5 9

[Pharo-project] External projects
by Schwab,Wilhelm K Dec. 28, 2009

Dec. 28, 2009

Hello all, I just noticed that the December web image (12.2) cannot open context menus for want of #isMethodNode and #isClassNode. When I last built an image, Citezen's installation was pointing to what I am told is an old copy of RIO which is broken on Windows. OS Process did not load cleanly. Do we have a plan to fix such things? There is an obvious tradeoff between using the external code in its ideally up-to-date state and having something that is known to work. At a minimum, we might have a section on the Wiki dedicated to workarounds for loading packages with problems on Pharo. PackagesTestedInPharo is close; the Notes column might link to package-specific notes elsewhere on th wiki?? In some cases (e.g. the context menus), we should probably have needed methods added to each image as it is built to avoid giving a broken image to new users. Bill

2 4

Dec. 28, 2009

hi here are the collection extensions we use in Moose. I copied them to PharoTaskForces so that we can discuss and tweak the code if wanted. My favorite is flatCollect:/flatCollectAsSet: groupedBy: There are really useful. Stef testFlatCollectArray "self debug: #testFlatCollectArray" self assert: ((#((1 2) (3 4) (5 3)) flatCollect: [ :each ]) = #(1 2 3 4 5 3)). self assert: ((#((1 2) (2 3) (1 3 4)) flatCollect: [:each]) = #(1 2 2 3 1 3 4)). self assert: ((#((1 2) (2 3) () ()) flatCollect: [:each]) = #(1 2 2 3)). self assert: ((#((1 2) (2 3) (1 3 4)) flatCollect: [:each| Array with: each]) = #(#(1 2) #(2 3) #(1 3 4))). self assert: ((#((1 2) (2 3) (1 3 4)) flatCollect: [:each| Set with: each]) = #(#(1 2) #(2 3) #(1 3 4))). testFlatCollectSet "self debug: #testFlatCollectSet" self assert: ((#((1 2) (1 2) (1 3 4)) asSet flatCollect: [:each]) = #(1 1 2 3 4) asSet). self assert: ((#() asSet flatCollect: [:each]) = #() asSet). self assert: ((#((1 2) () (1 3 4)) asSet flatCollect: [:each]) = #(1 1 2 3 4) asSet). self assert: ((#((1 2) #((99)) (1 3 4)) asSet flatCollect: [:each]) = #(1 1 2 3 4 (99)) asSet). self assert: ((#((1 2) #(()) (1 3 4)) asSet flatCollect: [:each]) = #(1 1 2 3 4 ()) asSet). testCollectAsSet "self debug: #testCollectAsSet" self assert: ((#() collectAsSet: [:each | each odd]) = Set new). self assert: (#(1 2 3 4 5 6) collectAsSet: [:each | each odd]) = (Set with: true with: false). self assert: (#(1 3 5 7 9 11) collectAsSet: [:each | each odd]) = (Set with: true). self assert: (#(1 2 3 4 5 4 3 2 1) collectAsSet: [:each | each]) = (1 to: 5) asSet. testGroupedByArray "self debug: #testGroupedByArray" | res | res := #(1 2 3 4 5) groupedBy: [:each | each odd]. self assert: (res at: true) = #(1 3 5). self assert: (res at: false) = #(2 4) Set>>flatCollect: aBlock ^self flatCollectAsSet: aBlock Symbol>>value "Allow this object to act as a ValueHolder on itself." ^self OrderedCollection>>removeAtIndex: anIndex "Remove the element of the collection at position anIndex. Answer the object removed." | obj | obj := self at: anIndex. self removeIndex: anIndex + firstIndex - 1. ^obj Collection ============================== collectAsSet: aBlock "Evaluates aBlock for each element of the receiver and collects the resulting values into a Set." "This is an efficient shorthand for [ (self collect: aBlock) asSet ]." "originally developed by a. kuhn and released under MIT." ^self inject: Set new into: [ :set :each | set add: (aBlock value: each); yourself ]. copyEmpty: aSize "Answer a copy of the receiver that contains no elements. This method should be redefined in subclasses that add instance variables, so that the state of those variables is preserved" ^self class new: aSize flatCollect: aBlock "Evaluate aBlock for each of the receiver's elements and answer the list of all resulting values flatten one level. Assumes that aBlock returns some kind of collection for each element. Equivalent to the lisp's mapcan" "original written by a. Kuhn and released under MIT" | stream | self isEmpty ifTrue: [ ^ self copy ]. stream := (self species new: 0) nsWriteStream. self do: [ :each | stream nextPutAll: (aBlock value: each) ]. ^ stream contents flatCollectAsSet: aBlock "Evaluate aBlock for each of the receiver's elements and answer the list of all resulting values flatten one level. Assumes that aBlock returns some kind of collection for each element. Equivalent to the lisp's mapcan" "original written by a. Kuhn and released under MIT" | set | self isEmpty ifTrue: [^self copy ]. set := Set new. self do: [ :each | set addAll: (aBlock value: each) ]. ^set flatten "Recursively collect each non-collection element of the receiver and its descendant collections. Please note, this implementation assumes that strings are to be treated as objects rather than as collection." ^self gather: [ :each ] groupedBy: aBlock "Return a dictionary whose keys are the result of evaluating aBlock for all elements in the collection, and the value for each key is the collection of elements that evaluated to that key. e.g. #(1 2 3 4 5) groupedBy: [:each | each odd] a Dictionary true ---> #( 1 3 5) false --> #(2 4) originally developed by a. kuhn and released under MIT." | result | result := Dictionary new. self do: [:each | | key collection | key := aBlock value: each. collection := result at: key ifAbsentPut: [OrderedCollection new]. collection add: each]. self species ~~ OrderedCollection ifTrue: ["Convert the result collections to be the right type. Note that it should be safe to modify the dictionary while iterating because we only replace values for existing keys" result keysAndValuesDo: [:key :value | result at: key put: (self species withAll: value)]]. ^result includesAll: aCollection "Answer true if the receiver includes all elements of aCollection with at least as many occurrences as in aCollection. For a less strict comparison please refer to supersetOf: and its inverse subsetOf:." ^(aCollection isCollection) and: [ aCollection size <= self size and: [ aCollection allSatisfy: [ :each | (aCollection occurrencesOf: each) <= (self occurrencesOf: each) ]]] nilSafeGroupedBy: aBlock ^ self groupedBy: [ :each | | value | value := aBlock value: each. value ifNil: [ UndefinedObject ]. ] selectAsSet: aBlock "Evaluate aBlock with each of the receiver's elements as the argument. Collect into a new set, only those elements for which aBlock evaluates to true. Answer the new collection." | newSet | newSet := Set new. self do: [:each | (aBlock value: each) ifTrue: [newSet add: each]]. ^newSet shuffle "Swaps the receiver's elements at random." self shuffle: (self size * self size log) asInteger sum: aSymbolOrBlock ^self inject: 0 into: [:sum :each | sum + (aSymbolOrBlock value: each)] shuffle: times "Swaps random elements of the receiver." | size random | size := self size. random := Random new. times timesRepeat: [ self swap: (random next * size) floor + 1 with: (random next * size) floor + 1 ].

6 23