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

Re: [Pharo-dev] [pharo-project/pharo-core] 4a02f5: 50273

by Yuriy Tymchuk

+1 > On 26 Aug 2015, at 15:28, Marcus Denker <marcus.denker(a)inria.fr> wrote: > >> >> 16265 World Menu should be invoked by right-click not left-click >> https://pharo.fogbugz.com/f/cases/16265 >> > > This is not good: on the mac, I think it should be always left click. > Historically the mac had one button, and the âdefaultâ action is > always left. (The âI want to start an actionâ, e.g. klicking on a button.) > Right click is for getting âoptionalâ or contextual menus. > > Marcus > >

Aug. 26, 2015

Re: [Pharo-dev] [pharo-project/pharo-core] 4a02f5: 50273

by Marcus Denker

> > 16265 World Menu should be invoked by right-click not left-click > https://pharo.fogbugz.com/f/cases/16265 > This is not good: on the mac, I think it should be always left click. Historically the mac had one button, and the âdefaultâ action is always left. (The âI want to start an actionâ, e.g. klicking on a button.) Right click is for getting âoptionalâ or contextual menus. Marcus

Aug. 26, 2015

[pharo-project/pharo-core] 4a02f5: 50273

by GitHub

Branch: refs/heads/5.0 Home: https://github.com/pharo-project/pharo-core Commit: 4a02f5e8f8315da5aaacb6d9c548c1e37f5a7fcf https://github.com/pharo-project/pharo-core/commit/4a02f5e8f8315da5aaacb6d9… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2015-08-26 (Wed, 26 Aug 2015) Changed paths: M Morphic-Core.package/PasteUpMorph.class/class/acessing/isMenuOpenByLeftClick.st M Nautilus.package/MethodWidget.class/instance/item creation/buildMethodsList.st R Nautilus.package/Nautilus.class/class/private/defaultCommentPosition.st R Nautilus.package/Nautilus.class/class/private/defaultPopulateMethodList.st M Nautilus.package/Nautilus.class/class/settings/nautilusSettingsOn_.st R Nautilus.package/Nautilus.class/class/settings/populateMethodList.st R Nautilus.package/Nautilus.class/class/settings/populateMethodList_.st M Refactoring-Critics.package/RBClassNotReferencedRule.class/instance/running/checkClass_.st R ScriptLoader50.package/ScriptLoader.class/instance/pharo - scripts/script50272.st A ScriptLoader50.package/ScriptLoader.class/instance/pharo - scripts/script50273.st R ScriptLoader50.package/ScriptLoader.class/instance/pharo - updates/update50272.st A ScriptLoader50.package/ScriptLoader.class/instance/pharo - updates/update50273.st M ScriptLoader50.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st A System-Support.package/SystemNavigation.class/instance/message sends/isUsedClass_.st A System-Support.package/extension/TBehavior/instance/isUsed.st A Traits.package/TBehavior.class/instance/testing method dictionary/hasSelectorReferringTo_.st Log Message: ----------- 50273 16074 Is RBClassNotReferencedRule ~200x slower in Pharo 4 vs Pharo 3 ? https://pharo.fogbugz.com/f/cases/16074 16384 populateMethodList Nautilus https://pharo.fogbugz.com/f/cases/16384 16265 World Menu should be invoked by right-click not left-click https://pharo.fogbugz.com/f/cases/16265 http://files.pharo.org/image/50/50273.zip

Aug. 26, 2015

[pharo-project/pharo-core]

by GitHub

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

Aug. 26, 2015

Re: [Pharo-dev] [Pharo-users] [ann] brick on top of bloc - preview

by Tudor Girba

