August 2012 - Pharo-dev - lists.pharo.org

Re: [Pharo-project] TestRunner/Nautilus shows yellow when there is a warning

by Alexandre Bergel

I am not sure to understand. I personally expect to see the test fail if I have: -=-=-=-=-=-=-=-=-=-=-=-= testFooBar Warning signal -=-=-=-=-=-=-=-=-=-=-=-= How could it be different? Alexandre On Aug 19, 2012, at 9:42 AM, Mariano Martinez Peck <marianopeck(a)gmail.com> wrote: > 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 > -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

Aug. 19, 2012

[Pharo-project] TestRunner/Nautilus shows yellow when there is a warning

by Mariano Martinez Peck

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

Aug. 19, 2012

Re: [Pharo-project] ANN: Periscope - Universal Navigation Sidebar for Nautilus

by Pavel Krivanek

On Sun, Aug 19, 2012 at 11:51 AM, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: > > On Aug 19, 2012, at 11:39 AM, Pavel Krivanek wrote: > >> 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 > what it is? > >> - Bookmarks plugin >> - Behavior references plugin that show class or trait references of >> the currently browsed class > > > > I would love to have a view that should me in and out going reference when I click on a package :) It's doable but the list could be really long for some packages :-) > >> >> 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. > > > I like the name, next one should be radar or echo :) Sonar would be more fitting name for Nautilus :-) -- Pavel >> >> Chees, >> -- Pavel >> <PeriscopeScreenshot.png> > >

Aug. 19, 2012

Re: [Pharo-project] ANN: Periscope - Universal Navigation Sidebar for Nautilus

by Pavel Krivanek

On Sun, Aug 19, 2012 at 12:00 PM, Benjamin <benjamin.vanryseghem.pharo(a)gmail.com> wrote: > That's really cool :) > > I like it :) Great! :-) > > On Aug 19, 2012, at 11:51 AM, StÃ©phane Ducasse wrote: > >> >> On Aug 19, 2012, at 11:39 AM, Pavel Krivanek wrote: >> >>> 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 >> what it is? > > A set of buttons to open a browser, a workspace, a test runner or a MC browser :) > >>> - Bookmarks plugin >>> - Behavior references plugin that show class or trait references of >>> the currently browsed class >> >> >> >> I would love to have a view that should me in and out going reference when I click on a package :) > > Without having a deep look at the implementation, I think it can be done quite easily :) > > Just a little thing missing, a "remove" button for bookmarks :) > But clearly, I _LOVE_ bookmarks :) well, the latest version can remove them > Thanks, > Ben > > >> >>> >>> 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. >> >> >> I like the name, next one should be radar or echo :) >> >>> >>> Chees, >>> -- Pavel >>> <PeriscopeScreenshot.png> >> >> > >

Aug. 19, 2012

Re: [Pharo-project] ANN: Periscope - Universal Navigation Sidebar for Nautilus

by Benjamin

That's really cool :) I like it :) On Aug 19, 2012, at 11:51 AM, StÃ©phane Ducasse wrote: > > On Aug 19, 2012, at 11:39 AM, Pavel Krivanek wrote: > >> 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 > what it is? A set of buttons to open a browser, a workspace, a test runner or a MC browser :) >> - Bookmarks plugin >> - Behavior references plugin that show class or trait references of >> the currently browsed class > > > > I would love to have a view that should me in and out going reference when I click on a package :) Without having a deep look at the implementation, I think it can be done quite easily :) Just a little thing missing, a "remove" button for bookmarks :) But clearly, I _LOVE_ bookmarks :) Thanks, Ben > >> >> 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. > > > I like the name, next one should be radar or echo :) > >> >> Chees, >> -- Pavel >> <PeriscopeScreenshot.png> > >

Aug. 19, 2012

Re: [Pharo-project] ANN: Periscope - Universal Navigation Sidebar for Nautilus

by StÃ©phane Ducasse

On Aug 19, 2012, at 11:39 AM, Pavel Krivanek wrote: > 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 what it is? > - Bookmarks plugin > - Behavior references plugin that show class or trait references of > the currently browsed class I would love to have a view that should me in and out going reference when I click on a package :) > > 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. I like the name, next one should be radar or echo :) > > Chees, > -- Pavel > <PeriscopeScreenshot.png>

Aug. 19, 2012

[Pharo-project] ANN: Periscope - Universal Navigation Sidebar for Nautilus

by Pavel Krivanek

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

Aug. 19, 2012

[Pharo-project] a thought for Finder

by Ben Coman

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

Aug. 19, 2012

Re: [Pharo-project] 'self halt' safety net

by Ben Coman

Sean P. DeNigris wrote: > Igor Stasenko wrote > >> in pharo you can use >> Halt now. >> which is imo the right way to do it.. >> >> but i so get used to type 'self halt' .. its hard to get rid of bad >> habits. :) >> >> > > One little carrot to use "Halt now." is that it opens the debugger on the > method with the halt in it instead of on Object>>halt, where you go to be > punished for using "self halt" ;) I just found that out because after > fighting to remove "self halt", I didn't get rid of my bad habit either, ha > ha > > - S > > Except that in Pharo 1.4 the 'Halt now' line is not highlighted upon entering the debugger. Probably not required to be fixed for 1.4 but perhaps could be checked for 2.0. cheers -ben

Aug. 19, 2012

Re: [Pharo-project] numLiterals > 0 is that possible?

by StÃ©phane Ducasse

Mariano don't you like all these ifNil around in caseâ¦ and sometimes this funny logic because one object is missing. ;) So the if is not brokenâ¦ is a tragedy: you know the story where at the end everybody die = no future. We should for example, replace all the MC string concat by an object like in Squeak. Now to answer your question I think that the answer is not about if this is broken or not but what scenario does it support. So do we have cases where we want to get the class of a method that is not bound to a class? When methodClass is accessed? Stef > Replacing something is not the same as removing, I agree. But if the hacks or workaround were for a particular very good reason and some point in time, with certain image and libraries, why to keep it NOW in Pharo? Say ReferenceStream had some hacks around the system. Now we have removed it. Why should we keep the hacks in Pharo itself? No problem if someone wants to install ReferenceStream again in Pharo. But if you do so, bring with you all the hacks/workarounds to make it work. We will not keep the garbage in the main image. > Take this very example of #methodClass. Why would be need to keep the "self literals > 0" ? (if the reasons are what Eliot said). If then Newspeak wants to be built on top of Pharo, great, bring the changes (like this one) with you. > > Finally, I am not afraid/shame of rollbacking. I prefer to clean something and then discover that it was actually needed than do nothing. In fact, I would be able to document why it was needed ;) > > > > frank > > > -- > > Mariano > > http://marianopeck.wordpress.com > > > > > > > -- > Mariano > http://marianopeck.wordpress.com >

Aug. 18, 2012