- Pharo-dev - lists.pharo.org

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

Re: [Pharo-dev] Windows users, please test!

by Nicolai Hess

2015-08-03 15:21 GMT+02:00 Esteban Lorenzano <estebanlm(a)gmail.com>: > I made a new SLICE trying to fix the FT2 crash problem windows (and I > think also linux?) are experiencingâ¦ can you please merge the SLICE for: > > https://pharo.fogbugz.com/f/cases/15633 > > and test a bitâ¦ and inform any new problems? > > Iâm not a windows user but I tested the solution some time in a virtual > imageâ¦ but we all know thatâs limited :) > > thanks! > Esteban > > > No, it still happens (attached crash.dmp) Sometimes it crashes on startup and sometimes it starts up but uses only non-ft fonts, as if FT was disabled.

Aug. 3, 2015

Re: [Pharo-dev] Windows users, please test!

by Blondeau Vincent

Seems to work! I will use it to develop and keep you informed tomorrow. Vincent De : Pharo-dev [mailto:pharo-dev-bounces@lists.pharo.org] De la part de Esteban Lorenzano EnvoyÃ© : lundi 3 aoÃ»t 2015 15:22 Ã : Pharo Development List Objet : [Pharo-dev] Windows users, please test! I made a new SLICE trying to fix the FT2 crash problem windows (and I think also linux?) are experiencingâ¦ can you please merge the SLICE for: https://pharo.fogbugz.com/f/cases/15633 and test a bitâ¦ and inform any new problems? Iâm not a windows user but I tested the solution some time in a virtual imageâ¦ but we all know thatâs limited :) thanks! Esteban ________________________________ Ce message et les piÃ¨ces jointes sont confidentiels et rÃ©servÃ©s Ã l'usage exclusif de ses destinataires. Il peut Ã©galement Ãªtre protÃ©gÃ© par le secret professionnel. Si vous recevez ce message par erreur, merci d'en avertir immÃ©diatement l'expÃ©diteur et de le dÃ©truire. L'intÃ©gritÃ© du message ne pouvant Ãªtre assurÃ©e sur Internet, la responsabilitÃ© de Worldline ne pourra Ãªtre recherchÃ©e quant au contenu de ce message. Bien que les meilleurs efforts soient faits pour maintenir cette transmission exempte de tout virus, l'expÃ©diteur ne donne aucune garantie Ã cet Ã©gard et sa responsabilitÃ© ne saurait Ãªtre recherchÃ©e pour tout dommage rÃ©sultant d'un virus transmis. This e-mail and the documents attached are confidential and intended solely for the addressee; it may also be privileged. If you receive this e-mail in error, please notify the sender immediately and destroy it. As its integrity cannot be secured on the Internet, the Worldline liability cannot be triggered for the message content. Although the sender endeavours to maintain a computer virus-free network, the sender does not warrant that this transmission is virus-free and will not be liable for any damages resulting from any virus transmitted.

Aug. 3, 2015

[pharo-project/pharo-core] 4417a7: 50206

by GitHub

Branch: refs/heads/5.0 Home: https://github.com/pharo-project/pharo-core Commit: 4417a7875a30c421fe9e3ea96a98718389d48c87 https://github.com/pharo-project/pharo-core/commit/4417a7875a30c421fe9e3ea9… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2015-08-03 (Mon, 03 Aug 2015) Changed paths: M Monticello-Tests.package/MCRepositoryTest.class/instance/tests/testCanCreateFiletreeRepositoryFromUrl.st R ScriptLoader50.package/ScriptLoader.class/instance/pharo - scripts/script50205.st A ScriptLoader50.package/ScriptLoader.class/instance/pharo - scripts/script50206.st R ScriptLoader50.package/ScriptLoader.class/instance/pharo - updates/update50205.st A ScriptLoader50.package/ScriptLoader.class/instance/pharo - updates/update50206.st M ScriptLoader50.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st M Tool-Diff.package/DiffMorph.class/instance/actions/calibrateScrollbar.st Log Message: ----------- 50206 15990 Failing tests testCanCreateFiletreeRepositoryFromUrl (on windows) https://pharo.fogbugz.com/f/cases/15990 16088 Fix DiffMorph when called from Komitter https://pharo.fogbugz.com/f/cases/16088 http://files.pharo.org/image/50/50206.zip