Hi Guille, Try this one in the latest Pharo 5.0 image: Gofer new smalltalkhubUser: 'Pharo' project: 'Brick'; configuration; loadDevelopment. Cheers, Doru On Wed, Aug 26, 2015 at 12:11 PM, Guillermo Polito < guillermopolito(a)gmail.com> wrote: > We did a change last week on MCDataStream. We did it with the intention of > making it backward compatible. > > Can somebody tell me a repo/package/version that I should try to load to > reproduce it? > > Guille > > El miÃ©., 26 de ago. de 2015 a la(s) 12:00 p. m., Nicolai Hess < > nicolaihess(a)web.de> escribiÃ³: > >> 2015-08-26 11:00 GMT+02:00 Marcus Denker <marcus.denker(a)inria.fr>: >> >>> >>> > On 26 Aug 2015, at 10:58, Blondeau Vincent < >>> vincent.blondeau(a)worldline.com> wrote: >>> > >>> > Loading traits only is working, there are traits in Moose and it is >>> well working... >>> > E.g.: >>> > Trait named: #TOODependencyQueries >>> > uses: TDependencyQueries >>> > category: 'Famix-Coreâ >>> > >>> >>> Yes, but there it might not fall back on loading the .st file but >>> instead de-seriaize the MC model. >>> >> >> Yes, I think this is again >> >> MCMczReader>>loadDefinitions >> definitions := OrderedCollection new. >> (self zip memberNamed: 'snapshot.bin') ifNotNil: >> [:m | [^ definitions := (MCDataStream on: m contentStream) next >> definitions] >> on: Error do: [:fallThrough]]. >> "otherwise" >> (self zip membersMatching: 'snapshot/*') >> do: [:m | self extractDefinitionsFrom: m]. >> >> if the first run wit hMCDataStream on: ... fails, it uses the "otherwise" >> path. >> But that one does not handle Trait definitions correctly. >> >> I don't know why the first one (MCDataStream ...) fails on some packages, >> may have something to do with >> non-ascii characters but I don't know if it failed always at that place >> and only the implementation in the >> second path changed? >> >> >> nicolai >> >> >> >> >> >> >>> >>> >>> > Vincent >>> > >>> > -----Message d'origine----- >>> > De : Pharo-users [mailto:pharo-users-bounces@lists.pharo.org] De la >>> part de Marcus Denker >>> > EnvoyÃ© : mercredi 26 aoÃ»t 2015 10:52 >>> > Ã : Any question about pharo is welcome >>> > Cc : Pharo Development List >>> > Objet : Re: [Pharo-users] [ann] brick on top of bloc - preview >>> > >>> > >>> >> On 26 Aug 2015, at 10:42, Tudor Girba <tudor(a)tudorgirba.com> wrote: >>> >> >>> >> Aha. Thanks for the help, Vincent. >>> >> >>> >> Now, the next problem: Does anyone know why the "Unrecognized class >>> definition" problem occurs? :) >>> >> >>> > >>> > It seems that >>> > >>> > 1) MC model loading of the serialised package fails >>> > 2) it falls back on using MCStReader >>> > 3) which fails to load the .st file for the definition of >>> TBlLayoutPropertiesOwner >>> > >>> > Maybe loading trait definitions does not work in general with >>> MCStReader? >>> > >>> > Marcus >>> > >>> > >>> > Ce message et les piÃ¨ces jointes sont confidentiels et rÃ©servÃ©s Ã >>> l'usage exclusif de ses destinataires. Il peut Ã©galement Ãªtre protÃ©gÃ© par >>> le secret professionnel. Si vous recevez ce message par erreur, merci d'en >>> avertir immÃ©diatement l'expÃ©diteur et de le dÃ©truire. L'intÃ©gritÃ© du >>> message ne pouvant Ãªtre assurÃ©e sur Internet, la responsabilitÃ© de >>> Worldline ne pourra Ãªtre recherchÃ©e quant au contenu de ce message. Bien >>> que les meilleurs efforts soient faits pour maintenir cette transmission >>> exempte de tout virus, l'expÃ©diteur ne donne aucune garantie Ã cet Ã©gard et >>> sa responsabilitÃ© ne saurait Ãªtre recherchÃ©e pour tout dommage rÃ©sultant >>> d'un virus transmis. >>> > >>> > This e-mail and the documents attached are confidential and intended >>> solely for the addressee; it may also be privileged. If you receive this >>> e-mail in error, please notify the sender immediately and destroy it. As >>> its integrity cannot be secured on the Internet, the Worldline liability >>> cannot be triggered for the message content. Although the sender endeavours >>> to maintain a computer virus-free network, the sender does not warrant that >>> this transmission is virus-free and will not be liable for any damages >>> resulting from any virus transmitted. >>> > >>> >>> >>> -- www.tudorgirba.com "Every thing has its own flow"

