August 2015 - Pharo-dev - lists.pharo.org

Re: [Pharo-dev] line endings

by Alexandre Bergel

I think this is for historical reason. Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > On Aug 3, 2015, at 3:57 PM, Peter UhnÃ¡k <i.uhnak(a)gmail.com> wrote: > > Why does Pharo save everything with CR line endings? Literally nobody uses that. > > Peter

Aug. 3, 2015

Re: [Pharo-dev] Yet another Athens font thread

by Nicolai Hess

2015-06-10 12:01 GMT+02:00 Aliaksei Syrel <alex.syrel(a)gmail.com>: > Hi > > I noticed that if I force use "Source Code Pro" as standard font for all > elements in the image I never have problems with font rendering. In case of > "Source Sans Pro" font is just not usable becasue of rendering bugs on mac, > windows and linux(?). If "Lucida Sans Pro" is used - no bugs too. > > Because bug is reproducable on all platform - it's platform independent > bug. > Because it's reproducable only with one specific font - maybe it's not an > athens issue but bug in font itself and if someone could change/update > Source Sans Pro to a newly version or to a similar font the problem will be > solved? > Did you try to use a new font version ? I don't know exactly how embedded fonts are included. I tried to create the font with a newer version but it did not work ( or at least I could not see any difference). > > Cheers, > Alex >

Aug. 3, 2015

wrong syntax highlighting in debugger

by Nicolai Hess

recent pharo 50 has wrong syntax highlighting. This is caused by my fix for issue 15773. I am working on that nicolai

Aug. 3, 2015

Re: [Pharo-dev] OSProcess on windows (was: Re: Google Code Shutdown)

by Levente Uzonyi

Thanks for the links. Unfortunately none of these really explain what the problem with OSProcess is. I see there were attempts to try using ProcessWrapper instead of OSProcess on windows, but there's no feedback on that thread, so there may be a solution out there, but no one is using it. Levente On Mon, 3 Aug 2015, Peter UhnÃ¡k wrote: > On Mon, Aug 3, 2015 at 7:14 PM, Levente Uzonyi <leves(a)elte.hu> wrote: > On Mon, 3 Aug 2015, Peter UhnÃ¡k wrote: > > > Â Â Â but the git user experience under Windows has to be improved if we want to use efficiently the other functionalities of github (pull requests, commit, branches,â¦). > > > Well some of the experience can be mitigated with tools like GitHub for Windows, but the main problem is that git with Pharo is incredibly unstable on Windows and crashes constantly. > That's our experience > with it so my colleague had to switch to pure filetree out of frustration. > This however is NOT problem of git, it's problem of OSProcess. But it does render it almost unusable for now. (At least for us.) > > > What's the problem with OSProcess on windows? > > > http://forum.world.st/Gitfiletree-unstable-on-Windows-td4816354.html > http://forum.world.st/gitfiletree-metadata-td4838970.html > http://forum.world.st/Git-gitfiletree-on-Pharo-vs-Windows-td4806791.html > >

Aug. 3, 2015

line endings

by Peter UhnÃ¡k

Why does Pharo save everything with CR line endings? Literally nobody uses that. Peter

Aug. 3, 2015

Re: [Pharo-dev] OSProcess on windows (was: Re: Google Code Shutdown)

by Peter UhnÃ¡k

On Mon, Aug 3, 2015 at 7:14 PM, Levente Uzonyi <leves(a)elte.hu> wrote: > On Mon, 3 Aug 2015, Peter UhnÃ¡k wrote: > > >> but the git user experience under Windows has to be improved if we >> want to use efficiently the other functionalities of github (pull requests, >> commit, branches,â¦). >> >> >> Well some of the experience can be mitigated with tools like GitHub for >> Windows, but the main problem is that git with Pharo is incredibly unstable >> on Windows and crashes constantly. That's our experience >> with it so my colleague had to switch to pure filetree out of frustration. >> This however is NOT problem of git, it's problem of OSProcess. But it >> does render it almost unusable for now. (At least for us.) >> > > What's the problem with OSProcess on windows? > http://forum.world.st/Gitfiletree-unstable-on-Windows-td4816354.html http://forum.world.st/gitfiletree-metadata-td4838970.html http://forum.world.st/Git-gitfiletree-on-Pharo-vs-Windows-td4806791.html

Aug. 3, 2015

OSProcess on windows (was: Re: Google Code Shutdown)

by Levente Uzonyi

On Mon, 3 Aug 2015, Peter UhnÃ¡k wrote: > > but the git user experience under Windows has to be improved if we want to use efficiently the other functionalities of github (pull requests, commit, branches,â¦). > > > Well some of the experience can be mitigated with tools like GitHub for Windows, but the main problem is that git with Pharo is incredibly unstable on Windows and crashes constantly. That's our experience > with it so my colleague had to switch to pure filetree out of frustration. > This however is NOT problem of git, it's problem of OSProcess. But it does render it almost unusable for now. (At least for us.) What's the problem with OSProcess on windows? Levente > > Peter > >

