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

Re: [Pharo-project] Spell check test cases

by Stan Shepherd

Hi Lukas, did you get a chance to look at this? Refactoring-Spelling-Tests-StanShepherd.7.mcz in http://www.squeaksource.com/RBBugFixes/ is the present version of the tests. They will still need the tweaks in your parser or normalizer to run green. ...Stan -- View this message in context: http://n2.nabble.com/Spell-check-test-cases-tp4288633p4434232.html Sent from the Pharo Smalltalk mailing list archive at Nabble.com.

Jan. 21, 2010

Re: [Pharo-project] O2: tester wanted!

by Adrian Lienhard

Hi David, in my PharoCore-1.0-10505 image I had #testSmartGroupSwitch that failed and #testExtensionNodes and #testStyling that errored. Cheers, Adrian On Jan 21, 2010, at 16:09 , David RÃ¶thlisberger wrote: > Hi Adrian, > >> However, there are 6 undeclared classes referenced in the code. > > ok, I fixed these undeclared references. > >> Also 2 tests have errors and one fails. > > Which tests fail? I only got one error in a test which I fixed now. > > Cheers, > David > > >> >> On Jan 19, 2010, at 23:11 , Mariano Martinez Peck wrote: >> >>> On Tue, Jan 19, 2010 at 11:03 PM, Alexandre Bergel < >>> alexandre.bergel(a)inria.fr> wrote: >>> >>>> Dear All, >>>> >>>> For people who do not know, O2 is the browser David has implemented in >>>> the last few years. It replaces class-categories on the left-hand side >>>> pane with a list of packages. We are still away from having packages >>>> as real first class entities, but this is a good step toward. Note >>>> that some people find O2 a bit slower than other available code >>>> browsers. >>>> >>>> David and I spent some time on fixing O2. O2 has now no dependencies >>>> to OB anymore. >>>> We would like that people try it and submit bug reports on the google >>>> bug tracker. In a fresh 10505, you can load O2 by evaluating: >>>> >>>> Gofer new squeaksource: 'MetacelloRepository'; package: >>>> 'ConfigurationOfO2'; load. (Smalltalk at: #ConfigurationOfO2) perform: >>>> #loadDefault >>>> >>>> >>> Yes, but be aware that that piece of code load only the core, as you can see >>> here: >>> >>> group: 'default' with: #('Core' ); >>> group: 'Core' with: #( 'OmniBrowser2' 'O2-Standard' 'O2-Morphic' >>> 'O2-Enhancements' ); >>> group: 'Dev' with: #( 'Core' 'O2-Refactory' 'OCForO2' ); >>> >>> >>> As I remember, most of the problems of O2 were sometimes related to the >>> integration to RB. So, if you really want to tests it, please, test it using >>> the RB: >>> >>> ((Smalltalk at: #ConfigurationOfO2) project version: '1.0') load: 'Dev' >>> >>> >>> As I already said to Alexandre and David in private, I will put O2 again in >>> the next image. So, it would be cool if it is tested "completely". >>> >>> >>> >>>> O2 does not need OB whatsoever. O2 loads in a Core (I tried in a >>>> 11165). Before and after loading O2, running OB tests give "548 run, >>>> 547 passes, 1 failures" [*]. >>>> >>>> >>> Yes, if someone can help with that failure would be cool, I have already >>> reported it. >>> >>> >>> >>>> Cheers, >>>> Alexandre >>>> >>>> [*] the test have been loaded using (ConfigurationOfOmniBrowser >>>> project version: '1.1') load: 'Dev Tests' >>>> -- >>>> _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: >>>> Alexandre Bergel http://www.bergel.eu >>>> ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. >>>> >>>> >>>> >>>> >>>> >>>> >>>> _______________________________________________ >>>> 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 >> > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Jan. 21, 2010

Re: [Pharo-project] Some code! (was Re: Date fromString: '6-Jan-10')

by StÃ©phane Ducasse