Aug. 26, 2015

[pharo-project/pharo-core]

by GitHub

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

Aug. 26, 2015

[pharo-project/pharo-core] 17fdcd: 50272

by GitHub

Branch: refs/heads/5.0 Home: https://github.com/pharo-project/pharo-core Commit: 17fdcdca289b99f8e3d2b670689dad083b9e27de https://github.com/pharo-project/pharo-core/commit/17fdcdca289b99f8e3d2b670… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2015-08-26 (Wed, 26 Aug 2015) Changed paths: R CodeImport.package/EvaluateCommandLineHandler.class/README.md R CodeImport.package/EvaluateCommandLineHandler.class/class/accessing/commandName.st R CodeImport.package/EvaluateCommandLineHandler.class/class/accessing/description.st R CodeImport.package/EvaluateCommandLineHandler.class/class/handler selection/isResponsibleFor_.st R CodeImport.package/EvaluateCommandLineHandler.class/definition.st R CodeImport.package/EvaluateCommandLineHandler.class/instance/activation/activate.st R CodeImport.package/EvaluateCommandLineHandler.class/instance/activation/argumentString.st R CodeImport.package/EvaluateCommandLineHandler.class/instance/activation/evaluateArguments.st R CodeImport.package/EvaluateCommandLineHandler.class/instance/activation/evaluateStdIn.st R CodeImport.package/EvaluateCommandLineHandler.class/instance/commands/evaluate_.st R CodeImport.package/STCommandLineHandler.class/README.md R CodeImport.package/STCommandLineHandler.class/class/accessing/commandName.st R CodeImport.package/STCommandLineHandler.class/class/accessing/description.st R CodeImport.package/STCommandLineHandler.class/class/handler selection/isResponsibleFor_.st R CodeImport.package/STCommandLineHandler.class/class/printing/printCompilerWarning_.st R CodeImport.package/STCommandLineHandler.class/definition.st R CodeImport.package/STCommandLineHandler.class/instance/activation/activate.st R CodeImport.package/STCommandLineHandler.class/instance/installing/handleErrorsDuring_reference_.st R CodeImport.package/STCommandLineHandler.class/instance/installing/installSourceFile_.st R CodeImport.package/STCommandLineHandler.class/instance/installing/installSourceFiles.st R CodeImport.package/STCommandLineHandler.class/instance/loading/loadSourceFiles_.st R CodeImport.package/STCommandLineHandler.class/instance/private/end.st R CodeImport.package/STCommandLineHandler.class/instance/private/handleError_.st R CodeImport.package/STCommandLineHandler.class/instance/private/handleError_reference_.st A CodeImportCommandLineHandlers.package/EvaluateCommandLineHandler.class/README.md A CodeImportCommandLineHandlers.package/EvaluateCommandLineHandler.class/class/accessing/commandName.st A CodeImportCommandLineHandlers.package/EvaluateCommandLineHandler.class/class/accessing/description.st A CodeImportCommandLineHandlers.package/EvaluateCommandLineHandler.class/class/handler selection/isResponsibleFor_.st A CodeImportCommandLineHandlers.package/EvaluateCommandLineHandler.class/definition.st A CodeImportCommandLineHandlers.package/EvaluateCommandLineHandler.class/instance/activation/activate.st A CodeImportCommandLineHandlers.package/EvaluateCommandLineHandler.class/instance/activation/argumentString.st A CodeImportCommandLineHandlers.package/EvaluateCommandLineHandler.class/instance/activation/evaluateArguments.st A CodeImportCommandLineHandlers.package/EvaluateCommandLineHandler.class/instance/activation/evaluateStdIn.st A CodeImportCommandLineHandlers.package/EvaluateCommandLineHandler.class/instance/commands/evaluate_.st A CodeImportCommandLineHandlers.package/STCommandLineHandler.class/README.md A CodeImportCommandLineHandlers.package/STCommandLineHandler.class/class/accessing/commandName.st A CodeImportCommandLineHandlers.package/STCommandLineHandler.class/class/accessing/description.st A CodeImportCommandLineHandlers.package/STCommandLineHandler.class/class/handler selection/isResponsibleFor_.st A CodeImportCommandLineHandlers.package/STCommandLineHandler.class/class/printing/printCompilerWarning_.st A CodeImportCommandLineHandlers.package/STCommandLineHandler.class/definition.st A CodeImportCommandLineHandlers.package/STCommandLineHandler.class/instance/activation/activate.st A CodeImportCommandLineHandlers.package/STCommandLineHandler.class/instance/installing/handleErrorsDuring_reference_.st A CodeImportCommandLineHandlers.package/STCommandLineHandler.class/instance/installing/installSourceFile_.st A CodeImportCommandLineHandlers.package/STCommandLineHandler.class/instance/installing/installSourceFiles.st A CodeImportCommandLineHandlers.package/STCommandLineHandler.class/instance/loading/loadSourceFiles_.st A CodeImportCommandLineHandlers.package/STCommandLineHandler.class/instance/private/end.st A CodeImportCommandLineHandlers.package/STCommandLineHandler.class/instance/private/handleError_.st A CodeImportCommandLineHandlers.package/STCommandLineHandler.class/instance/private/handleError_reference_.st M Nautilus.package/PackageTreeNautilusUI.class/instance/accessing/showHierarchy_.st R ScriptLoader50.package/ScriptLoader.class/instance/pharo - scripts/script50271.st A ScriptLoader50.package/ScriptLoader.class/instance/pharo - scripts/script50272.st R ScriptLoader50.package/ScriptLoader.class/instance/pharo - updates/update50271.st A ScriptLoader50.package/ScriptLoader.class/instance/pharo - updates/update50272.st M ScriptLoader50.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st M Traits.package/TBehavior.class/instance/queries/whichSelectorsRead_.st M Traits.package/TBehavior.class/instance/testing method dictionary/thoroughHasSelectorReferringTo_.st M Traits.package/TBehavior.class/instance/testing method dictionary/thoroughWhichSelectorsReferTo_.st M Traits.package/TBehavior.class/instance/testing method dictionary/whichSelectorsReferTo_.st Log Message: ----------- 50272 16277 Unselect the hierarchie button show the class definission https://pharo.fogbugz.com/f/cases/16277 16290 Get rid of System-CommandLine dependency from the bootstrap https://pharo.fogbugz.com/f/cases/16290 16369 do not use IdentitySet in whichSelectorsReferTo: and friends https://pharo.fogbugz.com/f/cases/16369 http://files.pharo.org/image/50/50272.zip

