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

Experience makers
by stepharo Nov. 4, 2014

Nov. 4, 2014

Dear experience makers (Martin, yuriy, tommaso, roberto and others,) you would like to have many people doing your experience.... I know you would love that. Here is my suggestion: ease the use of new images. Each time I want to load the projects I'm hacking and I do not have a jenkins for it, it is painful (setting up the repos.... loading....). So I do not change often images and I'm reluctant to load new stuff (like your experiments) - build a simple little tool that could be integrated in pharo and would do the following: - let the user (un)/select some packages or configurations - generate a script to reload these configurations really easily This way I can load my project and then you provide a script for your experience. and after I can reload my project with your material for experience in my new image. Right now I do not like to hack the preference file because I have images where I do not want any interference So is my proposal clear? Stef

5 8

VersionnerRepositoriesManager - Why clear okAction?
by Sean P. DeNigris Nov. 3, 2014

Nov. 3, 2014

No class is safe from my wrath he he... VersionnerRepositoriesManager class>>#open | dialog | dialog := remotesUI openDialogWithSpec. dialog okAction: [ ] - why were we wiping the okAction? "dialog okAction: [ ]" does not reveal any intention. At minimum, a comment would be good - it would be good to return something here so users can customize more easily. Even though this is tightly integrated with Versionner, a tiny bit of care makes the system more easily extensible. We should record some patterns here... ----- Cheers, Sean -- View this message in context: http://forum.world.st/VersionnerRepositoriesManager-Why-clear-okAction-tp47… Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

2 2

[pharo-project/pharo-core] dd006c: 40336
by GitHub Nov. 2, 2014

Nov. 2, 2014

Branch: refs/heads/4.0 Home: https://github.com/pharo-project/pharo-core Commit: dd006cefd42a50c221e5dbd395bbbd7788aeafee https://github.com/pharo-project/pharo-core/commit/dd006cefd42a50c221e5dbd3… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2014-10-28 (Tue, 28 Oct 2014) Changed paths: A ScriptLoader40.package/ScriptLoader.class/instance/pharo - scripts/script336.st A ScriptLoader40.package/ScriptLoader.class/instance/pharo - updates/update40336.st M ScriptLoader40.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st M Traits.package/TClassDescription.class/instance/organization updating/notifyOfRecategorizedSelector_from_to_.st Log Message: ----------- 40336 14337 Removing a trait usage raises an exception (2nd attempt) https://pharo.fogbugz.com/f/cases/14337 http://files.pharo.org/image/40/40336.zip

6 12

Trouble while defining a customized tab in GT inspector
by Luc Fabresse Nov. 2, 2014

Nov. 2, 2014

