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

Re: [Pharo-dev] [Article] Elegant Pharo Code

by phil＠highoctane.be

Super! Le 8 juil. 2014 00:23, "Sven Van Caekenberghe" <sven(a)stfx.eu> a Ã©crit : > Hi, > > I have written a new article presenting Pharo using a list of 23 short > examples. > > Elegant Pharo Code > > Beautiful & Powerful One-liners, Expressions and Snippets > > https://medium.com/@svenvc/elegant-pharo-code-bb590f0856d0 > > As mentioned at the end of the article, I welcome feedback, remarks, > comments, alternative solutions and other examples. The idea is to create > yet another way to lure people into exploring Pharo while explaining by > example why we like Pharo. > > Enjoy! > > Sven > > -- > Sven Van Caekenberghe > Proudly supporting Pharo > http://pharo.org > http://association.pharo.org > http://consortium.pharo.org > > > > > >

July 8, 2014

Re: [Pharo-dev] Smalltalk Syntax in a Postcard contest

by Yuriy Tymchuk

Sometimes StackExchange-related guys are really stupidâ¦ I think that we should put this contest in a visible place. And thanks HernÃ¡n, I think that itâs also cool that you can search for desired method like that in the image. Uko On 08 Jul 2014, at 09:07, HernÃ¡n Morales Durand <hernan.morales(a)gmail.com> wrote: > The contest is gone? > > Anyway, the closest useful method I have found by iterating all ASTs in standard 3.0 image : > > - Declares arguments > - Has assignment > - Has sequence > - Has blocks with 0 and 2 arguments > - Declares temporaries > - Has binary messages > - Has unary messages > - Has keyword messages > - Has super messages > - Has cascade > - Has return > - Uses String and Integer > > and this is the winner: > > RBMessageNode>>replaceSourceWithMessageNode: aNode > > | isBinaryToKeyword | > self numArgs = aNode numArgs ifFalse: [^super replaceSourceWith: aNode]. > self arguments with: aNode arguments > do: [:old :new | (self mappingFor: old) = new ifFalse: [^super replaceSourceWith: aNode]]. > (self mappingFor: self receiver) = aNode receiver > ifFalse: > [(self receiver isVariable and: [aNode receiver isVariable]) > ifFalse: > [^super replaceSourceWith: aNode]. > self addReplacement: > (RBStringReplacement > replaceFrom: self receiver start > to: self receiver stop > with: aNode receiver name)]. > (isBinaryToKeyword := self isBinary and: [aNode isKeyword]) > ifTrue: > [(self hasParentheses not and: [self parent precedence <= aNode precedence]) > ifTrue: > [self > addReplacement: (RBStringReplacement > replaceFrom: self start > to: self start - 1 > with: '('); > addReplacement: (RBStringReplacement > replaceFrom: self stop + 1 > to: self stop > with: ')')]]. > self selectorParts with: aNode selectorParts > do: > [:old :new | > old value ~= new value > ifTrue: > [self addReplacement: (RBStringReplacement > replaceFrom: old start > to: old stop > with: ((isBinaryToKeyword > and: [(self source at: old start - 1) isSeparator not]) > ifTrue: [' ' , new value] > ifFalse: [new value]))]] > > Cheers, > > HernÃ¡n > > > > 2014-07-06 13:16 GMT-03:00 MartinW <wm(a)fastmail.fm>: > As there was a recent discussion about the Smalltalk Syntax in a Postcard, i > added a contest on the Stackoverflow Programming Puzzles & Code Golf site: > http://codegolf.stackexchange.com/questions/33050/smalltalk-syntax-in-a-pos… > > > > -- > View this message in context: http://forum.world.st/Smalltalk-Syntax-in-a-Postcard-contest-tp4766793.html > Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com. > >

July 8, 2014

About the *-Settings packages

by Marcus Denker

