- Pharo-dev - lists.pharo.org

[Pharo-project] Idea for finding bugs/profiling...
by StÃ©phane Ducasse Oct. 15, 2012

Oct. 15, 2012

Hi alex would it not be possible to run and trace automatically the same tests in 1.4 and 2.0 and see the delta? because this would help us a lot of understand the differences. For example, I trying to fix the Gofer unload behavior and I'm stepping step by step in 1.4 and 2.0. Having some support would really help. Stef

2 3

[Pharo-project] [Issue Tracker] Issues that need a human review
by Marcus Denker Oct. 15, 2012

Oct. 15, 2012

Issues tagged "HumanReviewNeeded" Just 9 open! http://code.google.com/p/pharo/issues/list?can=2&q=status%3AHumanReviewNeed… These need to be checked. Look at the code. Test it a bit. Then decide: What still needs to be done? Or maybe it is already ready to be added? Marcus -- Marcus Denker -- http://marcusdenker.de

1 0

[Pharo-project] [Issue Tracker] Currently failing tests
by Marcus Denker Oct. 15, 2012

Oct. 15, 2012

For both 1.4 and 2.0: 7 open issues: http://code.google.com/p/pharo/issues/list?can=2&q=Status%3DFailingTest -- Marcus Denker -- http://marcusdenker.de

1 0

[Pharo-project] [update 2.0] #20341
by Marcus Denker Oct. 15, 2012

Oct. 15, 2012

20341 ----- Issue 6804: JobProgressMorph has two undeclared iVars http://code.google.com/p/pharo/issues/detail?id=6804 -- Marcus Denker -- http://marcusdenker.de

1 0

[Pharo-project] EncryptedMultiDisplayScanner, are you serious?
by Igor Stasenko Oct. 14, 2012

Oct. 14, 2012

An EncryptedMultiDisplayScanner is a MultiDisplayScanner displaying stars instead of characters (for password by example) Wow... this is soooo overkill! Look at the amount of extra code we have just to simply displaying stupid stars ... ************ See the: EncryptedTextMorphForFieldView>>drawOn: ... aCanvas encryptedParagraph: self paragraph bounds: fauxBounds color: color. ehh?.. Since when canvas (a tool for drawing graphic primitives and text) needs to know anything like that? I'm not sure if there could be better/simpler solution (considering that we don't have a simple line editor and need to go over overcomplicated text->composer->scanner->displayscanner chain to be able to edit even single string.. but that's really, really stupid to penetrate multiple layers of responsibility just to display stars instead of characters... What if i would like to display '%' instead of chars, should i also go and repeat same way?? We should get rid of this thing.. -- Best regards, Igor Stasenko.

5 8

[Pharo-project] Spec Documentation
by Sean P. DeNigris Oct. 14, 2012

Oct. 14, 2012

It seems like there have been many recent improvements to Spec. What's the best way to learn the latest features? Is there an updated doc? Examples of latest features? Thanks, Sean -- View this message in context: http://forum.world.st/Spec-Documentation-tp4651169.html Sent from the Pharo Smalltalk mailing list archive at Nabble.com.

2 2

[Pharo-project] Article On Modern Smalltalk
by blake Oct. 14, 2012

Oct. 14, 2012

Hello, folks-- I've been commissioned to write an article on modern Smalltalk and wanted to solicit feedback on what people thought the most interesting and useful aspects to cover would be. Obviously I wanted to talk about Squeak, Pharo, Amber, and at least touch on Lively, and talk about the commercial offerings (Dolphin, VAST, VW), and then there's Seaside and GLORP and Spoon and Cuis and...etc. etc. etc. Since it's not a book, I can't possibly cover everything, so I want to hit the highlights, and I'm trying to avoid being overly insular (e.g., only talking about what are the highlights for me). Any and all comments welcome. ===Blake===

3 3

[Pharo-project] Need more consistent #lines
by Igor Stasenko Oct. 14, 2012

Oct. 14, 2012

A total number of lines in string should be: one + number of line separators found. Explanation: a 'String cr/ crlf' stands for 'line separator'. By definition, a separator, is thing which separates two others.. i mean, there is no way how you can use 'separator' term without having TWO things which it separates. The problem is that #lines does not follows common sense: (String empty, String cr, String empty) lines size 1 so, our line separator "separates" one thing :) It means that we overload the definition: - a line separator separates two lines unless it is at the end of text. But think , how dearly this 'unless' will costs in terms of implementation! Everywhere where you may need to handle text, you should put this extra rule, and if you forget it, you will be punished.. Here what various #lines produces: ( 'A' ) lines size 1 ( 'A', String cr ) lines size 1 !!oops!!. ( String cr, 'A' ) lines size 2 ( 'A', String cr, 'A' ) lines size 2 ( 'A', String cr, 'A', String cr ) lines size 2 ( 'A', String cr, 'A', String cr ) lines size 2 !!oops!! You may think this is fine, but lets look at the problem from another angle: self assert: (string1, String cr, string2) lineCount >= 2 The 'string1, String cr, string2' above is an insertion operation. We inserting a line separator between two arbitrary strings. Now, in what universe the total number of lines may not get increased after such insertion? So, it is simply inconsistent. Or maybe you happy to put extra code everywhere where you handling text, to do a special handling if last character is line separator? But we can avoid all that mess it in a first place, if we obey to common sense. -- Best regards, Igor Stasenko.

5 5

[Pharo-project] [Issue Tracker] Help needed
by Marcus Denker Oct. 14, 2012

Oct. 14, 2012

Hi, We have right now - 160 issues tagged "2.0". http://code.google.com/p/pharo/issues/list?can=2&q=milestone%3D2.0&colspec=… We should check for each those: Is this a show stopping problem? Or just something "nice to have"? If it is not essential, the tag "2.0" should be removed. This way we have a short list of priority issues to look at. - There are 435 open issues in total http://code.google.com/p/pharo/issues/list?can=2&q=&colspec=ID+Type+Status+… Especially for very old issues, we should ask ourselves if it makes sense to keep them open. Here peopel should look especially at their own submissions and close the ones that have been fixed, that are not relavant anymore or that are just not important. In addition, issues that are pure wishes of big things of the style "it would be nice to replace morpic" should go on the wishlist, not the bugstracker: http://code.google.com/p/pharo/wiki/IdeasToImplement Marcus -- Marcus Denker -- http://marcusdenker.de

1 0

[Pharo-project] [update 2.0] #20340
by Marcus Denker Oct. 14, 2012

Oct. 14, 2012

20340 ----- Issue 6806: More cleanups related to ChangeSorters http://code.google.com/p/pharo/issues/detail?id=6806 -- Marcus Denker -- http://marcusdenker.de

1 0