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

Re: [Pharo-dev] #milliseconds versus #milliSeconds

by Stephan Eggermont

On 03/03/15 14:37, Sean P. DeNigris wrote: > I definitely recall feeling "lots of pain" with the subStringXyz -> > substringXyz that we're still dealing with in recent updates (I think I > started that push as a naive newbie), but I'm not sure about the "little > gain" part. It's hard to quantify the negative effect of inconsistency in > the system, or the empowering effect of uniformity. These kind of changes should be accompanied by a rewrite script, b.t.w. Upgrading is much easier if you can just select the rewrites you want to apply. Stephan

March 3, 2015

Re: [Pharo-dev] Seaside on Pharo 4 CI Job ?

by Stephan Eggermont

On 03/03/15 15:42, Tudor Girba wrote: > I think you mean Pharo 3.0, right? #'release3.0' is not going to be supported on Pharo 4, only #'release3.1' and #'release3.2'. Stephan

March 3, 2015

[pharo-project/pharo-core]

by GitHub

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

March 3, 2015

[pharo-project/pharo-core] 5c1ff5: 40532

by GitHub

Branch: refs/heads/4.0 Home: https://github.com/pharo-project/pharo-core Commit: 5c1ff59e7668b748d17ee792ca35a8a969047d82 https://github.com/pharo-project/pharo-core/commit/5c1ff59e7668b748d17ee792… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2015-03-03 (Tue, 03 Mar 2015) Changed paths: M Athens-Core.package/AthensCanvas.class/instance/caching/flushCacheAt_.st A Deprecated40.package/ShadowLabelMorph.class/README.md A Deprecated40.package/ShadowLabelMorph.class/definition.st A Deprecated40.package/ShadowLabelMorph.class/instance/drawing/drawOn_.st M Kernel.package/Class.class/instance/instance variables/addInstVarNamed_.st R Polymorph-Widgets.package/ShadowLabelMorph.class/README.md R Polymorph-Widgets.package/ShadowLabelMorph.class/definition.st R Polymorph-Widgets.package/ShadowLabelMorph.class/instance/drawing/drawOn_.st R ScriptLoader40.package/ScriptLoader.class/class/public/resetLogStream.st M ScriptLoader40.package/ScriptLoader.class/definition.st R ScriptLoader40.package/ScriptLoader.class/instance/generate scripts%2Fmethods/generateNewUpdateMethod.st R ScriptLoader40.package/ScriptLoader.class/instance/log/logContents.st R ScriptLoader40.package/ScriptLoader.class/instance/log/logStream.st R ScriptLoader40.package/ScriptLoader.class/instance/log/log_.st M ScriptLoader40.package/ScriptLoader.class/instance/log/withUpdateLog_.st R ScriptLoader40.package/ScriptLoader.class/instance/pharo - scripts/script531.st A ScriptLoader40.package/ScriptLoader.class/instance/pharo - scripts/script532.st R ScriptLoader40.package/ScriptLoader.class/instance/pharo - updates/update40531.st A ScriptLoader40.package/ScriptLoader.class/instance/pharo - updates/update40532.st M ScriptLoader40.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st R ScriptLoader40.package/ScriptLoader.class/instance/utils/generateCompleteFixList.st M Spec-Core.package/LabelModel.class/instance/initialization/initialize.st M Spec-Core.package/ListModel.class/README.md Log Message: ----------- 40532 15041 Deprecated ShadowLabelMorph https://pharo.fogbugz.com/f/cases/15041 15036 LabelModel>>initialize contains undeclared reference to textHolder https://pharo.fogbugz.com/f/cases/15036 15032 ScriptLoader does not need to log the change description https://pharo.fogbugz.com/f/cases/15032 15047 AthensSurface removeCacheAt: DNU https://pharo.fogbugz.com/f/cases/15047 15046 addInstVarNamed: fix for adding multiple vars https://pharo.fogbugz.com/f/cases/15046 http://files.pharo.org/image/40/40532.zip

March 3, 2015

strange bevahiour between three dependent Metacello configurations

by Andrei Chis

