January 2016 - Pharo-dev - lists.pharo.org

Re: [Pharo-dev] Contributing to Pharo

by stepharo

Le 15/1/16 20:45, David Allouche a Ã©crit : > Hello, > > I believe the Contributing to Pharo page > http://pharo.org/contribute-propose-fix > is out of date. Certainly. Time passes so fast. > > I found a bug > https://pharo.fogbugz.com/f/cases/17396/MonticelloRepositoryBrowser-example… > > and a made a fix in in a clean image (50525), created by the newly > fixed PharoLauncher. > > Then I followed the instruction on the page. > >> * Create a slice (group of packages): >> o Open the Monticello Browser. >> o Open the Slice Maker by clicking the "Slice" button. >> o In Slice Maker enter the Fogbugz issue number and "grab" the >> issue summary. >> o Select all dirty packages affected by your bug fix. >> > I have no idea how the "list of dirty packages" is generated, but > > 1. it shows a bunch of packages I have not touched > Sometimes MC is confused and some packages get dirty while they are not. > 1. it does not show the package that contains my fix (Spec-Tools) > This is strange. And MC shows the package as dirty? Then this is a bug. > > > I looked in the world menu, and I found this menu item called > "Komitter". That sounded like a good candidate. > > > Now, I guess I should select Pharo50Inbox as the Remote, write a > commit message, click Ok and hope for the best. Sounds correct. I'm not sure that I understand Komitter :). > > Is that right? > > I guess contributors are expected to use a recent image. Yes it is always better and also to only publish one change at a time (which is annoying when you have sequences of changes but nice to track down changes). > So I think it would be good that someone updates the documentation. Or > fix the slice maker. Or both. Can you reproduce the bug? BTW it would be nice that you print and sign the pharo license, then you send us a scanned or surface mail version and we will archive it. We ask that to every contributors. Stef

Jan. 15, 2016

Re: [Pharo-dev] 17348 Enhance shortcut learnability

by stepharo

ShortcutReminder should handle both - get a display strategy - it could use growl or a morph Stef Le 13/1/16 17:03, Cyril Ferlicot D. a Ã©crit : > Le 12/01/2016 21:03, Henrik Nergaard a Ã©crit : >> Hi Stef, >> >> >> >> Something like this? (see attachment) >> >> >> >> Best regards, >> >> Henrik >> >> > Hi, > > I think it would be cool to also have a setting to get it with an > #inform: instead of a full Morph. > > I would like to get a reminder of the shortcuts but not in all my > screen. A little popup at the bottom left is less invasive. > So I think that we should be able to get both. > What do you think ? > >

Jan. 15, 2016

Re: [Pharo-dev] How can we flush the remembered expressions of Playground?

by stepharo

Yes I saw and with animation. Le 15/1/16 14:14, Tudor Girba a Ã©crit : > Hi, > > For manipulating the active bindings, you have a menu item on the top > right: > > > Doru > > > >> On Jan 15, 2016, at 12:09 PM, Andrei Chis <chisvasileandrei(a)gmail.com >> <mailto:chisvasileandrei@gmail.com>> wrote: >> >> For remembered expressions: Delete the folders play-cache and >> play-stash from the directory of the image and run 'GTPlayBook >> cleanUp' before opening the playground. >> For the bindings: in the list of displayed binding each binding has >> an action that removes it from the list (It has an X icon) >> >> >> Andrei >> >> On Fri, Jan 15, 2016 at 12:02 PM, stepharo <stepharo(a)free.fr >> <mailto:stepharo@free.fr>> wrote: >> Because when I turn videos I want to control the starting state of >> the system.... >> Then how do I reset the binding list? >> I could not find a menu entry. >> I found the resetBindings but it is not simple to grab the correct >> object. >> >> >> Stef >> >> > > -- > www.tudorgirba.com <http://www.tudorgirba.com> > www.feenk.com > > "It's not how it is, it is how we see it." >

Jan. 15, 2016

Contributing to Pharo

by David Allouche

