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

Re: [Pharo-project] Notifications of windows opening/closing/focus

by Gary Chambers

Would be nice (if anyone needs it) to have a "global" access point (the World perhaps) for general notifcations as hinted at earlier. Kind of "window manager" notifications. In the individual window case, I see some use in being to pick up "reactivation" perhaps, to refresh contents etc. when costly to keep constantly in sync... Regards, Gary ----- Original Message ----- From: "Alexandre Bergel" <alexandre(a)bergel.eu> To: <Pharo-project(a)lists.gforge.inria.fr> Sent: Wednesday, January 06, 2010 3:17 PM Subject: Re: [Pharo-project] Notifications of windows opening/closing/focus >>> In this email I attached a .st file. Just load it, and it will >>> install the change set to get notifications. >> >> I see. The fact that the actual changes are in a method makes it a >> bit hard to browse (I like to browse things before installing them) >> >> Only problem is how to subscribe to a new window announcer when it >> pops up by any means (world menu, button, do-it....)? Should I scan >> World submorphs periodically? It does not seem right. >> Perhaps an announcement is missing in World, to notify a new window >> (then one can subscribe to the window) > > This is not supported currently. I haven't see a situation where I > personally need it. > I can easily add this... Do you want me to do it? > > Alexandre > >> >> >> >>> A number of people already expressed their need for such an >>> extension. >>> >>> Cheers, >>> Alexandre >>> >>> <MOMorphicExtensionInstaller.st> >>> On 4 Jan 2010, at 17:20, Gary Chambers wrote: >>> >>>> Nothing like that currently or previously AFAIK. >>>> >>>> Regards, Gary >>>> >>>> ----- Original Message ----- >>>> From: "Simon Denier" <Simon.Denier(a)inria.fr> >>>> To: "Pharo Development" <pharo-project(a)lists.gforge.inria.fr> >>>> Sent: Monday, January 04, 2010 4:00 PM >>>> Subject: [Pharo-project] Notifications of windows opening/closing/ >>>> focus >>>> >>>> >>>>> Hi >>>>> >>>>> How do you get notified of windows opening, closing, or getting >>>>> focus in >>>>> Pharo? Is there some announcements or some older events? >>>>> >>>>> >>>>> -- >>>>> Simon >>>>> >>>>> >>>>> >>>>> >>>>> _______________________________________________ >>>>> Pharo-project mailing list >>>>> Pharo-project(a)lists.gforge.inria.fr >>>>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >>>> >>>> >>>> _______________________________________________ >>>> Pharo-project mailing list >>>> Pharo-project(a)lists.gforge.inria.fr >>>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >>>> >>> >>> -- >>> _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: >>> Alexandre Bergel http://www.bergel.eu >>> ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. >>> >>> >>> >>> >>> >>> _______________________________________________ >>> Pharo-project mailing list >>> Pharo-project(a)lists.gforge.inria.fr >>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >> >> -- >> Simon >> >> >> >> >> _______________________________________________ >> Pharo-project mailing list >> Pharo-project(a)lists.gforge.inria.fr >> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >> > > -- > _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: > Alexandre Bergel http://www.bergel.eu > ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > > > > > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Jan. 6, 2010

[Pharo-project] [ANN 1.0] pre-build core #10504rc1

by Marcus Denker

http://gforge.inria.fr/frs/download.php/25143/PharoCore-1.0-10504rc1.zip

Jan. 6, 2010

Re: [Pharo-project] Dev images with or without tests?

by Alexandre Bergel

> For example, if I'm just writing a Seaside app. that does not change > Seaside itself, I would not want the Seaside tests around. I have a different opinion Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

Jan. 6, 2010

[Pharo-project] [ANN 1.1] prebuilt #11138

by Marcus Denker

http://gforge.inria.fr/frs/download.php/25142/PharoCore-1.1-11138-UNSTABLE.…

Jan. 6, 2010

Re: [Pharo-project] Dev images with or without tests?

by Alexandre Bergel

