- Pharo-dev - lists.pharo.org

Shout style table editor (Request for Feedback)

by Nicolai Hess

I am working on a syntax style table editor, see issue for some background about this. 18322 <https://pharo.fogbugz.com/f/cases/18322/Settings-for-Syntax-Highlighting-a-…> Settings for Syntax Highlighting a bit confusing 15409 <https://pharo.fogbugz.com/f/cases/15409/A-more-complete-set-of-syntactic-co…> A more complete set of syntactic colors is needed Load package ST-StylingPreview ST-StylingPreviewShoutExtension from MCHttpRepository location: 'http://smalltalkhub.com/mc/NicolaiHess/StylerTableEditor/main ' user: '' password: '' And open the preview/editor with: STStylerPreview open. This is a prototype, you can view builtin style tables, create and edit new custom style tables. This has some fake code styler methods to make the styling work for the code preview pane, and it supports more styling attributes than the default styler. This is what I would like to have as a syntax style setting dialog instead of the current confusing behavior. It may be helpful to actually see what syntax styling attributs are actually available.

Oct. 10, 2016

Re: [Pharo-dev] Pharo not working on Sierra OS

by Esteban Lorenzano

he has to copy it into /Applications because otherwise Sierra copy it into a sandbox (then it does not find sources). other problem, I did not noticed. Esteban > On 10 Oct 2016, at 18:06, Yuriy Tymchuk <yuriy.tymchuk(a)me.com> wrote: > > Hey Pharo vm developers (i.e. Esteban) we have one user who has problems. > > Though I guess we need more clarifications on how exactly it is "not working" > > Uko > > Sent from my iPhone > > Begin forwarded message: > >> From: Nevena Milojkovic <nevena(a)inf.unibe.ch <mailto:nevena@inf.unibe.ch>> >> Date: 10 October 2016 at 16:40:46 GMT+2 >> To: SCG staff <scg-staff(a)list.inf.unibe.ch <mailto:scg-staff@list.inf.unibe.ch>> >> Subject: [scg-staff] Pharo not working on Sierra OS >> >> Hi all, >> >> One of my students has problems with running Pharo on macOS Sierra. It is not working properly. >> >> Even the latest VM from today (https://dl.dropboxusercontent.com/u/7684634/pharo50-sierra-stable.zip <https://dl.dropboxusercontent.com/u/7684634/pharo50-sierra-stable.zip>) he says he can only open Nautilus. >> >> Any help? >> >> Cheers, >> Nevena >> >> >> >> >> >> >> >>

Oct. 10, 2016

Fwd: Pharo not working on Sierra OS

by Yuriy Tymchuk

Hey Pharo vm developers (i.e. Esteban) we have one user who has problems. Though I guess we need more clarifications on how exactly it is "not working" Uko Sent from my iPhone Begin forwarded message: > From: Nevena Milojkovic <nevena(a)inf.unibe.ch> > Date: 10 October 2016 at 16:40:46 GMT+2 > To: SCG staff <scg-staff(a)list.inf.unibe.ch> > Subject: [scg-staff] Pharo not working on Sierra OS > > Hi all, > > One of my students has problems with running Pharo on macOS Sierra. It is not working properly. > > Even the latest VM from today (https://dl.dropboxusercontent.com/u/7684634/pharo50-sierra-stable.zip) he says he can only open Nautilus. > > Any help? > > Cheers, > Nevena > > > > > > > >

Oct. 10, 2016

Re: [Pharo-dev] New Sierra-compatible Pharo 5.0+ VM, please test

by Sven Van Caekenberghe

> On 10 Oct 2016, at 12:09, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: > > Hi, > > Along with the pre-spur Pharo 4.0- (https://dl.dropboxusercontent.com/u/7684634/pharo40-sierra-stable.zip) I now built a VM suitable for Pharo 5.0+ (https://dl.dropboxusercontent.com/u/7684634/pharo50-sierra-stable.zip) > (this one is based on latest VM, commit 06744ef)â¦ it is still not âlatest-latestâ, but it should work for current Pharo environments. > > Iâm looking for feedback. > > cheers, > Esteban A quick test on my colleague's computer seems to confirm that both VM's work as advertised. Great! Tonight I will upgrade my own machine then and hope for the best. Thx, Sven

Oct. 10, 2016

New Sierra-compatible Pharo 5.0+ VM, please test

by Esteban Lorenzano

Hi, Along with the pre-spur Pharo 4.0- (https://dl.dropboxusercontent.com/u/7684634/pharo40-sierra-stable.zip) I now built a VM suitable for Pharo 5.0+ (https://dl.dropboxusercontent.com/u/7684634/pharo50-sierra-stable.zip <https://dl.dropboxusercontent.com/u/7684634/pharo50-sierra-stable.zip>). (this one is based on latest VM, commit 06744ef)â¦ it is still not âlatest-latestâ, but it should work for current Pharo environments. Iâm looking for feedback. cheers, Esteban

Oct. 10, 2016

Re: [Pharo-dev] Halt once

by Sven Van Caekenberghe

Can't Menu Item not be found with Spotter ? > On 10 Oct 2016, at 02:11, Ben Coman <btc(a)openinworld.com> wrote: > > In Pharo 6 I got stuck on the same and after some delay found it under > the World > Debugger menu. > It would be nice if such rearrangement of UI elements were announced > more obviously on the mail list. > cheers -ben > > On Mon, Oct 10, 2016 at 4:38 AM, phil(a)highoctane.be <phil(a)highoctane.be> wrote: >> Why no menu anymore? >> >> Phil >> >> On Sun, Oct 9, 2016 at 9:26 PM, stepharo <stepharo(a)free.fr> wrote: >>> >>> Hi guys >>> >>> we can do better in terms of comments. >>> >>> https://pharo.fogbugz.com/f/cases/19193/Halt-once-comment-mega-sucks >>> >>> In Pharo 60 I tried to use Halt once. >

Oct. 10, 2016

Re: [Pharo-dev] Halt once

by Ben Coman

In Pharo 6 I got stuck on the same and after some delay found it under the World > Debugger menu. It would be nice if such rearrangement of UI elements were announced more obviously on the mail list. cheers -ben On Mon, Oct 10, 2016 at 4:38 AM, phil(a)highoctane.be <phil(a)highoctane.be> wrote: > Why no menu anymore? > > Phil > > On Sun, Oct 9, 2016 at 9:26 PM, stepharo <stepharo(a)free.fr> wrote: >> >> Hi guys >> >> we can do better in terms of comments. >> >> https://pharo.fogbugz.com/f/cases/19193/Halt-once-comment-mega-sucks >> >> In Pharo 60 I tried to use Halt once.

Oct. 10, 2016

Re: [Pharo-dev] Halt once

by Ben Coman

On Mon, Oct 10, 2016 at 3:26 AM, stepharo <stepharo(a)free.fr> wrote: > Hi guys > > we can do better in terms of comments. > > https://pharo.fogbugz.com/f/cases/19193/Halt-once-comment-mega-sucks > > In Pharo 60 I tried to use Halt once. > > There is no menu to set it up anymore so I looked in the class ... :( > > What a supercool and welcoming comment > > Halt is provided to support Object>>halt. > > once > | callingContext senderContext node | > <debuggerCompleteToSender> I touched that last so I'll take it on the chin. I guess there were no comments before I updated it and was complacent about comments status quo. Freshening up existing comments (or lack of) hasn't been in the forefront of my mind, but you are right, modifying an existing method is a good opportunity to improve comments. cheers -ben

Oct. 10, 2016

Re: [Pharo-dev] Halt once

by phil＠highoctane.be

Why no menu anymore? Phil On Sun, Oct 9, 2016 at 9:26 PM, stepharo <stepharo(a)free.fr> wrote: > Hi guys > > we can do better in terms of comments. > > https://pharo.fogbugz.com/f/cases/19193/Halt-once-comment-mega-sucks > > In Pharo 60 I tried to use Halt once. > > There is no menu to set it up anymore so I looked in the class ... :( > > What a supercool and welcoming comment > > Halt is provided to support Object>>halt. > > once > | callingContext senderContext node | > <debuggerCompleteToSender> > > resetOnce > (#haltOnce senders, #inspectOnce senders) do: [ :method | > method ast sendNodes do: [ :sendNode| > sendNode removeProperty: #Once ifAbsent: [ ]]] > > Not a single comment! > I'm sure that we can do a lot better and think to all the newbies that > will check pharo. > > Please comments such methods and class. > > Stef > >

Oct. 9, 2016

Re: [Pharo-dev] Halt once

by stepharo

I submitted this as class comment. Halt is a special exception provided to support breakpoints as defined in Object>>halt. !! Basic usage To manually set a breakpoint you can use message halt as follows: [[[ anObject halt. ]]] You can also use [[[ Halt now ]]] [[[ Halt now: 'With a nice explanation' ]]] !! Advanced usage The class Halt supports different halting mechanisms such as conditionals, based on iteration or simply stopping the first time. !!! Conditionals [[[ foo ... Halt if: #invokedFromThisSelector ]]] This expression will only stop the execution of method foo if this method is in the call chain (is invoked from ) message invokedFromThisSelector. [[[ foo ... Halt if: aBlock ]]] The execution of foo will stop if aBlock returns true. !!! Counting Sometimes we need to stop after a given number of iteration. [[[ Halt count: 5 ]]] !!! Once It is really useful sometimes to stop only and only one time [[[ foo ... Halt once. ]]] It will be stopped the first time. Then if you need to rearm it to stop another time you should use [[[ Halt resetOnce ]]]

Oct. 9, 2016