Hi, We are having the following problem when trying to update GTolols to their latest version in the latest Pharo 4 image: Rubric does not get updated. We have: -- ConfigurationOfGTInspectorCore (2.0-baseline) -- ConfigurationOfGlamourCore (3.1-baseline) -- ConfigurationOfRubric (0.2-baseline) Performing [1] shows that rubric gets updated (atomic load : 0.2-baseline [ConfigurationOfRubric]) Performing [2] contains no trace of rubric. [1] (ConfigurationOfGlamourCore project version: #development) record loadDirective [2] (ConfigurationOfGTInspectorCore project version: #development) record loadDirective. Loading then the inspector [3] does not update Rubric. Loading just Glamour [4] updates it. [3] (ConfigurationOfGTInspectorCore project version: #development) load. [4] (ConfigurationOfGlamourCore project version: #development) load Any ideas or sugestions? Maybe we are missing something trivial. This updates the previous configurations to their latest versions: Gofer new smalltalkhubUser: 'Moose' project: 'GToolkit'; package: 'ConfigurationOfGTInspectorCore'; load. Gofer new smalltalkhubUser: 'Moose' project: 'Glamour'; package: 'ConfigurationOfGlamourCore'; load. Gofer new smalltalkhubUser: 'AlainPlantec' project: 'Rubric'; package: 'ConfigurationOfRubric'; load. Cheers, Andrei

March 3, 2015

Re: [Pharo-dev] Upgrading Fuel Data

by Sean P. DeNigris

Sean P. DeNigris wrote > To a newer user, this could be a confidence-shaking deal breaker. Workaround: 1. Revert Fuel package to v. 798 i.e. just before version bump 2. Materialize data 3. Reload original Fuel package (currently v. 804) Suggestions: 1. unless/until we have a Fuel migration tool, at minimum, any Fuel version integrated into latest Pharo must be loadable in the previous Pharo version. E.g. if Fuel 1.9.4 was loadable in Pharo 3.0, migration would be a bit awkward, but doable. 2. Maybe more guidance in the default error behavior would help e.g. put up text suggesting to either a) temporarily downgrade Fuel to whatever version on first materialization, or b) re-serialize in the image where the data was serialized after upgrading Fuel ----- Cheers, Sean -- View this message in context: http://forum.world.st/Upgrading-Fuel-Data-tp4809243p4809265.html Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

March 3, 2015

Re: [Pharo-dev] Upgrading Fuel Data

by Sean P. DeNigris

Max Leske wrote > Iâll check when I get home. 1.9.4 -> 1.9.4 should *definitely* work. There may be something wrong with the configuration. 1.9.4 loads Fuel.795, but the version was bumped in 799. ----- Cheers, Sean -- View this message in context: http://forum.world.st/Upgrading-Fuel-Data-tp4809243p4809256.html Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

March 3, 2015

Re: [Pharo-dev] Upgrading Fuel Data

by Max Leske

> On 03 Mar 2015, at 17:34, Sean P. DeNigris <sean(a)clipperadams.com> wrote: > > I'm baffled. I tried to materialize data in Pharo 4.0 that was serialized in > 3.0, and got the dreaded "FLBadVersion: Materialization error. Unexpected > stream version 193 where it should be 194". > > But here's the part I don't understand... I went back into the 3.0 image, > upgraded Fuel to 1.9.4, and re-serialized the data. But when materializing I > got the same error! What am I missing here? > > Thanks. Iâll check when I get home. 1.9.4 -> 1.9.4 should *definitely* work. > > > > ----- > Cheers, > Sean > -- > View this message in context: http://forum.world.st/Upgrading-Fuel-Data-tp4809243.html > Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com. >

March 3, 2015

Re: [Pharo-dev] Upgrading Fuel Data

by Sean P. DeNigris

Sean P. DeNigris wrote > I'm baffled Here's something interesting... After loading Fuel 1.9.4 via the Configurations Browser, FLSerializer>>#currentVersion reports 193. I tried loading the latest Fuel package via MC into Pharo 3.0, but it relies on, Context, which doesn't exist. Ugh. Migrating data should not be this hard. I know I will soon get my data back, but I'm only so confident because of my experience with Smalltalk and our great community. To a newer user, this could be a confidence-shaking deal breaker. ----- Cheers, Sean -- View this message in context: http://forum.world.st/Upgrading-Fuel-Data-tp4809243p4809254.html Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

March 3, 2015

Upgrading Fuel Data

by Sean P. DeNigris

I'm baffled. I tried to materialize data in Pharo 4.0 that was serialized in 3.0, and got the dreaded "FLBadVersion: Materialization error. Unexpected stream version 193 where it should be 194". But here's the part I don't understand... I went back into the 3.0 image, upgraded Fuel to 1.9.4, and re-serialized the data. But when materializing I got the same error! What am I missing here? Thanks. ----- Cheers, Sean -- View this message in context: http://forum.world.st/Upgrading-Fuel-Data-tp4809243.html Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

March 3, 2015