- Pharo-dev - lists.pharo.org

[Pharo 7.0-dev] Build #390: 20876-Drag-and-drop-of-methods-is-broken
by ci-pharo-ci-jenkins2＠inria.fr Dec. 19, 2017

Dec. 19, 2017

There is a new Pharo build available! The status of the build #390 was: FAILURE. The Pull Request #616 was integrated: "20876-Drag-and-drop-of-methods-is-broken" Pull request url: https://github.com/pharo-project/pharo/pull/616 Issue Url: https://pharo.fogbugz.com/f/cases/20876 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[ANN] Pharo TechTalk Dec 19: Contributing to Pharo7
by Marcus Denker Dec. 19, 2017

Dec. 19, 2017

Pharo TechTalk December 17: - 19 Dec 2017 5:00 PM - 7:00 PM (UTC+01:00) - Where? Discord / Youtube live Topic: Contributing. How to report bugs, submit code change. This will be a hands-on session where we show how to â¢ report bugs â¢ create pull requests â¢ help reviewing issues and pull requests https://association.pharo.org/event-2642666

1 1

[Pharo 7.0-dev] Build #381: 20796-String-should-understand-readStreamDowriteStreamDo-to-be-polymorph-with-FileReference
by ci-pharo-ci-jenkins2＠inria.fr Dec. 18, 2017

Dec. 18, 2017

There is a new Pharo build available! The status of the build #381 was: SUCCESS. The Pull Request #605 was integrated: "20796-String-should-understand-readStreamDowriteStreamDo-to-be-polymorph-with-FileReference" Pull request url: https://github.com/pharo-project/pharo/pull/605 Issue Url: https://pharo.fogbugz.com/f/cases/20796 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

4 6

[Ann] New Calypso version 0.8
by Denis Kudriashov Dec. 18, 2017

Dec. 18, 2017

Hello. I glad announce new Calypso version. It is a big refactoring on navigation model and browser pluggability. Look for details in my blog http://dionisiydk.blogspot.fr/2017/12/new-calypso-version-08-is-out.html. Now I start document new design and will post progress on it. Notice: this version is not adopted for TelePharo and Cargo. It will be done soon. Best regards, Denis

4 8

Re: [Pharo-dev] Epicea feedback - save points
by Martin Dias Dec. 17, 2017

Dec. 17, 2017

El 16 dic. 2017 5:04 AM, "Stephane Ducasse" <stepharo.self(a)gmail.com> escribiÃ³: I love epicea :) Did you see that now people use my extension to generate docs :) no i didnt! how could i see that? Stef On Sat, Dec 16, 2017 at 9:03 AM, Stephane Ducasse <stepharo.self(a)gmail.com> wrote: > Thanks Martin!!! > > On Wed, Dec 13, 2017 at 1:29 PM, Martin Dias <tinchodias(a)gmail.com> wrote: >> Hi >> >> When you "save and close" or "save as..." then next changes will go to a new >> log file. Then, they will have a new item of the left of the browser (as >> Stef said). >> When you just "save", I agree I'd like that. It was there originally but I >> disabled it because of a bug related with the announcement. Apparently now >> it can be re-enabled: >> https://pharo.fogbugz.com/f/cases/18754/Epicea-should-log-image-saving >> >> MartÃn >> >> On Wed, Dec 13, 2017 at 8:52 AM, Stephane Ducasse < stepharo.self(a)gmail.com> >> wrote: >>> >>> Ok so we should check because it should not be complex to add that. >>> The model is quite nice. >>> >>> On Wed, Dec 13, 2017 at 11:47 AM, Ben Coman <btc(a)openinworld.com> wrote: >>> > Hi Stef, >>> > >>> > I think that is incorrect. Its easy to be certain... >>> > 1. Open Epicea >>> > 2. Save and continue >>> > 3. Open Epicea and observe there is no difference >>> > >>> > cheers -ben >>> > >>> > >>> > On 13 December 2017 at 17:59, Stephane Ducasse < stepharo.self(a)gmail.com> >>> > wrote: >>> >> >>> >> I think that epicea save point are the list elements on the left. >>> >> >>> >> >>> >> On Wed, Dec 13, 2017 at 9:05 AM, Norbert Hartl <norbert(a)hartl.name> >>> >> wrote: >>> >> > Same for me. I thought the last save point would be the last session >>> >> > in >>> >> > the list but I donât think that is really true. So Iâm confused by >>> >> > Epicea, >>> >> > too. >>> >> > >>> >> > Norbert >>> >> > >>> >> >> Am 13.12.2017 um 08:27 schrieb Ben Coman <btc(a)openinworld.com>: >>> >> >> >>> >> >> When I'm in need Epicea, the common scenario is that I've working in >>> >> >> the same session of an Image most of the day, or even days, and I've >>> >> >> done >>> >> >> something stupid to lock up the UI, and its only been an hour since >>> >> >> my last >>> >> >> save point (force of habit). When I review Epicea, "Filter > Show >>> >> >> latest >>> >> >> changes" its still ahrd to determine which changes I'm missing. >>> >> >> What I've >>> >> >> just realised is I miss the visibility of the Save Point in the old >>> >> >> changes >>> >> >> system. I'd find it really useful for the save points to be show in >>> >> >> the >>> >> >> changes list, and also a filter I'd find really useful is "Shows >>> >> >> latest >>> >> >> changes since last save". >>> >> >> >>> >> >> >>> >> >> cheers -ben >>> >> > >>> >> >>> > >>> >>