+1 Alexandre On 5 Jan 2010, at 18:15, Tudor Girba wrote: > I vote for their presence for all the reasons you mentioned. > > Cheers, > Doru > > > > On 5 Jan 2010, at 22:11, Mariano Martinez Peck wrote: > >> Ok, that's the big questions. Until now, the Dev image only >> cointained the tests of the PharoCore image. Actually, it also >> included the tests fro those projects where the test were in the >> same package (for example, RoelTyer). Now, with the new Metacello >> infrastructure, you will be able to take a PharoCore and evaluate: >> >> (ConfigurationOfPharo project version: '10496') load (which it >> will load the defualt stuff, in this case, all the stuff for a dev >> image) >> >> or >> >> (ConfigurationOfPharo project version: '10496') load: >> 'StandardDevImageWithTests' >> >> which will loads not only all the packages, but also ALL the test of >> all packages (all packages that have tests). >> >> So, my question is, should the test be included in the default dev >> image? >> >> I think that yes, because of the following: >> >> 1) Tests are useful for documentation >> 2) It encourages people to run the tests before committing something >> (that may break something) >> 3) You can see the state of the image you are using. >> 4) Because they are not bad >> 5) Because if you don't want to load the test, just add a simple >> 'StandardDevImageWithoutTests' after the load. >> 6) I don't think they take a lot of size in an image. In addition, >> it is a DEV image, not production. In production is logic that you >> don't want the tests and that may be even done with something >> similar to ScriptLoader >> cleanUpForProduction >> >> So..what do you think ? >> >> Cheers >> >> Mariano >> >> _______________________________________________ >> Pharo-project mailing list >> Pharo-project(a)lists.gforge.inria.fr >> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > > -- > www.tudorgirba.com > > "Beauty is where we see it." > > > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

Jan. 6, 2010

Re: [Pharo-project] getting crazy with ImageSegment code

by Gary Chambers

