January 2017 - Pharo-users - lists.pharo.org

A little expression interpreter for new forthcoming book
by Stephane Ducasse Jan. 13, 2017

Jan. 13, 2017

I released a version of a little expression interpreter for the new book: Object-oriented programming and design with Pharo. https://ci.inria.fr/pharo-contribution/view/Books/job/LearningObjectOriente… Typos are welcome as pull requests. Stef

5 8

making scroll smooth
by Siemen Baader Jan. 13, 2017

Jan. 13, 2017

Hi All, I'm used to and like the smooth scrolling of modern browsers and OS'es and miss it in Pharo. It as discrete scroll deltas; when I scroll it moves the window content by several pixels or not at all if the movement is below a certain threshold. How can I enable smooth scroll / set that threshold to 1px? And how could I learn if I did not ask on the list? thanks, Siemen

5 6

Call of projects of open-dev lectures
by Stephane Ducasse Jan. 11, 2017

Jan. 11, 2017

Hi We are organising a lecture where students should - learn pharo - learn how to communicate with open source community - learn how to reverse engineer, fix bugs.... They should work by 3/4. We are looking for projects that would like to accept - propose some bugs to be fixed - to communicate with newbies and from time to time I was thinking about - MDL - Roassal - Moose ? - Pillar ? but nobody beside me and I do not have the time - DRGeoII - Telescope - Artefact - Scale - Ecstatic So if you have a project and you want to participate. We would like to have - web page? - mailing-list - bug trackers/todo? Stef

9 8

Pharo Days 2017: Date?
by Marcus Denker Jan. 11, 2017

Jan. 11, 2017

We checked which dates would make senseâ¦ the idea would be to do it after the release of Pharo6. For the place we are checking Lille, we can get some support from Inria/the University for doing a small event like this. The best here is April, either before or after school holidays. To know if this makes any sense, we have set up a doodle: http://doodle.com/poll/f8n5zhv7p8fqwyih Marcus

1 0

Re: [Pharo-users] [Pharo-dev] happy and bold new year
by Tudor Girba Jan. 10, 2017

Jan. 10, 2017

Hi Hilaire, GT is essentially a project that takes the relevant parts of Moose and make them applicable to plain Pharo. Pharo ships with only the core tools, but the complete configuration of GT also brings with it Roassal and a couple of other goodies. There are still more interesting things in Moose, but you can get quite far with only GT. About your particular question, itâs true that Pharo does not have static types, but that does not make it harder to understand. Only different. The first thing to realize is that Pharo is not about code, but about objects. That is why my advice is to not try too long to understand Pharo code statically because this is not where the power of Pharo is. You are in a much better position to understand a system when itâs running. So, the tools that I use the most are the inspector when I need to understand structural relationships or contracts between objects, and the debugger when I need to understand some algorithmic steps. Even when I look for code structure patterns, I mostly use the inspector because it allows me to query. Then you augment these tools with custom views and you get quite far. I know this sounds abstract, but I am practicing this since several years and I still find it amazing. I tried to provide a hint of how it works in the ESUG 2016 talk. Cheers, Doru > On Jan 9, 2017, at 2:02 PM, Hilaire <hilaire(a)drgeo.eu> wrote: > > Hello Doru, > > I am curious. > Yesterday I had a look to MessageBrowser, and realize I understand > nothing of it. I saw there is a mix of SpecXXX, models, Navigation > browser, Announcement, etc, then I knew I will have to spend a lot of > time browsing (multiple window again) to understand a bit how these > objects are related, and may be be able to change it in the way I want. > Does the Moose & al tools could help me understand code I don't know about? > > Given the fact Pharo/Smalltalk are not typed makes it harder for code > analysis, don't you? > > Happy new year to you too. > > Hiaire > > Le 09/01/2017 Ã 10:30, Tudor Girba a Ã©crit : >> Happy New Year, everyone! >> >> Over the last year, I went through a rather extensive tour and I directly exposed Moose, GT and Pharo to some 2000+ technical people through various sessions and trainings at conferences and companies. The tour will continue this year. >> >> Most of the sessions are not directly about Moose, GT or Pharo, but about broader topics that are served through what we do around here. These topics can relate to solving problems without reading code, to steering agile architecture, or more recently, to even broader topics like software environmentalism. If you are wondering what software environmentalism is, please take a look at this talk: >> https://youtu.be/N3l3eB62oSw?list=PLqvTNJtc942Cs9Qo4ikCGrUNtAw93Q0JA >> >> I now have the confirmation that there is a whole space which is unaddressed by mainstream technologies. Often people find themselves frustrated having to build their systems on top of opaque technologies with not much hope of understanding what is going on under the hood both because they do not have access to what is behind and because they are provided lack the tools to investigate. You see, developers are suppose to have the coolest job on the planet, and many of them are unhappy. This has to change, and we can do that. >> >> In a conversation I had with a highly respected researcher, after explaining how our tools allow us to work, he noted reluctantly âso, you are claiming that you are practicing a fundamentally different software engineering?â. This question took me a little by surprise because the only answer I found myself being able to provide was âyesâ. I sent him this talk: >> https://youtu.be/XWOOJa3kEa0?list=PLqvTNJtc942Cs9Qo4ikCGrUNtAw93Q0JA >> >> It is strange to be in the position to tell the world that we are constructing something fundamentally better, but I really do believe that we are. >> >> I wish you a happy and bold new year! >> >> Cheers, >> Doru >> > > -- > Dr. Geo > http://drgeo.eu -- www.tudorgirba.com www.feenk.com "If you can't say why something is relevant, it probably isn't."

