April 2015 - Pharo-users - lists.pharo.org

Re: [Pharo-users] [Moose-dev] QualityAssistant v0.4

by Johan Fabry

Hola, It looks like a really cool tool! I just added it to my LRP development image and I plan on using it full time. I am always interested in writing cleaner code. So expect comments from me :-) Actually I already have one: For one class I got the critic âReferences an abstract classâ and 'Subclass responsibility not definedâ. Excellent that you found it, but now I have to go through all the methods of the class to see where the first critic comes from, and through all methods of all leaf classes for the second one. :-( :-( :-( Thatâs a lot of work for me to rescue some information which apparently the tool already knows. Please add more information on where the issue is on these kinds of errors, so I can fix them more easily ... Thanks and keep up the good work! > On Apr 22, 2015, at 03:58, Yuriy Tymchuk <yuriy.tymchuk(a)me.com> wrote: > > Hi everyone! > > Probably most of you know, that I am developing a tool called QualityAssistant, which displays current critics about your code in SystemBrowser, Inspector and Spotter. > > Iâm happy to tell you that there is a new release v0.4 which does not require you to do any previous setup! Just load it from configuration browser (pharo 4 & 5) and it will start giving you feedback. More details can be found here: https://github.com/Uko/QualityAssistant#quality-assistant-beta- <https://github.com/Uko/QualityAssistant#quality-assistant-beta->. If you are upgrading from older version, it is recommended to load QualityAssistant into a fresh image, because multiple announcement and process changes may cause exceptions in old objects. > > Even if you are an experienced programmer you can find QualityAssistant useful for instantly spotting typos or making sure that you didnât forget some details about your code. > > Please give me a feedback about your experience, as I want to make it even more useful. Either write me an email, or open an entry at: https://github.com/Uko/QualityAssistant/issues <https://github.com/Uko/QualityAssistant/issues> > > Have a nice week! > Uko > > <critics.jpg> > _______________________________________________ > Moose-dev mailing list > Moose-dev(a)iam.unibe.ch > https://www.iam.unibe.ch/mailman/listinfo/moose-dev ---> Save our in-boxes! http://emailcharter.org <--- Johan Fabry - http://pleiad.cl/~jfabry PLEIAD lab - Computer Science Department (DCC) - University of Chile

April 22, 2015

Re: [Pharo-users] [Pharo-dev] QualityAssistant v0.4

by Tudor Girba

Hi, I only took a brief look, but I think that reaching the no-input-required situation is a major step forward. Nice job. Keep it up. Cheers, Doru On Wed, Apr 22, 2015 at 8:58 AM, Yuriy Tymchuk <yuriy.tymchuk(a)me.com> wrote: > Hi everyone! > > Probably most of you know, that I am developing a tool called > QualityAssistant, which displays current critics about your code in > SystemBrowser, Inspector and Spotter. > > Iâm happy to tell you that there is a new release v0.4 which does not > require you to do any previous setup! Just load it from configuration > browser (pharo 4 & 5) and it will start giving you feedback. More details > can be found here: > https://github.com/Uko/QualityAssistant#quality-assistant-beta-. If you > are upgrading from older version, it is recommended to load > QualityAssistant into a fresh image, because multiple announcement and > process changes may cause exceptions in old objects. > > Even if you are an experienced programmer you can find QualityAssistant > useful for instantly spotting typos or making sure that you didnât forget > some details about your code. > > Please give me a feedback about your experience, as I want to make it even > more useful. Either write me an email, or open an entry at: > https://github.com/Uko/QualityAssistant/issues > > Have a nice week! > Uko > > -- www.tudorgirba.com "Every thing has its own flow"

April 22, 2015

Woden-Roassal 3d object rotations

by Lusa Nicolas

