- Pharo-dev - lists.pharo.org

Windows users, please test!

by Esteban Lorenzano

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 <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

Aug. 3, 2015

Re: [Pharo-dev] about quality assistant

by Peter UhnÃ¡k

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> 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> 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> 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

Re: [Pharo-dev] Google Code Shutdown

by Blondeau Vincent

That is a solution but not for long term. I donât want to install linux to use pharo.. For now the solution is to use git as standalone app and filetree to export the code. I use it and it works well while you donât have to long paths. Vincent De : Pharo-dev [mailto:pharo-dev-bounces@lists.pharo.org] De la part de Dimitris Chloupis EnvoyÃ© : lundi 3 aoÃ»t 2015 13:42 Ã : Pharo Development List Objet : ** SPAM scored: Med **Re: [Pharo-dev] Google Code Shutdown A workaround if you absolutely want to use gitfiletree is to install linux using a VM like virtual box , Ubuntu for example works very well with pharo https://www.virtualbox.org/ This way you avoid booting to another OS , you can also share your git folder to both windows and linux vm. This way you can use gitfiletree without ditching windows. Of course dual boot can work too if you dont need to use Pharo with windoom. VM option works also if you want to install MacOS on your windows pc. On Mon, Aug 3, 2015 at 1:13 PM Blondeau Vincent <vincent.blondeau(a)worldline.com<mailto:vincent.blondeau@worldline.com>> wrote: Hi, Sorry but I am using Windowsâ¦ not because I want to but because I have to... So the therapy will not work ;) Actually, the bugtracker of Moose can be on github, 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,â¦). Cheers, Vincent De : Pharo-dev [mailto:pharo-dev-bounces@lists.pharo.org<mailto:pharo-dev-bounces@lists.pharo.org>] De la part de Peter UhnÃ¡k EnvoyÃ© : lundi 3 aoÃ»t 2015 11:56 Ã : Pharo Development List Objet : Re: [Pharo-dev] Google Code Shutdown As long as nobody on your team is using Windows, git(hub) is quite good. :) (And if you have Windows user, then find him a therapy first, or push for libcgit :)) On Mon, Aug 3, 2015 at 4:35 AM, Alexandre Bergel <alexandre.bergel(a)me.com<mailto:alexandre.bergel@me.com>> wrote: Github is indeed appealing. Cheers, Alexandre > On Aug 2, 2015, at 10:14 PM, Sean P. DeNigris <sean(a)clipperadams.com<mailto:sean@clipperadams.com>> wrote: > > Tudor Girba-2 wrote >> Would you like to help us move the moose-technology project? > > Sure. What do you have in mind? It seems exporting to GitHub is the easiest > option. There are a few limitations, but I've had good experiences... > > > > ----- > Cheers, > Sean > -- > View this message in context: http://forum.world.st/Google-Code-Shutdown-tp4814760p4840733.html > Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com. > -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. ________________________________ 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. ________________________________ 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 Dimitris Chloupis

A workaround if you absolutely want to use gitfiletree is to install linux using a VM like virtual box , Ubuntu for example works very well with pharo https://www.virtualbox.org/ This way you avoid booting to another OS , you can also share your git folder to both windows and linux vm. This way you can use gitfiletree without ditching windows. Of course dual boot can work too if you dont need to use Pharo with windoom. VM option works also if you want to install MacOS on your windows pc. On Mon, Aug 3, 2015 at 1:13 PM Blondeau Vincent < vincent.blondeau(a)worldline.com> wrote: > Hi, > > > > Sorry but I am using Windowsâ¦ not because I want to but because I have > to... So the therapy will not work ;) > > Actually, the bugtracker of Moose can be on github, 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,â¦). > > > > Cheers, > > Vincent > > > > *De :* Pharo-dev [mailto:pharo-dev-bounces@lists.pharo.org] *De la part > de* Peter UhnÃ¡k > *EnvoyÃ© :* lundi 3 aoÃ»t 2015 11:56 > *Ã :* Pharo Development List > *Objet :* Re: [Pharo-dev] Google Code Shutdown > > > > As long as nobody on your team is using Windows, git(hub) is quite good. :) > > (And if you have Windows user, then find him a therapy first, or push for > libcgit :)) > > > > On Mon, Aug 3, 2015 at 4:35 AM, Alexandre Bergel <alexandre.bergel(a)me.com> > wrote: > > Github is indeed appealing. > > Cheers, > Alexandre > > > > > > On Aug 2, 2015, at 10:14 PM, Sean P. DeNigris <sean(a)clipperadams.com> > wrote: > > > > Tudor Girba-2 wrote > >> Would you like to help us move the moose-technology project? > > > > Sure. What do you have in mind? It seems exporting to GitHub is the > easiest > > option. There are a few limitations, but I've had good experiences... > > > > > > > > ----- > > Cheers, > > Sean > > -- > > View this message in context: > http://forum.world.st/Google-Code-Shutdown-tp4814760p4840733.html > > Sent from the Pharo Smalltalk Developers mailing list archive at > Nabble.com. > > > > -- > _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: > Alexandre Bergel http://www.bergel.eu > ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > > > > > > ------------------------------ > > 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 serge.stinckwich＠gmail.com

