April 2015 - Pharo-dev - lists.pharo.org

Re: [Pharo-dev] Spotter

by Norbert Hartl

> Am 05.04.2015 um 19:09 schrieb Ben Coman <btc(a)openinworld.com>: > > > > On Sun, Apr 5, 2015 at 11:37 PM, stepharo <stepharo(a)free.fr <mailto:stepharo@free.fr>> wrote: > aliaksei > > what would be nice is that each time we click on a button or press a command key > you emit a growl notification with the description. > > Stef > > > > For just a moment there, I thought you wanted Spotter to start making bear noises? *grin* > Me, too. But the moment didn't finish yet Norbert

April 5, 2015

Re: [Pharo-dev] Spotter

by Ben Coman

On Sun, Apr 5, 2015 at 11:37 PM, stepharo <stepharo(a)free.fr> wrote: > aliaksei > > what would be nice is that each time we click on a button or press a > command key > you emit a growl notification with the description. > > Stef > > > For just a moment there, I thought you wanted Spotter to start making bear noises? *grin*

April 5, 2015

Re: [Pharo-dev] New Pull Request for UpdatedPharoByExample

by Gaurav Singh

Thanks :) On Sun, Apr 5, 2015 at 9:09 PM, Dmitri Zagidulin <dmitri(a)zagidulin.net> wrote: > Thanks, Gaurav! It is now merged. > > I don't think one needs to send an email to the mailing list, though, for > PRs. Github usually notifies anybody who's watching the repository, when > new PRs are made. > > On Sun, Apr 5, 2015 at 9:28 AM, Gaurav Singh <grvanm.coder(a)gmail.com> > wrote: > >> I have made a few corrections in the chapter Syntax in a Nutshell. >> Link to the pull request: >> https://github.com/SquareBracketAssociates/UpdatedPharoByExample/pull/30 >> Kindly review the pull request. >> > >

April 5, 2015

Re: [Pharo-dev] New Pull Request for UpdatedPharoByExample

by Dmitri Zagidulin

Thanks, Gaurav! It is now merged. I don't think one needs to send an email to the mailing list, though, for PRs. Github usually notifies anybody who's watching the repository, when new PRs are made. On Sun, Apr 5, 2015 at 9:28 AM, Gaurav Singh <grvanm.coder(a)gmail.com> wrote: > I have made a few corrections in the chapter Syntax in a Nutshell. > Link to the pull request: > https://github.com/SquareBracketAssociates/UpdatedPharoByExample/pull/30 > Kindly review the pull request. >

April 5, 2015

Re: [Pharo-dev] 14606 Really Important bug - Can't see some variables values while debugging closure

by Ben Coman