3 6

[ANN] Pharo Sprint First half 2017
by Marcus Denker Jan. 10, 2017

Jan. 10, 2017

Hi, As this year, there will be again âPharo Sprintsâ next year. At these dates we meet (virtual or real) to work on boring (or complex) issues together: Jan 27 Mar 3 Mar 31 Apr 28 May 26 Jun 30 Local sprints: - University of Chile (DCC). Not January, but likely the other dates - Inria Lille: All - Remote: All. We will try to improve remote sprint experience next year! - The sprints will be added to https://association.pharo.org/events Marcus

1 2

Design Challenge: metrics missing value...
by stepharong Jan. 10, 2017

Jan. 10, 2017

Hi dear great OO designers Here is a little challenges for your brainy souls :) In Moose when we compute metrics it may happen than a tool (often external to pharo) does not compute a metrics and when we request it in moose we check and often we return a not so good -1. I'm trying to brainstorm on a solution - first may be the simplest way is to not invoke a metrics when it is not computed. But it means that we should know it and that we should have a registration mechanism. After all this is probably the best solution. - Second we were thinking to use exception but when we have multiple entities missing one metrics.... I have serious doubts. - Second I was thinking about having the following behavior testCollect | uarray collected | uarray := UniformOrderedCollection new. uarray add: 10. uarray add: 20. uarray add: (MissingValue discarding). collected := uarray collect: [ :each | each ]. self assert: collected size equals: 2. testDo | res uarray | uarray := UniformOrderedCollection new. uarray add: 10. uarray add: 20. uarray add: (MissingValue discarding). uarray add: 40. res := 0. uarray do: [ :each | res := res + each ]. self assert: res equals: 70. testCollectDefaulting | uarray collected | uarray := UniformOrderedCollection new. uarray add: 10. uarray add: 20. uarray add: (MissingValue default: 33). collected := uarray collect: [ :each | each ]. self assert: collected size equals: 3. self assert: collected third equals: 33 I basically started to implement do: aBlock "Refer to the comment in Collection|do:." 1 to: self size do: [:index | (self at: index) toDo: aBlock on: self] collect: aBlock "Evaluate aBlock with each of the receiver's elements as the argument. Collect the resulting values into a collection like the receiver. Answer the new collection." | newCollection | newCollection := self species new. self do: [ :each | each toCollect: aBlock on: newCollection ]. ^ newCollection and DiscardingValue >> toCollect: aBlock on: aCollection "discard computation" ^ self Object >> toCollect: aBlock on: aCollection ^ aCollection add: (aBlock value: self) So I imagine that you see the design and I wanted to get your point of view. -- Using Opera a kind of bad mail client but far better than thunderbird

5 15

CPU hungry
by Hilaire Jan. 9, 2017

Jan. 9, 2017

Hello, When I download a fresh DrGeo16.10 (Pharo3 based), run it, open all window, I can see it eat almost 25% of cpu, when lucky it get down to 8% What can I do? Thanks Hilaire -- Dr. Geo http://drgeo.eu

2 2

happy and bold new year
by Tudor Girba Jan. 9, 2017

Jan. 9, 2017

Happy New Year, everyone! Over the last year, I went through a rather extensive tour and I directly exposed Moose, GT and Pharo to some 2000+ technical people through various sessions and trainings at conferences and companies. The tour will continue this year. Most of the sessions are not directly about Moose, GT or Pharo, but about broader topics that are served through what we do around here. These topics can relate to solving problems without reading code, to steering agile architecture, or more recently, to even broader topics like software environmentalism. If you are wondering what software environmentalism is, please take a look at this talk: https://youtu.be/N3l3eB62oSw?list=PLqvTNJtc942Cs9Qo4ikCGrUNtAw93Q0JA I now have the confirmation that there is a whole space which is unaddressed by mainstream technologies. Often people find themselves frustrated having to build their systems on top of opaque technologies with not much hope of understanding what is going on under the hood both because they do not have access to what is behind and because they are provided lack the tools to investigate. You see, developers are suppose to have the coolest job on the planet, and many of them are unhappy. This has to change, and we can do that. In a conversation I had with a highly respected researcher, after explaining how our tools allow us to work, he noted reluctantly âso, you are claiming that you are practicing a fundamentally different software engineering?â. This question took me a little by surprise because the only answer I found myself being able to provide was âyesâ. I sent him this talk: https://youtu.be/XWOOJa3kEa0?list=PLqvTNJtc942Cs9Qo4ikCGrUNtAw93Q0JA It is strange to be in the position to tell the world that we are constructing something fundamentally better, but I really do believe that we are. I wish you a happy and bold new year! Cheers, Doru -- www.tudorgirba.com www.feenk.com "Every thing should have the right to be different."

1 0

Pharo and WebAssembly
by horrido Jan. 8, 2017

Jan. 8, 2017

Hey, Rust can now target WebAssembly <https://blog.rust-lang.org/2016/12/22/Rust-1.14.html> . Pharo must do the same! -- View this message in context: http://forum.world.st/Pharo-and-WebAssembly-tp4928888.html Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com.

4 3