Create a repo for moose in order to have a bug tracker, move issues from Google code to this repo :-) Sorry I'm on my phone, I can't help now ;-) Sent from my iPhone > On 3 aoÃ»t 2015, at 13:00, Tudor Girba <tudor(a)tudorgirba.com> wrote: > > I just created this organization: > https://github.com/orgs/moosetechnology/dashboard > > What should I do next? > > Cheers, > Doru > >> On Mon, Aug 3, 2015 at 12:55 PM, <serge.stinckwich(a)gmail.com> wrote: >> Yes but at the moment only the bug tracker will be used I guess. Maybe someone can create a MOOSE org ? >> >> Sent from my iPhone >> >>> On 3 aoÃ»t 2015, at 11:56, Peter UhnÃ¡k <i.uhnak(a)gmail.com> wrote: >>> >>> As long as nobody on your team is using Windows, git(hub) is quite good. :) >>> (And if you have Windows user, then find him a therapy first, or push for libcgit :)) >>> >>>> On Mon, Aug 3, 2015 at 4:35 AM, Alexandre Bergel <alexandre.bergel(a)me.com> wrote: >>>> Github is indeed appealing. >>>> >>>> Cheers, >>>> Alexandre >>>> >>>> >>>> >>>> > On Aug 2, 2015, at 10:14 PM, Sean P. DeNigris <sean(a)clipperadams.com> wrote: >>>> > >>>> > Tudor Girba-2 wrote >>>> >> Would you like to help us move the moose-technology project? >>>> > >>>> > Sure. What do you have in mind? It seems exporting to GitHub is the easiest >>>> > option. There are a few limitations, but I've had good experiences... >>>> > >>>> > >>>> > >>>> > ----- >>>> > Cheers, >>>> > Sean >>>> > -- >>>> > View this message in context: http://forum.world.st/Google-Code-Shutdown-tp4814760p4840733.html >>>> > Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com. >>>> > >>>> >>>> -- >>>> _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: >>>> Alexandre Bergel http://www.bergel.eu >>>> ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > > > > -- > www.tudorgirba.com > > "Every thing has its own flow"

Aug. 3, 2015

Re: [Pharo-dev] Google Code Shutdown

by Tudor Girba

I just created this organization: https://github.com/orgs/moosetechnology/dashboard What should I do next? Cheers, Doru On Mon, Aug 3, 2015 at 12:55 PM, <serge.stinckwich(a)gmail.com> wrote: > Yes but at the moment only the bug tracker will be used I guess. Maybe > someone can create a MOOSE org ? > > Sent from my iPhone > > On 3 aoÃ»t 2015, at 11:56, Peter UhnÃ¡k <i.uhnak(a)gmail.com> wrote: > > As long as nobody on your team is using Windows, git(hub) is quite good. :) > (And if you have Windows user, then find him a therapy first, or push for > libcgit :)) > > On Mon, Aug 3, 2015 at 4:35 AM, Alexandre Bergel <alexandre.bergel(a)me.com> > wrote: > >> Github is indeed appealing. >> >> Cheers, >> Alexandre >> >> >> >> > On Aug 2, 2015, at 10:14 PM, Sean P. DeNigris <sean(a)clipperadams.com> >> wrote: >> > >> > Tudor Girba-2 wrote >> >> Would you like to help us move the moose-technology project? >> > >> > Sure. What do you have in mind? It seems exporting to GitHub is the >> easiest >> > option. There are a few limitations, but I've had good experiences... >> > >> > >> > >> > ----- >> > Cheers, >> > Sean >> > -- >> > View this message in context: >> http://forum.world.st/Google-Code-Shutdown-tp4814760p4840733.html >> > Sent from the Pharo Smalltalk Developers mailing list archive at >> Nabble.com. >> > >> >> -- >> _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: >> Alexandre Bergel http://www.bergel.eu >> ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. >> >> >> >> >> > -- www.tudorgirba.com "Every thing has its own flow"

