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

Re: [Pharo-project] what happened with Shout colors in Pharo 1.1?

by Mariano Martinez Peck

Thanks Levente, but yes, still agree with Ramon. Anyway, this is why this is a preference, and it is not fixed. But anyway, we should select a better default one. cheers mariano On Mon, Oct 25, 2010 at 9:43 PM, Ramon Leon <ramon.leon(a)allresnet.com>wrote: > On 10/25/2010 12:35 PM, Levente Uzonyi wrote: > >> On Mon, 25 Oct 2010, Mariano Martinez Peck wrote: >> >> Sorry Simon, but I agree with Ramon. It is much clear for my eyes :) >>> >> >> Check out this (the formatting may be broken, but it should work): >> > > Nope, you've removed the bold, I like the bold, it makes the color stand > out. Without bold, you can barely see the colors. > > -- > Ramon Leon > http://onsmalltalk.com > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

Oct. 25, 2010

Re: [Pharo-project] Deprecation policy (was: Re: Object>>at:modify:???)

by Michael Roberts

I think the idea was that the deprecation scheme was fairly simple, and slightly better than just the original deprecated: . What you describe looks a bit over the top to me. just my 2p... cheers, Mike 2010/10/24 Levente Uzonyi <leves(a)elte.hu>: > On Sat, 23 Oct 2010, Mariano Martinez Peck wrote: > >> On Sat, Oct 23, 2010 at 1:32 PM, StÃ©phane Ducasse >> <stephane.ducasse(a)inria.fr >>> >>> wrote: >> >>> Ok we can deprecate it. >>> >>> >> ys, but please please please use deprecated: anExplanationString on: date >> in: version > > Wouldn't it be easier to rely on method timestamps + a version cache, than > spreading redundant information all over the place? Something like: > > Object >> deprecated: anExplanationString > Â Â Â Â "Warn that the sending method has been deprecated." > > Â Â Â Â (Deprecation > Â Â Â Â Â Â Â Â method: thisContext sender method > Â Â Â Â Â Â Â Â explanation: anExplanationString > Â Â Â Â Â Â Â Â on: (TimeStamp fromMethodTimeStamp: thisContext sender method > timeStamp) date "Or something nicer") signal > > Deprecation class >> method: aCompiledMethod explanation: > anExplanationString on: date > > Â Â Â Â ^self new > Â Â Â Â Â Â Â Â method: aCompiledMethod > Â Â Â Â Â Â Â Â explanation: anExplanationString > Â Â Â Â Â Â Â Â on: date asString > Â Â Â Â Â Â Â Â in: (SystemVersion alphaVersionAt: date) > > Someone has to implement #alphaVersionAt: (which is easy, Â but SystemVersion > has to be modified). > Finally the developement process has to follow some simple rules. > > > Levente > >> >> cheers >> >> mariano >> >> >>> On Oct 22, 2010, at 11:04 PM, Hernan Wilkinson wrote: >>> >>>> In a 1.1 image I have, the class HttpRequest is using that message... >>>> >>>> On Thu, Oct 21, 2010 at 4:08 PM, stephane ducasse < >>> >>> stephane.ducasse(a)free.fr> wrote: >>>> >>>> I would like to deprecate the following method since nobody use it. >>>> What do you think? >>>> >>>> Stef >>>> >>>> _______________________________________________ >>>> Pharo-project mailing list >>>> Pharo-project(a)lists.gforge.inria.fr >>>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >>>> >>>> >>>> >>>> -- >>>> HernÃ¡n Wilkinson >>>> Agile Software Development, Teaching & Coaching >>>> Mobile: +54 - 911 - 4470 - 7207 >>>> email: hernan.wilkinson(a)10Pines.com >>>> site: http://www.10Pines.com >>>> >>>> _______________________________________________ >>>> Pharo-project mailing list >>>> Pharo-project(a)lists.gforge.inria.fr >>>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >>> >>> >>> _______________________________________________ >>> Pharo-project mailing list >>> Pharo-project(a)lists.gforge.inria.fr >>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >>> > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

Oct. 25, 2010

Re: [Pharo-project] what happened with Shout colors in Pharo 1.1?

by Ramon Leon

On 10/25/2010 12:35 PM, Levente Uzonyi wrote: > On Mon, 25 Oct 2010, Mariano Martinez Peck wrote: > >> Sorry Simon, but I agree with Ramon. It is much clear for my eyes :) > > Check out this (the formatting may be broken, but it should work): Nope, you've removed the bold, I like the bold, it makes the color stand out. Without bold, you can barely see the colors. -- Ramon Leon http://onsmalltalk.com

Oct. 25, 2010