On Sun, Apr 5, 2015 at 8:59 PM, stepharo <stepharo(a)free.fr> wrote: > > Thanks both of you for the energy you put into Pharo. > The tam really appreciates. > This is because there are guys like you that Pharo is worth being done. > Thanks for the tests. > Esteban has apparently found the bug on the VM. > > Stef > > Energy breeds energy. For me it was an opportunity to learn more deep stuff(tm) by digging with a goal. It remains a bit beyond me, but I'm happy if I've been able to beat the high grass enough to flush the tiger into the open where the marksman can take a shot at it. Nice to flush out a VM bug (can't be too many of those left ;). Let us know when we can do testing on it. I guess I'll read more about it on [vm-dev]. cheers -ben

April 5, 2015

Re: [Pharo-dev] Spotter

by stepharo

aliaksei what would be nice is that each time we click on a button or press a command key you emit a growl notification with the description. Stef Le 5/4/15 03:03, Aliaksei Syrel a Ã©crit : > Hi Ben, > > > This is quite a hidden and implicit key stroke. Regardless that I > know I've used it before follow a tutorial, I forgot it. Since > Spotter has a <Settings Icon> (which I like and think it could be > pushed as a standard throughout the system in Pharo 5), it might > be useful for Pharo 4 if the Spotter Settings page contains a "How > To" or "Keyboard shortcuts" item that just contains descriptive > text. Or if there is no facility for that, perhaps a few of the > keyboard shortcuts listed as individual items with descriptions, > even if you can't change them. I think this will be useful for > people presented with Spotter for the first time, particularly > since first use already prompts users to go to settings to send > usage data. > > > > Yes, you right, shortcuts were quite hidden. However, after we > received a lot of similar feedback we improved the situation with > shortcuts. Now all actions in Spotter have explicit action buttons: > Inline image 1 > > As soon as you press "shift" (you can't not to press shift during > usage of spotter) all action buttons are highlighted explicitly: > Inline image 2 > > If you hover action button for a few second a hint appears that tells > which shortcut is assigned to an action. If you hover the button while > pressing shift a hint appears immediately: > > Inline image 3 > > Also, in Pharo help there is a good tutorial listing all Spotter > shortcuts and assigned actions: > Inline image 4 > > How else can we improve discoverability of Spotter features? > > Cheers, > Alex > > > Cheers, > Alex > > On Sun, Apr 5, 2015 at 2:35 AM, Ben Coman <btc(a)openinworld.com > <mailto:btc@openinworld.com>> wrote: > > Thanks Aliaksei. > > This is quite a hidden and implicit key stroke. Regardless that I > know I've used it before follow a tutorial, I forgot it. Since > Spotter has a <Settings Icon> (which I like and think it could be > pushed as a standard throughout the system in Pharo 5), it might > be useful for Pharo 4 if the Spotter Settings page contains a "How > To" or "Keyboard shortcuts" item that just contains descriptive > text. Or if there is no facility for that, perhaps a few of the > keyboard shortcuts listed as individual items with descriptions, > even if you can't change them. I think this will be useful for > people presented with Spotter for the first time, particularly > since first use already prompts users to go to settings to send > usage data. > > cheers -ben > > On Sun, Apr 5, 2015 at 8:25 AM, Aliaksei Syrel > <alex.syrel(a)gmail.com <mailto:alex.syrel@gmail.com>> wrote: > > Hi Ben, > > It's CMD+Shift+Right > > On Apr 5, 2015 2:23 AM, "Ben Coman" <btc(a)openinworld.com > <mailto:btc@openinworld.com>> wrote: > > Just a note, I went back to an old image and really miss > the Spotter workflow. > > One thing, can you remind me how when it shows 5/30 > implementors I get a list of all 30? I'm sure I've done > this before but can't remember. Perhaps this means its not > obvious and maybe should appear in a "How To Use" section > in the Release Notes. > > cheers -ben > > >

April 5, 2015

Re: [Pharo-dev] Xtreams Now in MetaRepoForPharo40

by Ben Coman

Thanks Sean. On Sun, Apr 5, 2015 at 10:07 PM, Sean P. DeNigris <sean(a)clipperadams.com> wrote: > Sean P. DeNigris wrote > > It was a bit ugly... I asked a question on the MetaC list about cleaning > > it up. > > Okay, Dale explained how to do it properly > ( > http://forum.world.st/Xtreams-Pharo-4-0-Other-FileSystem-Images-tp4816537p4… > ). > New version published. > > > > ----- > Cheers, > Sean > -- > View this message in context: > http://forum.world.st/Xtreams-Now-in-MetaRepoForPharo40-tp4816538p4817681.h… > Sent from the Pharo Smalltalk Developers mailing list archive at > Nabble.com. > >

April 5, 2015

Metacello: Resolving Conflicting Attributes

by Sean P. DeNigris

Dale taught me something helpful (and maybe a little obscure) while fixing ConfigurationOfXtreams... Problem: Say you have a platform attribute #pharo4.x, and a #customProjectAttribute #FileSystem. The problem is that the FileSystem-related packages required for #pharo4.x are different than those for the default cases. spec for: #'pharo4.x' do: [ spec package: 'Xtreams-TerminalsFileSystem' with: 'Xtreams-TerminalsFileSystem.pharo40-SeanDeNigris.4' ]. ... spec for: #FileSystem do: [ spec package: 'Xtreams-TerminalsFileSystem' with: 'Xtreams-TerminalsFileSystem-nice.1'. ] Solution: Nest a "spec for: #FileSystem do:" inside the "spec for: #pharo4.x do:" declaring the #pharo4.x-specifics spec for: #'pharo4.x' do: [ spec for: #'FileSystem' do: [ spec package: 'Xtreams-TerminalsFileSystem' with: 'Xtreams-TerminalsFileSystem.pharo40-SeanDeNigris.4' ]. Why it works: Per Dale, "The spec:for:do: blocks are evaluated in attribute order (ConfigurationOfX project attributes) with top-level blocks evaluated before nested blocks ... second level blocks are evaluated in top-level block order after the first level block evaluation ... so having #FileSystem nested inside of #pharo4.x and given that #FileSystem follows #pharo4.x in attribute order means that the nested #FileSystem block inside of #pharo4.x is evaluated after to top-level #FileSystem block allowing you to do #pharo4.x specific overrides" ----- Cheers, Sean -- View this message in context: http://forum.world.st/Metacello-Resolving-Conflicting-Attributes-tp4817683.… Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

April 5, 2015

Re: [Pharo-dev] Xtreams Now in MetaRepoForPharo40

by Sean P. DeNigris

Sean P. DeNigris wrote > It was a bit ugly... I asked a question on the MetaC list about cleaning > it up. Okay, Dale explained how to do it properly (http://forum.world.st/Xtreams-Pharo-4-0-Other-FileSystem-Images-tp4816537p4…) New version published. ----- Cheers, Sean -- View this message in context: http://forum.world.st/Xtreams-Now-in-MetaRepoForPharo40-tp4816538p4817681.h… Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

April 5, 2015

New Pull Request for UpdatedPharoByExample

by Gaurav Singh

I have made a few corrections in the chapter Syntax in a Nutshell. Link to the pull request: https://github.com/SquareBracketAssociates/UpdatedPharoByExample/pull/30 Kindly review the pull request.

April 5, 2015