- Pharo-dev - lists.pharo.org

[pharo-project/pharo-core]
by GitHub Feb. 25, 2015

Feb. 25, 2015

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

1 0

[pharo-project/pharo-core] b6ce9b: 40507
by GitHub Feb. 25, 2015

Feb. 25, 2015

Branch: refs/heads/4.0 Home: https://github.com/pharo-project/pharo-core Commit: b6ce9b4070449bcb3b9d5565ad8923f9fcf2e7af https://github.com/pharo-project/pharo-core/commit/b6ce9b4070449bcb3b9d5565… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2015-02-25 (Wed, 25 Feb 2015) Changed paths: M ConfigurationOfShoreLineReporter.package/ConfigurationOfShoreLineReporter.class/instance/versions/stable_.st A ConfigurationOfShoreLineReporter.package/ConfigurationOfShoreLineReporter.class/instance/versions/version012_.st A ScriptLoader40.package/ScriptLoader.class/instance/pharo - scripts/script507.st A ScriptLoader40.package/ScriptLoader.class/instance/pharo - updates/update40507.st M ScriptLoader40.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st M ShoreLine-Report-Core.package/SlReportExtractor.class/instance/extraction/extractMetadata.st M ShoreLine-Report-Core.package/SlReportMessage.class/definition.st A ShoreLine-Report-Core.package/SlReportMessage.class/instance/accessing/auto.st A ShoreLine-Report-Core.package/SlReportMessage.class/instance/accessing/auto_.st M ShoreLine-Report-Core.package/SlReportMessage.class/instance/converting/metadata.st M ShoreLine-Report-Core.package/SlReporter.class/class/accessing/mimeType.st R ShoreLine-Report-Core.package/SlReporter.class/instance/actions/sendReport_.st A ShoreLine-Report-Core.package/SlReporter.class/instance/actions/serializeAndSend_.st A ShoreLine-Report-Core.package/SlReporter.class/instance/actions/serialize_.st M ShoreLine-Report-UI.package/SlReportWindow.class/instance/actions/openHelp.st M ShoreLine-Report-UI.package/SlReportWindow.class/instance/actions/submit.st Log Message: ----------- 40507 14987 ShoreLine Reporter version 0.1.2 https://pharo.fogbugz.com/f/cases/14987 http://files.pharo.org/image/40/40507.zip

1 0

development workflow for GTools (GToolkitCore)
by Nicolai Hess Feb. 25, 2015

Feb. 25, 2015

14850 <https://pharo.fogbugz.com/default.asp?14850> Integrate GTools #development "From this version onwards the development version should be integrated." Is this a good idea? Does the #development version always include *all* the latest changes, because after Andrei opened 14866 <https://pharo.fogbugz.com/default.asp?14866> Integrate GTools (which got integrated in 40475) I uploaded some changes for issue 14608 <https://pharo.fogbugz.com/default.asp?14608> ClassTest>>#testClassRespectsPolymorphismWithTrait failing due to Spotter methods I set the status to "Fix Review needed", but my changes are integrated in 40475 too! I am not satisfied with the way external packages are handled. 1. if there is not one slice/changeset per issue, it is even less likely someone will review the changes. 2. you don't know who works when on a issue. They are solved in a bulk. 3. a new configuration might not only includes bugfixes but new features as well. 4. often we have unbound globals / undeclared references or other test failures. Can we use the build server for those external projects (like GToolkitCore, Athens, TxText), and that if a project makes a new configuration, it uses the same issue validator for loading and testing that configuration? nicolai

5 10

[pharo-project/pharo-core]
by GitHub Feb. 25, 2015

Feb. 25, 2015

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

1 0

[pharo-project/pharo-core]
by GitHub Feb. 24, 2015

Feb. 24, 2015

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

1 0

[pharo-project/pharo-core] bae6b6: 40505
by GitHub Feb. 24, 2015

Feb. 24, 2015

