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

Re: [Pharo-dev] FileException only when opening image in certain way...

by Dale Henrichs

Mariano, I think your problem might have something to do with how the PWD env var is managed in OSX ... Check the value of the 'PWD' in your different examples and see if that sheds any light ... Dale On 7/26/16 5:49 AM, Mariano Martinez Peck wrote: > > > On Tue, Jul 26, 2016 at 9:48 AM, Mariano Martinez Peck > <marianopeck(a)gmail.com <mailto:marianopeck@gmail.com>> wrote: > > Hi guys, > > Davide Varvello reported me an issue with Fuel, failing to do: > > FLSerializer serialize: 'whatever' toFileNamed: 'demo.fuel'. > > Such a thing would bring an error like this: > > File>>openForWrite: > File>>openForWrite > File>>writeStream > File>>writeStreamDo: > FLPharo5Platform>>fileNamed:writeStreamDo: > FLSerializer>>serialize:toFileNamed: > FLSerializer class>>serialize:toFileNamed: > > The code is: > > FLPharo5Platform >> fileNamed: aFilename writeStreamDo: aBlock > ^ ((Smalltalk at: #File) named: aFilename) writeStreamDo: [ :stream | > stream binary. > aBlock value: stream ] > > > Now..I have tried to reproduce it but it happens only depending on > how the vm/image was started!!! And I only tested on OSX. > > Download the oneclick from here: > http://files.pharo.org/platform/Pharo5.0-mac.zip and see my results: > > 1) Executing VM from command line and passing the image as > argument: WORKS. > 2) Double clicking on the internal Pharo binary (which auto-starts > the image): WORKS > 3) Double clicking the internal Pharo image and then "Open With" > and I select the Pharo VM: DOES NOT WORK. > 4) Double clicking the Pharo one click: DOES NOT WORK. > > > I forgot to said... if you create the file in advance, with something > like: > > FileStream forceNewFileNamed: 'demo.fuel' do: [ :aStream | > FLSerializer serialize: 'whatever' on: aStream binary ] > > It does work in all cases. > > Has anyone experienced something like this? Looks like different > file / directory permissions when starting in different ways? > > Thanks in advance, > > > > -- > Mariano > http://marianopeck.wordpress.com > > > > > -- > Mariano > http://marianopeck.wordpress.com

July 26, 2016

Why nil needs class hierarchy protocol?

by Denis Kudriashov

Hi. Look at UndefinedObject instance side methods. You will see class hierarchy protocol. For example nil understands #subclasses message: nil subclasses "==> {ProtoObject}" It implemented like this: UndefinedObject >>subclassesDo: aBlock "Evaluate aBlock with all subclasses of nil. Others are not direct subclasses of Class." ^ Class subclassesDo: [:cl | cl isMeta ifTrue: [aBlock value: cl soleInstance]]. So my question is: why it needs to be like that? And does it really needed? I removed all this methods and not saw any problem.

July 26, 2016

Re: [Pharo-dev] FileException only when opening image in certain way...

by Mariano Martinez Peck

On Tue, Jul 26, 2016 at 9:48 AM, Mariano Martinez Peck < marianopeck(a)gmail.com> wrote: > Hi guys, > > Davide Varvello reported me an issue with Fuel, failing to do: > > FLSerializer serialize: 'whatever' toFileNamed: 'demo.fuel'. > > Such a thing would bring an error like this: > > File>>openForWrite: > File>>openForWrite > File>>writeStream > File>>writeStreamDo: > FLPharo5Platform>>fileNamed:writeStreamDo: > FLSerializer>>serialize:toFileNamed: > FLSerializer class>>serialize:toFileNamed: > > The code is: > > FLPharo5Platform >> fileNamed: aFilename writeStreamDo: aBlock > ^ ((Smalltalk at: #File) named: aFilename) writeStreamDo: [ :stream | > stream binary. > aBlock value: stream ] > > > Now..I have tried to reproduce it but it happens only depending on how the > vm/image was started!!! And I only tested on OSX. > > Download the oneclick from here: > http://files.pharo.org/platform/Pharo5.0-mac.zip and see my results: > > 1) Executing VM from command line and passing the image as argument: WORKS. > 2) Double clicking on the internal Pharo binary (which auto-starts the > image): WORKS > 3) Double clicking the internal Pharo image and then "Open With" and I > select the Pharo VM: DOES NOT WORK. > 4) Double clicking the Pharo one click: DOES NOT WORK. > > I forgot to said... if you create the file in advance, with something like: FileStream forceNewFileNamed: 'demo.fuel' do: [ :aStream | FLSerializer serialize: 'whatever' on: aStream binary ] It does work in all cases. > Has anyone experienced something like this? Looks like different file / > directory permissions when starting in different ways? > > Thanks in advance, > > > > -- > Mariano > http://marianopeck.wordpress.com > -- Mariano http://marianopeck.wordpress.com

July 26, 2016

FileException only when opening image in certain way...

by Mariano Martinez Peck

Hi guys, Davide Varvello reported me an issue with Fuel, failing to do: FLSerializer serialize: 'whatever' toFileNamed: 'demo.fuel'. Such a thing would bring an error like this: File>>openForWrite: File>>openForWrite File>>writeStream File>>writeStreamDo: FLPharo5Platform>>fileNamed:writeStreamDo: FLSerializer>>serialize:toFileNamed: FLSerializer class>>serialize:toFileNamed: The code is: FLPharo5Platform >> fileNamed: aFilename writeStreamDo: aBlock ^ ((Smalltalk at: #File) named: aFilename) writeStreamDo: [ :stream | stream binary. aBlock value: stream ] Now..I have tried to reproduce it but it happens only depending on how the vm/image was started!!! And I only tested on OSX. Download the oneclick from here: http://files.pharo.org/platform/Pharo5.0-mac.zip and see my results: 1) Executing VM from command line and passing the image as argument: WORKS. 2) Double clicking on the internal Pharo binary (which auto-starts the image): WORKS 3) Double clicking the internal Pharo image and then "Open With" and I select the Pharo VM: DOES NOT WORK. 4) Double clicking the Pharo one click: DOES NOT WORK. Has anyone experienced something like this? Looks like different file / directory permissions when starting in different ways? Thanks in advance, -- Mariano http://marianopeck.wordpress.com

July 26, 2016

[pharo-project/pharo-core] 155ec4: 60155

by GitHub

Branch: refs/heads/6.0 Home: https://github.com/pharo-project/pharo-core Commit: 155ec47963583298074f33a1abb53bfdda59e734 https://github.com/pharo-project/pharo-core/commit/155ec47963583298074f33a1… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2016-07-26 (Tue, 26 Jul 2016) Changed paths: M ConfigurationOfUnifiedFFI.package/ConfigurationOfUnifiedFFI.class/instance/symbolic versions/stable_.st A ConfigurationOfUnifiedFFI.package/ConfigurationOfUnifiedFFI.class/instance/versions/v0%5F22%5F2_.st M Kernel.package/Margin.class/instance/printing/printOn_.st M Morphic-Widgets-Pluggable.package/PluggableTextMorph.class/instance/actions/acceptBasic.st R ScriptLoader60.package/ScriptLoader.class/instance/pharo - scripts/script60154.st A ScriptLoader60.package/ScriptLoader.class/instance/pharo - scripts/script60155.st R ScriptLoader60.package/ScriptLoader.class/instance/pharo - updates/update60154.st A ScriptLoader60.package/ScriptLoader.class/instance/pharo - updates/update60155.st M ScriptLoader60.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st A Spec-Core.package/RadioButtonGroupModel.class/README.md A Spec-Core.package/RadioButtonGroupModel.class/class/example/example.st A Spec-Core.package/RadioButtonGroupModel.class/class/specs/defaultSpec.st A Spec-Core.package/RadioButtonGroupModel.class/definition.st A Spec-Core.package/RadioButtonGroupModel.class/instance/accessing/buttons.st A Spec-Core.package/RadioButtonGroupModel.class/instance/accessing/createWidgets.st A Spec-Core.package/RadioButtonGroupModel.class/instance/accessing/currentActivated.st A Spec-Core.package/RadioButtonGroupModel.class/instance/accessing/currentActivated_.st A Spec-Core.package/RadioButtonGroupModel.class/instance/accessing/rebuildWidget.st A Spec-Core.package/RadioButtonGroupModel.class/instance/initialization/initialize.st A Spec-Core.package/RadioButtonGroupModel.class/instance/initialization/initializePresenter.st A Spec-Core.package/RadioButtonGroupModel.class/instance/protocol-events/whenCanDeselectByClickChanged_.st A Spec-Core.package/RadioButtonGroupModel.class/instance/protocol-events/whenCurrentActivatedChanged_.st A Spec-Core.package/RadioButtonGroupModel.class/instance/protocol/addRadioButton_.st A Spec-Core.package/RadioButtonGroupModel.class/instance/protocol/canDeselectByClick.st A Spec-Core.package/RadioButtonGroupModel.class/instance/protocol/canDeselectByClick_.st A Spec-Core.package/RadioButtonGroupModel.class/instance/protocol/defaultOnce_.st A Spec-Core.package/RadioButtonGroupModel.class/instance/protocol/default_.st A Spec-Core.package/RadioButtonGroupModel.class/instance/protocol/linkRadioButton_.st A Spec-Core.package/RadioButtonGroupModel.class/instance/specs/dynamicLayout.st A Spec-Tests.package/RadioButtonGroupModelTest.class/README.md A Spec-Tests.package/RadioButtonGroupModelTest.class/definition.st A Spec-Tests.package/RadioButtonGroupModelTest.class/instance/running/setUp.st A Spec-Tests.package/RadioButtonGroupModelTest.class/instance/running/tearDown.st A Spec-Tests.package/RadioButtonGroupModelTest.class/instance/tests/testAddRadioButton.st A Spec-Tests.package/RadioButtonGroupModelTest.class/instance/tests/testAddingFocusOrder.st A Spec-Tests.package/RadioButtonGroupModelTest.class/instance/tests/testCurrentActivated.st A Spec-Tests.package/RadioButtonGroupModelTest.class/instance/tests/testDefault.st A Spec-Tests.package/RadioButtonGroupModelTest.class/instance/tests/testLinkRadioButton.st A Spec-Tests.package/RadioButtonGroupModelTest.class/instance/tests/testOpenAndClose.st A Spec-Tests.package/RadioButtonGroupModelTest.class/instance/tests/testRebuildWidget.st M Spec-Tests.package/TabManagerModelTest.class/instance/tabs creation/redMorphTab.st M Spec-Tests.package/TabModelTest.class/instance/instance creation/redMorphTab.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 Log Message: ----------- 60155 18734 Two tests failing in FFIExternalStructureTests https://pharo.fogbugz.com/f/cases/18734 18807 Improve Margin>>#printOn: https://pharo.fogbugz.com/f/cases/18807 18741 add RadioButtonGroupModel https://pharo.fogbugz.com/f/cases/18741 18775 Fix a typo https://pharo.fogbugz.com/f/cases/18775 http://files.pharo.org/image/60/60155.zip

July 26, 2016

[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