- Pharo-dev - lists.pharo.org

[Pharo-project] pharo-2.0-tests Â» 32,mac - Build # 308 - Failure!
by jenkins-pharo.ci.inria.fr＠jenkins-server.lille.inria.fr Aug. 21, 2012

Aug. 21, 2012

1 0

[Pharo-project] pharo-2.0-tests Â» 32,linux - Build # 308 - Failure!
by jenkins-pharo.ci.inria.fr＠jenkins-server.lille.inria.fr Aug. 21, 2012

Aug. 21, 2012

1 0

[Pharo-project] [update 2.0] #20261
by Marcus Denker Aug. 21, 2012

Aug. 21, 2012

20261 ----- Issue 6587: FileSystem API Improvement http://code.google.com/p/pharo/issues/detail?id=6587 -- Marcus Denker -- http://marcusdenker.de

1 0

[Pharo-project] Trait conflicts wtf?
by Guillermo Polito Aug. 21, 2012

Aug. 21, 2012

Trait named: #TA uses: {} category: 'ABC' Trait named: #TB uses: {} category: 'ABC' TA>>a ^10 TB>>a ^10 Object subclass: #A uses: TA + TB instanceVariableNames: '' classVariableNames: '' poolDictionaries: '' category: 'ABC' ==> A>>a ^self traitConflict ? Why not an exception from a conflictive composition? This is to Mariano me a silent failure :/ Guille

3 3

[Pharo-project] we lost the StopTheWorld status in the issue tracker?
by Mariano Martinez Peck Aug. 21, 2012

Aug. 21, 2012

I want to mark this: http://code.google.com/p/pharo/issues/detail?id=6588 but I cannot find the status...did we loose it? thanks, -- Mariano http://marianopeck.wordpress.com

2 2

[Pharo-project] [update 2.0] #20260
by Marcus Denker Aug. 20, 2012

Aug. 20, 2012

20260 ----- Issue 6577: Add Repackaging Announcements http://code.google.com/p/pharo/issues/detail?id=6577 -- Marcus Denker -- http://marcusdenker.de

1 0

[Pharo-project] [update 2.0] #20259
by Marcus Denker Aug. 20, 2012

Aug. 20, 2012

20259 ----- Issue 6567: fonts and LazyListMorph http://code.google.com/p/pharo/issues/detail?id=6567 Issue 6580: Making RPackage and PackageInfo polymorphic for migration http://code.google.com/p/pharo/issues/detail?id=6580 Issue 6581: New Spec version http://code.google.com/p/pharo/issues/detail?id=6581 -- Marcus Denker -- http://marcusdenker.de

1 0

[Pharo-project] TestRunner/Nautilus shows yellow when there is a warning
by Mariano Martinez Peck Aug. 19, 2012

Aug. 19, 2012

Even if the test is "green", the TestRunner (and Nautilus) shows yellow if there was a warning. Do we want that? cheers -- Mariano http://marianopeck.wordpress.com

2 1

[Pharo-project] ANN: Periscope - Universal Navigation Sidebar for Nautilus
by Pavel Krivanek Aug. 19, 2012

Aug. 19, 2012

Hi all, I want to introduce a tool that, as I hope, may improve your Smalltalk browsing experience. It is named Periscope and it is an universal navigation sidebar for Nautilus that is common for all Nautilus windows. It is snapped to the display edge as the topmost window. Periscope uses a system of plugins written using Spec you may easily improve and adapt it for your needs. Currently it contains only three plugins created mainly for the demonstration. It is: - Tools starters plugin - Bookmarks plugin - Behavior references plugin that show class or trait references of the currently browsed class Of course I can imagine a wide side of next plugins like Spotlight plugin, instance variables plugin, method versions plugin, senders etc. Really cool would be plugins that would show additional information while writing code. Please feel free to improve Periscope. I hope Ben will come with a lot of new ideas and improvements. To test Periscope take some recent 2.0 image and evaluate: Gofer new smalltalkhubUser: 'PavelKrivanek' project: 'Periscope'; package: 'Periscope'; load. Nautilus pluginClasses add: {(Smalltalk at: #NautilusPeriscopePlugin). #none} ...then open Nautilus or open Periscope from the tools menu. Chees, -- Pavel

3 4

[Pharo-project] a thought for Finder
by Ben Coman Aug. 19, 2012

Aug. 19, 2012

Just a thought on my personal usage of Finder (in Pharo 1.4). I find the majority of my use of the <Choose Packages> button in Finder is continually filtering on the same subset of packages. This subset may be different for different contexts that I am working in, but within each context it is fairly consistent. For instance, if I'm looking at the internals of Alexandre Bergel's Roassal package, then I am always choosing all of those packages. Further, I never seem to find myself using the <All packages> button. I seem to always just open a new Finder since I usually haven't finished with the "Roassal" one and this is quicker than later again filtering on "Roassal." My proposal is that the two buttons <Choose Packages> and <All Packages> be replaced by a pull down list for which the first two items would be the same as the buttons it replaces, plus my saved "context package filters". cheers -ben

1 0