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

transcript is plain bad
by StÃ©phane Ducasse Dec. 3, 2013

Dec. 3, 2013

I can tell that it does not work when loading partial code because all the compiler warnings make sure that you cannot see anythingâ¦. I should have pushed my logger more. :(

8 17

Re: [Pharo-dev] Grease conflicts #packages with RPackage
by Stephan Eggermont Dec. 3, 2013

Dec. 3, 2013

Mariano wrote: > You will only have problems with class side #packages. > Are all those 35 class side? 5 out of 35. 4 of which are in Pharo 3 Stephan

2 1

Spec table problem
by ClÃ©ment Bera Dec. 3, 2013

Dec. 3, 2013

This example I used to have does not work any more in the latest Pharo 3: tree := TreeModel new. tree openWithSpec. tree columns: (Array with: (TreeColumnModel new displayBlock: [:node | node content first asString ]; headerLabel: 'Name'; yourself) with: (TreeColumnModel new displayBlock: [:node | node content second asString ]; headerLabel: 'Last Name'; yourself) with: (TreeColumnModel new displayBlock: [:node | node content third asString ]; headerLabel: 'Age'; yourself) with: (TreeColumnModel new displayBlock: [:node | node content fourth asString ]; headerLabel: 'Gender'; yourself)). tree roots: { {'Benjamin'.'Van Ryseghem'.'26'.'M'} . {'Pamela'.'Anderson'.'Far too much'.'F'} }. How can I have a similar behavior to what it used to do ? Thanks !

2 1

Versionner CI?
by Sean P. DeNigris Dec. 3, 2013

Dec. 3, 2013

I was surprised there was no job on community contributions... ----- Cheers, Sean -- View this message in context: http://forum.world.st/Versionner-CI-tp4726899.html Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

3 3

Re: [Pharo-dev] Grease conflicts #packages with RPackage
by Stephan Eggermont Dec. 2, 2013

Dec. 2, 2013

Stef wrote: >Do you think that if an external library redefines the semantics of #class, it will be a Pharo bug? I donât know. I know I have 35 implementers of #packages in my Moose image, and 191 senders. And I know that in Magritte 3 we changed from using #description to #magritteDescription to avoid polluting the namespace with a word that is commonly used for other things. At the same time I donât exactly enjoy adding prefixes everywhere. DeprecationFinder tells me there are 60 projects on smalltalkhub using #packages. And I know I have to be careful about where I use #name. And when taking a look at the problem, I immediately run into lots of methods flagged #todo, a.o. (CompiledMethod>packageFromOrganizer:) that seems to suggest a different solution. I can imagine a more effective way of convincing Grease maintainers that they should switch API :) Stephan

2 1

Re: [Pharo-dev] Grease conflicts #packages with RPackage
by Stephan Eggermont Dec. 2, 2013

Dec. 2, 2013

Is there a pharo bug entry for this? It currently exists in Moose 5.0 (on Pharo 3.0) https://code.google.com/p/moose-technology/issues/detail?id=1018

3 2

Nautilus Tree
by Sean P. DeNigris Dec. 2, 2013

Dec. 2, 2013

That's really cool that we have started making the package list more manageable! I noticed that right now, separate packages within the same project are not collapsed. E.g. if I have MyProject-Core and MyProject-Platform, they will be siblings in the tree, instead of both under MyProject. It seems like it would be more useful to have - MyProject - Core - Platform in the tree ----- Cheers, Sean -- View this message in context: http://forum.world.st/Nautilus-Tree-tp4723819.html Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

8 18

Some squeaksource.com updates
by David T. Lewis Dec. 2, 2013

Dec. 2, 2013

Mail notifications for squeaksource.com updates have now been enabled. This function was disabled when squeaksource.com was initially re-hosted on squeak.org, and should now once again work as expected. Earlier problems that had caused repeat mail notifications for existing updates have been resolved and are not expected to cause further problems. The welcome page for http://squeaksource.com has been updated for factual content, and hopefully to appear less alarming for casual visitors. The policy of disabling new project creation remains in effect. With the welcome page updates, I also removed the instructions for moving projects from SqS to the newer repositories, because it seems a bit too unwelcoming for a "welcome" page. However, this is important information, so we need to keep it available somewhere. Is this (or could it be) available on a FAQ somewhere? If so I will link to it from the SqS welcome page. Here is the part that I removed: <h2>Migration to SmalltalkHub</h2> <p>To migrate so SmalltalkHub use the following script</p> <div class="format" style="color: #CD0A0A; background-color: #FEF1EC; border: 2px solid #CD0A0A; padding: 5px; border-radius: 4px; -moz-border-radius: 4px; -webkit-border-radius: 4px;">| source goSource destination goDestination files destinationFiles | <br/> source := MCHttpRepository location: ''http://www.squeaksource.com/YOURPROJECT''. destination := MCSmalltalkhubRepository     owner: ''YOURNAME''     project: ''YOURPROJECT''     user: ''YOURNAME''     password: ''YOURPASSWORD''. <br/> goSource := Gofer new repository: source. goDestination := Gofer new repository: destination. <br/> files := source allVersionNames. <br/> (goSource allResolved select: [ :resolved | files anySatisfy: [ :each |     resolved name = each ] ]) do: [ :each | goSource package: each packageName ]. <br/> goSource fetch. "downloads all mcz on your computer" <br/> destinationFiles := destination allVersionNames. "checks what files are already at destination" files reject: [ :file | destinationFiles includes: file ] thenDo: [ :file |     goDestination version: file ]. "selects only the mcz that are not yet at destination" <br/> goDestination push. "sends everything to SmalltalkHub" <br/> self assert: destination allVersionNames sorted = files sorted. "checks we have exactly the same files at source and destination"</div> Thanks, Dave

2 2

How to update Deep into Pharo Chapter
by Gabriel Cotelli Dec. 2, 2013

Dec. 2, 2013

Hi, Is there some way to update a Deep into Pharo Chapter? I made with the help of Sven a new extension to the exception handling and I want to contribute some words about it in the exceptions chapter. Gabriel

3 10

Pharo picture
by Yuriy Tymchuk Dec. 2, 2013

Dec. 2, 2013

Accidentally stumbled upon: http://www.deviantart.com/art/October-26-412316678 Have a nice week everyone! Uko

2 1