thanks goran Stef On Jan 21, 2010, at 11:12 AM, GÃ¶ran Krampe wrote: > Hi guys! > > I admit not having tracked this thread in detail BUT attached is a changeset that I dug out from the Squeak beginners list where I posted it waaay back. The added Date class method included below shows what it offers. > > And of course, there are TONS of more cool stuff it could handle, but it is meant to be "smart enough" for a reasonable set of cases. ...And it was an "hour hack" ... :) > > regards, GÃ¶ran > ----------------------------- > > readFrom: inputStream pattern: pattern > "Read a Date from the stream based on the pattern which can include the tokens: > > y = A year with 1-n digits > yy = A year with 2 digits > yyyy = A year with 4 digits > m = A month with 1-n digits > mm = A month with 2 digits > d = A day with 1-n digits > dd = A day with 2 digits > > ...and any other Strings inbetween. Representing $y, $m and $d is done using > \y, \m and \d and slash itself with \\. Simple example patterns: > > 'yyyy-mm-dd' > 'yyyymmdd' > 'yy.mm.dd' > 'y-m-d' > > A year given using only two decimals is considered to be >2000." > > | day month year patternStream char | > patternStream := pattern readStream. > [patternStream atEnd] whileFalse: [ > inputStream atEnd ifTrue: [^nil]. > char := patternStream next. > char = $\ > ifTrue: [inputStream next = patternStream next ifFalse: [^nil]] > ifFalse: [ > char = $y > ifTrue: [ > (patternStream nextMatchAll: 'yyy') > ifTrue: [year := (inputStream next: 4) asInteger] > ifFalse: [ > (patternStream peekFor: $y) > ifTrue: [ > year := (inputStream next: 2) asInteger] > ifFalse: [ > year := Integer readFrom: inputStream]]] > ifFalse: [ > char = $m > ifTrue: [ > (patternStream peekFor: $m) > ifTrue: [ > month := (inputStream next: 2) asInteger] > ifFalse: [ > month := Integer readFrom: inputStream]] > ifFalse: [ > char = $d > ifTrue: [ > (patternStream peekFor: $d) > ifTrue: [ > day := (inputStream next: 2) asInteger] > ifFalse: [ > day := Integer readFrom: inputStream]] > ifFalse: [ > inputStream next = char ifFalse: [^nil]]]]]]. > (year isNil | month isNil | day isNil) ifTrue: [^nil]. > ^self year: year month: month day: day! ! > <DateReadFromPattern.3.cs.gz>_______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Jan. 21, 2010

Re: [Pharo-project] Monticello remove methods

by Stan Shepherd

Merge appears to have the same result. It's at http://www.squeaksource.com/OBO2Merge ...Stan -- View this message in context: http://n2.nabble.com/Monticello-remove-methods-tp4433742p4434180.html Sent from the Pharo Smalltalk mailing list archive at Nabble.com.

Jan. 21, 2010

Re: [Pharo-project] O2: tester wanted!

by David RÃ¶thlisberger

