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

[Pharo-project] Issue 3475 in pharo: Finder insensitive selector/class researches
by pharo＠googlecode.com Dec. 22, 2010

Dec. 22, 2010

Status: Fixed Owner: Benjamin.VanRyseghem.Pharo New issue 3475 by Benjamin.VanRyseghem.Pharo: Finder insensitive selector/class researches http://code.google.com/p/pharo/issues/detail?id=3475 Now, the selector and class researches in Finder are case insensitive. Posted in PharoTaskForces and PharoInbox

1 1

[Pharo-project] Issue 3476 in pharo: ToolsTest.MessageTally.MessageTallyTest.testTallySends is now green
by pharo＠googlecode.com Dec. 22, 2010

Dec. 22, 2010

Status: Accepted Owner: alexandre.bergel CC: marcus.denker, stephane.ducasse Labels: Difficulty-Easy Milestone-1.2 New issue 3476 by alexandre.bergel: ToolsTest.MessageTally.MessageTallyTest.testTallySends is now green http://code.google.com/p/pharo/issues/detail?id=3476 In a 12284, testTallySends does yellow because one of the method invoked by printString changed. The test has been updated. ToolsTest-AlexandreBergel.denker.13 in the inbox

1 2

Re: [Pharo-project] Issue 2232 in pharo: digitValue speed up part one and two.
by pharo＠googlecode.com Dec. 22, 2010

Dec. 22, 2010

Comment #8 on issue 2232 by marcus.denker: digitValue speed up part one and two. http://code.google.com/p/pharo/issues/detail?id=2232 Next Action: -> What exactly means "first part is in?" -> Define what is left to do.

1 2

[Pharo-project] [TODO] 1.2 Core + Full
by Marcus Denker Dec. 22, 2010

Dec. 22, 2010

For 1.2 to to be released, we need to a) get all tests green. There are right now 9 failing tests in Core and 9 additional one in the full image. 9 of 7915 tests fail: https://pharo-ic.lille.inria.fr/hudson/job/Pharo%20Core%201.2/lastCompleted… 18 of 10284 tests fail: https://pharo-ic.lille.inria.fr/hudson/job/Pharo%201.2/lastCompletedBuild/t… some of those are test-server artefacts that only fail on the testserver. b) Bug Tracker. Here the issues need to be either resolved or decided to be not show-stoppers (there will be a 1.3 release! So somehting that is already not in 1.1, why do we need in in 1.2? A release is just a usable snapshot of an on-going process) 23 reports are tagged as 1.2: http://code.google.com/p/pharo/issues/list?can=2&q=milestone=1.2&colspec=ID… 8 reports are tagged as 1.2 for the full image? http://code.google.com/p/pharo/issues/list?can=2&q=milestone=1.2-DevImage&c… All failing tests do have bug-tracker entries. Marcus -- Marcus Denker -- http://www.marcusdenker.de INRIA Lille -- Nord Europe. Team RMoD.

6 6

[Pharo-project] about copy in the bug tracker
by StÃ©phane Ducasse Dec. 22, 2010

Dec. 22, 2010

Hi guys am i the only one having problem with copy (control-C when on the bug tracker)? I hate when it create a new entry. Stef

4 5

[Pharo-project] PharoCore #12884
by Sven Van Caekenberghe Dec. 22, 2010

Dec. 22, 2010

Hi, I just updated my 1.2 core to #12884 with 3 updates and my MC repos are gone from my packages, only the standard repos remain. Maybe this is a sign of something that went wrong. Sven

2 2

[Pharo-project] Issue 3453 in pharo: Primitive failed on ByteString>>copyFrom:To:
by pharo＠googlecode.com Dec. 22, 2010

Dec. 22, 2010

Status: Accepted Owner: laurent.laffont New issue 3453 by laurent.laffont: Primitive failed on ByteString>>copyFrom:To: http://code.google.com/p/pharo/issues/detail?id=3453 Pharo image: 1.2 beta 2 Pharo core version: 12281 Steps to reproduce: 1. ProfStef go. 2. put cursor after the dot of ProfStef next. CMD-D 3. idem in next screen BOOM - primitiveFailed on ByteString>>copyFrom:To: because start > stop (Fix to follow)

1 2

[Pharo-project] Issue 3459 in pharo: includesSubstring: aString caseSensitive: caseSensitive / includesSubString:
by pharo＠googlecode.com Dec. 22, 2010

Dec. 22, 2010

Status: Accepted Owner: Benjamin.VanRyseghem.Pharo New issue 3459 by Benjamin.VanRyseghem.Pharo: includesSubstring: aString caseSensitive: caseSensitive / includesSubString: http://code.google.com/p/pharo/issues/detail?id=3459 Maybe one of this two methods should be changed in order to start as the other one (includesSubstring: aString caseSensitive: caseSensitive have only 14 senders ^^)

1 3

[Pharo-project] Citezen vs. Google Scholar bug??
by Schwab,Wilhelm K Dec. 22, 2010

Dec. 22, 2010

Stef, I *think* Google Scholar is in the wrong here, but I'll mention it just in case. I've tried to paste the controversial entry below, but in case it gets corrupted in transfer, it is the third hit on Google Scholar with surface tension inclined tube stability Dumitrescu @article{couÃ«t1987effects, title={{The effects of surface tension and tube inclination on a two-dimensional rising bubble}}, author={Cou{\\"e}t, B. and Strumolo, G.S.}, journal={Journal of Fluid Mechanics}, volume={184}, pages={1--14}, issn={0022-1120}, year={1987}, publisher={Cambridge Univ Press} } The BibTeX source above is from GS' "Import into BibTeX" feature. Citezen didn't like it. I am assuming that the problem is that accented e in the key. Changing it to a "plain" e allowed my code to proceed. The real question is whether extended characters are legal in the key? If not, then Citezen is correct to complain. Bill

2 1

[Pharo-project] running osprocess
by Alexandre Bergel Dec. 22, 2010

Dec. 22, 2010

Hi! I wasn't able to run OSProcess on Mac and on Linux. I get the error "process accessor module not available". Doru mentioned it on Sep 23. Is the situation the same? Cheers, Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

6 8