Re: [Pharo-project] what happened with Shout colors in Pharo 1.1?

by Levente Uzonyi

On Mon, 25 Oct 2010, Mariano Martinez Peck wrote: > Sorry Simon, but I agree with Ramon. It is much clear for my eyes :) Check out this (the formatting may be broken, but it should work): ^#( "(symbol color [emphasisSymbolOrArray [textStyleName [pixelHeight]]])" (default black ) (invalid red ) (excessCode red ) (comment (cyan muchDarker) ) (unfinishedComment (red muchDarker) italic) (#'$' (red muchDarker) ) (character (red muchDarker) ) (integer (red muchDarker) ) (number (red muchDarker) ) (#- (red muchDarker) ) (symbol (blue muchDarker) ) (stringSymbol (blue muchDarker) ) (literalArray (blue muchDarker) ) (string (magenta muchDarker) normal ) (unfinishedString red normal ) (assignment nil bold ) (ansiAssignment nil bold) (literal nil italic) (keyword (blue muchDarker) ) (binary (blue muchDarker) ) (unary (blue muchDarker) ) (incompleteKeyword (gray muchDarker) underlined) (incompleteBinary (gray muchDarker) underlined) (incompleteUnary (gray muchDarker) underlined) (undefinedKeyword red ) (undefinedBinary red ) (undefinedUnary red ) (patternKeyword nil bold) (patternBinary nil bold) (patternUnary nil bold) (#self (red muchDarker) ) (#super (red muchDarker) ) (#true (red muchDarker) ) (#false (red muchDarker) ) (#nil (red muchDarker) ) (#thisContext (red muchDarker) ) (#return (red muchDarker) ) (patternArg (blue muchDarker) ) (methodArg (blue muchDarker) ) (blockPatternArg (blue muchDarker) ) (blockArg (blue muchDarker) ) (argument (blue muchDarker) ) (blockArgColon black ) (leftParenthesis black ) (rightParenthesis black ) (leftParenthesis1 (green muchDarker) ) (rightParenthesis1 (green muchDarker) ) (leftParenthesis2 (magenta muchDarker) ) (rightParenthesis2 (magenta muchDarker) ) (leftParenthesis3 (red muchDarker) ) (rightParenthesis3 (red muchDarker) ) (leftParenthesis4 (green darker) ) (rightParenthesis4 (green darker) ) (leftParenthesis5 (orange darker) ) (rightParenthesis5 (orange darker) ) (leftParenthesis6 (magenta darker) ) (rightParenthesis6 (magenta darker) ) (leftParenthesis7 blue ) (rightParenthesis7 blue ) (blockStart black ) (blockEnd black ) (blockStart1 (green muchDarker) ) (blockEnd1 (green muchDarker) ) (blockStart2 (magenta muchDarker) ) (blockEnd2 (magenta muchDarker) ) (blockStart3 (red muchDarker) ) (blockEnd3 (red muchDarker) ) (blockStart4 (green darker) ) (blockEnd4 (green darker) ) (blockStart5 (orange darker) ) (blockEnd5 (orange darker) ) (blockStart6 (magenta darker) ) (blockEnd6 (magenta darker) ) (blockStart7 blue ) (blockEnd7 blue ) (arrayStart black ) (arrayEnd black ) (arrayStart1 black ) (arrayEnd1 black ) (leftBrace black ) (rightBrace black ) (cascadeSeparator black ) (statementSeparator black ) (externalCallType black ) (externalCallTypePointerIndicator black ) (primitiveOrExternalCallStart black ) (primitiveOrExternalCallEnd black ) (methodTempBar gray ) (blockTempBar gray ) (blockArgsBar gray ) (primitive (green muchDarker) bold) (pragmaKeyword (green muchDarker) bold) (pragmaUnary (green muchDarker) bold) (pragmaBinary (green muchDarker) bold) (externalFunctionCallingConvention (green muchDarker) bold) (module (green muchDarker) bold) (blockTempVar gray ) (blockPatternTempVar gray ) (instVar black ) (workspaceVar black ) (undefinedIdentifier red ) (incompleteIdentifier (gray darker) (italic underlined)) (tempVar (gray darker) ) (patternTempVar (gray darker) ) (poolConstant (gray muchDarker) ) (classVar (gray muchDarker) ) (globalVar black ) ) Levente > > On Mon, Oct 25, 2010 at 8:35 PM, Ramon Leon <ramon.leon(a)allresnet.com>wrote: > >> On 10/25/2010 11:04 AM, Simon Denier wrote: >> >>> Uhuh, that's indeed the old theme, but as said before I now prefer the >>> current theme with some adaptations: it's less aggressive to the eye. >>> >> >> And several of us have said, we like the old theme, very much because it's >> so aggressive to the eye. It's easy to identify things. The new theme is >> much less useful. The new style has removed colors and italics and has too >> much stuff looking the same; it's just bland. The old style is simply >> better because it visually separates different kinds of variables and scopes >> with color and font style. Local variables don't look like arguments, etc. >> >> >> -- >> Ramon Leon >> http://onsmalltalk.com >> >> _______________________________________________ >> Pharo-project mailing list >> Pharo-project(a)lists.gforge.inria.fr >> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >> >