Aug. 3, 2015

Re: [Pharo-dev] about quality assistant

by Yuriy Tymchuk

I know that, and this is actually an issue that every system is facing. It is the next step to work on in QualityAssistant. One thing that I wander is whether there are people who want to keep noise. I.e. is it enough to simply cut off the non-accurate rules, people want to choose a threshold for the noiseâ¦ Uko > On 03 Aug 2015, at 15:08, Peter UhnÃ¡k <i.uhnak(a)gmail.com> wrote: > > I think that there is real problem with noise-to-signal ratio. > If I see four critics out of which tree makes in the context of the method/class no sense whatever then the result will not be that I improve my code, because I can't (those critics are false positives), but the result will be that I will start ignoring the critics altogether, because the ratio is too high. > > This of course depends a lot on the code... if you need a lot of metaprogramming, or a library has some specific method naming (to be easier to use by hand) or whatever then this is a real problem. > > Peter > > On Tue, Jul 28, 2015 at 3:55 PM, Peter UhnÃ¡k <i.uhnak(a)gmail.com <mailto:i.uhnak@gmail.com>> wrote: > #beSomething is quite common pattern (even recommended in Kent's Best Practice Patterns), maybe it should check for name 'be'<Uppercase> before applying the critic? > This is a good proposal. Would be nice to hear other opinions. Maybe we can open an issue on the bug tracker so people can comment. > > However I do not really want to ban the critic, because there may other legitimate applications in the method/class; and in Roassal-heavy code it's a nuisance. > So it would require context-aware checks (probably user-defined?) like "if receiver is subclass of RTShape then don't apply this (yourself) ruleâ. > > Yes, itâs a very good point. It is in my plans to see how we can allow frameworks to provide their own critics and interact/override the default ones. For now all I can suggest is to ban the critic on the level of the class, or if we will reach the common sense there can be a ban on the level of package tag, so you can keep all the roassal-related classes in one tag and ban the rule for them. > > I created issues for both so it doesn't get lost here. > > Peter > > > On Tue, Jul 28, 2015 at 3:24 PM, stepharo <stepharo(a)free.fr <mailto:stepharo@free.fr>> wrote: > > > Le 28/7/15 11:43, Alexandre Bergel a Ã©crit : > But, what does the useless button do? Does it remove from the rules quality assistant uses forever? Or is it per class? the rule "Too many methods" is useless for the class RTexample, but it is useful for other classes > > Alex > I was confused too :) > I guess that it does nothing. Just report to the server of yuriy that you think that this rule is useless. > So there is a clear problem at the UI level. The user cannot disntinguish what he is doing: > marking false positive > or giving feedback in general. > > Stef > > Alexandre > > > > Le 27 juil. 2015 Ã 12:53, Yuriy Tymchuk <yuriy.tymchuk(a)me.com <mailto:yuriy.tymchuk@me.com>> a Ã©crit : > > This is sad, and shows that I completely failed with that button. Because ideally you had to press it so I can know that this rule had a useful case for somebody. > > > > >

Aug. 3, 2015

open street map example

by Alexandre Bergel

Hi! Some of you have an interest in visualizing graphs on top of open street maps. Together with Hilaire we made a small example: -=-=-=-=-=-=-=-=-=-=-=-= | v map data b d whiteBackground london elementsAndEdges | v := RTView new. v @ RTDraggableView. map := RTOSM new. v add: map element. "Place to set the data and center the camera" london := 51.507222@ -0.1275. "Some arbitrary data" data := ((1 to: 500) collect: [ :i | 50 atRandom - 25 ]) cumsum. "We build the graph" b := RTGrapher new. b extent: 100@30. d := RTData new. d noDot. d connectColor: Color red. d points: data. b add: d. b axisY labelFontHeight: 6; color: Color red; title: 'Sale'. b axisX color: Color red; noTick; title: 'country'. b build. elementsAndEdges := b view elements, b view edges. "We create a white background" whiteBackground := (RTRoundedBox new color: Color white trans; borderRadius: 10) element. v add: whiteBackground. v addAll: elementsAndEdges. RTNest new on: whiteBackground nest: elementsAndEdges. whiteBackground translateTo: (map latLonToRoassal: london). v canvas camera translateTo: (map latLonToRoassal: london). v canvas camera noInitializationWhenOpen. v canvas camera scale: 1.5. v -=-=-=-=-=-=-=-=-=-=-=-= Cheers, Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

Aug. 3, 2015

TestRunner>>#allSelectedTestSuites does not select tests from abstract classes

by Christophe Demarey

Hi, Before opening a bug entry, I would like to know if there are situations where we do not want to select test methods from abstract classes? I have an example where a super class also has tests (common behavior with children) even if it is abstract. I do not see why to restrict test methods on concrete classes. Thanks, Christophe

Aug. 3, 2015