- Pharo-dev - lists.pharo.org

Re: [Pharo-project] Deprecations and Hudson
by Marcus Denker Jan. 24, 2011

Jan. 24, 2011

On Jan 23, 2011, at 10:57 AM, Mariano Martinez Peck wrote: > Hi. With Hudson we want to automatically build images. It can happens that external packages did not yet update their code and that are still using depreacted methods. So, by default we raise an exception. This is good because when the developer see an annoying popup, maybe he fix it ;) > > Now, the problem is that Hudson FAILS if there is a deprecated. So, I suggest changing the hudson dev build script to: > > > Deprecation raiseWarning: false. > Gofer new > squeaksource: 'MetacelloRepository'; > package: 'ConfigurationOfPharo'; > load. > > ((Smalltalk at: #ConfigurationOfPharo) project lastVersion) perform: #silently: with: true; perform: #load. > Deprecation raiseWarning: true. > > > This way, the build image can be always build and then at runtime, the user will see the popups. > > Marcus, please, let me know if you change this becasue I need it to fix a problem with Metacello. done. -- Marcus Denker -- http://www.marcusdenker.de INRIA Lille -- Nord Europe. Team RMoD.

5 6

Re: [Pharo-project] default styler is shout
by Marcus Denker Jan. 24, 2011

Jan. 24, 2011

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.

3 2

Re: [Pharo-project] Pharo Refactoring Tool
by ashubair＠scs.ryerson.ca Jan. 23, 2011

Jan. 23, 2011

Hi all, I'm really more than happy to be one of your super-active and supportive community.. Thank you for your ideas, and I will try my best to keep you updated with any achieved preogress.. Any new ideas are more than welcome! Mr.Ducasse, seems that the thread has been deleted from my inbox by mistake, I'll try to look for it in the archive and I'll get back to you as soon as I find it.. Mr.Peck, thanks for your valuable advice. Thanks all for your time and suggestions, Alia

1 0

[Pharo-project] Deprecations and Hudson
by Mariano Martinez Peck Jan. 23, 2011

Jan. 23, 2011

Hi. With Hudson we want to automatically build images. It can happens that external packages did not yet update their code and that are still using depreacted methods. So, by default we raise an exception. This is good because when the developer see an annoying popup, maybe he fix it ;) Now, the problem is that Hudson FAILS if there is a deprecated. So, I suggest changing the hudson dev build script to: Deprecation raiseWarning: false. Gofer new squeaksource: 'MetacelloRepository'; package: 'ConfigurationOfPharo'; load. ((Smalltalk at: #ConfigurationOfPharo) project lastVersion) perform: #silently: with: true; perform: #load.Deprecation raiseWarning: true. This way, the build image can be always build and then at runtime, the user will see the popups. Marcus, please, let me know if you change this becasue I need it to fix a problem with Metacello. mariano

1 0

[Pharo-project] Issue 3575 in pharo: [Failing Tests] Tests.Release.ReleaseTest.testObsoleteClasses
by pharo＠googlecode.com Jan. 23, 2011

Jan. 23, 2011

Status: Accepted Owner: marcus.d...(a)gmail.com Labels: Milestone-1.1.2 New issue 3575 by marcus.d...(a)gmail.com: [Failing Tests] Tests.Release.ReleaseTest.testObsoleteClasses http://code.google.com/p/pharo/issues/detail?id=3575 Full Build 1.1.1 hudson Tests.Release.ReleaseTest.testObsoleteClasses would be nice to fix that...

1 1

[Pharo-project] [update 1.1] #11418
by Marcus Denker Jan. 23, 2011

Jan. 23, 2011

11418 ----- [Failing Tests] Hudson Full 1.1 ToolsTest.Inspector.WeakSetInspectorTest.testSymbolTableM6812 -- Marcus Denker -- http://www.marcusdenker.de INRIA Lille -- Nord Europe. Team RMoD.

1 0

[Pharo-project] Issue 3577 in pharo: [Failing Tests] Hudson Full 1.1 ToolsTest.Inspector.WeakSetInspectorTest.testSymbolTableM6812
by pharo＠googlecode.com Jan. 23, 2011

Jan. 23, 2011

Status: Accepted Owner: marcus.d...(a)gmail.com Labels: Milestone-1.1.2 New issue 3577 by marcus.d...(a)gmail.com: [Failing Tests] Hudson Full 1.1 ToolsTest.Inspector.WeakSetInspectorTest.testSymbolTableM6812 http://code.google.com/p/pharo/issues/detail?id=3577 ToolsTest.Inspector.WeakSetInspectorTest.testSymbolTableM6812

1 2

[Pharo-project] default styler is shout
by Tudor Girba Jan. 23, 2011

Jan. 23, 2011

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."

3 4

[Pharo-project] TODO 1.2
by Marcus Denker Jan. 23, 2011

Jan. 23, 2011

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.

2 1

[Pharo-project] closeable tabs
by Tudor Girba Jan. 23, 2011

Jan. 23, 2011

Hi, I worked a bit on adding the possibility of closing tabs from a tab group. This is available for the moment in the I refactored the LazyTabGroupMorph from the Glamour repository. It would still be good to delegate a couple of things to the Theme, but other than that I think we could replace the logic from TabGroupMorph. What I did was to introduce a LazyTabPage that can lazily draw the page morph. If you (Alain, Gary?) have time, I could use a code review :). Gofer new squeaksource: 'Glamour'; package: 'ConfigurationOfGlamour'; load. (Smalltalk at: #ConfigurationOfGlamour) perform: #loadDefault Cheers, Doru -- www.tudorgirba.com "In a world where everything is moving ever faster, one might have better chances to win by moving slower."

1 0