Hi, I am still working with Woden, in particular with Woden-Roassal and I noticed that rotations on objects are missing (I feel that this is weird that it doesn't have such feature so I am not excluding that I can be wrong but I didn't manage to find anything in the code to rotate objects). Now if I would like to rotate objects it wouldn't be too bad if I were using Woden at his "lowest layer" but I am actually building cubes with Woden-Roassal and there I get lost. I already made some rotations on Woden built arbitrary objects, now I would like to extend it to objects built from Woden-Roassal but I honestly miss on finding the connection between the two. I saw that the base shape is built in: RWCube>>#createBaseShapeNode, I would be able to build a rotated shape from there but that would result in all shapes being rotated in such way since in RWSimpleShape>>#buildRenderableFor:view: when we select the shape: baseShape := aView baseShapeNodeNamed: self baseShapeName ifAbsentPut: [ self createBaseShapeNode ]. we would get back the previous base shape defined. Any suggestions on how to do it? Cheers, Nicolas

April 22, 2015

Re: [Pharo-users] [Moose-dev] [Pharo-dev] QualityAssistant v0.4

by Yuriy Tymchuk

I am definitely interested in it. Let me know what I should do for this. I havenât got a lot of feedback from users, but I fixed problems reported by my group and Alex Bergel. The remaining reported issues are quite minor and related to how SmallLint works. Changes to SmallLint will arrive later after I figure out what the rules are about and what is the way to improve them. Cheers, Uko > On 22 Apr 2015, at 12:23, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: > > this is so good. > what about integrate it to Pharo? > > cheers, > Esteban > >> On 22 Apr 2015, at 08:58, Yuriy Tymchuk <yuriy.tymchuk(a)me.com <mailto:yuriy.tymchuk@me.com>> wrote: >> >> Hi everyone! >> >> Probably most of you know, that I am developing a tool called QualityAssistant, which displays current critics about your code in SystemBrowser, Inspector and Spotter. >> >> Iâm happy to tell you that there is a new release v0.4 which does not require you to do any previous setup! Just load it from configuration browser (pharo 4 & 5) and it will start giving you feedback. More details can be found here: https://github.com/Uko/QualityAssistant#quality-assistant-beta- <https://github.com/Uko/QualityAssistant#quality-assistant-beta->. If you are upgrading from older version, it is recommended to load QualityAssistant into a fresh image, because multiple announcement and process changes may cause exceptions in old objects. >> >> Even if you are an experienced programmer you can find QualityAssistant useful for instantly spotting typos or making sure that you didnât forget some details about your code. >> >> Please give me a feedback about your experience, as I want to make it even more useful. Either write me an email, or open an entry at: https://github.com/Uko/QualityAssistant/issues <https://github.com/Uko/QualityAssistant/issues> >> >> Have a nice week! >> Uko >> >> <critics.jpg> > > _______________________________________________ > Moose-dev mailing list > Moose-dev(a)iam.unibe.ch > https://www.iam.unibe.ch/mailman/listinfo/moose-dev

April 22, 2015

Re: [Pharo-users] [Pharo-dev] QualityAssistant v0.4

by Esteban Lorenzano

this is so good. what about integrate it to Pharo? cheers, Esteban > On 22 Apr 2015, at 08:58, Yuriy Tymchuk <yuriy.tymchuk(a)me.com> wrote: > > Hi everyone! > > Probably most of you know, that I am developing a tool called QualityAssistant, which displays current critics about your code in SystemBrowser, Inspector and Spotter. > > Iâm happy to tell you that there is a new release v0.4 which does not require you to do any previous setup! Just load it from configuration browser (pharo 4 & 5) and it will start giving you feedback. More details can be found here: https://github.com/Uko/QualityAssistant#quality-assistant-beta- <https://github.com/Uko/QualityAssistant#quality-assistant-beta->. If you are upgrading from older version, it is recommended to load QualityAssistant into a fresh image, because multiple announcement and process changes may cause exceptions in old objects. > > Even if you are an experienced programmer you can find QualityAssistant useful for instantly spotting typos or making sure that you didnât forget some details about your code. > > Please give me a feedback about your experience, as I want to make it even more useful. Either write me an email, or open an entry at: https://github.com/Uko/QualityAssistant/issues <https://github.com/Uko/QualityAssistant/issues> > > Have a nice week! > Uko > > <critics.jpg>