Perhaps a helper method might be useful. Here's one I alsways end up implementing on Collection for whatever Smalltalk system... classifiedBy: aBlock "Answer a dictionary where the keys are the result of evaluating the block and the values are ordered collections of the elements of the receiver that caused the block to return that key." |d| d := Dictionary new. self do: [:e | (d at: (aBlock value: e) ifAbsentPut: [OrderedCollection new]) add: e]. ^d Regards, Gary ----- Original Message ----- From: "Adrian Lienhard" <adi(a)netstyle.ch> To: <Pharo-project(a)lists.gforge.inria.fr> Sent: Wednesday, January 06, 2010 2:57 PM Subject: Re: [Pharo-project] getting crazy with ImageSegment code >I extracted some old code and adapted it slightly (see below). I've > not executed this but just typed it in Mail. And I have not completely > read/understood your code but maybe it does what you need :) > > Cheers, > Adrian > > > symbols := Symbol allSymbols. > groups := Dictionary new. > SystemOrganization categories do: [ :cat | > groups > at: cat > put: ((SystemOrganization superclassOrder: cat) select: [:c | > aCollection includes: c]) asArray ]. > groups keys do: [ :cat | > roots := groups at: cat. > roots := roots reject: [ :each | unused includes: each ]. > roots := roots , (roots collect: #class). > (ImageSegment new > copyFromRoots: roots > sizeHint: 0 > areUnique: true) > extract; > writeToFile: cat ] > > On Jan 6, 2010, at 15:44 , Mariano Martinez Peck wrote: > >> Hi folks. I will pay a beer in next ESUG to the person that helps me >> to >> refactor this piece of code of ImageSegments: >> >> The idea is that I have a list of classes that were inactive and I >> want to >> group them by category (actually, seeing the code I think it is >> package) and >> to to create an ImageSegment per category (or package). >> >> This is the code (ONLYYYYY a piece...I cut all the rest) >> >> unused := self inactiveClassesDuringDiscovery. "These are the >> classes that >> were not used" >> groups := Dictionary new. >> SystemOrganization categories do: >> [:cat | >> i := (cat findLast: [:c | c = $-]) - 1. >> i <= 0 ifTrue: [i := cat size]. >> groups at: (cat copyFrom: 1 to: i) >> put: (groups at: (cat copyFrom: 1 to: i) ifAbsent: [Array >> new]) >> , >> ((SystemOrganization superclassOrder: cat) select: [:c | >> unused includes: c]) asArray]. >> groups keys do: >> [:cat | roots := groups at: cat. >> Transcript cr; cr; show: cat; cr; print: roots; endEntry. >> roots := roots , (roots collect: [:c | c class]). >> "There seems to be a problem with these packages, thus they are >> excluded." >> ((cat beginsWith: 'Sys') or: [cat beginsWith: 'Multilingual'] >> or: >> [cat beginsWith: 'Kerne'] ) ifFalse: >> [(ImageSegment new copyFromRoots: roots sizeHint: 0) >> extract; >> writeToFile: cat]. >> Transcript cr; print: Smalltalk garbageCollect; endEntry] >> >> >> Can someone help me tu rewrite this? I think I could use >> PackageOrganizer or >> PackageInfo but I have no idea. >> >> Thanks! >> >> Mariano >> _______________________________________________ >> Pharo-project mailing list >> Pharo-project(a)lists.gforge.inria.fr >> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Jan. 6, 2010

Re: [Pharo-project] Notifications of windows opening/closing/focus

by Alexandre Bergel

>> In this email I attached a .st file. Just load it, and it will >> install the change set to get notifications. > > I see. The fact that the actual changes are in a method makes it a > bit hard to browse (I like to browse things before installing them) > > Only problem is how to subscribe to a new window announcer when it > pops up by any means (world menu, button, do-it....)? Should I scan > World submorphs periodically? It does not seem right. > Perhaps an announcement is missing in World, to notify a new window > (then one can subscribe to the window) This is not supported currently. I haven't see a situation where I personally need it. I can easily add this... Do you want me to do it? Alexandre > > > >> A number of people already expressed their need for such an >> extension. >> >> Cheers, >> Alexandre >> >> <MOMorphicExtensionInstaller.st> >> On 4 Jan 2010, at 17:20, Gary Chambers wrote: >> >>> Nothing like that currently or previously AFAIK. >>> >>> Regards, Gary >>> >>> ----- Original Message ----- >>> From: "Simon Denier" <Simon.Denier(a)inria.fr> >>> To: "Pharo Development" <pharo-project(a)lists.gforge.inria.fr> >>> Sent: Monday, January 04, 2010 4:00 PM >>> Subject: [Pharo-project] Notifications of windows opening/closing/ >>> focus >>> >>> >>>> Hi >>>> >>>> How do you get notified of windows opening, closing, or getting >>>> focus in >>>> Pharo? Is there some announcements or some older events? >>>> >>>> >>>> -- >>>> Simon >>>> >>>> >>>> >>>> >>>> _______________________________________________ >>>> Pharo-project mailing list >>>> Pharo-project(a)lists.gforge.inria.fr >>>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >>> >>> >>> _______________________________________________ >>> Pharo-project mailing list >>> Pharo-project(a)lists.gforge.inria.fr >>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >>> >> >> -- >> _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: >> Alexandre Bergel http://www.bergel.eu >> ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. >> >> >> >> >> >> _______________________________________________ >> Pharo-project mailing list >> Pharo-project(a)lists.gforge.inria.fr >> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > > -- > Simon > > > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

Jan. 6, 2010

Re: [Pharo-project] getting crazy with ImageSegment code

by Adrian Lienhard

I extracted some old code and adapted it slightly (see below). I've not executed this but just typed it in Mail. And I have not completely read/understood your code but maybe it does what you need :) Cheers, Adrian symbols := Symbol allSymbols. groups := Dictionary new. SystemOrganization categories do: [ :cat | groups at: cat put: ((SystemOrganization superclassOrder: cat) select: [:c | aCollection includes: c]) asArray ]. groups keys do: [ :cat | roots := groups at: cat. roots := roots reject: [ :each | unused includes: each ]. roots := roots , (roots collect: #class). (ImageSegment new copyFromRoots: roots sizeHint: 0 areUnique: true) extract; writeToFile: cat ] On Jan 6, 2010, at 15:44 , Mariano Martinez Peck wrote: > Hi folks. I will pay a beer in next ESUG to the person that helps me > to > refactor this piece of code of ImageSegments: > > The idea is that I have a list of classes that were inactive and I > want to > group them by category (actually, seeing the code I think it is > package) and > to to create an ImageSegment per category (or package). > > This is the code (ONLYYYYY a piece...I cut all the rest) > > unused := self inactiveClassesDuringDiscovery. "These are the > classes that > were not used" > groups := Dictionary new. > SystemOrganization categories do: > [:cat | > i := (cat findLast: [:c | c = $-]) - 1. > i <= 0 ifTrue: [i := cat size]. > groups at: (cat copyFrom: 1 to: i) > put: (groups at: (cat copyFrom: 1 to: i) ifAbsent: [Array > new]) > , > ((SystemOrganization superclassOrder: cat) select: [:c | > unused includes: c]) asArray]. > groups keys do: > [:cat | roots := groups at: cat. > Transcript cr; cr; show: cat; cr; print: roots; endEntry. > roots := roots , (roots collect: [:c | c class]). > "There seems to be a problem with these packages, thus they are > excluded." > ((cat beginsWith: 'Sys') or: [cat beginsWith: 'Multilingual'] > or: > [cat beginsWith: 'Kerne'] ) ifFalse: > [(ImageSegment new copyFromRoots: roots sizeHint: 0) > extract; > writeToFile: cat]. > Transcript cr; print: Smalltalk garbageCollect; endEntry] > > > Can someone help me tu rewrite this? I think I could use > PackageOrganizer or > PackageInfo but I have no idea. > > Thanks! > > Mariano > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Jan. 6, 2010

[Pharo-project] getting crazy with ImageSegment code

by Mariano Martinez Peck

Hi folks. I will pay a beer in next ESUG to the person that helps me to refactor this piece of code of ImageSegments: The idea is that I have a list of classes that were inactive and I want to group them by category (actually, seeing the code I think it is package) and to to create an ImageSegment per category (or package). This is the code (ONLYYYYY a piece...I cut all the rest) unused := self inactiveClassesDuringDiscovery. "These are the classes that were not used" groups := Dictionary new. SystemOrganization categories do: [:cat | i := (cat findLast: [:c | c = $-]) - 1. i <= 0 ifTrue: [i := cat size]. groups at: (cat copyFrom: 1 to: i) put: (groups at: (cat copyFrom: 1 to: i) ifAbsent: [Array new]) , ((SystemOrganization superclassOrder: cat) select: [:c | unused includes: c]) asArray]. groups keys do: [:cat | roots := groups at: cat. Transcript cr; cr; show: cat; cr; print: roots; endEntry. roots := roots , (roots collect: [:c | c class]). "There seems to be a problem with these packages, thus they are excluded." ((cat beginsWith: 'Sys') or: [cat beginsWith: 'Multilingual'] or: [cat beginsWith: 'Kerne'] ) ifFalse: [(ImageSegment new copyFromRoots: roots sizeHint: 0) extract; writeToFile: cat]. Transcript cr; print: Smalltalk garbageCollect; endEntry] Can someone help me tu rewrite this? I think I could use PackageOrganizer or PackageInfo but I have no idea. Thanks! Mariano

Jan. 6, 2010

[Pharo-project] akuhn/SUnit: run faster tests first & step through tests

by Adrian Kuhn

Hi Pharo list, The lastest akuhn/SUnit runs fasters tests first. When running your test suite for the second time, faster tests are run first. For the whole 9000 tests in the dev image, this means that the first 8000 tests are run in like 10 milliseconds. Also I fixed the menues in the test runner, you can now mark either all or single tests are expected defect. If you mark expected defects through the UI they are stored on the class side. The #expectedFailures method on the instance side is still taken into account for compatibility, but storing expected defects on the class side is the preferred way to do it now. I also cleared up the vocabulary. There are no more history on the class side, rather there are two histories one called "last run" and one called "expected defects" that both serve different purposes. The "last run" history is used to mark test results in the browser. The "expected defects" history is used to keep track of expected / unexpected defects. (As far I know, the icons in O2 show this as well.) Plus I added the ability to step through a failed tests. This stops right before the actual test method, rather than at the failed assertion. To step through a failed test, run your tests with the test runner and use the menu of test failures or errors. (OB and O2 might consider adding this option as well. In particular in combination with running fasters tests first a "run and debug/step-through first failure" might be interesting.) To load akuhn/SUnit gofer SystemChangeNotifier uniqueInstance noMoreNotificationsFor: TestCase. Gofer it disablePackageCache; squeaksource: 'akuhn'; package: 'SUnit'; package: 'SUnitGUI'; load. Thank you all for the awesome feedback last time! More is welcome :) --AA

Jan. 6, 2010