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

Re: [Pharo-users] [Pharo-dev] Call of projects of open-dev lectures

by Cyril Ferlicot D.

On 04/01/2017 15:48, Stephane Ducasse wrote: > 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 Hi Stef, I updated MDL to be up to date. I just need to add a "CONTRIBUTING.md" file and it should be good for students. - WebPage: For now it is https://github.com/DuneSt/MaterialDesignLite - Mailing list: Pharo-user or Seaside - Bug Tracker: https://github.com/DuneSt/MaterialDesignLite/issues I still need to think of some features suitable for L3 students and to document them. I begun to add an OpenDev label if some students are interested: https://github.com/DuneSt/MaterialDesignLite/issues?q=is%3Aissue+is%3Aopen+… -- Cyril Ferlicot http://www.synectique.eu 2 rue Jacques PrÃ©vert 01, 59650 Villeneuve d'ascq France

Jan. 11, 2017

Pharo Days 2017: Date?

by Marcus Denker

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

Jan. 11, 2017

Re: [Pharo-users] [Pharo-dev] happy and bold new year

by Hilaire

Great! IMHO there is a lot to learn from newbies or naive users experience to improve the Pharo IDE tools. The Calypso multiple tab panels of edited methods is nice. By the way, when asking for the reference of a Trait it always returns an empty list, but I guess you already know it. Le 09/01/2017 Ã 21:31, Denis Kudriashov a Ã©crit : > I am going to show something really cool tomorrow :) -- Dr. Geo http://drgeo.eu

Jan. 10, 2017

Re: [Pharo-users] making scroll smooth

by phil＠highoctane.be

Try this: WorldState MinCycleLapse: 16. Should make things better. Phil On Tue, Jan 10, 2017 at 5:40 PM, Siemen Baader <siemenbaader(a)gmail.com> wrote: > 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 >

Jan. 10, 2017

making scroll smooth

by Siemen Baader

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

Jan. 10, 2017

Re: [Pharo-users] [ANN] Pharo Sprint First half 2017

by Marcus Denker

> On 10 Jan 2017, at 15:02, Marcus Denker <marcus.denker(a)inria.fr> wrote: > > >> On 23 Dec 2016, at 15:18, Marcus Denker <marcus.denker(a)inria.fr> wrote: >> >> 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: >> > > â¦. > >> May 26 > > This one we have to change: The 25th is a holiday here and the 26 a âpre allocated free day from the overtime that comes > from having officially a 35h work week but working 38.5 hoursâ where our office is closed. > The idea is to move it one week: Friday, June 2. Marcus

Jan. 10, 2017

Re: [Pharo-users] [ANN] Pharo Sprint First half 2017

by Marcus Denker

> On 23 Dec 2016, at 15:18, Marcus Denker <marcus.denker(a)inria.fr> wrote: > > 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: > â¦. > May 26 This one we have to change: The 25th is a holiday here and the 26 a âpre allocated free day from the overtime that comes from having officially a 35h work week but working 38.5 hoursâ where our office is closed. Marcus

Jan. 10, 2017

Re: [Pharo-users] [Moose-dev] Re: Design Challenge: metrics missing value...

by Serge Stinckwich

