[Pharo-dev] What the state of unifying Beacon with SystemLogger?

Hello. Year ago Beacon and SystemLogger were announced. There was big discussion about them. And there were plans to provide single solution. What was done around that? What exactly should be merged between this libraries? Was Beacon or SystemLogger planned to be end solution? We definitely need

[Pharo-dev] [pharo-project/pharo-core] a9feca: 50699

Branch: refs/heads/5.0 Home: https://github.com/pharo-project/pharo-core Commit: a9feca4038af25d8db84caebf25d29869dbb2ccd https://github.com/pharo-project/pharo-core/commit/a9feca4038af25d8db84caebf25d29869dbb2ccd Author: Jenkins Build Server Date: 2016-04-18 (Mon, 18 Apr 2016

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

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

Re: [Pharo-dev] [Pharo 5] Action needed: check issues for "Pharo5" milestone

Marcus Denker-4 wrote > Yes, it would be nice, but it would be even nicer to release Pharo5 :-) Quote of the week :) - Cheers, Sean -- View this message in context: http://forum.world.st/Pharo-5-Action-needed-check-issues-for-Pharo5-milestone-tp4890513p4890651.html Sent from the Phar

Re: [Pharo-dev] [Pharo 5] Action needed: check issues for "Pharo5" milestone

> On 18 Apr 2016, at 14:45, Marcus Denker wrote: > >> >> I am not even sure if those warnings and errors will cause trouble later, >> because the bigger problem still is, that after all that, the image size is >> exactly the same. >> > the error should be fixed. Can you add an issue? > > Fo

Re: [Pharo-dev] [Pharo 5] Action needed: check issues for "Pharo5" milestone

> > I am not even sure if those warnings and errors will cause trouble later, > because the bigger problem still is, that after all that, the image size is > exactly the same. > the error should be fixed. Can you add an issue? For the size. yes, the VM does not yet compact the Image. This is k

[Pharo-dev] [pharo-project/pharo-core] 488ba5: 50698

Branch: refs/heads/5.0 Home: https://github.com/pharo-project/pharo-core Commit: 488ba5c3d42d57bddf6781e2894da84f7f7724bb https://github.com/pharo-project/pharo-core/commit/488ba5c3d42d57bddf6781e2894da84f7f7724bb Author: Jenkins Build Server Date: 2016-04-18 (Mon, 18 Apr 2016

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

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

Re: [Pharo-dev] [Pharo 5] Action needed: check issues for "Pharo5" milestone

--- Begin Message --- There are several issues with the ImageCleaner, but I did not recognize any of them in the filter link mentioned. In a shiny new image with version 50695, if I execute: ImageCleaner cleanUpForProduction I get alternating growl notifications saying: InformationMissing example

Re: [Pharo-dev] [Pharo-users] GTDebugger shortcuts usability

Added as #10820 but for Pharo6 as per other requests Mark On 18/04/2016 10:30, Tudor Girba wrote: Hi, Indeed. This somehow slipped from the todo list. Could you please open an issue for making the shortcuts settable and mark it for Pharo 5? Cheers, Doru On Apr 17, 2016, at 10:32 PM, Mark

Re: [Pharo-dev] pharo -spur - vm source

> On 17 Apr 2016, at 16:56, Nicolai Hess wrote: > > Is https://github.com/pharo-project/pharo-vm > the place to look > for the current pharo spur vm source ? yes… in spur64 branch, I was going to merge it with “master”, but no time so far. Esteban

Re: [Pharo-dev] [Pharo-users] GTDebugger shortcuts usability

Hi, Indeed. This somehow slipped from the todo list. Could you please open an issue for making the shortcuts settable and mark it for Pharo 5? Cheers, Doru > On Apr 17, 2016, at 10:32 PM, Mark Bestley wrote: > > > The most important thing is allow the user to reassign them. > > e.g. when m

Re: [Pharo-dev] GTDebugger shortcuts usability

Hi Stef, This would have been our intention, but unfortunately, we cannot have that because most of these are already taken by other keybindings in the text editor. Doru > On Apr 18, 2016, at 8:54 AM, stepharo wrote: > > Would be nice to have > > Ctrl+ C create > Ctrl + P proceed >

Re: [Pharo-dev] [Ann] anObject haltOnNextCall

This is cool :) Cheers, Andrei On Fri, Apr 15, 2016 at 10:30 PM, stepharo wrote: > Sweet :) > > > Le 15/4/16 15:04, Denis Kudriashov a écrit : > > Hello. > > I glad to present very simple implementation of object centric debugging > based on Ghost and ObjectVirus projects. > > You can try it by

Re: [Pharo-dev] [Pharo 5] Action needed: check issues for "Pharo5" milestone

> On 18 Apr 2016, at 09:35, Marcus Denker wrote: > > Hi, > > We are down to 38 open issues that have the “Pharo5” Milestone: > > https://pharo.fogbugz.com/f/filters/125/5-0-All > > I just change the Milestone of all “would be nice” Cases. I added a note: As announced 1.5 weeks

[Pharo-dev] [Pharo 5] Action needed: check issues for "Pharo5" milestone

Hi, We are down to 38 open issues that have the “Pharo5” Milestone: https://pharo.fogbugz.com/f/filters/125/5-0-All It is now very important that we decide which of them we have to fix for being able to release Pharo5. It would be nice if *everyone* would have a look who is subscribed