- Pharo-dev - lists.pharo.org

[Pharo-project] Issue 3579 in pharo: "declare temp" adds the variable twice

by pharo＠googlecode.com

Status: Accepted Owner: laurent....(a)gmail.com Labels: Milestone-1.2-DevImage New issue 3579 by laurent....(a)gmail.com: "declare temp" adds the variable twice http://code.google.com/p/pharo/issues/detail?id=3579 Pharo image: 1.2 Pharo core version: 12303 Virtual machine used: Squeak VM Cog 32 5.8b12 Class browser used if applicable: OBSystemBrowserAdaptor Steps to reproduce: Open the browser, select a class and add a method foo bar := 2 Accept, "Unknown variable: bar please correct" dialog pops up. Select "declare temp". Now you have: foo | bar | | bar | "<- ????????" bar := 2 Works in PharoCore 1.2, so the problem may be related to OBSystemBrowserAdaptor

Jan. 23, 2011

[Pharo-project] How to browse users of a Trait

by laurent laffont

Hi, in the browser, when selecting a Trait -> right-click -> browse references the References browser is empty. Is it supposed to work or there's an another way to browse users of a Trait ? Laurent Laffont Pharo Smalltalk Screencasts: http://www.pharocasts.com/ Blog: http://magaloma.blogspot.com/

Jan. 23, 2011

Re: [Pharo-project] default styler is shout

by Marcus Denker

Hi, We need the imperfect, intermediate solution that is good enough for people to live with in 1.2. On Jan 22, 2011, at 4:25 PM, Tudor Girba wrote: > Hi, > > In the latest Morphic version, the default styler of the PluggableTextMorph is given by: > useDefaultStyler > "This should be changed to a proper registry but as long as there is only shout this will do" > > Smalltalk globals > at: #SHTextStylerST80 > ifPresent: [ :stylerClass | self styler: (stylerClass new view: self) ] > ifAbsent: [ self styler: ( NullTextStyler new view: self) ] > > Thus, if Shout is loaded, you will get it in all text morphs by default. Given that TextMorph should be general and be used in all sorts of contexts, the default behavior should be the original: > > useDefaultStyler > "This should be changed to a proper registry but as long as there is only shout this will do" > > self styler: (NullTextStyler new view: self; yourself). > > > What do you say? > > Cheers, > Doru > > -- > www.tudorgirba.com > > "We are all great at making mistakes." > > > > > > > > -- Marcus Denker -- http://www.marcusdenker.de INRIA Lille -- Nord Europe. Team RMoD.

Jan. 23, 2011

Re: [Pharo-project] default styler is shout

by StÃ©phane Ducasse

This seems ok for me. When others reply open a ticket + changes and we will integrate that. On Jan 22, 2011, at 4:25 PM, Tudor Girba wrote: > Hi, > > In the latest Morphic version, the default styler of the PluggableTextMorph is given by: > useDefaultStyler > "This should be changed to a proper registry but as long as there is only shout this will do" > > Smalltalk globals > at: #SHTextStylerST80 > ifPresent: [ :stylerClass | self styler: (stylerClass new view: self) ] > ifAbsent: [ self styler: ( NullTextStyler new view: self) ] > > Thus, if Shout is loaded, you will get it in all text morphs by default. Given that TextMorph should be general and be used in all sorts of contexts, the default behavior should be the original: > > useDefaultStyler > "This should be changed to a proper registry but as long as there is only shout this will do" > > self styler: (NullTextStyler new view: self; yourself). > > > What do you say? > > Cheers, > Doru > > -- > www.tudorgirba.com > > "We are all great at making mistakes." > > > > > > > >

Jan. 23, 2011

Re: [Pharo-project] Graphics with Anti-Aliasing

by StÃ©phane Ducasse

