- Pharo-dev - lists.pharo.org

Re: [Pharo-dev] Color yzw

by Nicolai Hess

2016-01-17 9:55 GMT+01:00 Tudor Girba <tudor(a)tudorgirba.com>: > Hi, > > Indeed. Thanks. > > Could you pass your sketch around? Maybe someone else can jump in. > Just look at the attachement and load instruction in http://forum.world.st/Color-yzw-tp4871486p4871899.html It seems to work, but this is just a first try. Please review and give feedback. > > Cheers, > Doru > > > > On Jan 17, 2016, at 9:49 AM, stepharo <stepharo(a)free.fr> wrote: > > > > This is supercool that you propose a working solution. > > I'm going over the Mooc exercises (text version first to get redy to > shoot the videos). > > > > Stef > > > > Le 16/1/16 13:26, Nicolai Hess a Ã©crit : > >> > >> > >> 2016-01-16 10:11 GMT+01:00 Marcus Denker <marcus.denker(a)inria.fr>: > >> > >>>> 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) > >>> > >> > >> yes, this would improve code completion a bit, too, as there are more > symbols than symbols that are actually names > >> of methods. > >> > >> The data could be created per environment (Smalltalk globals) the first > time and then cached till shutdown. > >> (it would be an array of size 46451, pointing to existing symbols). > >> > >> The environment could cache sent selectors, tooâ¦ pablo did an > experiment with that. > >> > >> Marcus > >> > >> > >> How about a new SymbolTable "SelectorTable" that gets new entries on > every method compilation ? > >> > >> I hacked a simple experimental version. > >> But I don't yet understand the workflow for initialisation of the > Symbol class (with rehash, interned, and compacting). > >> > >> > >> > >> > > > > -- > www.tudorgirba.com > www.feenk.com > > "There are no old things, there are only old ways of looking at them." > > > > > >

Jan. 17, 2016

Re: [Pharo-dev] [Vm-dev] Where to get Monitor implementation based on primitives?

by Frank Shearar

On 7 January 2016 at 17:12, Eliot Miranda <eliot.miranda(a)gmail.com> wrote: > Hi Denis, Hi ClÃ©ment, Hi Frank, > > On Thu, Jan 7, 2016 at 5:34 AM, ClÃ©ment Bera <bera.clement(a)gmail.com> wrote: >> >> Hello, >> >> Eliot, please, you told me you had the code and Denis is interested. >> >> It uses 3 primitives for performance. > > > Forgive the delay. I thought it proper to ask permission since the code was > written while I was at Qwaq. I'm attaching the code in a fairly raw state, > see the attached. The code is MIT, but copyright 3DICC. > > It is a plugin replacement for Squeak's Mutex, and with a little ingenuity > could be a replacement for Squeak's Monitor. It is quicker because it uses > three new primitives to manage entering a critical section and setting the > owner, exiting the critical section and releasing the owner, and testing if > a critical section, entering if the section is unowned. The use of the > primitives means fewer block activations and ensure: blocks in entering and > exiting the critical section, and that's the actual cause of the speed-up. > > You can benchmark the code as is. Here are some results on 32-bit Spur, on > my 2.2GHz Core i7 > > {Mutex new. Monitor new. CriticalSection new} collect: > [:cs| | n | > n := 0. > [cs critical: [n := n + 1]. cs critical: [n := n + 1]. cs critical: [n := n > + 1]. cs critical: [n := n + 1]. cs critical: [n := n + 1]. > cs critical: [n := n - 1]. cs critical: [n := n - 1]. cs critical: [n := n - > 1]. cs critical: [n := n - 1]. cs critical: [n := n - 1]. > n ] bench] > > {Mutex new. Monitor new. CriticalSection new} collect: > [:cs| | n | > n := 0. > cs class name, ' -> ', > [cs critical: [n := n + 1]. cs critical: [n := n + 1]. cs critical: [n := n > + 1]. cs critical: [n := n + 1]. cs critical: [n := n + 1]. > cs critical: [n := n - 1]. cs critical: [n := n - 1]. cs critical: [n := n - > 1]. cs critical: [n := n - 1]. cs critical: [n := n - 1]. > n ] bench] > > #( 'Mutex -> 440,000 per second. 2.27 microseconds per run.' > 'Monitor -> 688,000 per second. 1.45 microseconds per run.' > 'CriticalSection -> 1,110,000 per second. 900 nanoseconds per run.') > > Replacement is probably trivial; rename Mutex to OldMutex, rename > CriticalSection to Mutex, recompile. But there are lots of mutexes in the > system and these are potentially owned. Transforming unowned ones is > trivial, but transforming owned ones is, I think, impossible. But at least > in my system there are no owned mutexes or monitors. > > Frank (or anyone else), would you be interested in creating a replacement > for Squeak's Monitor based on CriticalSection? It sounds like an interesting problem. I watched the thread unfold and I'm still not massively clear on what is required though? (Apologies for the delay in responding: my cup overfloweth at the moment, but should resume normal levels in a month or so.) frank