Aug. 26, 2015

Re: [Pharo-dev] [Pharo-users] [ann] brick on top of bloc - preview

by Guillermo Polito

We did a change last week on MCDataStream. We did it with the intention of making it backward compatible. Can somebody tell me a repo/package/version that I should try to load to reproduce it? Guille El miÃ©., 26 de ago. de 2015 a la(s) 12:00 p. m., Nicolai Hess < nicolaihess(a)web.de> escribiÃ³: > 2015-08-26 11:00 GMT+02:00 Marcus Denker <marcus.denker(a)inria.fr>: > >> >> > On 26 Aug 2015, at 10:58, Blondeau Vincent < >> vincent.blondeau(a)worldline.com> wrote: >> > >> > Loading traits only is working, there are traits in Moose and it is >> well working... >> > E.g.: >> > Trait named: #TOODependencyQueries >> > uses: TDependencyQueries >> > category: 'Famix-Coreâ >> > >> >> Yes, but there it might not fall back on loading the .st file but instead >> de-seriaize the MC model. >> > > Yes, I think this is again > > MCMczReader>>loadDefinitions > definitions := OrderedCollection new. > (self zip memberNamed: 'snapshot.bin') ifNotNil: > [:m | [^ definitions := (MCDataStream on: m contentStream) next > definitions] > on: Error do: [:fallThrough]]. > "otherwise" > (self zip membersMatching: 'snapshot/*') > do: [:m | self extractDefinitionsFrom: m]. > > if the first run wit hMCDataStream on: ... fails, it uses the "otherwise" > path. > But that one does not handle Trait definitions correctly. > > I don't know why the first one (MCDataStream ...) fails on some packages, > may have something to do with > non-ascii characters but I don't know if it failed always at that place > and only the implementation in the > second path changed? > > > nicolai > > > > > > >> >> >> > Vincent >> > >> > -----Message d'origine----- >> > De : Pharo-users [mailto:pharo-users-bounces@lists.pharo.org] De la >> part de Marcus Denker >> > EnvoyÃ© : mercredi 26 aoÃ»t 2015 10:52 >> > Ã : Any question about pharo is welcome >> > Cc : Pharo Development List >> > Objet : Re: [Pharo-users] [ann] brick on top of bloc - preview >> > >> > >> >> On 26 Aug 2015, at 10:42, Tudor Girba <tudor(a)tudorgirba.com> wrote: >> >> >> >> Aha. Thanks for the help, Vincent. >> >> >> >> Now, the next problem: Does anyone know why the "Unrecognized class >> definition" problem occurs? :) >> >> >> > >> > It seems that >> > >> > 1) MC model loading of the serialised package fails >> > 2) it falls back on using MCStReader >> > 3) which fails to load the .st file for the definition of >> TBlLayoutPropertiesOwner >> > >> > Maybe loading trait definitions does not work in general with >> MCStReader? >> > >> > Marcus >> > >> > >> > Ce message et les piÃ¨ces jointes sont confidentiels et rÃ©servÃ©s Ã >> l'usage exclusif de ses destinataires. Il peut Ã©galement Ãªtre protÃ©gÃ© par >> le secret professionnel. Si vous recevez ce message par erreur, merci d'en >> avertir immÃ©diatement l'expÃ©diteur et de le dÃ©truire. L'intÃ©gritÃ© du >> message ne pouvant Ãªtre assurÃ©e sur Internet, la responsabilitÃ© de >> Worldline ne pourra Ãªtre recherchÃ©e quant au contenu de ce message. Bien >> que les meilleurs efforts soient faits pour maintenir cette transmission >> exempte de tout virus, l'expÃ©diteur ne donne aucune garantie Ã cet Ã©gard et >> sa responsabilitÃ© ne saurait Ãªtre recherchÃ©e pour tout dommage rÃ©sultant >> d'un virus transmis. >> > >> > This e-mail and the documents attached are confidential and intended >> solely for the addressee; it may also be privileged. If you receive this >> e-mail in error, please notify the sender immediately and destroy it. As >> its integrity cannot be secured on the Internet, the Worldline liability >> cannot be triggered for the message content. Although the sender endeavours >> to maintain a computer virus-free network, the sender does not warrant that >> this transmission is virus-free and will not be liable for any damages >> resulting from any virus transmitted. >> > >> >> >>

