June 2016 - Pharo-dev - lists.pharo.org

[pharo-project/pharo-core]
by GitHub June 14, 2016

June 14, 2016

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

1 0

[Ann] New version of Mocketry 3.0
by Denis Kudriashov June 13, 2016

June 13, 2016

I am glad to present simplest mocks for Pharo. In this version Mocketry is dramatically improved and changed. I try to provide most simple way to stub any message to any object and to verify any occurred behaviour. You can read full details in my blog http://dionisiydk.blogspot.fr/2016/04/new-version-of-mocketry-30.html Here is short example: mock := Mock new. mock *stub* someMessage *willReturn:* 1000. mock someMessage should be: 1000. mock *should got* someMessage. mock *should not* *got* anotherMessage. rect := 0@0 corner: 2@3. rect *stub* width willReturn: 1000. rect area should be: 3000 "area = width * height". rect *should got* width.

5 9

[pharo-project/pharo-core]
by GitHub June 13, 2016

June 13, 2016

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

1 0

[pharo-project/pharo-core] 82761e: 60081
by GitHub June 13, 2016

June 13, 2016

Branch: refs/heads/6.0 Home: https://github.com/pharo-project/pharo-core Commit: 82761ef6bfad01425d3d28814dd7b72a4395c1e3 https://github.com/pharo-project/pharo-core/commit/82761ef6bfad01425d3d2881… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2016-06-13 (Mon, 13 Jun 2016) Changed paths: M Rubric.package/RubAbstractTextArea.class/instance/event handling/yellowButtonActivity_.st M Rubric.package/RubLineNumberDisplayer.class/instance/event handling/yellowButtonActivity_.st R ScriptLoader60.package/ScriptLoader.class/instance/pharo - scripts/script60080.st A ScriptLoader60.package/ScriptLoader.class/instance/pharo - scripts/script60081.st R ScriptLoader60.package/ScriptLoader.class/instance/pharo - updates/update60080.st A ScriptLoader60.package/ScriptLoader.class/instance/pharo - updates/update60081.st M ScriptLoader60.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st M System-Sources.package/SourceFileArray.class/instance/private - accessing file streams/readStreamAtFileIndex_atPosition_ifPresent_ifAbsent_.st A System-Sources.package/SourceFileArray.class/instance/private/createReadOnlyFiles.st A System-Sources.package/SourceFileArray.class/instance/private/finishedReading_from_.st A System-Sources.package/SourceFileArray.class/instance/private/readOnlyQueueLimit.st M System-Sources.package/SourceFileArray.class/instance/public - file system operations/close.st M System-Sources.package/SourceFileArray.class/instance/public - file system operations/ensureOpen.st A Tests.package/SourceFileArrayTest.class/instance/testing/testChangesFileStream.st A Tests.package/SourceFileArrayTest.class/instance/testing/testSourcesFileStream.st Log Message: ----------- 60081 18448 Rubric: "Do not use #ifNotNilDo:ifNil:, #ifNil:ifNotNilDo:, #ifNotNilDo:" https://pharo.fogbugz.com/f/cases/18448 18468 Use readOnlyQueue when reading source files https://pharo.fogbugz.com/f/cases/18468 http://files.pharo.org/image/60/60081.zip

1 0

IMPORTANT: Proposal to create a github team for Voyage and MongoTalk
by Esteban Lorenzano June 13, 2016

June 13, 2016

Hi, (this mail is intended to Voyage/MongoTalk users and collaborators) Iâm spending a couple of days in Cologne, at 2Denker offices and I was talking Norbert about organisation of Voyage and the NoSQL driversâ¦ As a conclusion, we want to propose to move the Voyage and MongoTalk development to github, into a common team where other NoSQL drivers can eventually arrive (Voyage will incorporate other backends that might well be there). One reason from this is that I do not consider appropriate to keep Voyage into my repository, because is more a community project than a personal one. I want others to be able to participate more and I think this is the right step (also Dale is porting it to Gemstone soâ¦) Using github we can benefit of their tools to improve our process (issue tracker, travis and appveyor, etc.) and we will improve project visibility. So, we wanted to create âPharoNoSQL" team, and move all thereâ¦ then we will close sthub projects to avoid confusion and we will handle configurations and baselines same way as Yuriy does with QualityAssistance (so it will be available through catalog as always). Opinions? Esteban

11 17

[pharo-project/pharo-core]
by GitHub June 13, 2016

June 13, 2016

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

1 0

[pharo-project/pharo-core] 9ce64d: 60080
by GitHub June 13, 2016

June 13, 2016

