[Pharo-dev] Nautilus and Work group

Nautilus in Pharo 5 now includes per default a group "Configuration" and "Work". But one has to manually put new work into the "Work" group. Would it make sense to put newly created packages automagically into this group as typically one is working on them?

Re: [Pharo-dev] Strange Monticello bug: methods are not saved

> > > Great, Thierrys solution works. > > But I think there is still a problem with RGMethodDefinition. We call > self compiledMethod > on a RGMethodDefintion, the implementation *always* returns the compiled > method from the system, if > it exists (regardless whether this ring method is act

Re: [Pharo-dev] Strange Monticello bug: methods are not saved

2015-08-24 18:21 GMT+02:00 stepharo : > This is really nice to have people like you guys around. > This is a really nice example where the sum is more than its elements > > Stef > > Le 24/8/15 16:44, Thierry Goubier a écrit : > > > > 2015-08-24 16:32 GMT+02:00 Marcus Denker : > >> > >> > solves lo

[Pharo-dev] Stability of configurations

I would like to know your opinion on the following issue: Some supposedly stable published configurations are not loading properly. I read once Stef or someone else commented about validating configurations. I agree completely with such idea because guarantees quality. For example I tried to load

[Pharo-dev] Versionner and BaselineOf

For projects developed with git, BaselineOfXyzs replace ConfigurationOfXyzs. What are the plans to update Versionner for this development? I've gotten spoiled and I'm not enjoying writing BaselineOfs by hand! :/ - Cheers, Sean -- View this message in context: http://forum.world.st/Versionne

Re: [Pharo-dev] Random access to meta repos?

Hi Paul, do you still see some of this in one of the filetree branches when doing metacello integration testing? Thierry Le 24/08/2015 19:41, Paul DeBruicker a écrit : per this discussion: https://github.com/dalehenrich/metacello-work/issues/354 You might check that your copy of MCFileRepo

Re: [Pharo-dev] Random access to meta repos?

Le 24/08/2015 18:11, stepharo a écrit : I wanted to harvest the changes in squeak to have MCName but I failed a couple of years ago. Do you know what those changes are? Many of the things I thought were wrong with MC naming a while ago do not matter anymore once moved to git. Now MC naming qu

Re: [Pharo-dev] [pharo-project/pharo-core] 6e5dad: 50267

Nope. I will open a new issue, i guess it interates the wrong slice (I made the mistake that I renamed the issue… one should never rename an issue where a slide is submitted for the original thing). > On 24 Aug 2015, at 19:55, GitHub wrote: > > Branch: refs/heads/5.0 > Home: https://githu

[Pharo-dev] [pharo-project/pharo-core]

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

[Pharo-dev] [pharo-project/pharo-core] 6e5dad: 50267

Branch: refs/heads/5.0 Home: https://github.com/pharo-project/pharo-core Commit: 6e5dad7eb6771d49eabe5009bb2725f5add6e959 https://github.com/pharo-project/pharo-core/commit/6e5dad7eb6771d49eabe5009bb2725f5add6e959 Author: Jenkins Build Server Date: 2015-08-24 (Mon, 24 Aug 2015

Re: [Pharo-dev] Random access to meta repos?

per this discussion: https://github.com/dalehenrich/metacello-work/issues/354 You might check that your copy of MCFileRepositoryInspector>>#refresh doesn't refer to a nonexistent instvar Uko2 wrote > Hi, > > I’ve noticed that when I try to open a gitfiletree repo, before displaying > its cont

Re: [Pharo-dev] [pharo-project/pharo-core] e600c1: 50266

> > 16358 Can not commit three changed method to class TemporaryVariable > https://pharo.fogbugz.com/f/cases/16358 > aargh… monkey checked one, integrator integrated the other. Will do another update… Marcus

[Pharo-dev] [pharo-project/pharo-core] e600c1: 50266

Branch: refs/heads/5.0 Home: https://github.com/pharo-project/pharo-core Commit: e600c10119392bde5ca6dd0865607762f684f3a4 https://github.com/pharo-project/pharo-core/commit/e600c10119392bde5ca6dd0865607762f684f3a4 Author: Jenkins Build Server Date: 2015-08-24 (Mon, 24 Aug 2015

[Pharo-dev] [pharo-project/pharo-core]

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

Re: [Pharo-dev] Strange Monticello bug: methods are not saved

This is really nice to have people like you guys around. This is a really nice example where the sum is more than its elements Stef Le 24/8/15 16:44, Thierry Goubier a écrit : 2015-08-24 16:32 GMT+02:00 Marcus Denker >: > > solves loading Sven test pac

Re: [Pharo-dev] Strange Monticello bug: methods are not saved

indeed we extracted a chunkImporter or something like that out of crappy code logic. Le 24/8/15 17:08, Thierry Goubier a écrit : 2015-08-24 16:53 GMT+02:00 Nicolai Hess >: 2015-08-24 16:07 GMT+02:00 Thierry Goubier mailto:thierry.goub...@gmail.com>>:

Re: [Pharo-dev] Strange Monticello bug: methods are not saved

I know that we got a similar behavior with franck. It looks like the metadata of the package was confused. Stef Le 24/8/15 12:05, Marcus Denker a écrit : Hi, I have a *very* strange bug. I am trying to add change these three methods in class “TemporaryVariable”: (I copy the new version): e

Re: [Pharo-dev] Random access to meta repos?

I wanted to harvest the changes in squeak to have MCName but I failed a couple of years ago. Now relying on name is a bad idea (we got sometimes burnt by that). Stef Le 24/8/15 00:00, Thierry Goubier a écrit : Le 23/08/2015 22:00, Yuriy Tymchuk a écrit : Thanks Thierry! I’m not completely aw

Re: [Pharo-dev] Strange Monticello bug: methods are not saved

2015-08-24 16:53 GMT+02:00 Nicolai Hess : > > > 2015-08-24 16:07 GMT+02:00 Thierry Goubier : > >> Hi Nicolai, >> >> I think you're right. But why irregular errors? >> > > Good question, important question, because we need to know what may have > been wrongly imported. > > can you check this: > > M

Re: [Pharo-dev] Strange Monticello bug: methods are not saved

2015-08-24 16:07 GMT+02:00 Thierry Goubier : > Hi Nicolai, > > I think you're right. But why irregular errors? > Good question, important question, because we need to know what may have been wrongly imported. can you check this: MCMczReader>>loadDefinitions definitions := OrderedCollection

Re: [Pharo-dev] Strange Monticello bug: methods are not saved

2015-08-24 16:32 GMT+02:00 Marcus Denker : > > > > solves loading Sven test packages. Marcus, can you try on yours? > > > > Yes! Very good! > > Slice pushed to 16358. We'll see what the tests say. Why has it started to fail? All the involved code is old. Thierry > Marcus > > >

Re: [Pharo-dev] Strange Monticello bug: methods are not saved

> > solves loading Sven test packages. Marcus, can you try on yours? > Yes! Very good! Marcus

Re: [Pharo-dev] Strange Monticello bug: methods are not saved

> On 24 Aug 2015, at 16:18, Thierry Goubier wrote: > > > > 2015-08-24 16:13 GMT+02:00 Thierry Goubier : > > > 2015-08-24 16:07 GMT+02:00 Thierry Goubier : > Hi Nicolai, > > I think you're right. But why irregular errors? > > Ok, for that particular method, with Zinc smalltalkhub repo open

Re: [Pharo-dev] Strange Monticello bug: methods are not saved

2015-08-24 16:13 GMT+02:00 Thierry Goubier : > > > 2015-08-24 16:07 GMT+02:00 Thierry Goubier : > >> Hi Nicolai, >> >> I think you're right. But why irregular errors? >> >> Ok, for that particular method, with Zinc smalltalkhub repo open and >> Zn-Tests.231 selected (this forces a read of the mcz

Re: [Pharo-dev] Strange Monticello bug: methods are not saved

2015-08-24 16:07 GMT+02:00 Thierry Goubier : > Hi Nicolai, > > I think you're right. But why irregular errors? > > Ok, for that particular method, with Zinc smalltalkhub repo open and > Zn-Tests.231 selected (this forces a read of the mcz definitions in the > image), what I have is: > > ZnEntityTe

Re: [Pharo-dev] Strange Monticello bug: methods are not saved

Hi Nicolai, I think you're right. But why irregular errors? Ok, for that particular method, with Zinc smalltalkhub repo open and Zn-Tests.231 selected (this forces a read of the mcz definitions in the image), what I have is: ZnEntityTests>>#testUnspecifiedEncoding -> old version. ok MCMethodDe

Re: [Pharo-dev] Strange Monticello bug: methods are not saved

> On 24 Aug 2015, at 15:31, Nicolai Hess wrote: > > Can someone look at > > RGMethodDefinition>>#asMCMethodDefinition > I think this method uses one cache > (MCMethodDefinition cachedDefinitions) > even for both, methods from the MCPackage and methods from the image package, > of course, they

Re: [Pharo-dev] Strange Monticello bug: methods are not saved

> On 24 Aug 2015, at 15:24, Thierry Goubier wrote: > > > > 2015-08-24 15:11 GMT+02:00 Sven Van Caekenberghe : > > > > > > and that timestamp: "testUnspecifiedEncoding" : > > "SvenVanCaekenberghe 8/24/2015 14:30", > > Yes, that is the correct code with a version dated today.

Re: [Pharo-dev] Strange Monticello bug: methods are not saved

Can someone look at RGMethodDefinition>>#asMCMethodDefinition I think this method uses one cache (MCMethodDefinition cachedDefinitions) even for both, methods from the MCPackage and methods from the image package, of course, they should not be equal. But they are index by the compiledMethod and th

Re: [Pharo-dev] Strange Monticello bug: methods are not saved

2015-08-24 15:11 GMT+02:00 Sven Van Caekenberghe : > > > > and that timestamp: "testUnspecifiedEncoding" : > "SvenVanCaekenberghe 8/24/2015 14:30", > > Yes, that is the correct code with a version dated today. > > > But, yes, loading in the image nets me an older version: 5/4/2014,

Re: [Pharo-dev] Strange Monticello bug: methods are not saved

> On 24 Aug 2015, at 15:06, Martin Dias wrote: > > > On Mon, Aug 24, 2015 at 3:03 PM, Thierry Goubier > wrote: > > > 2015-08-24 14:43 GMT+02:00 Sven Van Caekenberghe >: > I have to concur, something very strange is wrong. > > #50265 >

Re: [Pharo-dev] Strange Monticello bug: methods are not saved

> On 24 Aug 2015, at 14:55, Thierry Goubier wrote: > > > > 2015-08-24 14:43 GMT+02:00 Sven Van Caekenberghe : > I have to concur, something very strange is wrong. > > #50265 > > Load Zinc-Tests-SvenVanCaekenberghe.231 from > http://mc.stfx.eu/ZincHTTPComponents > > ZnEntityTests>>#testUnsp

Re: [Pharo-dev] Strange Monticello bug: methods are not saved

On Mon, Aug 24, 2015 at 3:03 PM, Thierry Goubier wrote: > > > 2015-08-24 14:43 GMT+02:00 Sven Van Caekenberghe : > >> I have to concur, something very strange is wrong. >> >> #50265 >> >> Load Zinc-Tests-SvenVanCaekenberghe.231 from >> http://mc.stfx.eu/ZincHTTPComponents >> >> ZnEntityTests>>#te

Re: [Pharo-dev] Strange Monticello bug: methods are not saved

2015-08-24 14:43 GMT+02:00 Sven Van Caekenberghe : > I have to concur, something very strange is wrong. > > #50265 > > Load Zinc-Tests-SvenVanCaekenberghe.231 from > http://mc.stfx.eu/ZincHTTPComponents > > ZnEntityTests>>#testUnspecifiedEncoding should have today as latest > version and it simply

Re: [Pharo-dev] Strange Monticello bug: methods are not saved

2015-08-24 14:43 GMT+02:00 Sven Van Caekenberghe : > I have to concur, something very strange is wrong. > > #50265 > > Load Zinc-Tests-SvenVanCaekenberghe.231 from > http://mc.stfx.eu/ZincHTTPComponents > > ZnEntityTests>>#testUnspecifiedEncoding should have today as latest > version and it simply

Re: [Pharo-dev] [Pharo-users] issue with large file path on windows

2015-08-24 13:34 GMT+02:00 Henrik Johansen : > > On 23 Aug 2015, at 6:09 , Nicolai Hess wrote: > > And If you want to review the changes: > > > https://github.com/nicolaihess/pharo-vm/compare/master...nicolaihess:win-long-filename > > > 2015-08-23 13:44 GMT+02:00 Nicolai Hess : > >> For those who

Re: [Pharo-dev] Strange Monticello bug: methods are not saved

I have to concur, something very strange is wrong. #50265 Load Zinc-Tests-SvenVanCaekenberghe.231 from http://mc.stfx.eu/ZincHTTPComponents ZnEntityTests>>#testUnspecifiedEncoding should have today as latest version and it simply does not (the code is wrong too), I can't imagine how that is p

Re: [Pharo-dev] [ANN] Pharo Consortium New Gold Member: Projector Software GmbH

Great!! Norbert > Am 24.08.2015 um 12:37 schrieb Marcus Denker : > > > The Pharo Consortium is very happy to announce that Projector Software GmbH > has joined the Consortium as an Gold Member. > > About > - Projector Software GmbH: http://projector.de > - Pharo Consortium: http://consortium.p

Re: [Pharo-dev] [Pharo-users] [ANN] Pharo Consortium New Gold Member: Projector Software GmbH

It is nice to see the types of projects. Phil Le 24 août 2015 12:56, "Sven Van Caekenberghe" a écrit : > Excellent news! > > > On 24 Aug 2015, at 12:37, Marcus Denker wrote: > > > > > > The Pharo Consortium is very happy to announce that Projector Software > GmbH > > has joined the Consortium a

Re: [Pharo-dev] [Pharo-users] issue with large file path on windows

> On 23 Aug 2015, at 6:09 , Nicolai Hess wrote: > > And If you want to review the changes: > > https://github.com/nicolaihess/pharo-vm/compare/master...nicolaihess:win-long-filename > > > > > 2015-08-23

Re: [Pharo-dev] Strange Monticello bug: methods are not saved

2015-08-24 13:25 GMT+02:00 Thierry Goubier : > I'm trying on 50264, and, yes, there is something strange: > > Monticello diff only picks up two of the changes, instead of three. > Ok, by reformatting, ended up with exactly the same code for one of them :( Saved in the package cache and I have ev

Re: [Pharo-dev] Strange Monticello bug: methods are not saved

I'm trying on 50264, and, yes, there is something strange: Monticello diff only picks up two of the changes, instead of three. Thierry 2015-08-24 12:05 GMT+02:00 Marcus Denker : > Hi, > > I have a *very* strange bug. > > I am trying to add change these three methods in class “TemporaryVariable”

Re: [Pharo-dev] Strange Monticello bug: methods are not saved

On Mon, Aug 24, 2015 at 6:05 PM, Marcus Denker wrote: > Hi, > > I have a *very* strange bug. > > I am trying to add change these three methods in class “TemporaryVariable”: > (I copy the new version): I'm not clear on what you mean by copy. Do you mean you copied the class to MyTemporaryVariabl

Re: [Pharo-dev] VoyageMongo "Could not resolve: GT-Inspector [GT-Inspector-SeanDeNigris.308]"

On 24-08-15 00:11, Sean P. DeNigris wrote: Tudor Girba-2 wrote The dependency to Glamour should go through the #stable version Yes, ideally. But stable doesn't contain the fixes I want, and given that the Moose configs have no platform blocks, I assumed that Pharo 5.0-only code would be commit

Re: [Pharo-dev] [Pharo-users] [ANN] Pharo Consortium New Gold Member: Projector Software GmbH

Excellent news! > On 24 Aug 2015, at 12:37, Marcus Denker wrote: > > > The Pharo Consortium is very happy to announce that Projector Software GmbH > has joined the Consortium as an Gold Member. > > About > - Projector Software GmbH: http://projector.de > - Pharo Consortium: http://consortium.p

[Pharo-dev] [ANN] Pharo Consortium New Gold Member: Projector Software GmbH

The Pharo Consortium is very happy to announce that Projector Software GmbH has joined the Consortium as an Gold Member. About - Projector Software GmbH: http://projector.de - Pharo Consortium: http://consortium.pharo.org The goal of the Pharo Consortium is to allow companies and institutions

[Pharo-dev] Strange Monticello bug: methods are not saved

Hi, I have a *very* strange bug. I am trying to add change these three methods in class “TemporaryVariable”: (I copy the new version): ensureProperties method saveTemp: self. ^ Properties at: self ifAbsentPut: WeakKeyDictionary new removePropertiesIfEmpty ^ Prop

[Pharo-dev] [pharo-project/pharo-core]

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

[Pharo-dev] [pharo-project/pharo-core] 06011e: 50265

Branch: refs/heads/5.0 Home: https://github.com/pharo-project/pharo-core Commit: 06011e07ac516a5fc52a69634f8b19db6f6c3b44 https://github.com/pharo-project/pharo-core/commit/06011e07ac516a5fc52a69634f8b19db6f6c3b44 Author: Jenkins Build Server Date: 2015-08-24 (Mon, 24 Aug 2015

Re: [Pharo-dev] issue with large file path on windows

Hi Hernán Thanks for your feedback 2015-08-24 8:13 GMT+02:00 Hernán Morales Durand : > Nicolai > > 2015-08-23 8:44 GMT-03:00 Nicolai Hess : > >> For those who had problems with pharo on windows and github based >> repositories, >> I built a windows vm with support for long paths: >> >> >> https:/