Jan. 17, 2016

Re: [Pharo-dev] [Pharo-users] Getting Updated Pharo By Example out the door

by Dimitris Chloupis

Ok then I will move my focus to Pharo 5. On Sun, Jan 17, 2016 at 12:51 PM stepharo <stepharo(a)free.fr> wrote: > Thanks. > Ok I do not know. The difference is not that large between Pharo 40 and > Pharo50. > So when I will read it I will check and see. I will try to avoid to > document features that are 40 only. > And I will try to stay as compatible with Pharo 50 as possible. > > Once I have finished with the first exercise for the mooc > Counter today I will start reading chapter one. > > > Le 17/1/16 10:45, Dimitris Chloupis a Ã©crit : > > I am here to help you Stef , I am actually doing what you are doing going > one chapter at a time, but for me its not 3 chapter per week but rather 1 > chapter per week but I can boost my speed to 3 chapters per week and just > dont pay so much attention to detail as I currently do. My goal so far was > to focus on Pharo 4 and not Pharo 5, so I can make a Pharo 4 release > (github release and github tag) and then move to pharo 5 at least one month > before pharo 5 is released. > > But because I know that your MOOC is based on Pharo 5 maybe you want to > move UPBE directly to pharo 5 (not hard to do because we have already > documented some parts of pharo 5) which works for me too. > > On Sun, Jan 17, 2016 at 11:05 AM stepharo <stepharo(a)free.fr> wrote: > >> Hi guys >> >> I will read from start to end the book and we will get it on lulu. I >> plan to read up to 3 chapters per week. >> If you want to help for real this is the time. >> >> >> https://ci.inria.fr/pharo-contribution/view/Books/job/UpdatedPharoByExample… >> >> I rewrote the chapter on metaclass and a couple of other points because >> TranslucentColor is not available anymore. >> I will not rewrite what I do not like (I should now have written in the >> first place :). So I'm not looking >> for the perfect solution but to get something done. >> >> - First >> we will host http://www.pharoByExample.org at http://books.pharo.org >> >> - Second >> we will create a new entry for Updated pharo by example and (a new >> entry for numerical method book too). >> >> - Third >> Read and fix Updated >> Need a new cover (will ask lusy) >> -> done >> >> >> >> >> Stef >> >> >> >

Jan. 17, 2016

Re: [Pharo-dev] Contributing to Pharo

by stepharo

