Re: [Pharo-dev] Baseline/Configuration loading bars

Le 02/11/2017 à 20:01, Stephane Ducasse a écrit : > Super tx Cyril > Tx dale. I think that Camillo back then introduced Job. > Stef > > Hi, The issue is corrected in Metacello/metacello on github and Dale updated the Pharo 6.1/7.0 tags. (Thank you) Now, how should I integrate it in Pharo? Will

Re: [Pharo-dev] UFFI #rebuildFieldAccessors problem

I know this problem annonymousClassCreator ^ String streamContents: [ :stream | stream nextPutAll: '(FFITypeArray ofType: #'; print: self objectClass type class; nextPutAll: ' size: ';

Re: [Pharo-dev] Baseline/Configuration loading bars

Super tx Cyril Tx dale. I think that Camillo back then introduced Job. Stef On Thu, Nov 2, 2017 at 7:00 PM, Dale Henrichs wrote: > Cyrille has submitted a bug[1] and I believe that he is taking a crack at a > fix ... > > Personally I am not aware of whether or not > String>>displayProgressAt:from

Re: [Pharo-dev] Baseline/Configuration loading bars

Cyrille has submitted a bug[1] and I believe that he is taking a crack at a fix ... Personally I am not aware of whether or not String>>displayProgressAt:from:to:during: still exists and if not whether or not it is the approved api for interacting with progress bars ... I sort of assumed that

Re: [Pharo-dev] Baseline/Configuration loading bars

Hi dale I'm confused :) what we should do? I could not get it (ok I'm a doct waiting room so not a super place to check). Stef On Wed, Nov 1, 2017 at 4:43 PM, Dale Henrichs wrote: > Ben, > > I took a look at this and Metacell has wrapped the load expressions with a > MetacelloPlatform>>do:displa

Re: [Pharo-dev] OSWindow OS X VM bug

Thanks ronie! This is important for the future of Pharo. On Thu, Nov 2, 2017 at 2:48 AM, Ronie Salgado wrote: > Hi, > > I finally managed to track the problem with keyboard events with OSWindow. > However, I cannot fix it without introducing a crash in an autorelease, or a > memory leak. > > The

Re: [Pharo-dev] Debugger "reporting" feature

Can you open a bug entry? On Thu, Nov 2, 2017 at 4:16 PM, Ben Coman wrote: > sounds good. > cheers -ben > > On Thu, Nov 2, 2017 at 10:55 PM, Denis Kudriashov > wrote: >> >> Maybe we should name and implement it as "copy stack to clipboard"? >> >> 2017-11-02 13:19 GMT+01:00 Ben Coman : >>> >>> I'

Re: [Pharo-dev] [Pharo 7.0-dev] Build #251: 20616-Convert-file-format-to-tonel

Hi! this means you can go-back to contribute :) keep in mind: - you will need a new image. - you will need to have up-to-date your fork and clone. enjoy, Esteban > On 2 Nov 2017, at 16:12, ci-pharo-ci-jenki...@inria.fr wrote: > > There is a new Pharo build available! > > The status of

Re: [Pharo-dev] Debugger "reporting" feature

sounds good. cheers -ben On Thu, Nov 2, 2017 at 10:55 PM, Denis Kudriashov wrote: > Maybe we should name and implement it as "copy stack to clipboard"? > > 2017-11-02 13:19 GMT+01:00 Ben Coman : > >> I've never used it to auto-report to any remote remote server. That part >> can go. >> But as I

[Pharo-dev] [Pharo 7.0-dev] Build #251: 20616-Convert-file-format-to-tonel

There is a new Pharo build available! The status of the build #251 was: SUCCESS. The Pull Request #423 was integrated: "20616-Convert-file-format-to-tonel" Pull request url: https://github.com/pharo-project/pharo/pull/423 Issue Url: https://pharo.fogbugz.com/f/cases/20616 Build Url: htt

Re: [Pharo-dev] Debugger "reporting" feature

Maybe we should name and implement it as "copy stack to clipboard"? 2017-11-02 13:19 GMT+01:00 Ben Coman : > I've never used it to auto-report to any remote remote server. That part > can go. > But as I stated, I do find it useful for getting a text representation of > the stack for manually past

Re: [Pharo-dev] [Pharo 7.0-dev] Build #250: 20616-Convert-file-format-to-tonel

> On 2 Nov 2017, at 15:34, Guillermo Polito wrote: > > Fixed thanks! > > On Thu, Nov 2, 2017 at 3:10 PM, teso...@gmail.com > mailto:teso...@gmail.com>> wrote: > This is a problem in the network, Guille is going to restart the nodes. > > On Thu, Nov 2, 2017 at 3:

Re: [Pharo-dev] [Pharo 7.0-dev] Build #250: 20616-Convert-file-format-to-tonel

Fixed On Thu, Nov 2, 2017 at 3:10 PM, teso...@gmail.com wrote: > This is a problem in the network, Guille is going to restart the nodes. > > On Thu, Nov 2, 2017 at 3:08 PM, wrote: > >> There is a new Pharo build available! >> >> The status of the build #250 was: FAILURE. >> >> The Pull Request

Re: [Pharo-dev] [Pharo 7.0-dev] Build #250: 20616-Convert-file-format-to-tonel

This is a problem in the network, Guille is going to restart the nodes. On Thu, Nov 2, 2017 at 3:08 PM, wrote: > There is a new Pharo build available! > > The status of the build #250 was: FAILURE. > > The Pull Request #423 was integrated: "20616-Convert-file-format-to-tonel" > Pull request url:

[Pharo-dev] [Pharo 7.0-dev] Build #250: 20616-Convert-file-format-to-tonel

There is a new Pharo build available! The status of the build #250 was: FAILURE. The Pull Request #423 was integrated: "20616-Convert-file-format-to-tonel" Pull request url: https://github.com/pharo-project/pharo/pull/423 Issue Url: https://pharo.fogbugz.com/f/cases/20616 Build Url: htt

Re: [Pharo-dev] Debugger "reporting" feature

I've never used it to auto-report to any remote remote server. That part can go. But as I stated, I do find it useful for getting a text representation of the stack for manually pasting into fogbugz issues, instead of having to dig through the halos into the morph contents. Can this part be kept an

Re: [Pharo-dev] Debugger "reporting" feature

I think it is outdated feature and we should remove it to not confuse people. 2017-11-02 9:10 GMT+01:00 Peter Uhnák : > Is this functionality actually used? Where do the reports end up? What is > contained in the report? > > Peter > > On Thu, Nov 2, 2017 at 4:35 AM, Ben Coman wrote: > >> In the

Re: [Pharo-dev] Debugger "reporting" feature

Is this functionality actually used? Where do the reports end up? What is contained in the report? Peter On Thu, Nov 2, 2017 at 4:35 AM, Ben Coman wrote: > In the Pre-Debug window there is the button that coverts the call > stack to text that can be pasted into an email. But when you proceed