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

[pharo-project/pharo-core]

by GitHub

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

Nov. 21, 2014

[pharo-project/pharo-core] f9a0b8: 40380

by GitHub

Branch: refs/heads/4.0 Home: https://github.com/pharo-project/pharo-core Commit: f9a0b80a61c7f7cd29f7a833e93475d87b606d21 https://github.com/pharo-project/pharo-core/commit/f9a0b80a61c7f7cd29f7a833… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2014-11-21 (Fri, 21 Nov 2014) Changed paths: A ScriptLoader40.package/ScriptLoader.class/instance/pharo - scripts/script380.st A ScriptLoader40.package/ScriptLoader.class/instance/pharo - updates/update40380.st M ScriptLoader40.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st M Text-Edition.package/SimpleEditor.class/instance/nonediting%2Fnontyping keys/cursorHome_.st M Text-Edition.package/TextEditor.class/instance/nonediting%2Fnontyping keys/cursorHome_.st M Versionner-Spec-Browser.package/VersionnerRepositoriesManager.class/instance/initialization/initializeSelectedRemotes.st Log Message: ----------- 40380 14510 Wrong editing history positions after using home-key https://pharo.fogbugz.com/f/cases/14510 14495 Adding dependent projects in Versionner fails (adding to array instead of collection) https://pharo.fogbugz.com/f/cases/14495 http://files.pharo.org/image/40/40380.zip

Nov. 21, 2014

Re: [Pharo-dev] ConfigurationOfGlamour not connected to repository

by Stephan Eggermont

Doru wrote: >Indeed, these are not needed. Those groups are not maintainable and make tool building a nightmare. We will remove them from all Moose configurations eventually :). Sorry, afaik the groups are essential complexity and removing them just increases the problems. Configuration management is essentially a 5-dimensional problem and the tools need to support different workflows so they will never be simple. Stephan

Nov. 21, 2014

Re: [Pharo-dev] VM fixes to review

by Esteban Lorenzano

> On 21 Nov 2014, at 13:56, Marcus Denker <marcus.denker(a)inria.fr> wrote: > > >> On 21 Nov 2014, at 13:46, Ben Coman <btc(a)openInWorld.com> wrote: >> >> Ben Coman wrote: >>> Marcus Denker wrote: >>>>> On 21 Nov 2014, at 13:21, stepharo <stepharo(a)free.fr> wrote: >>>>> >>>>> can you mark them as 4.0 >>>>> >>>> >>>> The problem is that they now show up in the integrator app and the monkey will try to run them with a non-existing slice, failing them all. >>> I checked they are all tagged NoMonkey. >>> Sorry I didn't consider the Integrator app. >> >> Maybe the integrator app should only show issues tagged "Fix To Includeâ > > Yes, that might be a good idea. in the integrator app (latest version), you can configure the issues you want to see. default values are just âFix Review Neededâ and âFix Reviewed by the Monkey" Esteban > > Marcus > >

Nov. 21, 2014

Re: [Pharo-dev] VM fixes to review

by Marcus Denker

> On 21 Nov 2014, at 13:46, Ben Coman <btc(a)openInWorld.com> wrote: > > Ben Coman wrote: >> Marcus Denker wrote: >>>> On 21 Nov 2014, at 13:21, stepharo <stepharo(a)free.fr> wrote: >>>> >>>> can you mark them as 4.0 >>>> >>> >>> The problem is that they now show up in the integrator app and the monkey will try to run them with a non-existing slice, failing them all. >> I checked they are all tagged NoMonkey. >> Sorry I didn't consider the Integrator app. > > Maybe the integrator app should only show issues tagged "Fix To Includeâ Yes, that might be a good idea. Marcus

Nov. 21, 2014

Re: [Pharo-dev] VM fixes to review

by Esteban Lorenzano

> On 21 Nov 2014, at 13:46, Ben Coman <btc(a)openInWorld.com> wrote: > > Ben Coman wrote: >> Marcus Denker wrote: >>>> On 21 Nov 2014, at 13:21, stepharo <stepharo(a)free.fr> wrote: >>>> >>>> can you mark them as 4.0 >>>> >>> >>> The problem is that they now show up in the integrator app and the monkey will try to run them with a non-existing slice, failing them all. >> I checked they are all tagged NoMonkey. >> Sorry I didn't consider the Integrator app. > > Maybe the integrator app should only show issues tagged "Fix To Includeâ they are two things: 1) integrator app 2) monkey. is the 2nd one who will fail without noMonkey :) Esteban > -ben >

Nov. 21, 2014

Re: [Pharo-dev] ConfigurationOfGlamour not connected to repository

by Tudor Girba

Hi Stephan, Indeed, these are not needed. Those groups are not maintainable and make tool building a nightmare. We will remove them from all Moose configurations eventually :). Doru On Fri, Nov 21, 2014 at 1:41 PM, Stephan Eggermont <stephan(a)stack.nl> wrote: > Hmm, there are also other configurations still loaded that should have > been removed > ConfigurationOfGTInspector > ConfigurationOfGTPlayground. > > Though I'd prefer to see them as groups in a ConfigurationOfGToolkit > > Stephan > -- www.tudorgirba.com "Every thing has its own flow"

Nov. 21, 2014

Re: [Pharo-dev] VM fixes to review

by Ben Coman

Ben Coman wrote: > Marcus Denker wrote: >>> On 21 Nov 2014, at 13:21, stepharo <stepharo(a)free.fr> wrote: >>> >>> can you mark them as 4.0 >>> >> >> The problem is that they now show up in the integrator app and the >> monkey will try to run them with a non-existing slice, failing them all. > > I checked they are all tagged NoMonkey. > Sorry I didn't consider the Integrator app. Maybe the integrator app should only show issues tagged "Fix To Include" ? -ben

Nov. 21, 2014

Re: [Pharo-dev] VM fixes to review

by Ben Coman

Marcus Denker wrote: >> On 21 Nov 2014, at 13:21, stepharo <stepharo(a)free.fr> wrote: >> >> can you mark them as 4.0 >> > > The problem is that they now show up in the integrator app and the monkey will try to run them with a non-existing slice, failing them all. I checked they are all tagged NoMonkey. Sorry I didn't consider the Integrator app. -ben > >> Stef >> >> Le 16/11/14 01:52, Ben Coman a Ã©crit : >>> I notice several VM fixes [1] submitted by Nicolas 6 months ago. They >>> are categorized as Milestone=Later, so I'm bumping them here just in case these slipped through the cracks to get them into Pharo 4. >>> >>> [1] https://pharo.fogbugz.com/default.asp?pgx=LF&ixFilter=36 >>> >>> But then I think I remember that early in Pharo 4 cycle, the Pharo VM was aligned more closely with with Eliot's - so maybe some of these are already included? >>> >>> cheers -ben >>> >>> >>> >> > > >

Nov. 21, 2014

Re: [Pharo-dev] ConfigurationOfGlamour not connected to repository

by Stephan Eggermont

Hmm, there are also other configurations still loaded that should have been removed ConfigurationOfGTInspector ConfigurationOfGTPlayground. Though I'd prefer to see them as groups in a ConfigurationOfGToolkit Stephan

Nov. 21, 2014