>> No this is not really the case. In general we try hard to get alpha stable after you get some hiccups. >> This is not every day that we change FFI, GC, object internal representations and the text editors, syntax highli >> And our problems is that sometimes often we just jump over glitches (this is why I'm getting mad because when I do videos >> or other I see them in my face). Now I would love to have task forces that check glitches. > I get the picture now. I just checked in when the lobby, the roof and the plumbing of the hotel were undergoing renovations: it's not how it is usually. > > I could question whether it's a good idea to cram so much in a single release cycle. But release management is a difficult topic, and often there is no good solution, just one that has less downsides than the others. We do not control all the agendas. We were hesitating to get Pharo 50 without spur and for some people it would have been sad. Then it would have meant 2 months in beta and slow mode. And Esteban worked a lot on the new FFI because it was needed: you do not change an object header internal representation without impact and since the previous FFI was generating assembly on the fly and few people knew its implementation and Igor got a depression we got stuck. Then this is important to get the new FFI out because Ronie is coming to visit us and he should work with Clement and esteban on a faster version. This is as simple as that. It means that all the libraries using FFI would not have been available with Spur = no use for certain people like roassal, moose, synectique. Stef

Jan. 17, 2016

Re: [Pharo-dev] [Pharo-users] Getting Updated Pharo By Example out the door

by stepharo

Thanks. Ok I do not know. The difference is not that large between Pharo 40 and Pharo50. So when I will read it I will check and see. I will try to avoid to document features that are 40 only. And I will try to stay as compatible with Pharo 50 as possible. Once I have finished with the first exercise for the mooc Counter today I will start reading chapter one. Le 17/1/16 10:45, Dimitris Chloupis a Ã©crit : > I am here to help you Stef , I am actually doing what you are doing > going one chapter at a time, but for me its not 3 chapter per week but > rather 1 chapter per week but I can boost my speed to 3 chapters per > week and just dont pay so much attention to detail as I currently do. > My goal so far was to focus on Pharo 4 and not Pharo 5, so I can make > a Pharo 4 release (github release and github tag) and then move to > pharo 5 at least one month before pharo 5 is released. > > But because I know that your MOOC is based on Pharo 5 maybe you want > to move UPBE directly to pharo 5 (not hard to do because we have > already documented some parts of pharo 5) which works for me too. > > On Sun, Jan 17, 2016 at 11:05 AM stepharo <stepharo(a)free.fr > <mailto:stepharo@free.fr>> wrote: > > Hi guys > > I will read from start to end the book and we will get it on lulu. I > plan to read up to 3 chapters per week. > If you want to help for real this is the time. > > https://ci.inria.fr/pharo-contribution/view/Books/job/UpdatedPharoByExample… > > I rewrote the chapter on metaclass and a couple of other points > because > TranslucentColor is not available anymore. > I will not rewrite what I do not like (I should now have written > in the > first place :). So I'm not looking > for the perfect solution but to get something done. > > - First > we will host http://www.pharoByExample.org at > http://books.pharo.org > > - Second > we will create a new entry for Updated pharo by example and > (a new > entry for numerical method book too). > > - Third > Read and fix Updated > Need a new cover (will ask lusy) > -> done > > > > > Stef > >

Jan. 17, 2016

Re: [Pharo-dev] Why there is no setting to disable QA?

by stepharo

Hi nicolai Le 17/1/16 11:29, Nicolai Hess a Ã©crit : > > Hi > > Why there is no setting for that? > > Stef > > > > You can remove the Nautilus plugin (Nautilus window menu -> plugin > manager) Yes I saw looking around. Now I have to dive into it to script it so that I avoid to be forced as today to redo my screenshots (to avoid all the false positive on class creation). Because else > For the spotter and inspector integration, there is a setting (default > "disabled") >

Jan. 17, 2016

Re: [Pharo-dev] Why there is no setting to disable QA?

by Nicolai Hess

2016-01-17 11:22 GMT+01:00 stepharo <stepharo(a)free.fr>: > Hi > > Why there is no setting for that? > > Stef > > You can remove the Nautilus plugin (Nautilus window menu -> plugin manager) For the spotter and inspector integration, there is a setting (default "disabled")

Jan. 17, 2016

Why there is no setting to disable QA?

by stepharo

Hi Why there is no setting for that? Stef

Jan. 17, 2016

Re: [Pharo-dev] [Pharo-users] Getting Updated Pharo By Example out the door

by Dimitris Chloupis

I am here to help you Stef , I am actually doing what you are doing going one chapter at a time, but for me its not 3 chapter per week but rather 1 chapter per week but I can boost my speed to 3 chapters per week and just dont pay so much attention to detail as I currently do. My goal so far was to focus on Pharo 4 and not Pharo 5, so I can make a Pharo 4 release (github release and github tag) and then move to pharo 5 at least one month before pharo 5 is released. But because I know that your MOOC is based on Pharo 5 maybe you want to move UPBE directly to pharo 5 (not hard to do because we have already documented some parts of pharo 5) which works for me too. On Sun, Jan 17, 2016 at 11:05 AM stepharo <stepharo(a)free.fr> wrote: > Hi guys > > I will read from start to end the book and we will get it on lulu. I > plan to read up to 3 chapters per week. > If you want to help for real this is the time. > > > https://ci.inria.fr/pharo-contribution/view/Books/job/UpdatedPharoByExample… > > I rewrote the chapter on metaclass and a couple of other points because > TranslucentColor is not available anymore. > I will not rewrite what I do not like (I should now have written in the > first place :). So I'm not looking > for the perfect solution but to get something done. > > - First > we will host http://www.pharoByExample.org at http://books.pharo.org > > - Second > we will create a new entry for Updated pharo by example and (a new > entry for numerical method book too). > > - Third > Read and fix Updated > Need a new cover (will ask lusy) > -> done > > > > > Stef > > >

Jan. 17, 2016

Re: [Pharo-dev] gtdebugger in pharo 5.0

by Tudor Girba

Hi, Indeed, this is the goal. What is the deadline until when we could still do something visual with the debugger? Cheers, Doru > On Jan 17, 2016, at 9:55 AM, stepharo <stepharo(a)free.fr> wrote: > > Please publish this change fast because after all the coding videos of the mooc will be impacted. > > Le 17/1/16 09:05, Tudor Girba a Ã©crit : >> Hi, >> >> Indeed. See below how it looks like in the latest development version. >> >> We have not yet integrate this one because we still need little changes in FastTable to be able to resize columns and not make the column names clickable. >> >> >> <Mail Attachment.png> >> >> Cheers, >> Doru >> >> >>> On Jan 17, 2016, at 8:07 AM, Ben Coman <btc(a)openInWorld.com> wrote: >>> >>> On Sun, Jan 17, 2016 at 9:48 AM, Cyril Ferlicot D. >>> <cyril.ferlicot(a)gmail.com> wrote: >>>> >>>> And more, it make the debugger "ventilated" (I don't know if the term >>>> work in English too). I mean that with more space between the classes >>>> and the methods it's better for the eye of the user. >>> >>> Never heard the term used that way in graphic design, but it makes >>> perfect sense. >>> cheers -ben >>> >> >> -- >> www.tudorgirba.com >> www.feenk.com >> >> "If you can't say why something is relevant, >> it probably isn't." >> > -- www.tudorgirba.com www.feenk.com "Next time you see your life passing by, say 'hi' and get to know her."

Jan. 17, 2016