October 2012 - Pharo-dev - lists.pharo.org

Re: [Pharo-project] Need more consistent #lines

by Levente Uzonyi

On Sun, 14 Oct 2012, Igor Stasenko wrote: > 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!! The above two examples are the same. ;) > > 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. Read this before you do anything (wrong): "There is also some confusion whether newlines terminate or separate lines. If a newline is considered a separator, there will be no newline after the last line of a file. The general convention on most systems is to add a newline even after the last line, i.e. to treat newline as a line terminator.[citation needed] Some programs have problems processing the last line of a file if it is not newline terminated. Conversely, programs that expect newline to be used as a separator will interpret a final newline as starting a new (empty) line." From: http://en.wikipedia.org/wiki/Newline Levente > > -- > Best regards, > Igor Stasenko. > >

Oct. 14, 2012

[Pharo-project] [Issue Tracker] Help needed

by Marcus Denker

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

Oct. 14, 2012

Re: [Pharo-project] EncryptedMultiDisplayScanner, are you serious?

by StÃ©phane Ducasse

Me too but less and less :) On Oct 14, 2012, at 10:52 AM, phil(a)highoctane.be wrote: > I am always feeling like an archaelogist when looking at these things... > > Phil > > 2012/10/14 StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> > > On Oct 14, 2012, at 1:22 AM, Igor Stasenko wrote: > > > An EncryptedMultiDisplayScanner is a MultiDisplayScanner displaying > > stars instead of characters (for password by example) > > > > Wow... this is soooo overkill! > > Indeed I was not aware of that system. > > > > > 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.. > > Yes. > > > > > -- > > Best regards, > > Igor Stasenko. > > > > >

Oct. 14, 2012