Hi Adrian, > However, there are 6 undeclared classes referenced in the code. ok, I fixed these undeclared references. > Also 2 tests have errors and one fails. Which tests fail? I only got one error in a test which I fixed now. Cheers, David > > On Jan 19, 2010, at 23:11 , Mariano Martinez Peck wrote: > >> On Tue, Jan 19, 2010 at 11:03 PM, Alexandre Bergel < >> alexandre.bergel(a)inria.fr> wrote: >> >>> Dear All, >>> >>> For people who do not know, O2 is the browser David has implemented in >>> the last few years. It replaces class-categories on the left-hand side >>> pane with a list of packages. We are still away from having packages >>> as real first class entities, but this is a good step toward. Note >>> that some people find O2 a bit slower than other available code >>> browsers. >>> >>> David and I spent some time on fixing O2. O2 has now no dependencies >>> to OB anymore. >>> We would like that people try it and submit bug reports on the google >>> bug tracker. In a fresh 10505, you can load O2 by evaluating: >>> >>> Gofer new squeaksource: 'MetacelloRepository'; package: >>> 'ConfigurationOfO2'; load. (Smalltalk at: #ConfigurationOfO2) perform: >>> #loadDefault >>> >>> >> Yes, but be aware that that piece of code load only the core, as you can see >> here: >> >> group: 'default' with: #('Core' ); >> group: 'Core' with: #( 'OmniBrowser2' 'O2-Standard' 'O2-Morphic' >> 'O2-Enhancements' ); >> group: 'Dev' with: #( 'Core' 'O2-Refactory' 'OCForO2' ); >> >> >> As I remember, most of the problems of O2 were sometimes related to the >> integration to RB. So, if you really want to tests it, please, test it using >> the RB: >> >> ((Smalltalk at: #ConfigurationOfO2) project version: '1.0') load: 'Dev' >> >> >> As I already said to Alexandre and David in private, I will put O2 again in >> the next image. So, it would be cool if it is tested "completely". >> >> >> >>> O2 does not need OB whatsoever. O2 loads in a Core (I tried in a >>> 11165). Before and after loading O2, running OB tests give "548 run, >>> 547 passes, 1 failures" [*]. >>> >>> >> Yes, if someone can help with that failure would be cool, I have already >> reported it. >> >> >> >>> Cheers, >>> Alexandre >>> >>> [*] the test have been loaded using (ConfigurationOfOmniBrowser >>> project version: '1.1') load: 'Dev Tests' >>> -- >>> _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: >>> Alexandre Bergel http://www.bergel.eu >>> ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. >>> >>> >>> >>> >>> >>> >>> _______________________________________________ >>> 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 >

Jan. 21, 2010

Re: [Pharo-project] Monticello remove methods

by Alexandre Bergel

A merge should help no? Alexandre On 21 Jan 2010, at 11:12, Stan Shepherd wrote: > How do I get the new version to import without the old methods? -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

Jan. 21, 2010

Re: [Pharo-project] [ANN] ConfigurationOfProfStef in MetacelloRepository

by Alexandre Bergel

Thanks, I try to build a dev right now Alexandre On 21 Jan 2010, at 08:56, laurent laffont wrote: > Done. > > Laurent > > > On Thu, Jan 21, 2010 at 11:56 AM, Alexandre Bergel <alexandre(a)bergel.eu > > wrote: > Hi Laurent, > > Could you try to update ConfigurationOfPharo please? > > Cheers, > Alexandre > > > On 21 Jan 2010, at 07:53, laurent laffont wrote: > > > ProfStef is an interactive Smalltalk tutorial. > > > > To load it: > > > > Gofer it > > squeaksource: 'MetacelloRepository'; > > package: 'ConfigurationOfProfStef'; > > load. > > > > ((Smalltalk at: #ConfigurationOfProfStef) project version: '1.0') > > load. > > > > > > Cheers, > > > > Laurent Laffont > > _______________________________________________ > > Pharo-project mailing list > > Pharo-project(a)lists.gforge.inria.fr > > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > > -- > _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: > Alexandre Bergel http://www.bergel.eu > ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > > > > > > > _______________________________________________ > 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 -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

Jan. 21, 2010

Re: [Pharo-project] O2: tester wanted!

by Stan Shepherd

Henrik Sperre Johansen wrote: > > > but the refactoring items I've tried in O2PackageBrowser seem to work :) > > Indeed, nice job. That would remove my reason for sticking to the conventional browser. Just one (no two) tiny UI issues: if you right click a package -> Refactoring scope , -> *package* is greyed out. If you do the same from one of the classes of the package, it works. Am I right in thinking that a method name is italic iff it comes from a trait? Should it also be in a dynamic protocol called traits, or similar, and/or an icon? It shows an icon for override of superclass method, for which there is bubble help text, but there is no comparable way to find out where the trait method comes from. Cheers, ...Stan -- View this message in context: http://n2.nabble.com/O2-tester-wanted-tp4423250p4433917.html Sent from the Pharo Smalltalk mailing list archive at Nabble.com.

Jan. 21, 2010

[Pharo-project] [update 1.1] #11175

by StÃ©phane Ducasse

11175 ----- - preparing buffered file stream: integrating multibyteFileStream from Squeak trunk

Jan. 21, 2010

Re: [Pharo-project] Monticello remove methods

by Stan Shepherd

Sorry, finger trouble there. I have a refactoring as follows: OR2CmdLintCommand subclass: #OR2CmdRefresh instanceVariableNames: '' classVariableNames: '' poolDictionaries: '' category: 'OB-Refactory-Lint' methods: #execute #isEnabled etc becomes: OR2CmdLintCommand subclass: #OR2CmdRefresh uses: TGBCmdRefresh instanceVariableNames: '' classVariableNames: '' poolDictionaries: '' category: 'OBO2Merge' methods: none TGBCmdRefresh (trait) methods: #execute #isEnabled etc When I save to a Monticello repo, and import to a new image, TGBCmdRefresh still has the original methods. They are not in the class in the repository, when browsing that repository. Is this expected behaviour? Is it because of the change of package (and perhaps Issue 1760: Monticello enhancement: avoid removing a method when it does not belong to package anymore)? How do I get the new version to import without the old methods? Thanks, ...Stan -- View this message in context: http://n2.nabble.com/Monticello-remove-methods-tp4433742p4433808.html Sent from the Pharo Smalltalk mailing list archive at Nabble.com.

Jan. 21, 2010