2 1

Drag and drop of methods
by Cyril Ferlicot D. Dec. 16, 2017

Dec. 16, 2017

Hi, In the latest Pharo 7 I cannot drag and drop methods anymore in Nautilus. Pharo version: Pharo-7.0+alpha.build.389.sha.e642e96a93951b2765dc808a512b81dc3d52e150 (32 Bit) Stack: TransferMorph(Object)>>doesNotUnderstand: #buildWithSpec FTPluggableIconListMorphAdaptorDataSource>>transferFor:from: FTPluggableIconListMorphAdaptor(FTTableMorph)>>startDrag: MouseClickState>>drag: MouseClickState>>handleEvent:from: HandMorph>>handleEvent: HandMorph>>processEventsFromQueue: HandMorph>>processEvents -- Cyril Ferlicot https://ferlicot.fr http://www.synectique.eu 2 rue Jacques PrÃ©vert 01, 59650 Villeneuve d'ascq France

2 1

[Pharo 7.0-dev] Build #389: SUCCESS
by ci-pharo-ci-jenkins2＠inria.fr Dec. 16, 2017

Dec. 16, 2017

There is a new Pharo build available! The status of the build #389 was: SUCCESS. Could not extract further issue information from commit message: Tx. Indeed it is better that way Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 7.0-dev] Build #388: SUCCESS
by ci-pharo-ci-jenkins2＠inria.fr Dec. 16, 2017

Dec. 16, 2017

There is a new Pharo build available! The status of the build #388 was: SUCCESS. Could not extract further issue information from commit message: Look nicer. And tx! Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

Implementors of margins in GLMRubScrolledTextBrick
by Stephane Ducasse Dec. 16, 2017

Dec. 16, 2017

Hi I'm working on 16969 https://pharo.fogbugz.com/f/cases/16969/ which is basically cleaning the use of rectangle instead of using Margin. Now I'm surprised because GLMRubScrolledTextBrick>>withoutMargins uses self margins: but I cannot find the method. Did I misses something? I rewrote it as withoutMargins self margins: (0@0) asMargin but I'm still curious. Stef

3 4

[Pharo 7.0-dev] Build #387: 20870-Spec-FastTable-badly-support-drag-and-drop
by ci-pharo-ci-jenkins2＠inria.fr Dec. 16, 2017

Dec. 16, 2017

There is a new Pharo build available! The status of the build #387 was: FAILURE. The Pull Request #608 was integrated: "20870-Spec-FastTable-badly-support-drag-and-drop" Pull request url: https://github.com/pharo-project/pharo/pull/608 Issue Url: https://pharo.fogbugz.com/f/cases/20870 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0