Aug. 26, 2015

Re: [Pharo-dev] [Pharo-users] [ann] brick on top of bloc - preview

by Nicolai Hess

2015-08-26 11:00 GMT+02:00 Marcus Denker <marcus.denker(a)inria.fr>: > > > On 26 Aug 2015, at 10:58, Blondeau Vincent < > vincent.blondeau(a)worldline.com> wrote: > > > > Loading traits only is working, there are traits in Moose and it is well > working... > > E.g.: > > Trait named: #TOODependencyQueries > > uses: TDependencyQueries > > category: 'Famix-Coreâ > > > > Yes, but there it might not fall back on loading the .st file but instead > de-seriaize the MC model. > Yes, I think this is again MCMczReader>>loadDefinitions definitions := OrderedCollection new. (self zip memberNamed: 'snapshot.bin') ifNotNil: [:m | [^ definitions := (MCDataStream on: m contentStream) next definitions] on: Error do: [:fallThrough]]. "otherwise" (self zip membersMatching: 'snapshot/*') do: [:m | self extractDefinitionsFrom: m]. if the first run wit hMCDataStream on: ... fails, it uses the "otherwise" path. But that one does not handle Trait definitions correctly. I don't know why the first one (MCDataStream ...) fails on some packages, may have something to do with non-ascii characters but I don't know if it failed always at that place and only the implementation in the second path changed? nicolai > > > > Vincent > > > > -----Message d'origine----- > > De : Pharo-users [mailto:pharo-users-bounces@lists.pharo.org] De la > part de Marcus Denker > > EnvoyÃ© : mercredi 26 aoÃ»t 2015 10:52 > > Ã : Any question about pharo is welcome > > Cc : Pharo Development List > > Objet : Re: [Pharo-users] [ann] brick on top of bloc - preview > > > > > >> On 26 Aug 2015, at 10:42, Tudor Girba <tudor(a)tudorgirba.com> wrote: > >> > >> Aha. Thanks for the help, Vincent. > >> > >> Now, the next problem: Does anyone know why the "Unrecognized class > definition" problem occurs? :) > >> > > > > It seems that > > > > 1) MC model loading of the serialised package fails > > 2) it falls back on using MCStReader > > 3) which fails to load the .st file for the definition of > TBlLayoutPropertiesOwner > > > > Maybe loading trait definitions does not work in general with MCStReader? > > > > Marcus > > > > > > Ce message et les piÃ¨ces jointes sont confidentiels et rÃ©servÃ©s Ã > l'usage exclusif de ses destinataires. Il peut Ã©galement Ãªtre protÃ©gÃ© par > le secret professionnel. Si vous recevez ce message par erreur, merci d'en > avertir immÃ©diatement l'expÃ©diteur et de le dÃ©truire. L'intÃ©gritÃ© du > message ne pouvant Ãªtre assurÃ©e sur Internet, la responsabilitÃ© de > Worldline ne pourra Ãªtre recherchÃ©e quant au contenu de ce message. Bien > que les meilleurs efforts soient faits pour maintenir cette transmission > exempte de tout virus, l'expÃ©diteur ne donne aucune garantie Ã cet Ã©gard et > sa responsabilitÃ© ne saurait Ãªtre recherchÃ©e pour tout dommage rÃ©sultant > d'un virus transmis. > > > > This e-mail and the documents attached are confidential and intended > solely for the addressee; it may also be privileged. If you receive this > e-mail in error, please notify the sender immediately and destroy it. As > its integrity cannot be secured on the Internet, the Worldline liability > cannot be triggered for the message content. Although the sender endeavours > to maintain a computer virus-free network, the sender does not warrant that > this transmission is virus-free and will not be liable for any damages > resulting from any virus transmitted. > > > > >