Aug. 3, 2015

[pharo-project/pharo-core]

by GitHub

Branch: refs/tags/50206 Home: https://github.com/pharo-project/pharo-core

Aug. 3, 2015

Re: [Pharo-dev] Is Metacello in Pharo 5.0 up-to-date? and project locking

by Christophe Demarey

Hi, You can find a recent version of Metacello on the latest Pharo 5.0 image there: https://ci.inria.fr/rmod/job/Metacello-CDrepo I already have a pull request opened for that: https://github.com/dalehenrich/metacello-work/pull/351 Christophe Le 24 juil. 2015 Ã 11:48, Marcus Denker a Ã©crit : > >> On 24 Jul 2015, at 11:14, Thierry Goubier <thierry.goubier(a)gmail.com> wrote: >> >> Hi Peter, >> >> the FileTree part is solved, as far as I could do (i.e. all tests green with Pharo5 on Linux), but there is a failure in the travis CI of the most annoying type: the filetree code isn't even loaded :( >> >> I'm going on annual leave later today, and Dale told me he won't be easily available for a few weeks; I'll try to make some progress on it during the holidays, but don't count too much on it ;) >> >> In the meantime, if someone would be nice to setup Metacello and FileTree in Pharo5 as external projects with a configuration, it would immensely help. > > Yes, that would be nice! Sadly I have no time to do this until my holidaysâ¦ > > issue tracker entry is here: > https://pharo.fogbugz.com/f/cases/15456/Load-latest-version-of-metacello > > Marcus

Aug. 3, 2015

Re: [Pharo-dev] Windows users, please test!

by Blondeau Vincent

Thanks Esteban! I will try :) Vincent De : Pharo-dev [mailto:pharo-dev-bounces@lists.pharo.org] De la part de Esteban Lorenzano EnvoyÃ© : lundi 3 aoÃ»t 2015 15:22 Ã : Pharo Development List Objet : [Pharo-dev] Windows users, please test! I made a new SLICE trying to fix the FT2 crash problem windows (and I think also linux?) are experiencingâ¦ can you please merge the SLICE for: https://pharo.fogbugz.com/f/cases/15633 and test a bitâ¦ and inform any new problems? Iâm not a windows user but I tested the solution some time in a virtual imageâ¦ but we all know thatâs limited :) thanks! Esteban ________________________________ Ce message et les piÃ¨ces jointes sont confidentiels et rÃ©servÃ©s Ã l'usage exclusif de ses destinataires. Il peut Ã©galement Ãªtre protÃ©gÃ© par le secret professionnel. Si vous recevez ce message par erreur, merci d'en avertir immÃ©diatement l'expÃ©diteur et de le dÃ©truire. L'intÃ©gritÃ© du message ne pouvant Ãªtre assurÃ©e sur Internet, la responsabilitÃ© de Worldline ne pourra Ãªtre recherchÃ©e quant au contenu de ce message. Bien que les meilleurs efforts soient faits pour maintenir cette transmission exempte de tout virus, l'expÃ©diteur ne donne aucune garantie Ã cet Ã©gard et sa responsabilitÃ© ne saurait Ãªtre recherchÃ©e pour tout dommage rÃ©sultant d'un virus transmis. This e-mail and the documents attached are confidential and intended solely for the addressee; it may also be privileged. If you receive this e-mail in error, please notify the sender immediately and destroy it. As its integrity cannot be secured on the Internet, the Worldline liability cannot be triggered for the message content. Although the sender endeavours to maintain a computer virus-free network, the sender does not warrant that this transmission is virus-free and will not be liable for any damages resulting from any virus transmitted.

Aug. 3, 2015

Re: [Pharo-dev] Google Code Shutdown

by Sean P. DeNigris

Import in progress: Started thread on Moose list: http://forum.world.st/Moving-Issues-to-GitHub-tt4840767.html ----- Cheers, Sean -- View this message in context: http://forum.world.st/Google-Code-Shutdown-tp4814760p4840768.html Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

Aug. 3, 2015