Aug. 3, 2015

Re: [Pharo-dev] Google Code Shutdown

by serge.stinckwich＠gmail.com

Yes but at the moment only the bug tracker will be used I guess. Maybe someone can create a MOOSE org ? Sent from my iPhone > On 3 aoÃ»t 2015, at 11:56, Peter UhnÃ¡k <i.uhnak(a)gmail.com> wrote: > > As long as nobody on your team is using Windows, git(hub) is quite good. :) > (And if you have Windows user, then find him a therapy first, or push for libcgit :)) > >> On Mon, Aug 3, 2015 at 4:35 AM, Alexandre Bergel <alexandre.bergel(a)me.com> wrote: >> Github is indeed appealing. >> >> Cheers, >> Alexandre >> >> >> >> > On Aug 2, 2015, at 10:14 PM, Sean P. DeNigris <sean(a)clipperadams.com> wrote: >> > >> > Tudor Girba-2 wrote >> >> Would you like to help us move the moose-technology project? >> > >> > Sure. What do you have in mind? It seems exporting to GitHub is the easiest >> > option. There are a few limitations, but I've had good experiences... >> > >> > >> > >> > ----- >> > Cheers, >> > Sean >> > -- >> > View this message in context: http://forum.world.st/Google-Code-Shutdown-tp4814760p4840733.html >> > Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com. >> > >> >> -- >> _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: >> Alexandre Bergel http://www.bergel.eu >> ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. >

Aug. 3, 2015

Re: [Pharo-dev] Google Code Shutdown

by Peter UhnÃ¡k

> > 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.) Peter

Aug. 3, 2015

Re: [Pharo-dev] Google Code Shutdown

by Blondeau Vincent

Hi, Sorry but I am using Windowsâ¦ not because I want to but because I have to... So the therapy will not work ;) Actually, the bugtracker of Moose can be on github, 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,â¦). Cheers, Vincent De : Pharo-dev [mailto:pharo-dev-bounces@lists.pharo.org] De la part de Peter UhnÃ¡k EnvoyÃ© : lundi 3 aoÃ»t 2015 11:56 Ã : Pharo Development List Objet : Re: [Pharo-dev] Google Code Shutdown As long as nobody on your team is using Windows, git(hub) is quite good. :) (And if you have Windows user, then find him a therapy first, or push for libcgit :)) On Mon, Aug 3, 2015 at 4:35 AM, Alexandre Bergel <alexandre.bergel(a)me.com<mailto:alexandre.bergel@me.com>> wrote: Github is indeed appealing. Cheers, Alexandre > On Aug 2, 2015, at 10:14 PM, Sean P. DeNigris <sean(a)clipperadams.com<mailto:sean@clipperadams.com>> wrote: > > Tudor Girba-2 wrote >> Would you like to help us move the moose-technology project? > > Sure. What do you have in mind? It seems exporting to GitHub is the easiest > option. There are a few limitations, but I've had good experiences... > > > > ----- > Cheers, > Sean > -- > View this message in context: http://forum.world.st/Google-Code-Shutdown-tp4814760p4840733.html > Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com. > -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. ________________________________ 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 Peter UhnÃ¡k

As long as nobody on your team is using Windows, git(hub) is quite good. :) (And if you have Windows user, then find him a therapy first, or push for libcgit :)) On Mon, Aug 3, 2015 at 4:35 AM, Alexandre Bergel <alexandre.bergel(a)me.com> wrote: > Github is indeed appealing. > > Cheers, > Alexandre > > > > > On Aug 2, 2015, at 10:14 PM, Sean P. DeNigris <sean(a)clipperadams.com> > wrote: > > > > Tudor Girba-2 wrote > >> Would you like to help us move the moose-technology project? > > > > Sure. What do you have in mind? It seems exporting to GitHub is the > easiest > > option. There are a few limitations, but I've had good experiences... > > > > > > > > ----- > > Cheers, > > Sean > > -- > > View this message in context: > http://forum.world.st/Google-Code-Shutdown-tp4814760p4840733.html > > Sent from the Pharo Smalltalk Developers mailing list archive at > Nabble.com. > > > > -- > _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: > Alexandre Bergel http://www.bergel.eu > ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > > > > >

Aug. 3, 2015