Branch: refs/heads/4.0 Home: https://github.com/pharo-project/pharo-core Commit: bae6b613b78ba1afa63218d5768c46808fae0cea https://github.com/pharo-project/pharo-core/commit/bae6b613b78ba1afa63218d5… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2015-02-24 (Tue, 24 Feb 2015) Changed paths: A Compiler.package/EncoderForSistaV1.class/class/instruction stream support/nonExtensionBytecodeAt_in_.st A Compiler.package/EncoderForV3PlusClosures.class/class/instruction stream support/nonExtensionBytecodeAt_in_.st M Kernel.package/CompiledMethod.class/class/class initialization/initialize.st A Kernel.package/CompiledMethod.class/class/instance creation/headerFlagForEncoder_.st M Kernel.package/CompiledMethod.class/definition.st M Kernel.package/CompiledMethod.class/instance/accessing/clearFlag.st A Kernel.package/CompiledMethod.class/instance/accessing/clearSignFlag.st M Kernel.package/CompiledMethod.class/instance/accessing/encoderClass.st M Kernel.package/CompiledMethod.class/instance/accessing/flag.st M Kernel.package/CompiledMethod.class/instance/accessing/frameSize.st M Kernel.package/CompiledMethod.class/instance/accessing/numArgs.st M Kernel.package/CompiledMethod.class/instance/accessing/numLiterals.st M Kernel.package/CompiledMethod.class/instance/accessing/numTemps.st M Kernel.package/CompiledMethod.class/instance/accessing/primitive.st A Kernel.package/CompiledMethod.class/instance/accessing/setSignFlag.st M Kernel.package/CompiledMethod.class/instance/debugger support/prepareForSimulationWith_.st M Kernel.package/CompiledMethod.class/instance/initialize-release/setFrameBit_.st A ScriptLoader40.package/ScriptLoader.class/instance/pharo - scripts/script505.st A ScriptLoader40.package/ScriptLoader.class/instance/pharo - updates/update40505.st M ScriptLoader40.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st Log Message: ----------- 40505 14980 Method missing to decode bytecode set https://pharo.fogbugz.com/f/cases/14980 14979 Fixes for SistaV1 bytecode set https://pharo.fogbugz.com/f/cases/14979 http://files.pharo.org/image/40/40505.zip

1 0

[pharo-project/pharo-core] 3fabea: 40497
by GitHub Feb. 24, 2015

Feb. 24, 2015

Branch: refs/heads/4.0 Home: https://github.com/pharo-project/pharo-core Commit: 3fabea9dab3061c6749f77aef01dc44bad73167c https://github.com/pharo-project/pharo-core/commit/3fabea9dab3061c6749f77ae… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2015-02-23 (Mon, 23 Feb 2015) Changed paths: A Kernel.package/Number.class/instance/converting/percent.st A KernelTests.package/NumberTest.class/instance/tests/testPercent.st A RPackage-SystemIntegration.package/extension/String/instance/asPackage.st A RPackage-SystemIntegration.package/extension/String/instance/asPackageIfAbsent_.st A RPackage-Tests.package/RPackageStringExtensionTest.class/README.md A RPackage-Tests.package/RPackageStringExtensionTest.class/definition.st A RPackage-Tests.package/RPackageStringExtensionTest.class/instance/tests/testAsPackage.st A RPackage-Tests.package/RPackageStringExtensionTest.class/instance/tests/testAsPackageIfAbsent.st A RPackage-Tests.package/RPackageStringExtensionTest.class/instance/tests/testAsPackageWithError.st A ScriptLoader40.package/ScriptLoader.class/instance/pharo - scripts/script497.st A ScriptLoader40.package/ScriptLoader.class/instance/pharo - updates/update40497.st M ScriptLoader40.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st M Spec-PolyWidgets.package/DateModel.class/instance/initialization/initializeWidgets.st Log Message: ----------- 40497 14949 String>>asPackage https://pharo.fogbugz.com/f/cases/14949 14957 Number>>#percent https://pharo.fogbugz.com/f/cases/14957 14958 DateModel>>#initializeWidgets error https://pharo.fogbugz.com/f/cases/14958 http://files.pharo.org/image/40/40497.zip

10 26

Issue 12970 - 16 steps to get through #halt - PROPOSED FIX
by Ben Coman Feb. 24, 2015

Feb. 24, 2015

I've found a fix for something that has annoyed me for a long time - but I can't determine what it might break. 1. In Workspace I evaluate the following Halt enableHaltOnce. a := 1. self halt. b := 2. self haltOnce. c := 3. Transcript show: a + b + c. 2. In the debugger after it stops at the #halt, it takes a SINGLE <Step Over> to move to d:=2 - no problem. 3. Now <Restart> and then <Step Over> down to c:=3 and observe: * the #halt now takes EIGHT (used to be SIXTEEN) steps to traverse (ouch!) * the #haltOnce takes THREE steps to traverse (good) Tracing through for both #halt and #haltOnce it seems that the specific conditional reference to #halt in Halt>>signalerContext is the difference! Removing that condition results in the #halt behaving like #haltOnce, taking only THREE <Step Over>s to traverse a restarted #halt. Halt>>signalerContext ^ signalContext findContextSuchThat: [ :context | (context receiver == self or: [ (context receiver == self class) or: [ context method selector = #halt ]]) not ] Now #haltOnce seems to have been operating without a problem for a long timer, so presumably its okay to make #halt behave the same way. But this is deep stuff I don't fully understand. Anyone see a problem with removing that last condition? cheers -ben

5 13

about dark theme
by stepharo Feb. 24, 2015

Feb. 24, 2015

just some feedback because I was forced to use it because the projector quality was not great. and now I cannot use it on my machine :) the caret is black as well as the window cross and it is really difficult to see them on my machine. Stef

2 1

Spotter does not respect the selected fonts
by stepharo Feb. 24, 2015

Feb. 24, 2015

Hi guys yesterday I gave a presentation and spotter fonts were not updated to the font changes Stef

2 1