July 2015 - Pharo-dev - lists.pharo.org

Re: [Pharo-dev] About nextPutAll: $(

by Igor Stasenko

On 27 July 2015 at 12:23, stepharo <stepharo(a)free.fr> wrote: > May be I raised a not important issue. > > My impression too. :) > Stef > > Le 27/7/15 09:53, Peter UhnÃ¡k a Ã©crit : > > > stream surround: aBlock between: '( ' and: ' )' >> > > This may be personal preference, but I do not like having more method > arguments after a block argument... because if the block is longer it may > not be visible... > e.g. > > stream > surround: [ :aStream | > self size > 100 > ifTrue: [ > aStream nextPutAll: 'size '. > self size printOn: aStream ] > ifFalse: [ > self keysSortedSafely > do: [ :key | > aStream > print: key; > nextPutAll: '->'; > print: (self at: key); > space ] ] ] > between: $( > and: $) > > vs between:and:surround: > > if you actually run this through formatter in Pharo, the between:and: is > not even visible --- you have to scroll to see it. Of course if aBlock is a > variable, than my argument falls. > > From visual perspective the current state actually isn't that bad > because you immediately see where is beginning and where is end without > even looking... with surround:between:and: not so much... > > Peter > > > -- Best regards, Igor Stasenko.

July 27, 2015

[pharo-project/pharo-core]

by GitHub

Branch: refs/tags/50194 Home: https://github.com/pharo-project/pharo-core

July 27, 2015

[pharo-project/pharo-core] c6fbf8: 50194

by GitHub

Branch: refs/heads/5.0 Home: https://github.com/pharo-project/pharo-core Commit: c6fbf8f77ac7f2dce8ca4307a64d38f86b47fe57 https://github.com/pharo-project/pharo-core/commit/c6fbf8f77ac7f2dce8ca4307… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2015-07-27 (Mon, 27 Jul 2015) Changed paths: A ConfigurationOfTxText.package/ConfigurationOfTxText.class/instance/versions/version211_.st M SUnit-UITesting.package/SimulateKeystrokesSpecification.class/instance/tests/testSimulateCmdKeystroke.st M SUnit-UITesting.package/SimulateMouseSpecification.class/instance/tests/testSimulateRightClick.st R ScriptLoader50.package/ScriptLoader.class/instance/pharo - scripts/script50193.st A ScriptLoader50.package/ScriptLoader.class/instance/pharo - scripts/script50194.st R ScriptLoader50.package/ScriptLoader.class/instance/pharo - updates/update50193.st A ScriptLoader50.package/ScriptLoader.class/instance/pharo - updates/update50194.st M ScriptLoader50.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st M Spec-Examples.package/DropListExample.class/instance/initialization/initializeWidgets.st M StartupPreferences.package/StartupPreferencesLoader.class/class/example/example.st M StartupPreferences.package/extension/SettingDeclaration/instance/displayExportAction.st M System-Settings.package/SettingBrowser.class/class/private helpers/viewAllSettings.st M Tool-TxWorkspace.package/TxWorkspace.class/instance/opening/wireEvents.st M TxText-Athens.package/TxScrollbarDecorator.class/instance/accessing/setContainer_.st M TxText-Athens.package/TxScrollbarDecorator.class/instance/initialization/setupView_.st M TxText-Athens.package/TxScrollbarDecorator.class/instance/initialize/initScrollbar.st R TxText-Athens.package/TxSlider.class/class/as yet unclassified/test.st A TxText-Athens.package/TxSlider.class/class/tests/test.st A TxText-Styler.package/TxTextStyler.class/instance/visiting/addAttribute_startPosition_stopPosition_.st A TxText-Styler.package/TxTextStyler.class/instance/visiting/addAttributes_startPosition_stopPosition_.st A TxText-Styler.package/TxTextStyler.class/instance/visiting/addStyle_startPosition_stopPosition_.st M TxText-Styler.package/TxTextStyler.class/instance/visiting/visitMessageNode_.st Log Message: ----------- 50194 15951 remove all direct references to Workspace https://pharo.fogbugz.com/f/cases/15951 16042 TxTxt: load latest in image https://pharo.fogbugz.com/f/cases/16042 http://files.pharo.org/image/50/50194.zip

July 27, 2015