Hi, The Settings framework is very nice: there are no dependencies to the framework itself anywhere, so you can run with both the Setting Browser and *the framework itself* unloaded. All the settings definitions are in their own packages, so you can even unload *those*. But I wonder if that is not one thing too much: -> the definition itself does not create dependencies at all -> the definitions are *tiny* (5-30 line methods) -> the packages contains just one class with (often) just one method, managing a complete package for that should pay of, and I would say it does not (âI can save 500 bytes of dead code by not shipping the settings definition in my deployment image!"). I guess nobody ever unloaded a settings package for deployment! (#cleanUpForProduction does not) I would like to move the definitions of settings close to the code that the settings manipulate (and from itâs own class just to the main class of that package, class side). - you can still unload the settings framework after - the only âuselessâ things staying in the system after unloading the settings framework is a method that is not used (but that does not introduce dependencies) - managing the code base in turn gets simpler - less classes and packages to manage Marcus

July 8, 2014

Re: [Pharo-dev] Smalltalk Syntax in a Postcard contest

by HernÃ¡n Morales Durand

The contest is gone? Anyway, the closest useful method I have found by iterating all ASTs in standard 3.0 image : - Declares arguments - Has assignment - Has sequence - Has blocks with 0 and 2 arguments - Declares temporaries - Has binary messages - Has unary messages - Has keyword messages - Has super messages - Has cascade - Has return - Uses String and Integer and this is the winner: RBMessageNode>>replaceSourceWithMessageNode: aNode | isBinaryToKeyword | self numArgs = aNode numArgs ifFalse: [^super replaceSourceWith: aNode]. self arguments with: aNode arguments do: [:old :new | (self mappingFor: old) = new ifFalse: [^super replaceSourceWith: aNode]]. (self mappingFor: self receiver) = aNode receiver ifFalse: [(self receiver isVariable and: [aNode receiver isVariable]) ifFalse: [^super replaceSourceWith: aNode]. self addReplacement: (RBStringReplacement replaceFrom: self receiver start to: self receiver stop with: aNode receiver name)]. (isBinaryToKeyword := self isBinary and: [aNode isKeyword]) ifTrue: [(self hasParentheses not and: [self parent precedence <= aNode precedence]) ifTrue: [self addReplacement: (RBStringReplacement replaceFrom: self start to: self start - 1 with: '('); addReplacement: (RBStringReplacement replaceFrom: self stop + 1 to: self stop with: ')')]]. self selectorParts with: aNode selectorParts do: [:old :new | old value ~= new value ifTrue: [self addReplacement: (RBStringReplacement replaceFrom: old start to: old stop with: ((isBinaryToKeyword and: [(self source at: old start - 1) isSeparator not]) ifTrue: [' ' , new value] ifFalse: [new value]))]] Cheers, HernÃ¡n 2014-07-06 13:16 GMT-03:00 MartinW <wm(a)fastmail.fm>: > As there was a recent discussion about the Smalltalk Syntax in a Postcard, > i > added a contest on the Stackoverflow Programming Puzzles & Code Golf site: > > http://codegolf.stackexchange.com/questions/33050/smalltalk-syntax-in-a-pos… > > > > -- > View this message in context: > http://forum.world.st/Smalltalk-Syntax-in-a-Postcard-contest-tp4766793.html > Sent from the Pharo Smalltalk Developers mailing list archive at > Nabble.com. > >

July 8, 2014

Close to 1000 followers on twitter... (>990 right now)

by Marcus Denker

â¦ who will be the 1000th follower? Marcus

July 8, 2014

[pharo-project/pharo-core]

by GitHub

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

July 8, 2014

[pharo-project/pharo-core] 17b0c1: 40071

by GitHub

Branch: refs/heads/4.0 Home: https://github.com/pharo-project/pharo-core Commit: 17b0c1d35a362b46bf15b20230d55096560ee3d1 https://github.com/pharo-project/pharo-core/commit/17b0c1d35a362b46bf15b202… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2014-07-08 (Tue, 08 Jul 2014) Changed paths: A Deprecated40.package/extension/RPackageOrganizer/instance/renamePackage_in_.st M Kernel.package/MessageNotUnderstood.class/definition.st M Kernel.package/PragmaCollector.class/definition.st M Kernel.package/PragmaCollectorReset.class/definition.st M Kernel.package/SimulationExceptionWrapper.class/definition.st M Kernel.package/ZeroDivide.class/definition.st M Nautilus.package/extension/Class/instance/definitionForNautilusWithSlots.st M RPackage-Core.package/RPackage.class/instance/accessing/extensionSelectors.st A RPackage-Core.package/RPackageOrganizer.class/instance/private testing/debuggingName.st A RPackage-Core.package/RPackageOrganizer.class/instance/private testing/debuggingName_.st R RPackage-Core.package/RPackageOrganizer.class/instance/private testing/includesPackageBackPointerForClassNamed_.st R RPackage-Core.package/RPackageOrganizer.class/instance/private/debuggingName.st R RPackage-Core.package/RPackageOrganizer.class/instance/private/debuggingName_.st R RPackage-Core.package/RPackageOrganizer.class/instance/renaming/renamePackage_in_.st R RPackage-Core.package/RPackageRenamed.class/class/as yet unclassified/to_oldName_newName_.st A RPackage-Core.package/RPackageRenamed.class/class/instance creation/to_oldName_newName_.st M RPackage-Core.package/RPackageTag.class/instance/updating/updateDefinedClassNamed_withNewName_.st R RPackage-Core.package/extension/CompiledMethod/instance/handleUnpackaged_.st R RPackage-Core.package/extension/PackageInfo/instance/withClassesAndCategoriesDo_.st A ScriptLoader40.package/ScriptLoader.class/instance/pharo - scripts/script71.st A ScriptLoader40.package/ScriptLoader.class/instance/pharo - updates/update40071.st M ScriptLoader40.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st Log Message: ----------- 40071 13488 Small recategorization of Classes in Kernel https://pharo.fogbugz.com/f/cases/13488 13485 Move RPackageOrganizer>>#renamePackage:in: to Deprecated40 https://pharo.fogbugz.com/f/cases/13485 13477 Small critique cleanup RPackage https://pharo.fogbugz.com/f/cases/13477 http://files.pharo.org/image/40/40071.zip

July 8, 2014

Re: [Pharo-dev] Workaround monticello issue

by GOUBIER Thierry

Sebastian, FileTree is already integrated in Pharo3 and has probably diverged a bit from Dale FileTree repository, so you don't have to reload it (shouldn't). Thierry ________________________________ De : Pharo-dev [pharo-dev-bounces(a)lists.pharo.org] de la part de Sebastian Sastre [sebastian(a)flowingconcept.com] EnvoyÃ© : mardi 8 juillet 2014 01:19 Ã : Pharo Development List Objet : Re: [Pharo-dev] Workaround monticello issue Hi Thierry, is a Pharo3.0 Latest update: #30851 with Gofer new url: 'http://ss3.gemstone.com/ss/FileTree'; package: 'ConfigurationOfFileTree'; load. ((Smalltalk at: #ConfigurationOfFileTree) project version: #'stable') load. in it thanks for taking a look! On Jul 7, 2014, at 6:18 PM, GOUBIER Thierry <thierry.goubier(a)cea.fr<mailto:thierry.goubier@cea.fr>> wrote: Hi Sebastian, which version are you using? I looked into 3.0 and 4.0, and there is nothing there about setting packageList to nil in MCFileRepositoryInspector. Thierry ________________________________ De : Pharo-dev [pharo-dev-bounces(a)lists.pharo.org<mailto:pharo-dev-bounces@lists.pharo.org>] de la part de Sebastian Sastre [sebastian(a)flowingconcept.com<mailto:sebastian@flowingconcept.com>] EnvoyÃ© : lundi 7 juillet 2014 22:45 Ã : Pharo Development List Objet : [Pharo-dev] Workaround monticello issue Hi there, Iâve just hit an issue that prevented to open packages in monticello MessageNotUnderstood: receiver of "indexOf:" is nil UndefinedObject(Object)>>doesNotUnderstand: #indexOf: MCFileRepositoryInspector>>packageSelection PluggableListMorph>>getCurrentSelectionIndex PluggableListMorph>>updateList PluggableListMorph>>update: MCFileRepositoryInspector(Object)>>changed: in Block: [ :aDependent | aDependent update: aParameter ] DependentsArray>>do: MCFileRepositoryInspector(Object)>>changed: MCFileRepositoryInspector>>refresh MCFileRepositoryInspector>>setRepository:workingCopy: in Block: [ ... BlockClosure>>newProcess in Block: [ ... This is what Iâm using as hacky workaround: MCFileRepositoryInspector>>packageSelection ^ self packageList isNil ifTrue:[ 1 ] ifFalse:[ self packageList indexOf: selectedPackage ] The problem is that packageList is nil for some reason. Looks like filetree is involved since 1. Iâm using it and 2. it sets an extension method #refresh that makes packageList := nil sebastian<https://about.me/sebastianconcept> o/ blog: http://sebastianconcept.com<http://sebastianconcept.com/> LinkedIn: http://www.linkedin.com/in/sebastiansastre github: https://github.com/sebastianconcept