Branch: refs/heads/6.0 Home: https://github.com/pharo-project/pharo-core Commit: 9ce64d0d95207eeef83586fa91e37b792ef74606 https://github.com/pharo-project/pharo-core/commit/9ce64d0d95207eeef83586fa… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2016-06-13 (Mon, 13 Jun 2016) Changed paths: A ConfigurationOfTxText.package/ConfigurationOfTxText.class/instance/versions/version2124_.st A ConfigurationOfVersionner.package/ConfigurationOfVersionner.class/instance/as yet unclassified/version21315_.st M ConfigurationOfVersionner.package/ConfigurationOfVersionner.class/instance/symbolic versions/stable_.st M Refactoring-Core.package/RBMoveInstVarToClassRefactoring.class/instance/accessing/oldClass_.st M Refactoring-Core.package/RBMoveInstVarToClassRefactoring.class/instance/transforming/collectSendersOfInstVar.st M Refactoring-Core.package/RBMoveInstVarToClassRefactoring.class/instance/transforming/transform.st R ScriptLoader60.package/ScriptLoader.class/instance/pharo - scripts/script60079.st A ScriptLoader60.package/ScriptLoader.class/instance/pharo - scripts/script60080.st R ScriptLoader60.package/ScriptLoader.class/instance/pharo - updates/update60079.st A ScriptLoader60.package/ScriptLoader.class/instance/pharo - updates/update60080.st M ScriptLoader60.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st R TxText-Model.package/TxModel.class/instance/private/applyAttribute_to_.st M Versionner-Core-Commands.package/MBRevertPackageCommand.class/instance/execute/execute.st M Versionner-Core-Commands.package/VSOpenRepositoryCommand.class/instance/accessing/repository.st M Versionner-Core-Commands.package/VSOpenRepositoryCommand.class/instance/execute/execute.st M Versionner-Core-DependenciesModel.package/MCModel2MTModelVisitor.class/instance/visiting/visitMCProjectAsRequiredProject_.st M Versionner-Core-DependenciesModel.package/MTPackage.class/instance/displaying/displayString.st M Versionner-Core-DependenciesModel.package/VersionnerToolBox.class/instance/spec creation/projectSpecFromRequiredProject_.st M Versionner-Core-Model.package/MBConfigurationInfo.class/instance/accessing/repositories.st M Versionner-Spec-Browser.package/VSGroupNode.class/instance/accessing/childNodeClassFor_.st M Versionner-Spec-Browser.package/VersionListModel.class/instance/initialization/initialize.st M Versionner-Spec-Browser.package/VersionnerProjectBrowser.class/instance/initialization/initializeWidgets.st M Versionner-Spec-Browser.package/VersionnerProjectBrowser.class/instance/refreshing/update.st M Versionner-Spec-Browser.package/VersionnerProjectPackagesPanel.class/instance/actions/addPackageRequirement.st M Versionner-Spec-Browser.package/VersionnerProjectPanel.class/instance/actions/addProjectLoadDirective.st M Versionner-Spec-Browser.package/VersionnerProjectPanel.class/instance/actions/browseSelectedProject.st M Versionner-Spec-Browser.package/VersionnerProjectPanel.class/instance/initialization/initializePresenter.st M Versionner-Spec-Browser.package/VersionnerProjectToolBar.class/instance/actions/executeWithDevWorkflow_.st M Versionner-Spec-Browser.package/VersionnerSpecBrowser.class/instance/initialization/initializeWidgets.st M Versionner-Spec-Browser.package/VersionnerToolBar.class/instance/initialization/initializePresenter.st Log Message: ----------- 60080 18474 move var to class refactoring broken II https://pharo.fogbugz.com/f/cases/18474 18476 update Versionner to 2.13.15 https://pharo.fogbugz.com/f/cases/18476 18072 TxModel >>#applyAttribute:to: sends unimplemented message https://pharo.fogbugz.com/f/cases/18072 http://files.pharo.org/image/60/60080.zip

1 0

[pharo-project/pharo-core] a72a72: 60079
by GitHub June 13, 2016

June 13, 2016

Branch: refs/heads/6.0 Home: https://github.com/pharo-project/pharo-core Commit: a72a728f22884bd1aab16e1ffa5b21a151dde715 https://github.com/pharo-project/pharo-core/commit/a72a728f22884bd1aab16e1f… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2016-06-13 (Mon, 13 Jun 2016) Changed paths: M Kernel.package/ClassDescription.class/instance/accessing method dictionary/addAndClassifySelector_withMethod_inProtocol_notifying_.st M NautilusRefactoring.package/NautilusRefactoring.class/instance/private-inst var/privateMoveInstVarToClass_.st R ScriptLoader60.package/ScriptLoader.class/instance/pharo - scripts/script60078.st A ScriptLoader60.package/ScriptLoader.class/instance/pharo - scripts/script60079.st R ScriptLoader60.package/ScriptLoader.class/instance/pharo - updates/update60078.st A ScriptLoader60.package/ScriptLoader.class/instance/pharo - updates/update60079.st M ScriptLoader60.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st Log Message: ----------- 60079 18473 move var to class refactoring broken https://pharo.fogbugz.com/f/cases/18473 18475 Do not announce method creation if the class is anonymous https://pharo.fogbugz.com/f/cases/18475 http://files.pharo.org/image/60/60079.zip

1 0

[pharo-project/pharo-core]
by GitHub June 13, 2016

June 13, 2016

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

1 0

A question on the catalog
by Esteban Lorenzano June 13, 2016

June 13, 2016

Hi, I was doing a pass on the catalogâ¦ I think is very negative that non-documented projects appear thereâ¦ because most people does not know what does projects are about and newcomers will find weird a project install tool with lots of projects without any description. So I was thinking on put an option âshow allâ and hide those projects by defaultâ¦ but now I think those projects SHOULD NOT BE VISIBLE AT ALL, as a way of: - offer better experience to non-power users, and - encourage people to actually document their projectsâ¦ is very annoying to have so much of them without any documentation. What do you think? cheers, Esteban

7 14