Hello, I believe the Contributing to Pharo page http://pharo.org/contribute-propose-fix <http://pharo.org/contribute-propose-fix> is out of date. I found a bug https://pharo.fogbugz.com/f/cases/17396/MonticelloRepositoryBrowser-example… <https://pharo.fogbugz.com/f/cases/17396/MonticelloRepositoryBrowser-example…> and a made a fix in in a clean image (50525), created by the newly fixed PharoLauncher. Then I followed the instruction on the page. > Create a slice (group of packages): > Open the Monticello Browser. > Open the Slice Maker by clicking the "Slice" button. > In Slice Maker enter the Fogbugz issue number and "grab" the issue summary. > Select all dirty packages affected by your bug fix. I have no idea how the "list of dirty packages" is generated, but it shows a bunch of packages I have not touched it does not show the package that contains my fix (Spec-Tools) I looked in the world menu, and I found this menu item called "Komitter". That sounded like a good candidate. Now, I guess I should select Pharo50Inbox as the Remote, write a commit message, click Ok and hope for the best. Is that right? I guess contributors are expected to use a recent image. So I think it would be good that someone updates the documentation. Or fix the slice maker. Or both.

Jan. 15, 2016

Re: [Pharo-dev] [Moose-dev] [Pharo-users] [ann] gtdebugger in pharo 5.0

by stepharo

>> - is "stackTop" now gone ? I thought you wanted to add it to the stack ? If we add it back I would like to have a real video explaining it. For now I'm starting to redo some old videos and also simple ones to explain basic points in Pharo. Stef >> - thisContext is gone as well ? > These were removed due to emergency mail exchange that happened during the last weekend. > > >> - the Bytecode/GT button is badly placed, it looks like the "downarrow" window menu icon >> is a dropdown menu with label âBytecode" > We could try to fix by adding more space to the left of the menu bar in the theme. Could you open an issue? > > >> (since when do we put buttons in the title pane? > Since Glamour makes it easy to have them there :). The GTPlayground and GTInspector have them, too. > > >> - the evaluator pane is shown as "dirty", as it does not make a difference if we >> accept the text in this pane, there shouldn't be a dirty indicator. > This is a problem that seems to exist with basically every pharoScript in Glamour. You commented on an issue for this: > https://pharo.fogbugz.com/f/cases/16757/GLMHighlighterTextRubEditingMode-al… > > > >> - you can not use the inspector pane to change inst var values > This is a problem but it is not specific to the debugger. > > >> - there is no way to refresh the inspector pane > Indeed. Would it be enough if we added a refresh for the whole debugger? > > Cheers, > Doru > > >> I don't open bugtracker entries now, I 'll wait maybe this issues aren't bugs but >> features. >> >> >> nicolai >> >> >> >> _______________________________________________ >> Moose-dev mailing list >> Moose-dev(a)list.inf.unibe.ch >> https://www.list.inf.unibe.ch/listinfo/moose-dev > -- > www.tudorgirba.com > www.feenk.com > > "Not knowing how to do something is not an argument for how it cannot be done." > > >

Jan. 15, 2016

Re: [Pharo-dev] Color yzw

by stepharo

> > No, you are right. It isn't shown in red, even if it is a unknown > symbol. > > > > I'll have a look. > > Oh, that is bad. > The check for existing Symbols always succeeds, because > Parsing an expression with RBParser creates RBMethod- and RBMessageNodes > And they use always #asSymbol for its selectors. > Argh this is a pity because this is a really useful > > That means, as soon as we parse an expression, we add all new Symbols. > > And as the parser is now used for syntax highlighting as well, this means > new symbols will be added on compiling new methods and expressions > or just highlighting them. That's bad. > Yes I was discussing with students that used Pharo 40 during a lecture and they loved it. > > anyone an idea? > I'm trying to think. Looks like it would be good to be able to make a distinction between symbols and selectors (selectors installed in method dictionaries) Stef > > > >> 2016-01-15 13:10 GMT+01:00 stepharo <stepharo(a)free.fr > <mailto:stepharo@free.fr>>: > >>> > >>> Hi > >>> > >>> In the past in Pharo when a message was not matching an existing > selector the selector was turned into red > >> > >> > >> I think this only happened for names not known as a symbol, > regardless whether this symbol exists as a message selector or just a > symbol. > >> > >> If no symbol table includes the symbol yzw > >> > >> Color yzw > >> > >> will show yzw red, > >> > >> Color yello > >> will print yello in italic > >> Color yellow > >> will print yellow normal > >> Color jaune > >> will print jaune red, as long it is not in a SymbolTable. > >> > >> > >>> > >>> So we could see immediately that you typed an error. > >>> > >>> Right now, the behavior only exists for Class > >>> so > >>> > >>> Po is italiczec > >>> Pox is red > >>> > >>> I played with the blueStyleTable but I cannot get it working on > selector. > >>> Does anybody know? > >>> > >>> Such kind of glitch is slowing me when shooting new pharo videos. > >>> > >>> Stef > >>> > >>> > >> > > >

