September 2010 - Pharo-dev - lists.pharo.org

Re: [Pharo-project] simpleLog in pharo?

by StÃ©phane Ducasse

>> GÃ¶ran, >> >> I think before we adopt anything, it should have the "left running" scenario addressed in some way. Pharo is supposed to be robust. > > That mean losing the silent failures, and doing so in a way that the new information does not bring the system to its knees. > > First - I did not bring this up, so feel free to fix any flaws you see/find :). The code base is very small. > > Secondly - my impression of Pharo so far is not really "robust", and don't get me wrong here - it is not criticism, but my feeling every time I have used Pharo is that it is smack full of new stuff (completion, OB browsers etc etc) which quite often seems to break and also makes it painful to develop on my old trusty kinda slow Dell laptop. Where are your feedback? When did you mention that? And yes the system should change because I can list a lot of skeletons and paper tape that make the system believe it is working but is brittle. > It seems to me that "progress" (new shiny stuff!) has been put in favor of robustness, Apparently all the bugs we close do not count? Come on goran... > which probably is why Pharo is attractive to a lot of people. Perhaps Pharo changed focus for next release? > > Sorry for that little rant, don't really "mean" anything with it, just curious to see if I am the only one with this feeling. >> On Windows, OutputDebugString() is probably good enough. Since I am doing everything I can to ditch said platform, I might not be the best person to ask. Certainly, it is where I would go for a live view, and a file-based log would then cover everything else - I think.

Sept. 9, 2010

Re: [Pharo-project] WebClient License Update

by StÃ©phane Ducasse

> For string concatenation on the other hand, we're basically talking about dispersing a whole load of FUD about all the things that "may" go wrong. Fact is, nothing actually *does* go wrong with the change, but the change does fix situations that are *very* difficult to handle otherwise. One of the unfortunate realities of string concatenation is that it's very often used around error messages and logging, often in corner cases that aren't well tested, like: > > <some impossible condition> ifTrue:[ > self log: 'Found impossible condition: ', foo. > ]. I do not buy this argument. We should fix the code and not break the libraries. Your argument is bogus. We do not want such kind of extensions that opens the door to really sloppy code. Then we should avoid overrides as much as possible. Stef

Sept. 9, 2010

Re: [Pharo-project] Changing the world menu

by StÃ©phane Ducasse

On Sep 9, 2010, at 11:49 AM, Hilaire Fernandes wrote: > How can I change programmatically the world menu? > Which class to look at? PasteUpMorph? Setting? > > Hilaire > > -- > Dr. Geo, to discover geometry on Linux, Windows, MAC and XO > http://community.ofset.org/index.php/DrGeo > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Sept. 9, 2010

Re: [Pharo-project] Feature Request: Strict Compiler / Monticello Mode

by StÃ©phane Ducasse

ok let us know how we can help. There are methods from grease that I would love to have in Pharo to get better libraries. Stef > I suggest that we just remove the two methods (Collection>>#sorted and > Colection>>#sorted:) from Grease. It doesn't look like the system > itself is calling them on Collection, and most subclasses override > them anyway. > > Lukas > > On 9 September 2010 11:10, Philippe Marschall <kustos(a)gmx.net> wrote: >> Hi >> >> It seems like we unintentionally introduced an override for Collection >>>> #sorted in Grease. That puts in a hard place because we can't simply >> remove it from Grease. Because if you do that everybody who updates >> looses the method and potentially breaks his image. Yeah, I see that the >> real fix you be for Monticello to restore the old method but that hasn't >> happened in years. >> >> Monticello / the compiler already warns about a lot of less important >> things. Now I know adding an additional preference for that is ugly and >> I'd welcome and better/nicer solution. >> >> Cheers >> Philippe

Sept. 9, 2010

Re: [Pharo-project] Feature Request: Strict Compiler / Monticello Mode

by Lukas Renggli

Btw, same problem with WriteStream>>crlf. Lukas On 9 September 2010 12:10, Lukas Renggli <renggli(a)gmail.com> wrote: > I suggest that we just remove the two methods (Collection>>#sorted and > Colection>>#sorted:) from Grease. It doesn't look like the system > itself is calling them on Collection, and most subclasses override > them anyway. > > Lukas > > On 9 September 2010 11:10, Philippe Marschall <kustos(a)gmx.net> wrote: >> Hi >> >> It seems like we unintentionally introduced an override for Collection >>>> #sorted in Grease. That puts in a hard place because we can't simply >> remove it from Grease. Because if you do that everybody who updates >> looses the method and potentially breaks his image. Yeah, I see that the >> real fix you be for Monticello to restore the old method but that hasn't >> happened in years. >> >> Monticello / the compiler already warns about a lot of less important >> things. Now I know adding an additional preference for that is ugly and >> I'd welcome and better/nicer solution. >> >> Cheers >> Philippe >> >> >> _______________________________________________ >> Pharo-project mailing list >> Pharo-project(a)lists.gforge.inria.fr >> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >> > > > > -- > Lukas Renggli > www.lukas-renggli.ch > -- Lukas Renggli www.lukas-renggli.ch

Sept. 9, 2010

Re: [Pharo-project] Feature Request: Strict Compiler / Monticello Mode

by Lukas Renggli

I suggest that we just remove the two methods (Collection>>#sorted and Colection>>#sorted:) from Grease. It doesn't look like the system itself is calling them on Collection, and most subclasses override them anyway. Lukas On 9 September 2010 11:10, Philippe Marschall <kustos(a)gmx.net> wrote: > Hi > > It seems like we unintentionally introduced an override for Collection >>> #sorted in Grease. That puts in a hard place because we can't simply > remove it from Grease. Because if you do that everybody who updates > looses the method and potentially breaks his image. Yeah, I see that the > real fix you be for Monticello to restore the old method but that hasn't > happened in years. > > Monticello / the compiler already warns about a lot of less important > things. Now I know adding an additional preference for that is ugly and > I'd welcome and better/nicer solution. > > Cheers > Philippe > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > -- Lukas Renggli www.lukas-renggli.ch

Sept. 9, 2010

[Pharo-project] Pharo taskbar

by Hilaire Fernandes

I added a button to the taskbar, but this one is regularly pooled and udpated with the active window. So my button is deleted. As far as I can see from the taskbar code there is no mechanism to add alternate widget to the taskbar, right? Hilaire -- Dr. Geo, to discover geometry on Linux, Windows, MAC and XO http://community.ofset.org/index.php/DrGeo

Sept. 9, 2010

[Pharo-project] [update 1.2] #12128

by StÃ©phane Ducasse

12128 ----- - Issue 2888: floating point printing is wrong. Thanks Paolo Bonzini and Nicolas Cellier. Now 0.3-0.2 prints 0.09999999999999998 - Issue 2919: SystemNavigation package support. Thanks Eliot Miranda.

Sept. 9, 2010

[Pharo-project] Changing the world menu

by Hilaire Fernandes

How can I change programmatically the world menu? Which class to look at? Hilaire -- Dr. Geo, to discover geometry on Linux, Windows, MAC and XO http://community.ofset.org/index.php/DrGeo

Sept. 9, 2010

Re: [Pharo-project] [update 1.2] #12127

by Mariano Martinez Peck

On Thu, Sep 9, 2010 at 11:07 AM, stephane ducasse <stephane.ducasse(a)free.fr>wrote: > 12127 > ----- > > - 2920 and 2921: Some little recategorizations with Gabriela Arevalo, > Gabriel Barbuto, Nicolas Paez and Martin Dias. > what happened to pharo ? all argentinians now? :) > > Stef > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

Sept. 9, 2010