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

[Pharo-project] gtinspector
by Tudor Girba Dec. 25, 2011

Dec. 25, 2011

Hi, Just out of curiosity: Does any of you use the GTInspector? For those that wonder what that is, here is a demo: http://www.humane-assessment.com/blog/glamorous-inspector-for-smalltalk This is available in any recent Moose image mapped as Explorer (CMD+I). You can load it in a Pharo 1.3 image by: Gofer new squeaksource: 'glamoroust'; package: 'ConfigurationOfGlamoroust'; load.(Smalltalk at: #ConfigurationOfGlamoroust) loadDefault.(Smalltalk at: #GTInspector) registerToolsOn: Smalltalk tools. Cheers, Doru -- www.tudorgirba.com "Every thing has its own flow"

4 17

[Pharo-project] [update 1.4] #14267
by stephane ducasse Dec. 25, 2011

Dec. 25, 2011

14267 ----- - Issue 5113: Use ZnClient instead of HttpClient. Let us try to see if the update stream is ok after that one. Stef

3 2

[Pharo-project] [update 1.4] #14268
by StÃ©phane Ducasse Dec. 25, 2011

Dec. 25, 2011

14268 ----- - Issue 5126: french Date format. Thanks Olivier Overlot. http://code.google.com/p/pharo/issues/detail?id=5126

1 0

[Pharo-project] [update 1.4] #14266
by StÃ©phane Ducasse Dec. 25, 2011

Dec. 25, 2011

14266 ----- - Issue 5117: MNU: Transcripter class>>open. Thanks vpnbecmann. http://code.google.com/p/pharo/issues/detail?id=5117 - Issue 5122: ZnUpdate-Dec-20. Thanks sven van caekenberghe. http://code.google.com/p/pharo/issues/detail?id=5120 Stef

1 0

[Pharo-project] IdentitySet but using #hash rather than #identityHash ?
by Mariano Martinez Peck Dec. 25, 2011

Dec. 25, 2011

Hi guys. I hope this is not a very stupid question. Background: in Fuel we have a IdentityDictionary where we put each of the objects we find while traversing the graph. We need to use IdentitySet because we cannot have repetitions (and to avoid loops) so we NEED to use #==. In such dictionary we put ALL objects of the graph, so it can be very big. Since IdentitySet uses #identityHash, it means it will be using those ONLY 12 bits in the object header. It means that we have 2^12 = 4096 different values. Question: having explained the previous, I wanted to be able to use #hash rather than #identityHash since several classes implement #hash and hence I thought that using #hash I could have less colisions and hence a better performance. I tried to make a subclass of IdentitySet that uses #hash rather than #identityHash but my image freezes. I also tried something like: set := PluggableSet new. set hashBlock: [ :elem | elem hash ]. set equalBlock: [ :a :b | a == b ]. But it doesn't work either. I works with simple tests in a workspace but when I run the full tests of Fuel, it enters in a loop in the method #hash of Collection.. Anyway, my question is, should that work? if not, what is the exact reason? Thanks in advance, -- Mariano http://marianopeck.wordpress.com

8 16

[Pharo-project] Wrong number with message tally?
by Alexandre Bergel Dec. 24, 2011

Dec. 24, 2011

Hi! MessageTally seems to give wrong values regarding the relative time spent. Consider: MessageTally spyOn: [ 100 timesRepeat: [ 1000 factorial ] ] It gives something like: -=-=-=-=-=-=-=-=-=-=-=-= - 377 tallies, 379 msec. **Tree** -------------------------------- Process: (40s) 464519168: nil -------------------------------- 65.8% {249ms} SmallInteger(Integer)>>factorial 65.8% {249ms} SmallInteger(Integer)>>factorial 65.8% {249ms} SmallInteger(Integer)>>factorial 65.8% {249ms} SmallInteger(Integer)>>factorial ... -=-=-=-=-=-=-=-=-=-=-=-= I would expect to have 100% at the root of the call graph since other threads are not reported. Is there something I am missing? If no, then I will dive into MessageTally. This is annoying. Cheers, Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

4 9

[Pharo-project] [update 1.4] #14265
by StÃ©phane Ducasse Dec. 24, 2011

Dec. 24, 2011

- Issue 5124: Chronology Printing/Accessing Efficiency Improvements. Thanks Sven van Caekenberghe. http://code.google.com/p/pharo/issues/detail?id=5124 - Issue 5067: Make package cache location changeable (first part). Thanks Mariano Martinez-Peck. http://code.google.com/p/pharo/issues/detail?id=5067. - Issue 4866: NonInteractiveTranscript Thanks Sven van Caekenberghe. http://code.google.com/p/pharo/issues/detail?id=4866 Stef