Aug. 26, 2015

Re: [Pharo-dev] Working Directory and FileSystem

by Thierry Goubier

Hi Guile, http://forum.world.st/Working-directory-td4631865.html I think there is some discussions about that a while ago. Thierry 2015-08-26 11:32 GMT+02:00 Guillermo Polito <guillermopolito(a)gmail.com>: > (I cc the VM dev as this topic touches a bit the VM) > > Hi, chasing a bug I found that FileSystem does not handle well the working > directory of the system. The working directory of a process is the > directory from where we started the process. That is, the directory from > where we launched the VM with the image. > > However, FileSystem has two problems with this: > 1) it believes that the workingDirectory is where the image *is* and not > where it was open. (Check: FileSystem workingDirectory). > 2) if you try to use a relative file name FileSystem will use the working > directory he believes instead of letting the primitive do his job. (Just > open your image from another directory and do 'asd.txt' asFileReference > fullName). > > This problem becomes apparent when you use the launcher, or when you > launch your image from other directory. > > Now, I was checking with Santi how to obtain the working directory of the > process and we saw that there are two primitives """"included""" in the VM > as part of the OSProcess plugins to do it (Included as they are in the > PharoVM build). > > <primitive: 'primitiveGetCurrentWorkingDirectory' module: > 'Win32OSProcessPlugin' > > > AND > > <primitive: 'primitiveGetCurrentWorkingDirectory' module: > 'UnixOSProcessPlugin' > > > > So I'd like to propose: > - include those primitives in the default VM (as we already have the ones > to get the image file path and the vm file path). > - Add methods calling those primitives in OSPlatform and subclasses > - Change FileSystem to have the working directory work as expected. > > What do you think? > Guille >

Aug. 26, 2015