- Pharo-dev - lists.pharo.org

[pharo-project/pharo-core]

by GitHub

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

July 26, 2016

Re: [Pharo-dev] Pharo 5.0 Tiny Feature Request

by Sean P. DeNigris

Sean P. DeNigris wrote > Reviewed by the monkey. Please integrate at your earliest convenience :) > https://pharo.fogbugz.com/f/cases/18757/Simple-Shell-Command-Eval-for-5-0 Bump :) [waiting patiently while all my build scripts are broken in Pharo 5.0] ----- Cheers, Sean -- View this message in context: http://forum.world.st/Pharo-5-0-Tiny-Feature-Request-tp4901682p4907992.html Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

July 26, 2016

Re: [Pharo-dev] Nautilus... switching from hierarchy to package

by Denis Kudriashov

Hi. Could you explain more? (your scenario works for me) 2016-07-25 20:51 GMT+02:00 stepharo <stepharo(a)free.fr>: > Hi > > I would like to know what you think. > > I found annoying that when I'm browsing an hierarchy I cannot switch to > the package view > > when I click on a class outside of the current package. > > > Stef > > >

July 26, 2016

Re: [Pharo-dev] git feature request

by Serge Stinckwich

On Fri, Jul 22, 2016 at 10:57 PM, Nicolas Passerini <npasserini(a)gmail.com> wrote: > In Iceberg you currently can: > > 1) Download a project using metacello github:// protocol > 2) Use Iceberg to make it "writable" (i.e. transform it to an Iceberg > repository, pointing to the same remote repository), this is just one step. > 3) Commit and push using the new repo, etc. Thank you for all the work you are doing ! I will try to use Iceberg to made a report. > What it is not done yet is the integration with github (or whatever) fork/pr > capabilities, it is in the roadmap but not just now because those are not > standard git operations, so it will involve communicating directly to the > github rest api (and others, we will not be attached to git nor github). > > So you should add two extra steps which are forking and pull requesting from > outside Pharo (or requesting access to the respository to commit right > there). Be careful to not linked too much Iceberg to github specificities. PR are github specificities. Branches can be transformed as PR automatically on github. > This should be a normal flow for contributing to a tool you are using, right > now is partially supported to be done from a git(hub) repository, I intend > to extend it to be done also from tools installed from smalltalkhub, etc. > Should be the same thing. > > > About the discussion between commits and PRs... I've seen both models > working right, I think that both have their advantages and I would like to > build tools to support both schemas. Personally, I prefer to give people the > possibility to commit, but even so I am used to work with PRs, because it > really helps the code review. Yes you can have your own branch, and I can > see the changes introduced by any commit, but usually is a PR that moves > people towards looking to the code, and I think that it is a nice model that > works well in practice. > In other projects, you have to fork, commit there, then PR, if two people > want to work together in an issue is not obvious how to do it... it adds > more bureaucracy, it might be necessary for a large project like Pharo, but > normally I prefer to avoid it. As you know git is agnostic in terms of workflow and several workflows have been proposed, like : centralized workflow, feature branch workflow, etc ... Do Iceberg will enforce some specific workflow ? I guess workflows for Pharo-dev and others projects might be different. Regards, -- Serge Stinckwich UCBN & UMI UMMISCO 209 (IRD/UPMC) Every DSL ends up being Smalltalk http://www.doesnotunderstand.org/

July 26, 2016

Nautilus... switching from hierarchy to package

by stepharo

Hi I would like to know what you think. I found annoying that when I'm browsing an hierarchy I cannot switch to the package view when I click on a class outside of the current package. Stef

July 25, 2016

Re: [Pharo-dev] pharo 5 crashing

by Max Leske

