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

rogue window instances

by Tudor Girba

Hi, In the latest Pharo #50125, I do this from the command line: ./pharo Pharo.image eval "SystemWindow allSubInstances" ==> an OrderedCollection(a RubFindReplaceDialogWindow(534511616) a GLMSystemWindow(58720256)) There are two strange things: - the GLMSystemWindow has a nil model, although if you inspect it, it visually looks like a Playground window (normal playgrounds have a GTPlayground instance as model). - the RubFindReplaceDialogWindow has findTextField as nil (while normally it should be some PluggableTextFieldMorph). Does anyone know where these come from? Cheers, Doru -- www.tudorgirba.com "Every thing has its own flow"

June 21, 2015

Re: [Pharo-dev] http://mc.stfx.eu/ZincHTTPComponents

by stepharo

+ 1 Le 20/6/15 12:48, Damien Cassou a Ã©crit : > Sven Van Caekenberghe <sven(a)stfx.eu> writes: > >> Just a quick note to help you all keep your sanity: the last days >> there was a problem with the http://mc.stfx.eu/ZincHTTPComponents >> repository. It hit 1000 entries, which was an internal limit for AWS >> S3 that is used as the backing store for mc.stfx.eu. I had to work >> around that (see Zinc-AWS if you are interested). Of course, it took a >> while to realise what was happening, it was all pretty weird ;-) TLDR; >> things should be back to normal now. > > > thank you very much Sven. Your work is important. >

June 21, 2015

Re: [Pharo-dev] getting the history of a method?

by stepharo

Alex from memory an activeRing definition is always returning the current method definition. aspassive I guess is creating one that represents a method at a certain point. and yes we should continue to improving ring. > Hi! > > I have the following: > > Object subclass: #A. > A compile: 'foo ^ 5'. > A compile: 'foo ^ 10'. > > (A >> #foo) asHistoricalRingDefinition > > But I have no idea how I can get the two time stamps of A>>foo and the two source code? did you check the api? > > I cannot figure out what is the difference between asPassiveRingDefinition, asActiveRingDefinition, asFullRingDefinitionâ¦ > These methods all return a RGMethodDefinition. Yes what is different is the way they access and return their source. > > Cheers, > Alexandre

June 21, 2015

crm in pharo?

by Tudor Girba

Hi, Is there any CRM (customer relationship manager) library for Pharo? Cheers, Tudor -- www.tudorgirba.com "Every thing has its own flow"

June 21, 2015

[pharo-project/pharo-core]

by GitHub

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

June 21, 2015

[pharo-project/pharo-core] 75debe: 50125

by GitHub

