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

[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

[Pharo-project] moose collection extensions
by StÃ©phane Ducasse Dec. 28, 2009

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

Re: [Pharo-project] Issue with gofer/metacello
by Dale Henrichs Dec. 28, 2009

Dec. 28, 2009

Gofer-dkh.105 or whichever later version predates the move of the instance variable would get Metacello back into a bootable form for all versions of Pharo. I agree that for 1.0 a stable version of Gofer be chosen ... I'm trying to restrict the current Metacello changes to avoid significant API changes, but every time Gofer moves out from under me, I'm forced into making fundamental changes. Dale ----- "Lukas Renggli" <renggli(a)gmail.com> wrote: | >> | | >> After proceeding these warnings, I have a rollback: MNU | >> | | >> GoferPackageReference class>>name:repository: | >> | | > | >> | | > Can you evaluate | >> | | > | >> | | > Â [ Gofer gofer load ] | >> | | > Â Â Â on: Error | >> | | > Â Â Â do: [ :err | err retry ]. | >> | | > Â Gofer gofer recompile. | >> | | > | >> | | > ? I don't have any senders of #name:repository: to | >> | | > GoferPackageReference. | | We can remove the deprecated warnings, but that will not solve the | real problem. Metacello is using some internal parts of Gofer that | had | to be changed to properly support fetch/push operations on multiple | repositories. | | People have to stick with an old version of Gofer/Monticello. That's | the same as with Pharo 1.1: Do not use the latest one. | | Lukas | | -- | Lukas Renggli | http://www.lukas-renggli.ch | | _______________________________________________ | Pharo-project mailing list | Pharo-project(a)lists.gforge.inria.fr | http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

3 4

[Pharo-project] When writing comment, do you use 1st person?
by Adrian Kuhn Dec. 28, 2009

Dec. 28, 2009

I know that originally all Smalltalk comments used 1st person. What is your take on that? --AA

7 8

[Pharo-project] ArchiveViewer rescue to Pharo
by Mariano Martinez Peck Dec. 28, 2009

Dec. 28, 2009

Hi folks: Yesterday with Stef we rescued ArchiveViewer from Squeak 3.9. This little tool is integrated to the FileList browser and let you unzip and zip files and stuff like this. The only thing we have to change in the core is this: http://code.google.com/p/pharo/issues/detail?id=1701 To use it, you need PharoCore version 11118 which integrates that fix (you can take and old image and load that slice). and you must download the package ArchiveViewer from ' http://www.squeaksource.com/PharoMorphicExtras' It will then be part of the pharo dev I guess. Example: 1) Open the File Browser 2) Select a zip file and you will see the options "Open zip" and "extract all" 3) After opening the zip you have a pop up with different options. I have a problem here that is using the ugly fonts instead of the StrikeFonts or even TrueType. Does someone know how can I fix this? The ArchiveViewer repository is global read/write so you can commit :) Thanks! Mariano

2 1

Dec. 28, 2009

Hi mike today: no fun no smalltalk -> just project writing. so this evening I will do an update. Stef Begin forwarded message: > From: Michael Rueger <m.rueger(a)acm.org> > Date: December 28, 2009 10:07:38 AM GMT+01:00 > To: stephane ducasse <stephane.ducasse(a)free.fr> > Subject: Re: Is mac hostmenu cleanup ready for inclusion? > > Michael Rueger wrote: >> not yet, a couple of fixes missing. > > there is now a new test and HostMenu package in the inbox. > You need to save and quit the image after the update. > > People should also test if the double paste is gone, otherwise I need to come up with new test scripts... > > Michael >

1 0

[Pharo-project] How to get item under a menu?
by Adrian Kuhn Dec. 28, 2009

Dec. 28, 2009

How can I get the item under a menu? TestRunner is built with the ToolBuilder. The lists are specified with the pluggableListSpec and I can provide a selector that builds the menu. When building the menu I can add selector for the menu entries. As it seems, the item unter the menu is never known to me. Neither when building the menu nor when performing a menu item action. So what I did is the following (an obvious hack) buildMenu: aMenu | morph index | morph := thisContext sender receiver; index := morph rowAtLocation: Sensor currentPoint. itemUnderMenu := list at: index ifAbsent: nil. itemUnderMenu ifNil: [ ^ aMenu ]. ^ aMenu title: itemUnderMenu; add: 'action' action: #action; yourself action self performActionWith: itemUnderMenu Can I get this done without a thisContext hack? --AA

1 0