[Pharo-dev] WhatsUp from: 2015-09-07 until: 2015-09-20

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_ACHIEVE

Re: [Pharo-dev] Did no find yet a way to reproduce QA concurrent access

Also, when if this kind of error happens again, can you please fuel it out and sent it to me? Having a stack can be helpful in understanding. Uko > On 06 Sep 2015, at 22:17, stepharo wrote: > > I thought that I could reproduce the QA concurrent access raising a DNU when > we remove a method >

Re: [Pharo-dev] Did no find yet a way to reproduce QA concurrent access

I think that it is related to how I was working with Nautilus announcements. Now as announcements are changed, I can improve that. Just give me a bit of time :) Uko > On 06 Sep 2015, at 22:17, stepharo wrote: > > I thought that I could reproduce the QA concurrent access raising a DNU when >

[Pharo-dev] Did no find yet a way to reproduce QA concurrent access

I thought that I could reproduce the QA concurrent access raising a DNU when we remove a method but I failed. I got again this bug. What I did was selecting a method in Nautilus and removing this method after an implementors and from the message list browser. But I cannot reproduce it. Stef

Re: [Pharo-dev] chunk file format (unrecoverable changes)

Le 6/9/15 21:56, Nicolai Hess a écrit : Do we have a documentation about the format of - class definitions - methods - class comments for the changes file ? Not that I know besides the implementation. I am asking because some entries are using two separator "! !" and some only one "!" And

Re: [Pharo-dev] remove MczInstaller?

Le 5/9/15 18:24, Marcus Denker a écrit : On 05 Sep 2015, at 15:54, stepharo wrote: Are you sure that it is not used when we drag an MCZ on the desktop? No, at least I do not think so. it’s the installer that was added to Squeak before Monticello. The idea is that it can be used to install

Re: [Pharo-dev] remove MczInstaller?

Thanks a lot martin! I checked also and I got confused :) I have to investigate more. Could you open a bug entry because this is handy to be able to browse an mcz by dropping it on the world My impression is that we could remove MCMcmReader class MCMcdReader class Le 5/9/15 19

[Pharo-dev] chunk file format (unrecoverable changes)

Do we have a documentation about the format of - class definitions - methods - class comments for the changes file ? I am asking because some entries are using two separator "! !" and some only one "!" And we have a problem with the "Recover lost changes" browser (https://pharo.fogbugz.com/f/cases

Re: [Pharo-dev] ***important*** cannot remove a class anymore...

What I would like is to have all the changes after one integration with + and - showing the changes. I grouped a bit my analysis in https://pharo.fogbugz.com/f/cases/16491/Revisiting-TextDiffBuilder But now I should finish the other tasks I have pending. I should finish also some issues I sta

[Pharo-dev] [pharo-project/pharo-core] b9b044: 50309

Branch: refs/heads/5.0 Home: https://github.com/pharo-project/pharo-core Commit: b9b04483fa5c00b4ca24f703cd877a066afa8d08 https://github.com/pharo-project/pharo-core/commit/b9b04483fa5c00b4ca24f703cd877a066afa8d08 Author: Jenkins Build Server Date: 2015-09-06 (Sun, 06 Sep 2015

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

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

Re: [Pharo-dev] Low traffic [ANN] only list

> On 06 Sep 2015, at 16:43, Peter Uhnák wrote: > > Subscribing is quite cumbersome. > > 1. subscribe > 2. confirm my subscription > 3. confirm my humanity > > why not just the first? This could discourage people easily midway. > Ok, I have turned 3) off. Marcus

Re: [Pharo-dev] Low traffic [ANN] only list

Subscribing is quite cumbersome. 1. subscribe 2. confirm my subscription 3. confirm my humanity why not just the first? This could discourage people easily midway. Peter On Sun, Sep 6, 2015 at 4:32 PM, Marcus Denker wrote: > Hello, > > We have set up a low traffic announce-only list: > > http

[Pharo-dev] Low traffic [ANN] only list

Hello, We have set up a low traffic announce-only list: http://eepurl.com/byhgL9 The idea is that this is max one mail per month. Marcus

Re: [Pharo-dev] Rubric #mouseDown, #mouseUp and #click

On 06/09/15 11:11, Nicolai Hess wrote: Does the mouseUp on JobProgressMorph work ? I always wondered how I can stop a long running task. I don't know. Not when running tests from the TestRunner. Stephan

Re: [Pharo-dev] ***important*** cannot remove a class anymore...

