October 2013 - Pharo-users - lists.pharo.org

Re: [Pharo-users] [Pharo-dev] Start with a trivial improvement!

by StÃ©phane Ducasse

good idea yes for the blog entry On Oct 10, 2013, at 1:42 PM, Tudor Girba <tudor(a)tudorgirba.com> wrote: > Thank you, Marcus! > > Could you post this on the Pharo blog? > > Doru > > > On Thu, Oct 10, 2013 at 1:36 PM, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > +100 > > On 10 Oct 2013, at 13:21, Marcus Denker <marcus.denker(a)inria.fr> wrote: > > > One nice way to get in the mood of doing (and at the same time testing the system) is to start > > with trivial improvements. > > > > This is especially nice as a "starter" when you never contributed any change to Pharo. > > > > And by trivial I mean *really* mean trivial: > > -> a typo in a comment > > -> remove a temp not accessed > > -> clean out some trivial dead code > > -> do a simplistic refactoring of a bad smell, even inside a single method > > -> document something > > -> structure bad stuff better so it is easier to replace later > > > > Taken in itself, single changes like these have no influence, but: > > > > -> they get you in a mood of doing. > > -> they make you feel that Pharo is "owned" by you. > > -> take 1000 of those trivialities and they *do* make a difference. > > -> next time something bothers you, you will have the context of "I can just fix it". > > > > The critic tools is one way of finding these places, another is to just note down every time > > you see a triviality and later go through that list. The bug tracker can be source, too. > > > > > > <wtfm.jpg> > > > > Marcus > > > > > > -- > www.tudorgirba.com > > "Every thing has its own flow"

Oct. 10, 2013

Re: [Pharo-users] Monticello and HTTPS

by Manfred KrÃ¶hnert

Hello Sven, On Thu, Oct 10, 2013 at 3:50 PM, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > Hi Manfred, > > On 10 Oct 2013, at 15:41, Manfred KrÃ¶hnert <mkroehnert42(a)googlemail.com> > wrote: > > > Hi everyone, > > > > I am one of the guys helping Nico with Amber. > > > > Now, I recently started to experiment with Pharo for a small project. > > After some reading and experimenting I was able to get something running > thanks to the good documentation available. > > > > While I was on the go I tried to save my code with Monticello on a > private WebDAV share. > > However, the server is only accessible via HTTPS which resulted in an > error accessing it from the Monticello browser. > > > > Now my question is if HTTPS is supported by Montichello or not. > > Since the server is accessed with username/password I'd rather not use > plain HTTP. > > > > Best, > > Manfred > > It should work. But I am not aware of any official, public repositories > that run HTTPS, so its hard to test. I also understand that it could be > difficult to give stack traces, but details are necessary to make any > progress on helping you. > > One thing you could try is to access the repository directly: i.e. create > a ZnClient that tries to read the listing or a specific package. > > Sven > thanks for the initial info that it should work. I would have given further details but currently I can't access the machine where I tried it. I'll try your suggestion and provide a more detailed report as soon as possible. Best, Manfred

Oct. 10, 2013

Re: [Pharo-users] Monticello and HTTPS

by Sven Van Caekenberghe

Hi Manfred, On 10 Oct 2013, at 15:41, Manfred KrÃ¶hnert <mkroehnert42(a)googlemail.com> wrote: > Hi everyone, > > I am one of the guys helping Nico with Amber. > > Now, I recently started to experiment with Pharo for a small project. > After some reading and experimenting I was able to get something running thanks to the good documentation available. > > While I was on the go I tried to save my code with Monticello on a private WebDAV share. > However, the server is only accessible via HTTPS which resulted in an error accessing it from the Monticello browser. > > Now my question is if HTTPS is supported by Montichello or not. > Since the server is accessed with username/password I'd rather not use plain HTTP. > > Best, > Manfred It should work. But I am not aware of any official, public repositories that run HTTPS, so its hard to test. I also understand that it could be difficult to give stack traces, but details are necessary to make any progress on helping you. One thing you could try is to access the repository directly: i.e. create a ZnClient that tries to read the listing or a specific package. Sven

Oct. 10, 2013

Re: [Pharo-users] visual clues help

by Paolo Piccinelli

Thanks Ben, you confirmed my doubts. Paolo From: benjamin.vanryseghem.pharo(a)gmail.com Date: Thu, 10 Oct 2013 14:35:28 +0200 To: pharo-users(a)lists.pharo.org Subject: Re: [Pharo-users] visual clues help A gray and white box means the package is emptythe fray one is the regular icon :) Welcome in Pharo :P Ben On Oct 10, 2013, at 2:22 PM, Paolo Piccinelli <captain86(a)hotmail.it> wrote:Good Morning Everyone, my name is Paolo Piccinelli and i'm a rookie in using Pharo. I installed the version 2.0, and I'd like to know what's the difference between a gray and white cube and a totally gray gift box near the name of the Packages. The first kind of cube, does it means that there are some classes missing in the package? Where can i find something about these visual clues?Thanks in advance for all the explanations. Best; Paolo

Oct. 10, 2013