Oct. 25, 2010

Re: [Pharo-project] what happened with Shout colors in Pharo 1.1?

by Mariano Martinez Peck

Sorry Simon, but I agree with Ramon. It is much clear for my eyes :) On Mon, Oct 25, 2010 at 8:35 PM, Ramon Leon <ramon.leon(a)allresnet.com>wrote: > On 10/25/2010 11:04 AM, Simon Denier wrote: > >> Uhuh, that's indeed the old theme, but as said before I now prefer the >> current theme with some adaptations: it's less aggressive to the eye. >> > > And several of us have said, we like the old theme, very much because it's > so aggressive to the eye. It's easy to identify things. The new theme is > much less useful. The new style has removed colors and italics and has too > much stuff looking the same; it's just bland. The old style is simply > better because it visually separates different kinds of variables and scopes > with color and font style. Local variables don't look like arguments, etc. > > > -- > Ramon Leon > http://onsmalltalk.com > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

Oct. 25, 2010

Re: [Pharo-project] Fwd: [squeak-dev] bug in OBMetagraphBuilder>>#reference

by Lukas Renggli

This was fixed in April 2010 to use pragmas, looks like the original poster uses an old version. 2010/10/25 Mariano Martinez Peck <marianopeck(a)gmail.com>: > lukas? > > ---------- Forwarded message ---------- > From: Chris Muller <asqueaker(a)gmail.com> > Date: Mon, Oct 25, 2010 at 6:16 PM > Subject: [squeak-dev] bug in OBMetagraphBuilder>>#reference > To: squeak dev <squeak-dev(a)lists.squeakfoundation.org> > > > Hi, I just wanted to let the maintainers of OmniBrowser know, there is > a bug with this method. > > The method reflects on its class and performs all that begin with > #populate. Â However, it is not unusual to expect that someone's > application might have a selector that also begins with the word > 'populate'. Â And so those selectors would be performed as well. > > This is why, for cases like this, it is better for a tool, which is > just a means, not an end, to be polite with the namespace; such as > checking for 'obPopulate' perhaps rather than simply 'populate'. > > But that's just a mini-rant, not even the bug. Â The bug is, my > 'populate' is not a unary message, so I get a failure on the perform, > "incorrect number of arguments." > > I therefore always change the method to: > > OBMetagraphBuilder >> execute > Â Â Â Â ((self class allSelectors select: [:ea | (ea beginsWith: 'populate') > and: [ ea isUnary ]]) asSortedArray) > Â Â Â Â Â Â Â Â do: [:selector | self perform: selector]. > Â Â Â Â ^ self root > > Thank you, > Â Chris > > > > _______________________________________________ > 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

Oct. 25, 2010

[Pharo-project] Fwd: [squeak-dev] bug in OBMetagraphBuilder>>#reference

by Mariano Martinez Peck

lukas? ---------- Forwarded message ---------- From: Chris Muller <asqueaker(a)gmail.com> Date: Mon, Oct 25, 2010 at 6:16 PM Subject: [squeak-dev] bug in OBMetagraphBuilder>>#reference To: squeak dev <squeak-dev(a)lists.squeakfoundation.org> Hi, I just wanted to let the maintainers of OmniBrowser know, there is a bug with this method. The method reflects on its class and performs all that begin with #populate. However, it is not unusual to expect that someone's application might have a selector that also begins with the word 'populate'. And so those selectors would be performed as well. This is why, for cases like this, it is better for a tool, which is just a means, not an end, to be polite with the namespace; such as checking for 'obPopulate' perhaps rather than simply 'populate'. But that's just a mini-rant, not even the bug. The bug is, my 'populate' is not a unary message, so I get a failure on the perform, "incorrect number of arguments." I therefore always change the method to: OBMetagraphBuilder >> execute ((self class allSelectors select: [:ea | (ea beginsWith: 'populate') and: [ ea isUnary ]]) asSortedArray) do: [:selector | self perform: selector]. ^ self root Thank you, Chris

Oct. 25, 2010

Re: [Pharo-project] problem with metacello in 1.2

by Dale Henrichs