July 8, 2014

Re: [Pharo-dev] [Pharo-users] [Article] Elegant Pharo Code

by Tudor Girba

Neat :) Doru On Tue, Jul 8, 2014 at 12:21 AM, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > Hi, > > I have written a new article presenting Pharo using a list of 23 short > examples. > > Elegant Pharo Code > > Beautiful & Powerful One-liners, Expressions and Snippets > > https://medium.com/@svenvc/elegant-pharo-code-bb590f0856d0 > > As mentioned at the end of the article, I welcome feedback, remarks, > comments, alternative solutions and other examples. The idea is to create > yet another way to lure people into exploring Pharo while explaining by > example why we like Pharo. > > Enjoy! > > Sven > > -- > Sven Van Caekenberghe > Proudly supporting Pharo > http://pharo.org > http://association.pharo.org > http://consortium.pharo.org > > > > > > -- www.tudorgirba.com "Every thing has its own flow"

July 8, 2014

Re: [Pharo-dev] [Article] Elegant Pharo Code

by Guy

Sven, I must applaud your enthusiasm and commitment to smalltalk and specifically Pharo. You are one of the dedicated people developing and enhancing the best programming language. I have been a long time smalltalk aficionado and user but no more than an enthusiastic hobbyist. If you are a premature baby then I perhaps display the same dedication to the cause. If you donât mind me pokingâ¦ may I suggest the appropriate spelling Hopefully these examples have piqued your interestâ Guy On 8/07/2014, at 10:21 am, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > Hi, > > I have written a new article presenting Pharo using a list of 23 short examples. > > Elegant Pharo Code > > Beautiful & Powerful One-liners, Expressions and Snippets > > https://medium.com/@svenvc/elegant-pharo-code-bb590f0856d0 > > As mentioned at the end of the article, I welcome feedback, remarks, comments, alternative solutions and other examples. The idea is to create yet another way to lure people into exploring Pharo while explaining by example why we like Pharo. > > Enjoy! > > Sven > > -- > Sven Van Caekenberghe > Proudly supporting Pharo > http://pharo.org > http://association.pharo.org > http://consortium.pharo.org > > > > >

July 8, 2014