Branch: refs/heads/5.0 Home: https://github.com/pharo-project/pharo-core Commit: 75debe796eb007604b61ccb80f86b43fbc6081f8 https://github.com/pharo-project/pharo-core/commit/75debe796eb007604b61ccb8… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2015-06-21 (Sun, 21 Jun 2015) Changed paths: R AST-Core.package/ManifestASTCore.class/class/meta data/rejectClasses.st R Fuel.package/ManifestFuel.class/class/meta data/rejectClasses.st R Fuel.package/ManifestFuel.class/class/meta data/rejectRules.st R Kernel.package/ManifestKernel.class/class/meta data/rejectClasses.st R Kernel.package/ManifestKernel.class/class/meta data/rejectRules.st A Kernel.package/PackageManifest.class/class/code-critics/rejectClasses.st A Kernel.package/PackageManifest.class/class/code-critics/rejectRules.st R Kernel.package/PackageManifest.class/instance/code-critics/rejectClasses.st R Kernel.package/PackageManifest.class/instance/code-critics/rejectRules.st R Kernel.package/PackageManifest.class/instance/comparing/=.st R Kernel.package/PackageManifest.class/instance/comparing/hash.st R KernelTests.package/ManifestKernelTests.class/class/meta data/rejectClasses.st R KernelTests.package/ManifestKernelTests.class/class/meta data/rejectRules.st R Manifest-Core.package/ManifestManifestCore.class/class/meta data/rejectClasses.st M Manifest-Core.package/TheManifestBuilder.class/instance/accessing/manifest.st M Manifest-Core.package/TheManifestBuilder.class/instance/private/compileSelector_returnValue_.st M Manifest-Core.package/extension/RPackage/instance/packageManifest.st M Nautilus-Tests.package/PackageTreeNautilusTest.class/instance/tests/testPackagePatternStringRootPackageTag.st R Nautilus.package/MethodIsScriptAction.class/instance/order/isActionHandled.st R Nautilus.package/MethodIsScriptAction.class/instance/order/isScriptMethod.st R Nautilus.package/MethodIsScriptAction.class/instance/order/privateActionIcon.st R Nautilus.package/MethodIsScriptAction.class/instance/order/runScript.st A Nautilus.package/MethodIsScriptAction.class/instance/private - accessing/pragmaName.st A Nautilus.package/MethodIsScriptAction.class/instance/private - accessing/privateActionIcon.st A Nautilus.package/MethodIsScriptAction.class/instance/private - actions/runScript.st A Nautilus.package/MethodIsScriptAction.class/instance/private - actions/runScriptForPragma_.st A Nautilus.package/MethodIsScriptAction.class/instance/testing/isActionHandled.st M Nautilus.package/MethodIsScriptWithArgumentAction.class/definition.st R Nautilus.package/MethodIsScriptWithArgumentAction.class/instance/order/actionOrder.st R Nautilus.package/MethodIsScriptWithArgumentAction.class/instance/order/isActionHandled.st R Nautilus.package/MethodIsScriptWithArgumentAction.class/instance/order/isScriptMethodWithScript.st R Nautilus.package/MethodIsScriptWithArgumentAction.class/instance/order/privateActionIcon.st R Nautilus.package/MethodIsScriptWithArgumentAction.class/instance/order/runScript.st A Nautilus.package/MethodIsScriptWithArgumentAction.class/instance/private - accessing/pragmaName.st A Nautilus.package/MethodIsScriptWithArgumentAction.class/instance/private - actions/runScriptForPragma_.st A Nautilus.package/MethodIsScriptWithArgumentAction.class/instance/testing/isActionHandled.st R OpalCompiler-Core.package/ManifestOpalCompilerCore.class/class/meta data/rejectClasses.st A Ring-Core-Kernel.package/RGMethodDefinition.class/instance/accessing/ast.st R ScriptLoader50.package/ScriptLoader.class/instance/pharo - scripts/script50124.st A ScriptLoader50.package/ScriptLoader.class/instance/pharo - scripts/script50125.st R ScriptLoader50.package/ScriptLoader.class/instance/pharo - updates/update50124.st A ScriptLoader50.package/ScriptLoader.class/instance/pharo - updates/update50125.st M ScriptLoader50.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st R UserManager-Tests.package/ManifestKeyChainTest.class/class/meta data/rejectClasses.st R UserManager-Tests.package/ManifestKeyChainTest.class/class/meta data/rejectRules.st Log Message: ----------- 50125 15812 MessageNotUnderstood: RGMethodDefinition>>ast (Suggestions expects it) https://pharo.fogbugz.com/f/cases/15812 15791 Cleanup Script actions for methods https://pharo.fogbugz.com/f/cases/15791 15557 New PackageManifests should be classes, not instances https://pharo.fogbugz.com/f/cases/15557 http://files.pharo.org/image/50/50125.zip

June 21, 2015

Re: [Pharo-dev] New Cog VMs available

by Attila Magyar

Eliot Miranda-2 wrote > ... at http://www.mirandabanda.org/files/Cog/VM/VM.r3386 > > CogVM binaries as per VMMaker.oscog-eem.1370/r3386 > > Add the ARMv5/ARMv6 Cog Spur JIT VM! Thanks. This is a huge improvement compared to the stack vm. I've just tried it on my Raspberry pi, with this image http://files.pharo.org/image/50/latest-spur32.zip. arm cog on raspberry pi 2 model b: 1 tinyBenchmarks. -> '110726643 bytecodes/sec; 7349080 sends/sec' stackvm on raspberry pi 2 model b: 1 tinyBenchmarks. -> '15108593 bytecodes/sec; 865704 sends/sec' My app also runs noticeably faster. -- View this message in context: http://forum.world.st/New-Cog-VMs-available-tp4833350p4833366.html Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

June 21, 2015

Re: [Pharo-dev] New Cog VMs available

by Stephan Eggermont

On 21-06-15 03:26, Eliot Miranda wrote: > ... at http://www.mirandabanda.org/files/Cog/VM/VM.r3386 > > CogVM binaries as per VMMaker.oscog-eem.1370/r3386 > > Add the ARMv5/ARMv6 Cog Spur JIT VM! Oh, that's great news! Thanks to all who made this possible. Stephan

June 21, 2015

Re: [Pharo-dev] getting the history of a method?

by Nicolai Hess

2015-06-21 2:47 GMT+02:00 Alexandre Bergel <alexandre.bergel(a)me.com>: > Hi! > > I have the following: > > Object subclass: #A. > A compile: 'foo ^ 5'. > A compile: 'foo ^ 10'. > > (A >> #foo) asHistoricalRingDefinition > > But I have no idea how I can get the two time stamps of A>>foo and the two > source code? > I think we don't have this yet. (Maybe we don't need this, but we need better tool support for Ring). You can see some examples how I played with RGMethods in the version browser scanVersionsOf: method class: aClass meta: meta category: cat selector: aSelector and in ChangeSorterApplication createRingMethodForRemovedSelector: aSelector inClass: aClass > > I cannot figure out what is the difference between > asPassiveRingDefinition, asActiveRingDefinition, asFullRingDefinitionâ¦ > These methods all return a RGMethodDefinition. > Yes, all are RGMethodDefinitions, the difference is "where the real data is" active ring -> image ( active ring method sourceCode -> code of the actual compiled method) historical ring -> source/changes files ( historical ring method sourceCode -> code fetched from source/changes file (needs a valid sourcePointer)) passive ring -> nowhere, init by instantiation (passive ring method sourceCode -> whatever was provided by the RGMethodDefinition construction) full ring definition controls what other elements are retrieved as ringdefinition, For example every method has a package, but not every RGMethodDefinitions needs to now or has a package: (A>>#foo) asRingDefinition package. -> nil (A>>#foo) asFullRingDefinition package. -> "RGPackage(Unclassified)" > > Cheers, > Alexandre > -- > _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: > Alexandre Bergel http://www.bergel.eu > ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > > > > >

June 21, 2015

Re: [Pharo-dev] Pharo 4 and Roassal

by Alejandro Infante

I have changed the blessing of Roassal2 version 1.12 and 1.13 to #broken, so now you will install by default version 1.11 that works out of the box in Pharo4. I have just tested this so feel free to ask us if you have any problems. We will restore the blessing of 1.12 and 1.13 to #stable when ConficurationOfGlamourCore is fixed. Cheers, Alejandro > On Jun 20, 2015, at 11:05 PM, Alejandro Infante <alejandroinfante91(a)gmail.com> wrote: > > It is loaded in Pharo4, but in order to verify that it is up to date, Metacello needs to check the ConfigurationOf for the required version and that fails. > > Alejandro > >> On Jun 20, 2015, at 10:29 PM, Alexandre Bergel <alexandre.bergel(a)me.com> wrote: >> >> I think this is because the latest glamour core was not in the base imageâ¦ I do not remember exactly. >> >> Alexandre >> >> >>> On Jun 20, 2015, at 10:25 PM, Alejandro Infante <alejandroinfante91(a)gmail.com> wrote: >>> >>> Exactly, all the customized views are dependent of GlamourCore and also the Easel depends on Glamour for showing the examples. >>> >>> Alejandro >>> >>>> On Jun 20, 2015, at 10:22 PM, Alexandre Bergel <alexandre.bergel(a)me.com> wrote: >>>> >>>> Alejandro, >>>> >>>> I do not remember why Roassal depends on Glamour? >>>> I guess this is because of the GTInspector? >>>> >>>> Alexandre >>>> >>>>> On Jun 19, 2015, at 8:11 AM, Stephan Eggermont <stephan(a)stack.nl> wrote: >>>>> >>>>> On 19-06-15 07:11, Alejandro Infante wrote: >>>>>> Hi, >>>>>> I did that because when using: >>>>>> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ >>>>>> Gofer it >>>>>> smalltalkhubUser: 'ObjectProfile' project: 'Roassal2'; >>>>>> configurationOf: 'Roassal2'; >>>>>> loadStable >>>>>> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ >>>>>> It was installing 1.52 even though the stable version of Roassal was 1.12. >>>>>> Instead if I used: >>>>>> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ >>>>>> Gofer new smalltalkhubUser: 'ObjectProfile' >>>>>> project: 'Roassal2'; >>>>>> package: 'ConfigurationOfRoassal2'; >>>>>> load. >>>>>> ((Smalltalk at: #ConfigurationOfRoassal2) project version: #stable) load >>>>>> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ >>>>>> I was getting the right version (1.12). >>>>> >>>>> Gofer>>loadStable does not use the >>>>> >>>>> ConfigurationOfRoassal2 class>>loadStable >>>>> >>>>> (which is undefined, but many configurations define as >>>>> >>>>> self project load: #stable >>>>> >>>>> but loadVersion: #stable, which uses the latest version marked #stable. >>>>> >>>>> So yes, that is something you'd want to fix in place. >>>>> And warn about on the mailing list. >>>>> >>>>> In this version 1.12 then we see that Roassal is tightly coupled to >>>>> an old version of GlamourCore. So either ConfigurationOfRoassal2 >>>>> needs to add a new #stable version every time GlamourCore #stable >>>>> for Pharo 4 is updated, or it should depend on GlamourCore #stable. >>>>> And ConfigurationOfGlamourCore has actually the same problem, as >>>>> #stable currently depends on an old version of Rubric. So that >>>>> should have been one or two versions more. And please note that >>>>> this is for the released Pharo 4, where we are only supposed to >>>>> backport important fixes. >>>>> >>>>> I strongly suggest to make ConfigurationOfGlamourCore #stable >>>>> depend on ConfigurationOfRubric #stable, and to make ConfigurationOfRoassal2 depend on ConfigurationOfGlamourCore #stable. >>>>> >>>>> Depending on #stable instead of #release1 or so works out ok >>>>> here as long there is not supposed to be a new release for Pharo 4. >>>>> >>>>> Stephan >>>>> >>>>> >>>>> >>>>> >>>>> >>>> >>>> -- >>>> _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: >>>> Alexandre Bergel http://www.bergel.eu >>>> ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. >>>> >>>> >>>> >>>> >>> >>> >> >> -- >> _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: >> Alexandre Bergel http://www.bergel.eu >> ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. >> >> >> >> >

June 21, 2015