> All, > > does somebody has a pointer to a graphics lib/framework/engine for Pharo which works with Anti-Aliasing. > > My first tests with Balloon2D were disappointing (maybe I'm doing something wrong). But even setting aaLevel does not seem to bring any result. I.e. the line drawing code falls back to superclass code which simply draws the same jagged lines like always. > > Any pointers? did you check a bit in CUIS or Squeak because I know that there were a couple a little fixes. Now I do not know if this fix your problems. What we would like to do probably over the summer, is to propose a Cairo and openVG back end via a common api: rome like. But this is not for tomorrow, just something we want to have. > > CU, > > Udo > >

Jan. 23, 2011

Re: [Pharo-project] Graphics with Anti-Aliasing

by Guillermo Polito

I cc'ed Carla. I'm sure she should know something about this :) On Sat, Jan 22, 2011 at 11:37 AM, Udo Schneider < udo.schneider(a)homeaddress.de> wrote: > All, > > does somebody has a pointer to a graphics lib/framework/engine for Pharo > which works with Anti-Aliasing. > > My first tests with Balloon2D were disappointing (maybe I'm doing something > wrong). But even setting aaLevel does not seem to bring any result. I.e. the > line drawing code falls back to superclass code which simply draws the same > jagged lines like always. > > Any pointers? > > CU, > > Udo > > >

Jan. 23, 2011

Re: [Pharo-project] default styler is shout

by Guillermo Polito

Anyways, I'm looking that PluggableTextMorph>>textMorphClass "Answer the class used to create the receiver's textMorph" ^TextMorphForEditView and TextMorphForEditView>>editorClass ^ SmalltalkEditor So it's what I suggested needs a lot of work more... On Sat, Jan 22, 2011 at 10:58 PM, Guillermo Polito < guillermopolito(a)gmail.com> wrote: > Ufa,... > > Editor>>styler > ^NullTextStyler new > > SmalltalkEditor>>styler > ^... > > Guille > > > On Sat, Jan 22, 2011 at 10:54 PM, Guillermo Polito < > guillermopolito(a)gmail.com> wrote: > >> Why not delegate it in the used Editor ? SmalltalkEditor should use shout >> while the other editors should use the NullTextStyler. Maybe something like >> this: >> >> PluggableTextMorph>>useDefaultStyler >> self styler: textMorph editor styler >> >> Or better: >> >> PluggableTextMorph>>useDefaultStyler >> self styler: textMorph styler >> >> And then >> >> Editor>>styler >> >> >> >> On Sat, Jan 22, 2011 at 12:25 PM, Tudor Girba <tudor.girba(a)gmail.com>wrote: >> >>> Hi, >>> >>> In the latest Morphic version, the default styler of the >>> PluggableTextMorph is given by: >>> useDefaultStyler >>> "This should be changed to a proper registry but as long as there >>> is only shout this will do" >>> >>> Smalltalk globals >>> at: #SHTextStylerST80 >>> ifPresent: [ :stylerClass | self styler: (stylerClass new >>> view: self) ] >>> ifAbsent: [ self styler: ( NullTextStyler new view: self) >>> ] >>> >>> Thus, if Shout is loaded, you will get it in all text morphs by default. >>> Given that TextMorph should be general and be used in all sorts of contexts, >>> the default behavior should be the original: >>> >>> useDefaultStyler >>> "This should be changed to a proper registry but as long as there >>> is only shout this will do" >>> >>> self styler: (NullTextStyler new view: self; yourself). >>> >>> >>> What do you say? >>> >>> Cheers, >>> Doru >>> >>> -- >>> www.tudorgirba.com >>> >>> "We are all great at making mistakes." >>> >>> >>> >>> >>> >>> >>> >>> >>> >> >

Jan. 23, 2011

Re: [Pharo-project] default styler is shout

by Guillermo Polito

Ufa,... Editor>>styler ^NullTextStyler new SmalltalkEditor>>styler ^... Guille On Sat, Jan 22, 2011 at 10:54 PM, Guillermo Polito < guillermopolito(a)gmail.com> wrote: > Why not delegate it in the used Editor ? SmalltalkEditor should use shout > while the other editors should use the NullTextStyler. Maybe something like > this: > > PluggableTextMorph>>useDefaultStyler > self styler: textMorph editor styler > > Or better: > > PluggableTextMorph>>useDefaultStyler > self styler: textMorph styler > > And then > > Editor>>styler > > > > On Sat, Jan 22, 2011 at 12:25 PM, Tudor Girba <tudor.girba(a)gmail.com>wrote: > >> Hi, >> >> In the latest Morphic version, the default styler of the >> PluggableTextMorph is given by: >> useDefaultStyler >> "This should be changed to a proper registry but as long as there >> is only shout this will do" >> >> Smalltalk globals >> at: #SHTextStylerST80 >> ifPresent: [ :stylerClass | self styler: (stylerClass new >> view: self) ] >> ifAbsent: [ self styler: ( NullTextStyler new view: self) ] >> >> Thus, if Shout is loaded, you will get it in all text morphs by default. >> Given that TextMorph should be general and be used in all sorts of contexts, >> the default behavior should be the original: >> >> useDefaultStyler >> "This should be changed to a proper registry but as long as there >> is only shout this will do" >> >> self styler: (NullTextStyler new view: self; yourself). >> >> >> What do you say? >> >> Cheers, >> Doru >> >> -- >> www.tudorgirba.com >> >> "We are all great at making mistakes." >> >> >> >> >> >> >> >> >> >

Jan. 23, 2011

Re: [Pharo-project] default styler is shout

by Guillermo Polito

Why not delegate it in the used Editor ? SmalltalkEditor should use shout while the other editors should use the NullTextStyler. Maybe something like this: PluggableTextMorph>>useDefaultStyler self styler: textMorph editor styler Or better: PluggableTextMorph>>useDefaultStyler self styler: textMorph styler And then Editor>>styler On Sat, Jan 22, 2011 at 12:25 PM, Tudor Girba <tudor.girba(a)gmail.com> wrote: > Hi, > > In the latest Morphic version, the default styler of the PluggableTextMorph > is given by: > useDefaultStyler > "This should be changed to a proper registry but as long as there is > only shout this will do" > > Smalltalk globals > at: #SHTextStylerST80 > ifPresent: [ :stylerClass | self styler: (stylerClass new > view: self) ] > ifAbsent: [ self styler: ( NullTextStyler new view: self) ] > > Thus, if Shout is loaded, you will get it in all text morphs by default. > Given that TextMorph should be general and be used in all sorts of contexts, > the default behavior should be the original: > > useDefaultStyler > "This should be changed to a proper registry but as long as there is > only shout this will do" > > self styler: (NullTextStyler new view: self; yourself). > > > What do you say? > > Cheers, > Doru > > -- > www.tudorgirba.com > > "We are all great at making mistakes." > > > > > > > > >

Jan. 23, 2011

Re: [Pharo-project] TODO 1.2

by Guillermo Polito

>From the stacktrace, the build is broken because MetacelloVersionNumberTestCase>>testVersion10 is sending a sortBy: message, which is deprecated in pharo. Dale, how can that be fixed? :) On Fri, Jan 21, 2011 at 4:26 AM, Marcus Denker <marcus.denker(a)inria.fr>wrote: > > 1.2 Core: > Bugs: > http://code.google.com/p/pharo/issues/list?can=2&q=milestone=1.2 > Tests: > https://pharo-ic.lille.inria.fr/hudson/job/Pharo%20Core%201.2/lastCompleted… > > 1.2 Full: > Bugs: > http://code.google.com/p/pharo/issues/list?can=2&q=milestone=1.2-DevImage > Tests: N/A, as the buld is broken: > https://pharo-ic.lille.inria.fr/hudson/job/Pharo%201.2/75/console > > There will be *no release of 1.2* if those things are not fixed. If you are > interested, in some way or another, > to have a 1.2 release, you will get it if you help fixing the last bugs. > (hint, hint). > > Marcus > > -- > Marcus Denker -- http://www.marcusdenker.de > INRIA Lille -- Nord Europe. Team RMoD. > > >

Jan. 23, 2011