Hi all, I try to play with the GT inspector (thx Andrei and Doru for the great hands on session @ ESUG'14!). In short, I try to add a customized tab for Persons objects using a PersonUI facade and a subclass of GTObjectVariablesBrowser (ok I can explain why if needed ;-)). Like that: Person>>gtInspectorCustomUIIn: composite <gtInspectorPresentationOrder: 5> ^ (composite custom: (MyGTCustomObjectVariablesBrowser new startOn: (PersonUI on: self) )) " <----- HERE" title: 'Customized view'; yourself But, the #variableValuePairsFor: message is not sent to the PersonUI object but to the Person object even if I passed a PersonUI one to the #startOn: method (cf. HERE). startOn: seems to not store properly the object to use afterwards or I missed a something. Did I? please find a code sample attached if needed. Try: Person new inspect Thx for any hint, Cheers, #Luc

2 2

Time Series in Smalltalk
by Blondeau Vincent Nov. 1, 2014

Nov. 1, 2014

Hi ! I am looking for a time series library available for Pharo. Serge Stinckwich asked the same thing a year ago (http://lists.pharo.org/pipermail/pharo-dev_lists.pharo.org/2013-February/07…) and I would know whether any improvement has been made since? Thanks Cheers, Vincent BLONDEAU ________________________________ 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.

4 15

Nw Cog VMs available
by Eliot Miranda Oct. 31, 2014

Oct. 31, 2014

...at http://www.mirandabanda.org/files/Cog/VM/VM.r3120/. These contain a few important bug fixes to Spur which will increase stability. CogVM binaries as per VMMaker.oscog-eem.916 Spur: Reimplement deriving the accessorDepth and retrying primitives on primitive failure machinery. Always take the primitive index from newMethod (setting newMethod to a SmallInteger for primitiveDoPrimitiveWithArgs. Have the Cogit always set primitiveFunctionPointer and newMethod for the retry. Add isNonInteger(Non)Immediate: and use it in several of the integer conversion routines that were missing code to exclude Character immediates, with fatal consequences. With these changes the Pharo 4 test suite runs without crashing on the latest Pharo Spur boot image. Fix processWeakSurvivor: so that it answers whether a weak object refers to a young object. The old version only scanned weak fields, ignoring refs to young objs from strong fields. Move check for valid classes from findClassOfMethod: forReceiver: into findClassContainingMethod:startingAt:, hence making findClassOfMethod:forReceiver: et al more robust. Implement safe access to contexts and methods when creating image segments (since internally married contexts and jitted methods have hidden state encoded in odd ways). As a result: Fix baaad bug in SpurMemoryManager>>lastPointerOf: for contexts, caused by transcription from (New)ObjectMemory where the method works on a wing and a prayer because BaseHeaderSize = BytesPerOop. And I can't be arsed to fix it. Fix baaad bug in accessibleObjectAfter: and add an assert to primitiveNextObject to catch similar bugs. Can now enumerate objects in new space, which will sort-of work, but code should really use allObjects. Will fix at the image level as time allows. Eliminate isInSurvivorSpace: in favour of the identical isInPastSpace:. All: Refactor decoding of context instruction pointers so there is only one copy of the code. -- best, Eliot

1 0

[pharo-project/pharo-core]
by GitHub Oct. 31, 2014

Oct. 31, 2014

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

1 0

[pharo-project/pharo-core] 016101: 40344
by GitHub Oct. 31, 2014

Oct. 31, 2014

Branch: refs/heads/4.0 Home: https://github.com/pharo-project/pharo-core Commit: 01610158cd63c7eba02bdb886ede5ae5df90b43c https://github.com/pharo-project/pharo-core/commit/01610158cd63c7eba02bdb88… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2014-10-31 (Fri, 31 Oct 2014) Changed paths: R KeyChainTest.package/ManifestKeyChainTest.class/README.md R KeyChainTest.package/ManifestKeyChainTest.class/class/meta data/rejectClasses.st R KeyChainTest.package/ManifestKeyChainTest.class/class/meta data/rejectRules.st R KeyChainTest.package/ManifestKeyChainTest.class/class/meta data/ruleLongMethodsRuleV1FalsePositive.st R KeyChainTest.package/ManifestKeyChainTest.class/definition.st R KeyChainTest.package/PharoUserPermissionsTest.class/README.md R KeyChainTest.package/PharoUserPermissionsTest.class/definition.st R KeyChainTest.package/PharoUserPermissionsTest.class/instance/tests/testCanBrowse.st R KeyChainTest.package/PharoUserPermissionsTest.class/instance/tests/testCanDebug.st R KeyChainTest.package/PharoUserPermissionsTest.class/instance/tests/testCanDropOSFile.st R KeyChainTest.package/PharoUserPermissionsTest.class/instance/tests/testCanEditCode.st R KeyChainTest.package/PharoUserPermissionsTest.class/instance/tests/testCanEditUser.st R KeyChainTest.package/PharoUserPermissionsTest.class/instance/tests/testCanEvaluateCode.st R KeyChainTest.package/PharoUserPermissionsTest.class/instance/tests/testCanInspect.st R KeyChainTest.package/PharoUserPermissionsTest.class/instance/tests/testCanRunStartupScript.st R KeyChainTest.package/PharoUserPermissionsTest.class/instance/tests/testCanSaveImage.st R KeyChainTest.package/PharoUserPermissionsTest.class/instance/tests/testCanShowMorphHalo.st R KeyChainTest.package/PharoUserPermissionsTest.class/instance/tests/testIsRoot.st R KeyChainTest.package/PharoUserTest.class/README.md R KeyChainTest.package/PharoUserTest.class/definition.st R KeyChainTest.package/PharoUserTest.class/instance/tests/testUsername.st A ScriptLoader40.package/ScriptLoader.class/instance/pharo - scripts/script344.st A ScriptLoader40.package/ScriptLoader.class/instance/pharo - updates/update40344.st M ScriptLoader40.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st A UserManager-Tests.package/ManifestKeyChainTest.class/README.md A UserManager-Tests.package/ManifestKeyChainTest.class/class/meta data/rejectClasses.st A UserManager-Tests.package/ManifestKeyChainTest.class/class/meta data/rejectRules.st A UserManager-Tests.package/ManifestKeyChainTest.class/class/meta data/ruleLongMethodsRuleV1FalsePositive.st A UserManager-Tests.package/ManifestKeyChainTest.class/definition.st A UserManager-Tests.package/PharoUserPermissionsTest.class/README.md A UserManager-Tests.package/PharoUserPermissionsTest.class/definition.st A UserManager-Tests.package/PharoUserPermissionsTest.class/instance/tests/testCanBrowse.st A UserManager-Tests.package/PharoUserPermissionsTest.class/instance/tests/testCanDebug.st A UserManager-Tests.package/PharoUserPermissionsTest.class/instance/tests/testCanDropOSFile.st A UserManager-Tests.package/PharoUserPermissionsTest.class/instance/tests/testCanEditCode.st A UserManager-Tests.package/PharoUserPermissionsTest.class/instance/tests/testCanEditUser.st A UserManager-Tests.package/PharoUserPermissionsTest.class/instance/tests/testCanEvaluateCode.st A UserManager-Tests.package/PharoUserPermissionsTest.class/instance/tests/testCanInspect.st A UserManager-Tests.package/PharoUserPermissionsTest.class/instance/tests/testCanRunStartupScript.st A UserManager-Tests.package/PharoUserPermissionsTest.class/instance/tests/testCanSaveImage.st A UserManager-Tests.package/PharoUserPermissionsTest.class/instance/tests/testCanShowMorphHalo.st A UserManager-Tests.package/PharoUserPermissionsTest.class/instance/tests/testIsRoot.st A UserManager-Tests.package/PharoUserTest.class/README.md A UserManager-Tests.package/PharoUserTest.class/definition.st A UserManager-Tests.package/PharoUserTest.class/instance/tests/testUsername.st Log Message: ----------- 40344 14330 rename KeyChainTest --> KeyChainTests so it gets unloaded by #cleanUpForProduction https://pharo.fogbugz.com/f/cases/14330 14362 Iconset is wrong https://pharo.fogbugz.com/f/cases/14362 http://files.pharo.org/image/40/40344.zip

1 0

Zinc running on privileged ports
by Christophe Demarey Oct. 31, 2014

Oct. 31, 2014

Hello, I just tried to get a simple Zinc server running on the standard HTTP port (80) and it is not working. ZnServer startDefaultOn: 80 My image was run with a standard user. As the standard HTTP port is a privileged port (each port number < 1024 is a privileged port), I tried to run it through sudo. It is not working with PharoLauncher (loss of permissions with the process fork?) but works by running the image directly. The thing that is strange to me is that if I try to run Zinc on a port with not enough permissions, I do not get an error. I saw a test of the socket validity in ZnNetworkingUtils>>serverSocketOn: but I think it is not catching the permissions problem. Is it difficult to detect? If not, it would be good to have an exception if the specified port cannot be used. Christophe.

2 2

[pharo-project/pharo-core]
by GitHub Oct. 31, 2014

Oct. 31, 2014

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

1 0