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

[pharo-project/pharo-core]

by GitHub

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

Sept. 18, 2014

[pharo-project/pharo-core] 342b32: 40232

by GitHub

Branch: refs/heads/4.0 Home: https://github.com/pharo-project/pharo-core Commit: 342b328cf66c6917c57e23a04b7cacf8e8fd8b17 https://github.com/pharo-project/pharo-core/commit/342b328cf66c6917c57e23a0… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2014-09-18 (Thu, 18 Sep 2014) Changed paths: M EmbeddedFreeType.package/EmbeddedFreeTypeFontInstaller.class/class/class initialization/initialize.st A EmbeddedFreeTypeTests.package/EmbeddedFreeTypeFontInstallerTest.class/instance/accessing/currentInstallerOrError.st A EmbeddedFreeTypeTests.package/EmbeddedFreeTypeFontInstallerTest.class/instance/accessing/currentProviderOrError.st M EmbeddedFreeTypeTests.package/EmbeddedFreeTypeFontInstallerTest.class/instance/tests/testIsRegistred.st M EmbeddedFreeTypeTests.package/EmbeddedFreeTypeFontInstallerTest.class/instance/tests/testinstallAllFontsIn.st A FontInfrastructureTests.package/LogicalFontManagerTest.class/instance/accessing/currentProviderOrError.st M FontInfrastructureTests.package/LogicalFontManagerTest.class/instance/tests/testHasCurrentFreeTypeFontProvider.st A ScriptLoader40.package/ScriptLoader.class/instance/pharo - scripts/script232.st A ScriptLoader40.package/ScriptLoader.class/instance/pharo - updates/update40232.st M ScriptLoader40.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st Log Message: ----------- 40232 14032 Fix test cases and access singletons using slots https://pharo.fogbugz.com/f/cases/14032 http://files.pharo.org/image/40/40232.zip

Sept. 18, 2014

Re: [Pharo-dev] [pharo-project/pharo-core] 7c2c6d: 30857

by Ben Coman

Sept. 18, 2014

Re: [Pharo-dev] Why Bloc?

by Alain Plantec

On 18 Sep 2014, at 15:40, Alain Plantec <alain.plantec(a)yahoo.com> wrote: > > On 18 Sep 2014, at 14:37, Sean P. DeNigris <sean(a)clipperadams.com> wrote: > >> Alain Plantec-3 wrote >>> then you are ready to run a Bloc world: >>> world menu>Bloc>New Bloc space >>> world menu>Bloc>Switch to Bloc space... >>> choose 'Bloc-1' >> >> I loaded via the config and then the steps above seemed to freeze the image. >> Mac w. #30856. Eventually a ton of MNU ThreadSafeTranscript>>stepGlobal >> windows appeared over a purple background. ahh, ok, this is related to the Transcript updating fixe introduced in 4.0. So try with a 4.0 image. Cheers Alain > > I guess the configuration is not up-to-date. > can you try by directly load the last version of the packages with monticello ? > Alain > > >> >> >> >> ----- >> Cheers, >> Sean >> -- >> View this message in context: http://forum.world.st/Why-Bloc-tp4771757p4778746.html >> Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com. >> >

Sept. 18, 2014

Re: [Pharo-dev] Why Bloc?

by Alain Plantec

On 18 Sep 2014, at 14:37, Sean P. DeNigris <sean(a)clipperadams.com> wrote: > Alain Plantec-3 wrote >> then you are ready to run a Bloc world: >> world menu>Bloc>New Bloc space >> world menu>Bloc>Switch to Bloc space... >> choose 'Bloc-1' > > I loaded via the config and then the steps above seemed to freeze the image. > Mac w. #30856. Eventually a ton of MNU ThreadSafeTranscript>>stepGlobal > windows appeared over a purple background. I guess the configuration is not up-to-date. can you try by directly load the last version of the packages with monticello ? Alain > > > > ----- > Cheers, > Sean > -- > View this message in context: http://forum.world.st/Why-Bloc-tp4771757p4778746.html > Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com. >

Sept. 18, 2014

[pharo-project/pharo-core]

by GitHub

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

Sept. 18, 2014

[pharo-project/pharo-core] 8e48ab: 40231

by GitHub

Branch: refs/heads/4.0 Home: https://github.com/pharo-project/pharo-core Commit: 8e48ab60bf74e2c1c11c78517c08a26eb44b4a7a https://github.com/pharo-project/pharo-core/commit/8e48ab60bf74e2c1c11c7851… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2014-09-18 (Thu, 18 Sep 2014) Changed paths: A ScriptLoader40.package/ScriptLoader.class/instance/pharo - scripts/script231.st A ScriptLoader40.package/ScriptLoader.class/instance/pharo - updates/update40231.st M ScriptLoader40.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st R Spec-MorphicAdapters.package/MorphicTabManagerAdapter.class/instance/widget API/selectedTab_.st A Spec-MorphicAdapters.package/MorphicTabManagerAdapter.class/instance/widget API/tabSelected_.st Log Message: ----------- 40231 14030 MorphicTabManagerAdapter>>doesNotUnderstand: #tabSelected: https://pharo.fogbugz.com/f/cases/14030 http://files.pharo.org/image/40/40231.zip

Sept. 18, 2014

Re: [Pharo-dev] [pharo-project/pharo-core] 7c2c6d: 30857

by Sean P. DeNigris

On Sep 18, 2014, at 8:35 AM, Marcus Denker-4 [via Smalltalk] <ml-node+s1294792n4778745h83(a)n4.nabble.com> wrote: > The rational is: Simplify API evolution. > â¦ > we can reduce the pain of people *a lot* Ah, oh cool. Thanks for the explanation :) ----- Cheers, Sean -- View this message in context: http://forum.world.st/pharo-project-pharo-core-7c2c6d-30857-tp4778741p47787… Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

Sept. 18, 2014

Re: [Pharo-dev] Why Bloc?

by Sean P. DeNigris

Alain Plantec-3 wrote > then you are ready to run a Bloc world: > world menu>Bloc>New Bloc space > world menu>Bloc>Switch to Bloc space... > choose 'Bloc-1' I loaded via the config and then the steps above seemed to freeze the image. Mac w. #30856. Eventually a ton of MNU ThreadSafeTranscript>>stepGlobal windows appeared over a purple background. ----- Cheers, Sean -- View this message in context: http://forum.world.st/Why-Bloc-tp4771757p4778746.html Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

Sept. 18, 2014

Re: [Pharo-dev] [pharo-project/pharo-core] 7c2c6d: 30857

by Marcus Denker

On 18 Sep 2014, at 14:30, Sean P. DeNigris <sean(a)clipperadams.com> wrote: > GitHub wrote >> 14018 backport #uncapitalized to Pharo3 > > Not a big deal, but this doesn't seem to fit our bugfix-only backport > policy. What was the rationale? > The rational is: Simplify API evolution. If we deprecate a method in Pharo4, people like to change their code base *and* use the same code on Pharo3. (Zinc is one example of that). So for simple ârenameâ changes like this, we can reduce the pain of people *a lot* by providing the same method in Pharo3. Keep in mind that we do *not* do the actual change of rewriting all senders and deprecating the old method. That is just done in Pharo4. Marcus

Sept. 18, 2014