April 22, 2015

Re: [Pharo-users] Wrong slave for CI job

by Blondeau Vincent

Nice ! You're welcome ! Vincent -----Message d'origine----- De : Pharo-users [mailto:pharo-users-bounces@lists.pharo.org] De la part de Serge Stinckwich EnvoyÃ© : mercredi 22 avril 2015 10:49 Ã : Any question about pharo is welcome Objet : Re: [Pharo-users] Wrong slave for CI job Ok seems to work better now. The error reported was not really helpful ;-) All builds are green now (including Pharo 5.0) ! https://ci.inria.fr/pharo-contribution/job/CORMAS/ Thank you for your help. On Tue, Apr 21, 2015 at 5:49 PM, Blondeau Vincent <vincent.blondeau(a)worldline.com> wrote: > Indeed, but it seems that is not the main problem. > As you use a configuration matrix, you should go inside one "cell" to see the real problem. > For example, go to: > https://ci.inria.fr/pharo-contribution/job/Cormas/PHARO=40,VERSION=dev > elopment,VM=vm,label=32/8/console You will see that the job tries to > access: http://smalltalkhub.com/mc/cormas/Cormas/main which is not existing. > > Vincent > > -----Message d'origine----- > De : Pharo-users [mailto:pharo-users-bounces@lists.pharo.org] De la > part de Serge Stinckwich EnvoyÃ© : mardi 21 avril 2015 17:39 Ã : Any > question about pharo is welcome Objet : Re: [Pharo-users] Wrong slave > for CI job > > Thank you Vincent. > > I add the Slaves axis in the configuration and select 32, but the job is still running on raspberry pi ... > > On Tue, Apr 21, 2015 at 5:30 PM, Blondeau Vincent <vincent.blondeau(a)worldline.com> wrote: >> Hi, >> >> In the configuration of your job, you should add in the configuration matrix the slaves on which your job should be executed. >> Click on add axis, and choose "Slaves" to add it. After you have to choose one label. I think that "32" is nice for a standard job. >> >> Best, >> Vincent Blondeau >> >> -----Message d'origine----- >> De : Pharo-users [mailto:pharo-users-bounces@lists.pharo.org] De la >> part de Serge Stinckwich EnvoyÃ© : mardi 21 avril 2015 17:17 Ã : Any >> question about pharo is welcome Objet : [Pharo-users] Wrong slave for >> CI job >> >> I add a new CI job >> here:https://ci.inria.fr/pharo-contribution/job/Cormas/ >> bu every time I try to run the job, the job is executed on a pharo-contribution-raspberrypi-linux slave and fails ... I try to change the node without success ... >> >> -- >> Serge Stinckwich >> UCBN & UMI UMMISCO 209 (IRD/UPMC) >> Every DSL ends up being Smalltalk >> http://www.doesnotunderstand.org/ >> >> >> >> 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. > > > > -- > Serge Stinckwich > UCBN & UMI UMMISCO 209 (IRD/UPMC) > Every DSL ends up being Smalltalk > http://www.doesnotunderstand.org/ > > > > 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. -- Serge Stinckwich UCBN & UMI UMMISCO 209 (IRD/UPMC) Every DSL ends up being Smalltalk http://www.doesnotunderstand.org/ 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.

April 22, 2015

Re: [Pharo-users] Wrong slave for CI job

by Serge Stinckwich