1 0

[Pharo-project] PBE2 - Draft chapters for review
by jannik.laval Dec. 24, 2011

Dec. 24, 2011

Hi list, As you probably know, the Pharo By Example 2 is in progress. Some chapters will be finished soon. And we hope to provide the whole book in 2012. So, for Chrismas, we provide you some chapters, that you can review. Feel free to send us comments if you have any. The new page is temporarily available here: http://rmod.lille.inria.fr/pbe2/. It currently has the layout of the previous book but will be changed soon. Merry Chrismas ! Jannik

1 0

Dec. 24, 2011

14264 ----- - Issue 5118: Check pointsTo: and InstVarInclude: in squeak. Thanks levente and mariano. http://code.google.com/p/pharo/issues/detail?id=5118 - Issue 5123: Clone is sent but not defined in FloatArray http://code.google.com/p/pharo/issues/detail?id=5123 - Issue 5112: More consistent SharedPool protocol. Thanks Mariano. http://code.google.com/p/pharo/issues/detail?id=5112 Stef (more to come)â¦but this is sunny today :)

1 0

[Pharo-project] Newbie observations on use of Metacello
by Ben Coman Dec. 23, 2011

Dec. 23, 2011

Some observations from the perspective of as a newbie on Pharo Package Management. I'm likely to me missing in the philosophy of the design, but from the narrow view of my own usage.... 1. When I read about Metacello being the package management system, I expected there to be a "command"(*) Metacallo but instead I see Gopher being used. This is a mixed message that lowers my comfort level feeling I understand the system as I'm trying to pick up a bundle of new ideas. As I now understand it Metacello is more about a system of backend configuration than a front end user interface. I am now more comfortable using Gopher direct - but I reflect on how I felt the first time. (*) While technically a "command" is like a verb, and Gopher is like a noun rather than a verb - I can't yet completely disengage my prior learning that considers the first part of the statement to be a "command" - and I expect other newbies might find the same. 2. The strong convention of naming things ConfigurationOfXXXX is somewhat redundant from a user perspective. 3. If copy-paste into the Workspace from a web site a sample package load (for example b> below) and then highlight the whole thing and execute, it tells me "Unknown variable: ConfigurationOfSqueakDBX, please correct, or cancel" Duh! What? Oh, I need to execute it in two parts. No one wrote that down anywhere.... The alternative "(Smalltalk at: #ConfigurationOfSqueakDBX)" adds further complexity in the eyes of a newbie. Based on the above points, it would be nice to have... a> Metacello configuration: 'SqueakDBX' load rather than... b> Gofer new b> squeaksource: 'MetacelloRepository'; b> package: 'ConfigurationOfSqueakDBX'; b> load. b> ConfigurationOfSqueakDBX project latestVersion load. While only a small saving in typing, I think it significant for newbies in terms of polish and the marketing message that Metacello really is the chosen package management system. A very rough implementation (with much of the syntax likely wrong) might be just... c> Metacello class >> package: aPackage c> | packageConfig | c> packageConfig := 'ConfigurationOf', aPackage; c> Gopher new c> squeaksource: 'MetacelloRepository'; c> package: packageConfig c> load c> ^((Smalltalk at: (packageConfig asSymbol)) Now after I've written the above I contemplate that there must have been an early design decision to not implement a separate Metacello class to avoid duplication/overlap with Monticello. However perhaps now that the system is implemented as it is, a thin shim can be put over the top to assist getting the ConfigurationOfXXX files downloaded. Additional things this Metacello class might later provide: a. Improved reliability by downloading from a system of package repository mirrors. SqueakSource was having some issues and I found [1] a fortunate backup. b. A GUI for browsing package versions c. A GUI for browsing compatibility tables from a continuous integration system that tries different permutations of Montecello packages together. 4. It seems that every ConfigurationOfXXX has its own category in the SystemBrowser. Each of these categories has only one class. This seems to me like unneeded clutter of the System Browser. It would be neater if Metacello specified its configurations to be grouped under a single category "MetacelloConfigurations" or similar. 5. The sample Metacello PBE is very good in the detail for developers to provide configurations. However there is not much directed clearly at a 'mere' user. Even though Smalltalk makes us all developers, newbies all start as mere users while exploring the system. [1] Gofer new url: 'http://dsal.cl/squeaksource/MonticelloRedirect'; package: 'MontiRedirect'; load. MRManager redirectFrom: 'http://www.squeaksource.com/' to: 'http://dsal.cl/squeaksource/'. Cheers, Ben

9 18