But this is all implementation details, I'm still not sure what exactly we (Stef) want to send. * change diff after each successful CI build for an issue? * diff after the change has been integrated? Peter

Re: [Pharo-dev] ***important*** cannot remove a class anymore...

> > You are right, Peter. But the way the rest of the world (and many people > using git from Pharo or other Smalltalk implementations) is that you > propose patches which I believe are quite similar to commits. That would be > the equivalent of our slice, I guess. I don't think that slice has eq

[Pharo-dev] [pharo-project/pharo-core] 56e3cc: 50308

Branch: refs/heads/5.0 Home: https://github.com/pharo-project/pharo-core Commit: 56e3cce6d903a8bdca1427aad2d90eb15627d7e6 https://github.com/pharo-project/pharo-core/commit/56e3cce6d903a8bdca1427aad2d90eb15627d7e6 Author: Jenkins Build Server Date: 2015-09-06 (Sun, 06 Sep 2015

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

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

Re: [Pharo-dev] ***important*** cannot remove a class anymore...

On 6 Sep 2015 7:42 am, "Peter Uhnák" wrote: >> >> git clone https://github.com/pharo-project/pharo-core.git >> cd pharo-core/ >> git show 2536752ecdd88e15b00c6d3e29cb055d108731c8 > > > But this is post-integration, we want to review things before they break something, not after. > So ideally monke

Re: [Pharo-dev] Rubric #mouseDown, #mouseUp and #click

Does the mouseUp on JobProgressMorph work ? I always wondered how I can stop a long running task. 2015-09-02 12:25 GMT+02:00 Stephan Eggermont : > We have a few morphs where #on:#mouseDown send: aMessage to: aTarget is > used where I'd expected that to be on #click. Mostly in Rubric and the > Nau

[Pharo-dev] Nautilus strange pattern

Hi I'm trying to understand what there is a need for this window ifNil: [^ self ] And I wonder is this is not problem due to a global announcer that would keep announcer even when the nautilus widget has been deleted. Any other suggestions? Stef classRemoved: anAnnouncement | class oldP

Re: [Pharo-dev] when:send:to: vs. subscribe:send:to:

Le 5/9/15 22:42, Tudor Girba a écrit : +1. We already deprecated on:send:to:/on:do: and I think we should do the same for the subscribe:send:to:. Thanks Doru. I thought the same. Because each time I read subscribe: my mind stops for about half or a second until I remember that this is the s

Re: [Pharo-dev] ***important*** cannot remove a class anymore...

Hi, There is clearly no downside of having more detailed diff information available. We do not have it now, and the proposal of Stef is more than reasonable. It would be great to have someone willing to spend a bit of time helping him to achieve this. Who would like to give this a try? Cheers, D

Re: [Pharo-dev] ***important*** cannot remove a class anymore...

Le 6/9/15 00:33, Sven Van Caekenberghe a écrit : On 05 Sep 2015, at 21:34, stepharo wrote: Le 5/9/15 19:18, Yuriy Tymchuk a écrit : In fact you couldn’t spot the issue by just looking at the patch :) there was a very strange thing that could be fixed with one line, but to identify it I’ve

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

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

Re: [Pharo-dev] ***important*** cannot remove a class anymore...

Peter I just want to get an idea of what is happening. Even after commit. Le 6/9/15 01:41, Peter Uhnák a écrit : git clone https://github.com/pharo-project/pharo-core.git cd pharo-core/ git show 2536752ecdd88e15b00c6d3e29cb055d108731c8 But this is post-integration, we want to rev

[Pharo-dev] [pharo-project/pharo-core] 96f3ce: 50307

Branch: refs/heads/5.0 Home: https://github.com/pharo-project/pharo-core Commit: 96f3ceffe16fa3c72e2ba9e7c7590e00118c4d2f https://github.com/pharo-project/pharo-core/commit/96f3ceffe16fa3c72e2ba9e7c7590e00118c4d2f Author: Jenkins Build Server Date: 2015-09-06 (Sun, 06 Sep 2015

Re: [Pharo-dev] ***important*** cannot remove a class anymore...

> On 06 Sep 2015, at 01:41, Peter Uhnák wrote: > > git clone https://github.com/pharo-project/pharo-core.git > cd pharo-core/ > git show 2536752ecdd88e15b00c6d3e29cb055d108731c8 > > But this is post-integration, we want to review things before they break > something, not after. > So ideally mo