Stef, I've wrapped my head around this one a little more ... the only stack that I saw, showed a 'Error: file is too short' error which is probably coming from the ZipArchive code ... this usually means that there was a network failure when trying to read a file from an HTTP repository. Perhaps SqueakSource was being saturated? Dale On 10/25/2010 11:44 AM, Dale Henrichs wrote: > Stef, > > I'm not sure what problem you are referring to. I haven't released a new > version of Metacello since the beginning of September.... > > Dale > > On 10/24/2010 09:55 AM, StÃ©phane Ducasse wrote: >> Dale >> >> did something change on the server side? >> >> This is strange >> >> 199 - Issue 3048: MC method cache fix. Thanks Igor Stasenko >> 200 - Issue 2653: Editor cursor fix: remove autoclose in texteditor. >> - Issue 3128: AuthorRequestImprovement. Thanks Alain Plantec - Issue 3099: Create method in the debugger does not provides getter/setters implementors. Thanks Hernan Wilkinson >> 201 - Issue 1800: MenuIcons and ThemeIcons should be merged. Big thanks to alain plantec!!! >> 202 - Issue 3070: weird replacements in TextEditor. Thanks Alain Plantec!!! >> 203 - Issue 654: inconsistent highlight color. Thanks Alain Plantec >> - Issue 3101: Wrong Monticello packages initialization order. Thanks Pavel Krivanek >> 204 - Issue 2868: allClassesUsingPool: allClassesUsingPoolVariable: for systemNavigation >> - Issue 3046: BUG: LineMorph class>>from:to:color:width: returns a PolygonMorph >> - Issue 3130: MethodReference>> #isLocalSelector should not be part of Monticello package >> - Issue 3095: Character isLiteral is in wrong category >> - Issue 3134: Cleaning uniclasses from smartRefStream >> Jannik can you check with the Utilities trick I sent you to try >> >> Utilities readServer: Utilities serverUrls updatesThrough: 12200 saveLocally: false updateImage: true >> >> 199 >> 200 >> 201 >> 202 >> 203 >> 204 >> >> so that we try to identify the problem >> >> Stef >> >> >> >> >> _______________________________________________ >> Pharo-project mailing list >> Pharo-project(a)lists.gforge.inria.fr >> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

Oct. 25, 2010

Re: [Pharo-project] problem with metacello in 1.2

by Dale Henrichs

Stef, I'm not sure what problem you are referring to. I haven't released a new version of Metacello since the beginning of September.... Dale On 10/24/2010 09:55 AM, StÃ©phane Ducasse wrote: > Dale > > did something change on the server side? > > This is strange > > 199 - Issue 3048: MC method cache fix. Thanks Igor Stasenko > 200 - Issue 2653: Editor cursor fix: remove autoclose in texteditor. > - Issue 3128: AuthorRequestImprovement. Thanks Alain Plantec - Issue 3099: Create method in the debugger does not provides getter/setters implementors. Thanks Hernan Wilkinson > 201 - Issue 1800: MenuIcons and ThemeIcons should be merged. Big thanks to alain plantec!!! > 202 - Issue 3070: weird replacements in TextEditor. Thanks Alain Plantec!!! > 203 - Issue 654: inconsistent highlight color. Thanks Alain Plantec > - Issue 3101: Wrong Monticello packages initialization order. Thanks Pavel Krivanek > 204 - Issue 2868: allClassesUsingPool: allClassesUsingPoolVariable: for systemNavigation > - Issue 3046: BUG: LineMorph class>>from:to:color:width: returns a PolygonMorph > - Issue 3130: MethodReference>> #isLocalSelector should not be part of Monticello package > - Issue 3095: Character isLiteral is in wrong category > - Issue 3134: Cleaning uniclasses from smartRefStream > Jannik can you check with the Utilities trick I sent you to try > > Utilities readServer: Utilities serverUrls updatesThrough: 12200 saveLocally: false updateImage: true > > 199 > 200 > 201 > 202 > 203 > 204 > > so that we try to identify the problem > > Stef > > > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Oct. 25, 2010

Re: [Pharo-project] what happened with Shout colors in Pharo 1.1?

by Ramon Leon

On 10/25/2010 11:04 AM, Simon Denier wrote: > Uhuh, that's indeed the old theme, but as said before I now prefer the > current theme with some adaptations: it's less aggressive to the eye. And several of us have said, we like the old theme, very much because it's so aggressive to the eye. It's easy to identify things. The new theme is much less useful. The new style has removed colors and italics and has too much stuff looking the same; it's just bland. The old style is simply better because it visually separates different kinds of variables and scopes with color and font style. Local variables don't look like arguments, etc. -- Ramon Leon http://onsmalltalk.com

Oct. 25, 2010