How large are those images? There was a VM issue (I think itâs fixed in trunk) that prevented large images from opening. You could try using the latest VM (http://files.pharo.org/vm/pharo-spur32/) Cheers, Max > On 25 Jul 2016, at 12:42, Sean Glazier <sglazier456(a)gmail.com> wrote: > > Hi, > > I have been saving and restarting my images all night and I carefully do a save as regularly in case I toast an image. This morning I can not seem to start up any of my images including a clean one. Head scratch. std err has it dying in the weak array finalization process. Could I get enlightened as to why? > > [31m > [0mProcess>>terminate > WeakArray class>>restartFinalizationProcess > WeakArray class>>startUp: > ClassSessionHandler>>startup: > [ :each | each startup: isImageStarting ] in WorkingSession>>runStartup: in Block: [ :each | each startup: isImageStarting ] > [ aBlock value: each ] in [ :each | > [ aBlock value: each ] > on: Exception > do: [ :error | self errorHandler handleError: error ] ] in WorkingSession>>runList:do: in Block: [ aBlock value: each ] > BlockClosure>>on:do: > [ :each | > [ aBlock value: each ] > on: Exception > do: [ :error | self errorHandler handleError: error ] ] in WorkingSession>>runList:do: in Block: [ :each | ... > Array(SequenceableCollection)>>do: > WorkingSession>>runList:do: > WorkingSession>>runStartup: > WorkingSession>>start: > SessionManager>>snapshot:andQuit: > SmalltalkImage>>snapshot:andQuit: > [ Smalltalk snapshot: true andQuit: false ] in WorldState class>>saveSession in Block: [ Smalltalk snapshot: true andQuit: false ] > BlockClosure>>ensure: > CursorWithMask(Cursor)>>showWhile: > WorldState class>>saveSession > [ | selArgCount | > "show cursor in case item opens a new MVC window" > (selArgCount := selector numArgs) = 0 > ifTrue: [ target perform: selector ] > ifFalse: [ selArgCount = arguments size > ifTrue: [ target perform: selector withArguments: arguments ] > ifFalse: [ target perform: selector withArguments: (arguments copyWith: evt) ]. > self showShortcut ]. > self changed ] in ToggleMenuItemMorph(MenuItemMorph)>>invokeWithEvent: in Block: [ | selArgCount |... > BlockClosure>>ensure: > Cursor>>showWhile: > ToggleMenuItemMorph(MenuItemMorph)>>invokeWithEvent: > ToggleMenuItemMorph(MenuItemMorph)>>mouseUp: > ToggleMenuItemMorph(MenuItemMorph)>>handleMouseUp: > MouseButtonEvent>>sentTo: > ToggleMenuItemMorph(Morph)>>handleEvent: > MorphicEventDispatcher>>dispatchDefault:with: > MorphicEventDispatcher>>handleMouseUp: > MouseButtonEvent>>sentTo: > [ ^ anEvent sentTo: self ] in MorphicEventDispatcher>>dispatchEvent:with: in Block: [ ^ anEvent sentTo: self ] > [0m > > Kind Regards, > > Sean Glazier >

July 25, 2016

[pharo-project/pharo-core]

by GitHub

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

July 25, 2016

[pharo-project/pharo-core] daa0bf: 60154

by GitHub

Branch: refs/heads/6.0 Home: https://github.com/pharo-project/pharo-core Commit: daa0bfae35c7694f246493ecd1fe7909d665408c https://github.com/pharo-project/pharo-core/commit/daa0bfae35c7694f246493ec… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2016-07-25 (Mon, 25 Jul 2016) Changed paths: A Morphic-Widgets-Pluggable.package/ManifestMorphicWidgetsPluggable.class/README.md A Morphic-Widgets-Pluggable.package/ManifestMorphicWidgetsPluggable.class/class/code-critics/ruleEmptyExceptionHandlerRuleV1FalsePositive.st A Morphic-Widgets-Pluggable.package/ManifestMorphicWidgetsPluggable.class/class/code-critics/ruleSentNotImplementedRuleV1FalsePositive.st A Morphic-Widgets-Pluggable.package/ManifestMorphicWidgetsPluggable.class/definition.st R Morphic-Widgets-Pluggable.package/PluggableTextFieldMorph.class/instance/actions/accept.st M Morphic-Widgets-Pluggable.package/PluggableTreeMorph.class/instance/node access/hasNodeContents_.st R ScriptLoader60.package/ScriptLoader.class/instance/pharo - scripts/script60153.st A ScriptLoader60.package/ScriptLoader.class/instance/pharo - scripts/script60154.st R ScriptLoader60.package/ScriptLoader.class/instance/pharo - updates/update60153.st A ScriptLoader60.package/ScriptLoader.class/instance/pharo - updates/update60154.st M ScriptLoader60.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st M Spec-Layout.package/AbstractSpecLayoutAction.class/definition.st A Spec-Layout.package/AbstractSpecLayoutAction.class/instance/accesing/arguments.st A Spec-Layout.package/AbstractSpecLayoutAction.class/instance/accesing/arguments_.st A Spec-Layout.package/AbstractSpecLayoutAction.class/instance/accesing/selector.st A Spec-Layout.package/AbstractSpecLayoutAction.class/instance/accesing/selector_.st M Spec-Layout.package/SpecColumnLayout.class/definition.st M Spec-Layout.package/SpecColumnLayout.class/instance/private/autoFractionComputation.st M Spec-Layout.package/SpecLayout.class/definition.st M Spec-Layout.package/SpecLayoutSend.class/definition.st R Spec-Layout.package/SpecLayoutSend.class/instance/accessing/arguments.st R Spec-Layout.package/SpecLayoutSend.class/instance/accessing/arguments_.st R Spec-Layout.package/SpecLayoutSend.class/instance/accessing/selector.st R Spec-Layout.package/SpecLayoutSend.class/instance/accessing/selector_.st M Spec-Layout.package/SpecRowLayout.class/definition.st M Spec-Layout.package/SpecRowLayout.class/instance/private/manualFractionComputation.st M Spec-Layout.package/SpecTableLayoutSend.class/definition.st R Spec-Layout.package/SpecTableLayoutSend.class/instance/accessing/arguments.st R Spec-Layout.package/SpecTableLayoutSend.class/instance/accessing/arguments_.st R Spec-Layout.package/SpecTableLayoutSend.class/instance/accessing/selector.st R Spec-Layout.package/SpecTableLayoutSend.class/instance/accessing/selector_.st Log Message: ----------- 60154 18812 epicea is not respecting the new pharo-local directory https://pharo.fogbugz.com/f/cases/18812 18770 Add a manifest and fix critics https://pharo.fogbugz.com/f/cases/18770 18772 Fix critics in SpecLayout https://pharo.fogbugz.com/f/cases/18772 http://files.pharo.org/image/60/60154.zip

July 25, 2016

[pharo-project/pharo-core] bafa4c: 60153

by GitHub

Branch: refs/heads/6.0 Home: https://github.com/pharo-project/pharo-core Commit: bafa4c840ce118b84a40f5ffba50bdd7968412a0 https://github.com/pharo-project/pharo-core/commit/bafa4c840ce118b84a40f5ff… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2016-07-25 (Mon, 25 Jul 2016) Changed paths: R ScriptLoader60.package/ScriptLoader.class/instance/pharo - scripts/script60152.st A ScriptLoader60.package/ScriptLoader.class/instance/pharo - scripts/script60153.st R ScriptLoader60.package/ScriptLoader.class/instance/pharo - updates/update60152.st A ScriptLoader60.package/ScriptLoader.class/instance/pharo - updates/update60153.st M ScriptLoader60.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st M UnifiedFFI-Tests.package/FFIExternalStructureTests.class/instance/tests/testExternalStructWithArray.st M UnifiedFFI-Tests.package/FFIExternalStructureTests.class/instance/tests/testNestedStructureWithArray.st M UnifiedFFI-Tests.package/FFIExternalStructureTests.class/instance/tests/testStructWithArray.st M UnifiedFFI-Tests.package/FFITestArrayStructure.class/instance/accessing structure variables/byte10_.st M UnifiedFFI-Tests.package/FFITestArrayStructure.class/instance/accessing structure variables/char5_.st Log Message: ----------- 60153 18734 Two tests failing in FFIExternalStructureTests https://pharo.fogbugz.com/f/cases/18734 http://files.pharo.org/image/60/60153.zip

July 25, 2016

[pharo-project/pharo-core]

by GitHub

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

July 25, 2016