- Pharo-dev - lists.pharo.org

[Pharo-project] Set with nil is fixed and waiting for a nice reviewer
by StÃ©phane Ducasse March 17, 2010

March 17, 2010

during the sprint niko schwarz and oscar nierstrasz fixed the Set in nil entry. Thanks. http://code.google.com/p/pharo/issues/detail?id=1907 Now does somebody with knowledge could have a look because this is a sensitive part of the system and more eyes does not hurt. Stef

5 9

[Pharo-project] SystemDictionary and SmalltalkImage problem
by Mariano Martinez Peck March 17, 2010

March 17, 2010

Hi folks. I took a clean PharoCore-1.1-11268-UNSTABLE and I did a system update to 11276. I don't know why but it seems I have a lot of duplicated methods between those two classes. I don't know exactly all these changes that has been done last days in those classes. But, take for example the category "shrinking" of both classes (SystemDictionary and SmalltalkImage) and you will notice both have the same methods implemented the same way. Maybe there was a problem with MC or system update ? Thanks Mariano

2 1

[Pharo-project] [update 1.1] #11276
by StÃ©phane Ducasse March 17, 2010

March 17, 2010

11276 ----- - Issue 2157: Squeak font rendering cleanup. Thanks nicolas Stef

1 0

[Pharo-project] BTree packaging
by Chris Muller March 17, 2010

March 17, 2010

Hi Lukas, are there plans to include BTree standard in the Pharo image? I was just wondering whether that was why the package is named Collections-BTree, or if you would renaming it to simply BTree. It's mostly intangible that I have a dirty Collections package in many image (because I often use BTree). Except that, I do find myself sometimes checking in Monticello, "did I change something in Collections? Oh, no, it's just BTree.. Or is it? Let me scroll this list to be sure....." :) Kind of inconvenient, kind of inconsistent for an external package. What do you think?

4 6

[Pharo-project] squeaksource is down....
by StÃ©phane Ducasse March 17, 2010

March 17, 2010

4 9

[Pharo-project] Case statement and lazy comparison in Pharo
by nullPointer March 16, 2010

March 16, 2010

Well, perhaps is a theme worked in another times but... is possible for Pharo have a basic Case or elseIf statement? I know is easy create you own structure control, but not is more useful have a "standard" for everybody? IÂ´m tired of write code like that... (self currentRow == sortedRows last and: [ self currentCell isNil ]) ifTrue: [ self navigationKey: event ] ifFalse: [ (self currentRow notNil and: [ self currentCell isNil ]) ifTrue: [ self setCurrentRowToNext. ] ifFalse: [ (self currentRow notNil and: [ self currentCell notNil ]) ifTrue: [ self setCurrentCellToNext. self currentCell notNil ifTrue: [ self currentCell performKeyFocus: event inCellBounds: (self pvtGetCellBounds: self currentCell). ]. ]. ]. ]. Write code with that format is pathetical :( Is valid too have a "and" and "or" lazy? Exists a not lazy with #& and #| , but could exists an #&& and #|| . Is more easy... value1 == value2 and:[ <condition> ] and: [<condition>] ...... or value1 == value2 && <condition> && <condition> ......... ??? Well, perhaps is a stupid question but I miss a more complete way for write code. If in Smalltalk is possible do easy that and include it in "core" why not do it? Is a reasonable desire :) Regards -- View this message in context: http://n4.nabble.com/Case-statement-and-lazy-comparison-in-Pharo-tp1594080p… Sent from the Pharo Smalltalk mailing list archive at Nabble.com.

6 5

[Pharo-project] [enh] Cleaning of and test for MessageTally
by Alexandre Bergel March 16, 2010

March 16, 2010

Waiting in PharoInbox. This fix has been developed in a 11271. SLICE-MessageTallyCleaningAndTest-Alexandre_Bergel.1 This slices comprises an update for two packages, Tools and ToolsTest. The new version of Tools clean MessageTally. A user of MessageTally may now decide whether he wants to close the tally. Although it is convenient to close it (in order to not keep a reference of the compiled method and the class), this behavior is not always wished. Especially when test have to be written! The user has now the option to not open the result window. ToolsTest contains few and simple tests. Cheers, Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

2 7

[Pharo-project] About long tests.
by stephane ducasse March 16, 2010

March 16, 2010

Hi jorge did you publish the cleans for the tests you did during the sprint? Thanks Stef

5 9

[Pharo-project] Fixed strange coloring in TestRunner
by Lukas Renggli March 16, 2010

March 16, 2010

Name: SUnitGUI-LukasRenggli.61 Author: lr Time: 16 March 2010, 7:42:35 pm UUID: afa7782a-a37f-4607-8d44-6d03d0f847d6 Ancestors: SUnitGUI-StephaneDucasse.60 - fixed priority of coloring test result: if there are errors then red else if there are failures then yellow else -> green -- Lukas Renggli http://www.lukas-renggli.ch

2 1

[Pharo-project] What is the best way to...
by Hernan Wilkinson March 16, 2010

March 16, 2010

generate a document with the source code of a package? We will use pharo at the university and I want to find an easy way for the students to print out the source code of their work. Thanks. Hernan.

5 7