Jan. 15, 2016

Re: [Pharo-dev] Powerful ARM server

by Thierry Goubier

Le 15/01/2016 02:07, Ben Coman a Ã©crit : > This might make a good CI server for ARM, or ARM based Pharo cloud. > > http://hothardware.com/news/amd-unveils-64-bit-arm-based-opteron-a1100-soc-… > > cheers -ben > > Have been waiting for that one for a long time... We'll have a inhouse system with some server-ARMs at some point in the close future, so, maybe I'll be able to test a few Pharo benchmarks. But not an Opteron-based one. Thierry

Jan. 15, 2016

Re: [Pharo-dev] [Pharo-users] [ANN] OSSubprocess first milestone

by Johan Fabry

That looks very cool to me, it would have come quite in handy for some project that I did last year ;-) > On Jan 15, 2016, at 13:13, Mariano Martinez Peck <marianopeck(a)gmail.com> wrote: > > Luc, Damien, et all. > > I implemented the kind of API Luc suggested, which was a great idea. I took also his API to answer Damien question of could we do a "tail -f" example. So I made a little example where I run "tail -f system.log" and I keep a Playground updated with the stdout :) > Here is the video: > > https://dl.dropboxusercontent.com/u/6980943/tailExample.mov <https://dl.dropboxusercontent.com/u/6980943/tailExample.mov> > > Let me know what do you think. > > Cheers, > ---> Save our in-boxes! http://emailcharter.org <--- Johan Fabry - http://pleiad.cl/~jfabry PLEIAD and RyCh labs - Computer Science Department (DCC) - University of Chile

Jan. 15, 2016

Git repository and branch for spur enable pharo-vm

by Holger Freyther

Hi, what is the official pharo-vm git repository? It looks like github.com/pharo-project/pharo-vm is not being updated right now. It looks like esteban's fork is currently being used and the spur64 branch. Is that correct? Can it it to be used for spur32 and spure64? Is there any plan to merge this back into a repositpory in pharo-project/pharo-vm? kind regards holger

Jan. 15, 2016

Re: [Pharo-dev] [Moose-dev] [Pharo-users] [ann] gtdebugger in pharo 5.0

by David Allouche

> On 15 Jan 2016, at 13:39, Tudor Girba <tudor(a)tudorgirba.com> wrote: >> On Jan 14, 2016, at 12:59 PM, Andrei Chis <chisvasileandrei(a)gmail.com> wrote: > >> Most (all?) other tools don't have Accept/Cancel buttons. > > The logic is that these are actions that do not depend on the selection, so in Glamour we map these on actions that are applicable to the entire presentation. A similar approach is present in the inspector, although probably it does not appear so prominently because there is no text. We could try to add them in a dropdown menu. Would that help? In my opinion, they actions should either be directly visible in the window, or in the contextual menu, or both. But not in a dropdown. They are common actions, so I see no value in putting them in a dropdown. Dropdown menus are only interesting for actions that need to be discoverable, by providing a visual clue to explore. But they are more often than not, a bad idea. Actually, I would love if Pharo had more toolbars and menu bars. A good rule of Human Interface Guidelines (HIG) is that actions should be accessible in multiple ways: Toolbars and buttons. Not too many of them please, just for essential, application-specific actions. Menus, either in the window MS-style or at the top of the display Apple-style. Contextual menu. Shortcuts (all of them, discoverable by examining menus and contextual menus).

Jan. 15, 2016