Monticello and HTTPS

by Manfred KrÃ¶hnert

Hi everyone, I am one of the guys helping Nico with Amber. Now, I recently started to experiment with Pharo for a small project. After some reading and experimenting I was able to get something running thanks to the good documentation available. While I was on the go I tried to save my code with Monticello on a private WebDAV share. However, the server is only accessible via HTTPS which resulted in an error accessing it from the Monticello browser. Now my question is if HTTPS is supported by Montichello or not. Since the server is accessed with username/password I'd rather not use plain HTTP. Best, Manfred

Oct. 10, 2013

Re: [Pharo-users] visual clues help

by Benjamin

A gray and white box means the package is empty the fray one is the regular icon :) Welcome in Pharo :P Ben On Oct 10, 2013, at 2:22 PM, Paolo Piccinelli <captain86(a)hotmail.it> wrote: > Good Morning Everyone, > > my name is Paolo Piccinelli and i'm a rookie in using Pharo. I installed the version 2.0, and I'd like to know what's the difference between a gray and white cube and a totally gray gift box near the name of the Packages. The first kind of cube, does it means that there are some classes missing in the package? Where can i find something about these visual clues? > Thanks in advance for all the explanations. > > Best; > > Paolo

Oct. 10, 2013

visual clues help

by Paolo Piccinelli

Good Morning Everyone, my name is Paolo Piccinelli and i'm a rookie in using Pharo. I installed the version 2.0, and I'd like to know what's the difference between a gray and white cube and a totally gray gift box near the name of the Packages. The first kind of cube, does it means that there are some classes missing in the package? Where can i find something about these visual clues?Thanks in advance for all the explanations. Best; Paolo

Oct. 10, 2013

Re: [Pharo-users] [Pharo-dev] Start with a trivial improvement!

by Marcus Denker

On Oct 10, 2013, at 1:43 PM, Tudor Girba <tudor(a)tudorgirba.com> wrote: > Thank you, Marcus! > > Could you post this on the Pharo blog? > Good idea, yes, I will do that. Marcus

Oct. 10, 2013

Re: [Pharo-users] Start with a trivial improvement!

by Yuriy Tymchuk

On Oct 10, 2013, at 1:42 PM, Tudor Girba <tudor(a)tudorgirba.com> wrote: > Thank you, Marcus! > > Could you post this on the Pharo blog? And put a link to Camillo's guide on bug fixing, so enthusiasts will know how to contribute :) > > Doru > > > On Thu, Oct 10, 2013 at 1:36 PM, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > +100 > > On 10 Oct 2013, at 13:21, Marcus Denker <marcus.denker(a)inria.fr> wrote: > > > One nice way to get in the mood of doing (and at the same time testing the system) is to start > > with trivial improvements. > > > > This is especially nice as a "starter" when you never contributed any change to Pharo. > > > > And by trivial I mean *really* mean trivial: > > -> a typo in a comment > > -> remove a temp not accessed > > -> clean out some trivial dead code > > -> do a simplistic refactoring of a bad smell, even inside a single method > > -> document something > > -> structure bad stuff better so it is easier to replace later > > > > Taken in itself, single changes like these have no influence, but: > > > > -> they get you in a mood of doing. > > -> they make you feel that Pharo is "owned" by you. > > -> take 1000 of those trivialities and they *do* make a difference. > > -> next time something bothers you, you will have the context of "I can just fix it". > > > > The critic tools is one way of finding these places, another is to just note down every time > > you see a triviality and later go through that list. The bug tracker can be source, too. > > > > > > <wtfm.jpg> > > > > Marcus > > > > > > -- > www.tudorgirba.com > > "Every thing has its own flow"

Oct. 10, 2013

Re: [Pharo-users] Start with a trivial improvement!

by Tudor Girba

Thank you, Marcus! Could you post this on the Pharo blog? Doru On Thu, Oct 10, 2013 at 1:36 PM, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > +100 > > On 10 Oct 2013, at 13:21, Marcus Denker <marcus.denker(a)inria.fr> wrote: > > > One nice way to get in the mood of doing (and at the same time testing > the system) is to start > > with trivial improvements. > > > > This is especially nice as a "starter" when you never contributed any > change to Pharo. > > > > And by trivial I mean *really* mean trivial: > > -> a typo in a comment > > -> remove a temp not accessed > > -> clean out some trivial dead code > > -> do a simplistic refactoring of a bad smell, even inside a > single method > > -> document something > > -> structure bad stuff better so it is easier to replace later > > > > Taken in itself, single changes like these have no influence, but: > > > > -> they get you in a mood of doing. > > -> they make you feel that Pharo is "owned" by you. > > -> take 1000 of those trivialities and they *do* make a difference. > > -> next time something bothers you, you will have the context of > "I can just fix it". > > > > The critic tools is one way of finding these places, another is to just > note down every time > > you see a triviality and later go through that list. The bug tracker can > be source, too. > > > > > > <wtfm.jpg> > > > > Marcus > > > -- www.tudorgirba.com "Every thing has its own flow"

Oct. 10, 2013