February 2011 - Pharo-dev - lists.pharo.org

Re: [Pharo-project] Issue 3583 in pharo: Shout should only be active in code panes

by pharo＠googlecode.com

Comment #43 on issue 3583 by tudor.gi...(a)gmail.com: Shout should only be active in code panes http://code.google.com/p/pharo/issues/detail?id=3583 Hi Stef, I just loaded the following slice in PharoDev based on 12331 and everything works just fine. SLICE-Issue-3583--Shout-should-only-be-active-in-code-panes-BenjaminVanRyseghem.1

Feb. 10, 2011

Re: [Pharo-project] Issue 3583 in pharo: Shout should only be active in code panes

by pharo＠googlecode.com

Comment #42 on issue 3583 by stephane...(a)gmail.com: Shout should only be active in code panes http://code.google.com/p/pharo/issues/detail?id=3583 Arghhhhhh I could not release because workspace protocol changed between 1.2 and 1.3 So sorry guy but may be we will stay like that for now edit: aText label: labelString accept: anAction "Open an editor on the given string/text" ^(Workspace openLabel: labelString) acceptContents: aText; acceptAction: anAction; yourself.

Feb. 10, 2011

Re: [Pharo-project] Issue 3583 in pharo: Shout should only be active in code panes

by pharo＠googlecode.com

Updates: Status: Closed Comment #41 on issue 3583 by stephane...(a)gmail.com: Shout should only be active in code panes http://code.google.com/p/pharo/issues/detail?id=3583 (No comment was entered for this change.)

Feb. 10, 2011

Re: [Pharo-project] Issue 3583 in pharo: Shout should only be active in code panes

by pharo＠googlecode.com

Comment #40 on issue 3583 by stephane...(a)gmail.com: Shout should only be active in code panes http://code.google.com/p/pharo/issues/detail?id=3583 When I try to load the cs in order I get an error.... if I drop the file and ask the code browser. So I drop the file and loaded as new cs, so this means that we will have yet another bug in two versions.... So I sugges that we stop. systemCategoryListIndex: anInteger "Set the selected system category index to be anInteger. Update all other selections to be deselected." self textMorph beStyled. does not understand beStyled. I integrated the change in 12334 and now if there is a bug. You should provide a fix and before try a lot of behavior. This bug will not be a showstopper I imagine.

Feb. 10, 2011

Re: [Pharo-project] Issue 3583 in pharo: Shout should only be active in code panes

by pharo＠googlecode.com

Comment #39 on issue 3583 by stephane...(a)gmail.com: Shout should only be active in code panes http://code.google.com/p/pharo/issues/detail?id=3583 Since I have to cherrypick the changes and I do not know them... I will not do it using the slice. I will try with the cs but it fails then somebody should provide us a slice loading only the changes in 1.2.

Feb. 10, 2011

Re: [Pharo-project] [COTDC] 7 - CodeAnnotationMorph

by Noury Bouraqadi

Ok, let's join the party ;-) I am a "lightweight" Morph. I display annotations for some code holder (such as a browser). Noury Le 10 fÃ©vr. 2011 Ã 18:14, laurent laffont a Ã©crit : > Today: CodeAnnotationMorph > > > Comment Of The Day Contest - One Day One Comment > Rules: > #1: Each day a not commented class is elected. Each day the best comment will be integrated with name of the author(s). > #2: If you cannot comment it, deprecate it. > Results: http://code.google.com/p/pharo/wiki/CommentOfTheDayContest > > Laurent Noury Bouraqadi http://car.mines-douai.fr/noury -- -6th National Conference on âControl Architecture of Robotsâ 24-25 mai 2011, Grenoble area, France http://car2011.inrialpes.fr/ -19th ESUG International Smalltalk Conference 22-26 August 2011, Edinburgh, UK http://www.esug.org/Conferences/2011

Feb. 10, 2011

Re: [Pharo-project] Issue 3583 in pharo: Shout should only be active in code panes

by pharo＠googlecode.com

Comment #38 on issue 3583 by stephane...(a)gmail.com: Shout should only be active in code panes http://code.google.com/p/pharo/issues/detail?id=3583 I'm trying a last time for today now.

Feb. 10, 2011

Re: [Pharo-project] Issue 3583 in pharo: Shout should only be active in code panes

by pharo＠googlecode.com

Comment #37 on issue 3583 by stephane...(a)gmail.com: Shout should only be active in code panes http://code.google.com/p/pharo/issues/detail?id=3583 When I load this slice into 1.2, workspace does not open anymore!!! So doru if you want this fix in 1.2, help because I cannot spend time on it now. The slice of ben worked well in 1.3 but probably 1.2 and 1.3 are diverging.

Feb. 10, 2011

Re: [Pharo-project] Issue 3583 in pharo: Shout should only be active in code panes

by pharo＠googlecode.com

Comment #36 on issue 3583 by stephane...(a)gmail.com: Shout should only be active in code panes http://code.google.com/p/pharo/issues/detail?id=3583 in 12334

Feb. 10, 2011

[Pharo-project] [update 1.3] #13051

by StÃ©phane Ducasse

13051 ----- - Issue 3583: Shout should only be active in code panes. Thanks benjamin van ryseghem. - Issue 3689: Transcript preference for #characterLimit.

Feb. 10, 2011