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

[pharo-project/pharo-core]

by GitHub

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

Sept. 21, 2015

[pharo-project/pharo-core]

by GitHub

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

Sept. 21, 2015

[pharo-project/pharo-core] 436b56: 40622

by GitHub

Branch: refs/heads/4.0 Home: https://github.com/pharo-project/pharo-core Commit: 436b56db239a8618a4533b43d0abc8180c4a2710 https://github.com/pharo-project/pharo-core/commit/436b56db239a8618a4533b43… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2015-09-21 (Mon, 21 Sep 2015) Changed paths: M Compression.package/extension/StandardFileStream/instance/compressFile.st M Files.package/StandardFileStream.class/instance/-- all --/compressFile.st M ScriptLoader40.package/ScriptLoader.class/instance/-- all --/commentForCurrentUpdate.st R ScriptLoader40.package/ScriptLoader.class/instance/-- all --/script621.st A ScriptLoader40.package/ScriptLoader.class/instance/-- all --/script622.st R ScriptLoader40.package/ScriptLoader.class/instance/-- all --/update40621.st A ScriptLoader40.package/ScriptLoader.class/instance/-- all --/update40622.st R ScriptLoader40.package/ScriptLoader.class/instance/pharo - scripts/script621.st A ScriptLoader40.package/ScriptLoader.class/instance/pharo - scripts/script622.st R ScriptLoader40.package/ScriptLoader.class/instance/pharo - updates/update40621.st A ScriptLoader40.package/ScriptLoader.class/instance/pharo - updates/update40622.st M ScriptLoader40.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st Log Message: ----------- 40622 10235 StandardFileStream>>compressFile cant create new compressed file https://pharo.fogbugz.com/f/cases/10235 http://files.pharo.org/image/40/40622.zip

Sept. 21, 2015

Re: [Pharo-dev] WhatsUp from: 2015-09-21 until: 2015-09-30

by stepharo

Le 21/9/15 05:00, seaside(a)rmod.lille.inria.fr a Ã©crit : > Hi! We're sending this automatic email twice a month, to give the community an opportunity to easily know what's happening and to coordinate efforts. Just answer informally, and feel free to spawn discussions thereafter! > > ### Here's what I've been up to since the last WhatsUp: - Working on Pharo starter kit - Working on Mooc - Helping on bootstrap > > ### What's next, until 2015-09-30 (*): > - Publish Pharo Starter Kit - Finish design Slide - For the next iteration after finish to update the Magritte tutorial

Sept. 21, 2015

WhatsUp from: 2015-09-21 until: 2015-09-30

by seaside＠rmod.lille.inria.fr

Hi! We're sending this automatic email twice a month, to give the community an opportunity to easily know what's happening and to coordinate efforts. Just answer informally, and feel free to spawn discussions thereafter! ### Here's what I've been up to since the last WhatsUp: - $HEROIC_ACHIEVEMENTS_OR_DISMAL_FAILURES_OR_SIMPLE_BORING_NECESSARY_TASKS ### What's next, until 2015-09-30 (*): - $NEXT_STEPS_TOWARDS_WORLD_DOMINATION (*) we'll be expecting results by then ;)

Sept. 21, 2015

Re: [Pharo-dev] Contribution scheme confusing ...

by Torsten Bergmann

https://pharo.fogbugz.com/f/cases/16611 > Gesendet: Sonntag, 20. September 2015 um 16:30 Uhr > Von: "Marcus Denker" <marcus.denker(a)inria.fr> > An: "Pharo Development List" <pharo-dev(a)lists.pharo.org> > Betreff: Re: [Pharo-dev] Contribution scheme confusing ... > > Yes, this is good to put it in the imageâ¦ I will update the website later, too. > > can you make an issue? > > > On 17 Sep 2015, at 17:35, Torsten Bergmann <astares(a)gmx.de> wrote: > > > > Hi Marcus, > > > > Could work - but is a fragile rule. We should document it somewhere. > > > > What about providing this info directly in the image. Alexandre has already added a help topic on how > > to contribute (but yet only for the slice process). > > > > I changed it so we can have the differences of config managed ones described as well and > > we can list the configs there. See the attached changeset that you can file in into the latest > > Pharo5.0 Latest update: #50329 > > > > File in and check "How to contribute to Pharo base code" topic in Help -> Help Browser > > > > I guess this would be more clear to us and the users and we can simply point to > > the help info is someone asks. And look up ourself when we forgot. > > > > Thx > > T. > > > >> Gesendet: Donnerstag, 17. September 2015 um 15:40 Uhr > >> Von: "Marcus Denker" <marcus.denker(a)inria.fr> > >> An: "Pharo Development List" <pharo-dev(a)lists.pharo.org> > >> Betreff: Re: [Pharo-dev] Contribution scheme confusing ... > >> > >>>> > >>>> Also: > >>>> I did a simple fix on NautilusGroupAutoBuilder package - there is > >>>> a ConfigurationOfNautilusGroupAutoBuilder. But is it managed internally > >>>> or externally now? > >>>> > >>> Even I can not tell you. > >>> > >> > >> I think the rule we should adopt: if there is a dedicated repository defined in the image for a package, people should commit > >> there. If there is non (just the inbox), then this should be used (with the Slice mechanism). > >> > >> The repositories in the image should be already up to date, I think. > >> > >> Marcus > >> > >> > > <HowToContributeHelp class.TorstenBergmann.cs> > > >

Sept. 20, 2015

Re: [Pharo-dev] Need a decision on subString: vs substring:

by Esteban Lorenzano

> On 20 Sep 2015, at 19:14, Sean P. DeNigris <sean(a)clipperadams.com> wrote: > > > What is the decision? > The consensus seemed to be #substrings:, and a compatibility package if necessary. â¦ because substring is real english while subString is not, AFAIK :) > Cheers, > Sean > > View this message in context: Re: Need a decision on subString: vs substring: <http://forum.world.st/Need-a-decision-on-subString-vs-substring-tp4847932p4…> > Sent from the Pharo Smalltalk Developers mailing list archive <http://forum.world.st/Pharo-Smalltalk-Developers-f1294837.html> at Nabble.com.

Sept. 20, 2015

ConfigurationOfRoassal2 broken

by Stephan Eggermont

Can anyone explain ConfigurationOfRoassal2? Where does that work? stable: spec <symbolicVersion: #'stable'> spec for: #'common' version: '1.11'. spec for: #'pharo4.x' version: '1.13'. spec for: #'pharo3.x' version: '1.6'. development: spec <symbolicVersion: #'development'> spec for: #'common' version: '1.4-baseline'. spec for: #'pharo4.x' version: '1.5-baseline'.

Sept. 20, 2015

Re: [Pharo-dev] Need a decision on subString: vs substring:

by Sean P. DeNigris

> What is the decision? The consensus seemed to be #substrings:, and a compatibility package if necessary. ----- Cheers, Sean -- View this message in context: http://forum.world.st/Need-a-decision-on-subString-vs-substring-tp4847932p4… Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

Sept. 20, 2015

[pharo-project/pharo-core]

by GitHub

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

Sept. 20, 2015