Re: [Pharo-dev] About nextPutAll: $(

by stepharo

May be I raised a not important issue. Stef Le 27/7/15 09:53, Peter UhnÃ¡k a Ã©crit : > > stream surround: aBlock between: '( ' and: ' )' > > > This may be personal preference, but I do not like having more method > arguments after a block argument... because if the block is longer it > may not be visible... > e.g. > > stream > surround: [ :aStream | > self size > 100 > ifTrue: [ > aStream nextPutAll: 'size '. > self size printOn: aStream ] > ifFalse: [ > self keysSortedSafely > do: [ :key | > aStream > print: key; > nextPutAll: '->'; > print: (self at: key); > space ] ] ] > between: $( > and: $) > > vs between:and:surround: > > if you actually run this through formatter in Pharo, the between:and: > is not even visible --- you have to scroll to see it. Of course if > aBlock is a variable, than my argument falls. > > From visual perspective the current state actually isn't that bad > because you immediately see where is beginning and where is end > without even looking... with surround:between:and: not so much... > > Peter

July 27, 2015

Re: [Pharo-dev] About nextPutAll: $(

by stepharo

Could be ok too. Le 27/7/15 09:53, Peter UhnÃ¡k a Ã©crit : > > stream surround: aBlock between: '( ' and: ' )' > > > This may be personal preference, but I do not like having more method > arguments after a block argument... because if the block is longer it > may not be visible... > e.g. > > stream > surround: [ :aStream | > self size > 100 > ifTrue: [ > aStream nextPutAll: 'size '. > self size printOn: aStream ] > ifFalse: [ > self keysSortedSafely > do: [ :key | > aStream > print: key; > nextPutAll: '->'; > print: (self at: key); > space ] ] ] > between: $( > and: $) > > vs between:and:surround: > > if you actually run this through formatter in Pharo, the between:and: > is not even visible --- you have to scroll to see it. Of course if > aBlock is a variable, than my argument falls. > > From visual perspective the current state actually isn't that bad > because you immediately see where is beginning and where is end > without even looking... with surround:between:and: not so much... > > Peter

July 27, 2015

Re: [Pharo-dev] About nextPutAll: $(

by HernÃ¡n Morales Durand

2015-07-27 4:24 GMT-03:00 Nicolai Hess <nicolaihess(a)web.de>: > > > 2015-07-27 8:26 GMT+02:00 HernÃ¡n Morales Durand <hernan.morales(a)gmail.com> > : > >> >> 2015-07-26 15:49 GMT-03:00 Esteban Lorenzano <estebanlm(a)gmail.com>: >> >>> Hi, >>> >>> Well, If there wouldn't be already a way to do it, I wouldn't care which >>> one to take. But this is not the case: we are discussing the introduction >>> of a new vocabulary when there is already another who is fulfilling the >>> place. >>> In that sense, the proposed method solves a problem who is actually not >>> there. >>> If we do not like #<<, then we should remove it from system, but please, >>> let's not add a more limited method when we have a more generic one who >>> does the job... >>> >> >> << is horrible, it reminds me to std::cout in C++ and all those cryptic >> languages where you cannot write a line without checking the API reference >> manual. >> > > I like "<<" because it reminds me to std::cout in C++ > > :) > > Maybe you're more comfortable in a C++ forum too ;) Seriously, I don't know, but whatever you choose please make it human inferrable from just by reading the selector name. Because << is arithmetic/bitwise operator for most coders in the world, and there are more developers to come and be newbies, than smalltalkers ever. HernÃ¡n

July 27, 2015

Re: [Pharo-dev] About nextPutAll: $(

by Vladimir Musulainen

I'm seeing that all causes of "output between brackets" are located in printString/printOn: methods Perhaps, it will be better to create special method like nextPutAllWithClassName: or something like it? 27/07/15 10:59, Denis Kudriashov Ð¿Ð¸ÑÐµÑ: > Hi. > > In most cases we always surround text by "()". Can we just provide > method for this and not duplicate "between: '( ' and: ' )'" > everywhere? Something like "stream>>printInBrackets:" > > 2015-07-27 10:33 GMT+03:00 stepharo <stepharo(a)free.fr > <mailto:stepharo@free.fr>>: > > Esteban > > I'm confused. I know << and I use it. > Now << is different to what I mentioned. > The point is not to replace nextPutAll: by << > I'm not that stupid. > > The point is the surrounding behavior (opening and closing). > Sven of course there are more than a name so this is why I thought > about > > stream surround: aBlock between: '( ' and: ' )' > > With << it means that we will have all the surrounding logic in > all the code. > > Stef > >

July 27, 2015

Re: [Pharo-dev] About nextPutAll: $(

by Denis Kudriashov

Hi. In most cases we always surround text by "()". Can we just provide method for this and not duplicate "between: '( ' and: ' )'" everywhere? Something like "stream>>printInBrackets:" 2015-07-27 10:33 GMT+03:00 stepharo <stepharo(a)free.fr>: > Esteban > > I'm confused. I know << and I use it. > Now << is different to what I mentioned. > The point is not to replace nextPutAll: by << > I'm not that stupid. > > The point is the surrounding behavior (opening and closing). > Sven of course there are more than a name so this is why I thought about > > stream surround: aBlock between: '( ' and: ' )' > > With << it means that we will have all the surrounding logic in all the > code. > > Stef > >

July 27, 2015

Re: [Pharo-dev] [Pharo4] reviews needed: 15977 Metacello Browser should only load from the selected repo

by Stephan Eggermont

On 26-07-15 11:25, Marcus Denker wrote: > Hi, > > This needs two positive reviews before we can even think about looking at it for Pharo4: > > 15977 Metacello Browser should only load from the selected repo > https://pharo.fogbugz.com/f/cases/15977 Don't I want the cache as fallback? Not all repos are reachable all the time. The same version number is more of a Monticello issue than a Metacello one, I'm not sure working around it here is the right thing. Please convince me Stephan

July 27, 2015

Re: [Pharo-dev] About nextPutAll: $(

by Peter UhnÃ¡k

> stream surround: aBlock between: '( ' and: ' )' > This may be personal preference, but I do not like having more method arguments after a block argument... because if the block is longer it may not be visible... e.g. stream surround: [ :aStream | self size > 100 ifTrue: [ aStream nextPutAll: 'size '. self size printOn: aStream ] ifFalse: [ self keysSortedSafely do: [ :key | aStream print: key; nextPutAll: '->'; print: (self at: key); space ] ] ] between: $( and: $) vs between:and:surround: if you actually run this through formatter in Pharo, the between:and: is not even visible --- you have to scroll to see it. Of course if aBlock is a variable, than my argument falls. >From visual perspective the current state actually isn't that bad because you immediately see where is beginning and where is end without even looking... with surround:between:and: not so much... Peter

July 27, 2015