Ok seems to work better now. The error reported was not really helpful ;-) All builds are green now (including Pharo 5.0) ! https://ci.inria.fr/pharo-contribution/job/CORMAS/ Thank you for your help. On Tue, Apr 21, 2015 at 5:49 PM, Blondeau Vincent <vincent.blondeau(a)worldline.com> wrote: > Indeed, but it seems that is not the main problem. > As you use a configuration matrix, you should go inside one "cell" to see the real problem. > For example, go to: > https://ci.inria.fr/pharo-contribution/job/Cormas/PHARO=40,VERSION=developm… > You will see that the job tries to access: http://smalltalkhub.com/mc/cormas/Cormas/main which is not existing. > > Vincent > > -----Message d'origine----- > De : Pharo-users [mailto:pharo-users-bounces@lists.pharo.org] De la part de Serge Stinckwich > EnvoyÃ© : mardi 21 avril 2015 17:39 > Ã : Any question about pharo is welcome > Objet : Re: [Pharo-users] Wrong slave for CI job > > Thank you Vincent. > > I add the Slaves axis in the configuration and select 32, but the job is still running on raspberry pi ... > > On Tue, Apr 21, 2015 at 5:30 PM, Blondeau Vincent <vincent.blondeau(a)worldline.com> wrote: >> Hi, >> >> In the configuration of your job, you should add in the configuration matrix the slaves on which your job should be executed. >> Click on add axis, and choose "Slaves" to add it. After you have to choose one label. I think that "32" is nice for a standard job. >> >> Best, >> Vincent Blondeau >> >> -----Message d'origine----- >> De : Pharo-users [mailto:pharo-users-bounces@lists.pharo.org] De la >> part de Serge Stinckwich EnvoyÃ© : mardi 21 avril 2015 17:17 Ã : Any >> question about pharo is welcome Objet : [Pharo-users] Wrong slave for >> CI job >> >> I add a new CI job >> here:https://ci.inria.fr/pharo-contribution/job/Cormas/ >> bu every time I try to run the job, the job is executed on a pharo-contribution-raspberrypi-linux slave and fails ... I try to change the node without success ... >> >> -- >> Serge Stinckwich >> UCBN & UMI UMMISCO 209 (IRD/UPMC) >> Every DSL ends up being Smalltalk >> http://www.doesnotunderstand.org/ >> >> >> >> 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. > > > > -- > Serge Stinckwich > UCBN & UMI UMMISCO 209 (IRD/UPMC) > Every DSL ends up being Smalltalk > http://www.doesnotunderstand.org/ > > > > 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. -- Serge Stinckwich UCBN & UMI UMMISCO 209 (IRD/UPMC) Every DSL ends up being Smalltalk http://www.doesnotunderstand.org/

April 22, 2015

QualityAssistant v0.4

by Yuriy Tymchuk

Hi everyone! Probably most of you know, that I am developing a tool called QualityAssistant, which displays current critics about your code in SystemBrowser, Inspector and Spotter. Iâm happy to tell you that there is a new release v0.4 which does not require you to do any previous setup! Just load it from configuration browser (pharo 4 & 5) and it will start giving you feedback. More details can be found here: https://github.com/Uko/QualityAssistant#quality-assistant-beta- <https://github.com/Uko/QualityAssistant#quality-assistant-beta->. If you are upgrading from older version, it is recommended to load QualityAssistant into a fresh image, because multiple announcement and process changes may cause exceptions in old objects. Even if you are an experienced programmer you can find QualityAssistant useful for instantly spotting typos or making sure that you didnât forget some details about your code. Please give me a feedback about your experience, as I want to make it even more useful. Either write me an email, or open an entry at: https://github.com/Uko/QualityAssistant/issues Have a nice week! Uko

April 22, 2015

You love success stories, us too

by stepharo

Hi guys http://pharo.org/success I know that you love success stories and we love them too. So to get success stories we need people to give us theirs. A success story is simple! - you do not have to been able to buy google based on your cash flow - you do not have to buy apple either - you have to have a solution to a problem and it should be in Pharo - it can be technical - it is good if there is a business value but this is not mandatory A success story is two paragraphs - one paragraph for your cool app/solution is - one paragraph for how cool pharo is - if you have a visual support even better Stef

April 22, 2015

Re: [Pharo-users] [Bulk] Re: Fwd: Fwd: Debris' Quuve - Technologies used

by stepharo

April 22, 2015