Something interesting about missing values and data-structure to represent them like shadow matrix: https://github.com/njtierney/naniar?utm_content=buffer26e7b Some month ago, I build a Roassal viz in order to see missing values in CSV file: https://twitter.com/SergeStinckwich/status/705839378917167104 On Thu, Dec 22, 2016 at 9:34 AM, stepharong <stepharong(a)free.fr> wrote: > > > Yes I see. I will keep thinking about it. > > > On Wed, 21 Dec 2016 20:58:26 +0100, Tudor Girba <tudor(a)tudorgirba.com> > wrote: > >> Hi, >> >>> On Dec 21, 2016, at 3:05 PM, stepharong <stepharong(a)free.fr> wrote: >>> >>> >>> >>>> Hi Alex, >>>> >>>> Following the design proposed by Stef, in your case you would use a >>>> different collection. >>> >>> >>> Doru I have multiple missingValue so that they embed their own strategy. >>> Now I do not know for the scenario of alex. >> >> >> Yes, yes. And that is great. >> >> It seemed to me that Alex wanted to find from the collection the elements >> that have a MissingValue, and for that he wants to use collect:. But, your >> collection collect: ignores the MissingValue. That is why I thought that he >> can serve his case with another collection type. >> >> Cheers, >> Doru >> >> >>>> >>>> Cheers, >>>> Doru >>>> >>>> >>>>> On Dec 21, 2016, at 8:13 AM, Alexandre Bergel <alexandre.bergel(a)me.com> >>>>> wrote: >>>>> >>>>> Hi Stef, >>>>> >>>>> You are raising an interesting point to discuss. This MissingValue is >>>>> indeed better than having -1 >>>>> Something to keep in mind: it may be that one would like to focus on >>>>> the missing value and not really the value. >>>>> >>>>> Consider: >>>>> >>>>>> 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. >>>>> >>>>> >>>>> It could well be that I would like to be able to query over the >>>>> MissingValue. >>>>> Can something like possible: uarray collect: #isMissing >>>>> ? >>>>> >>>>> Cheers, >>>>> Alexandre >>>>> >>>>> >>>>>> On Dec 20, 2016, at 10:15 PM, stepharong <stepharong(a)free.fr> wrote: >>>>>> >>>>>> 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 >>>>>> _______________________________________________ >>>>>> Moose-dev mailing list >>>>>> Moose-dev(a)list.inf.unibe.ch >>>>>> https://www.list.inf.unibe.ch/listinfo/moose-dev >>>>> >>>>> >>>>> -- >>>>> _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: >>>>> Alexandre Bergel http://www.bergel.eu >>>>> ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. >>>>> >>>>> >>>>> >>>>> _______________________________________________ >>>>> 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 >>>> >>>> "If you interrupt the barber while he is cutting your hair, >>>> you will end up with a messy haircut." >>>> >>>> >>> >>> >>> -- >>> Using Opera's mail client: http://www.opera.com/mail/ >> >> >> -- >> www.tudorgirba.com >> www.feenk.com >> >> âThe smaller and more pervasive the hardware becomes, the more physical >> the software gets." >> > > > -- > Using Opera's mail client: http://www.opera.com/mail/ > _______________________________________________ > Moose-dev mailing list > Moose-dev(a)list.inf.unibe.ch > https://www.list.inf.unibe.ch/listinfo/moose-dev -- Serge Stinckwich UCBN & UMI UMMISCO 209 (IRD/UPMC) Every DSL ends up being Smalltalk http://www.doesnotunderstand.org/

Jan. 10, 2017

Re: [Pharo-users] [Pharo-dev] happy and bold new year

by Denis Kudriashov

2017-01-09 16:37 GMT+01:00 Hilaire <hilaire(a)drgeo.eu>: > But we are far from my initial question. I will be happy to watch a > video demonstration about what I don't know in Pharo to understand more > easily the MessageBrowser, for example. Final goal will be to change > MessageBrwoser so asking for implementors does not open a new window but > use its existing window. > I am going to show something really cool tomorrow :)

Jan. 9, 2017

Re: [Pharo-users] [Pharo-dev] happy and bold new year

by Hilaire

I should add I am stick with Pharo3 for DrGeo, however the new inspector in Pharo 4 and 5 reduces a lot the cascade of inspector windows, thanks to its horizontal slider. Le 09/01/2017 Ã 16:37, Hilaire a Ã©crit : > We are refering to the same things. I express a feeling from a user > experience. After diving in the code with several inspector windows, you > get lost quickly. -- Dr. Geo http://drgeo.eu

Jan. 9, 2017