- Pharo-dev - lists.pharo.org

[Pharo 8.0] Build #181: 2813-Failing-tests-in-MorphicTextInputFieldAdapterTest

by ci-pharo-ci-jenkins2＠inria.fr

There is a new Pharo build available! The status of the build #181 was: FAILURE. The Pull Request #3003 was integrated: "2813-Failing-tests-in-MorphicTextInputFieldAdapterTest" Pull request url: https://github.com/pharo-project/pharo/pull/3003 Issue Url: https://github.com/pharo-project/pharo/issues/2813 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

March 25, 2019

Re: [Pharo-dev] How to manage your code with Iceberg

by Serge Stinckwich

On Mon, Mar 25, 2019 at 10:11 AM ducasse <stepharo(a)netcourrier.com> wrote: > For recent projects but for old projects we will not be able to update > them anymore. > Iâm looking for an alternative to bintray. > > Why not using github releases like Etienne is doing here: https://github.com/cormas/Booklet-CORMAS -- Serge Stinckwic h Int. Research Unit on Modelling/Simulation of Complex Systems (UMMISCO) Sorbonne University (SU) French National Research Institute for Sustainable Development (IRD) U niversity of YaoundÃ© I, Cameroun "Programs must be written for people to read, and only incidentally for machines to execute." https://twitter.com/SergeStinckwich

March 25, 2019

[Pharo 8.0] Build #180: 2996-test-failing-on-CI-GTSpotterExtensionsOnClassTesttestBasic

by ci-pharo-ci-jenkins2＠inria.fr

There is a new Pharo build available! The status of the build #180 was: FAILURE. The Pull Request #3001 was integrated: "2996-test-failing-on-CI-GTSpotterExtensionsOnClassTesttestBasic" Pull request url: https://github.com/pharo-project/pharo/pull/3001 Issue Url: https://github.com/pharo-project/pharo/issues/2996 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

March 25, 2019

Re: [Pharo-dev] How to manage your code with Iceberg

by ducasse

For recent projects but for old projects we will not be able to update them anymore. Iâm looking for an alternative to bintray. Stef > On 25 Mar 2019, at 01:57, Sean P. DeNigris <sean(a)clipperadams.com> wrote: > > Sean P. DeNigris wrote >> FYI the bin tray link on GH -> âThe requested path was not found.â > > It's working now. > > > > ----- > Cheers, > Sean > -- > Sent from: http://forum.world.st/Pharo-Smalltalk-Developers-f1294837.html >

March 25, 2019

Esteban's ChangeLog week of 18 March 2019

by estebanlm＠gmail.com

Hello! This is my weekly ChangeLog, from 18 March 2019 to 24 March 2019. You can see it in a better format by going here: http://log.smallworks.eu/web/search?from=18/3/2019&to=24/3/2019 ChangeLog ========= 21 March 2019: -------------- * I worked (despite being sick ;) ) on fixing how some announcements are handled in +WindowPresenter+ The problem was: +WidgetBuilt+ and +WindowBuilt+ announcers were called after call an open command. This is usuallu not a problem but: * What happens if you run a modal dialog? No announce will be sent until modal is over. * What happens if I want to modify the presenter 'after' is built but 'before' is shown? So, I moved this announcements to right after the window is built, and I added a new vocabulary +#whenOpenedDo:+ to match the older +#whenClosedDo:+ (btw... I think I will need an event to validate window closing... but that's another 2c) 19 March 2019: -------------- * Fixing UFFI architecture problems * * * I spent some time fixing some problems detected in UFFI. What happeneds is that when the inclusion of different architectures, some older asumptions were not valid anymore: 1) +long ~= void*+ This means passing +0+ as a +NULL+ is no longer valid! And that, of course, crashes some libraries, specially on windows. To fix this: * now passing nil will be mapped to +ExternalAddress null+ instead +0+. Somehow, I do not like to use the nil as NULL, and because of that: * I introduced the "constant" value +NULL+. Yes, now you can put +NULL+ in your call invocations and they will be translated to a NULL in the callout. 2) Not all constant values are equivallent. In UFFI, you can do something like this: ---- self ffiCall: #(void aFunction(42)) ---- means passing a constant value instead an argument. This is very useful in some contexts... But we cannot longer assume this value is same size as required. We need to make explicit the type! So, I modified the parser and now you can have calls like this: ---- self ffiCall: #(void aFunction( (ulong) 42 )) ---- Making the thing usable again :) *BEWARE:* This will only work for "numeric" types. You cannot cast anything as in C! cheers! Esteban

March 25, 2019

Re: [Pharo-dev] How to manage your code with Iceberg

by Sean P. DeNigris

Sean P. DeNigris wrote > FYI the bin tray link on GH -> âThe requested path was not found.â It's working now. ----- Cheers, Sean -- Sent from: http://forum.world.st/Pharo-Smalltalk-Developers-f1294837.html

March 25, 2019

Re: [Pharo-dev] How to manage your code with Iceberg

by Tim Mackinnon

Damn you autocorrect - I mean âBOFâ about releaser. > On 24 Mar 2019, at 20:31, Tim Mackinnon <tim(a)testit.works> wrote: > > Possibly it could be a bot - as Iâd be interested in understanding more about that too. > >> On 24 Mar 2019, at 17:51, Tudor Girba <tudor(a)tudorgirba.com> wrote: >> >> Weâd be happy to talk about it :) >> >> Doru >> >> >> >>> On Mar 24, 2019, at 4:40 PM, ducasse <stepharo(a)netcourrier.com> wrote: >>> >>> We will add patterns of management. >>> >>> I would like to discuss about releaser at Pharodays :) >>> >>> Stef >>> >>>> On 24 Mar 2019, at 15:21, Tudor Girba <tudor(a)tudorgirba.com> wrote: >>>> >>>> Nice work! And very useful for newcomers, too :) >>>> >>>> Doru >>>> >>>>> On Mar 24, 2019, at 10:22 AM, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: >>>>> >>>>> Hi >>>>> >>>>> I'm happy to announce a new booklet (soon to be released) on how to manage code with Iceberg. We plan to discuss management patterns in the future. >>>>> >>>>> https://github.com/SquareBracketAssociates/Booklet-ManagingCode >>>>> >>>>> Stef and Guille >>>>> >>>>> -------------------------------------------- >>>>> StÃ©phane Ducasse >>>>> http://stephane.ducasse.free.fr >>>>> http://www.synectique.eu / http://www.pharo.org >>>>> 03 59 35 87 52 >>>>> Assistant: Julie Jonas >>>>> FAX 03 59 57 78 50 >>>>> TEL 03 59 35 86 16 >>>>> S. Ducasse - Inria >>>>> 40, avenue Halley, >>>>> Parc Scientifique de la Haute Borne, BÃ¢t.A, Park Plaza >>>>> Villeneuve d'Ascq 59650 >>>>> France >>>>> >>>> >>>> -- >>>> www.feenk.com >>>> >>>> "Presenting is storytelling." >>>> >>>> >>> >>> >>> >> >> -- >> www.feenk.com >> >> "Sometimes the best solution is not the best solution." >> >> > >

March 24, 2019

Re: [Pharo-dev] How to manage your code with Iceberg

by Sean P. DeNigris

StÃ©phane Ducasse wrote > I'm happy to announce a new booklet Cool! FYI the bin tray link on GH -> âThe requested path was not found.â ----- Cheers, Sean -- Sent from: http://forum.world.st/Pharo-Smalltalk-Developers-f1294837.html

March 24, 2019

Re: [Pharo-dev] How to manage your code with Iceberg

by Tim Mackinnon

Possibly it could be a bot - as Iâd be interested in understanding more about that too. > On 24 Mar 2019, at 17:51, Tudor Girba <tudor(a)tudorgirba.com> wrote: > > Weâd be happy to talk about it :) > > Doru > > > >> On Mar 24, 2019, at 4:40 PM, ducasse <stepharo(a)netcourrier.com> wrote: >> >> We will add patterns of management. >> >> I would like to discuss about releaser at Pharodays :) >> >> Stef >> >>> On 24 Mar 2019, at 15:21, Tudor Girba <tudor(a)tudorgirba.com> wrote: >>> >>> Nice work! And very useful for newcomers, too :) >>> >>> Doru >>> >>>> On Mar 24, 2019, at 10:22 AM, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: >>>> >>>> Hi >>>> >>>> I'm happy to announce a new booklet (soon to be released) on how to manage code with Iceberg. We plan to discuss management patterns in the future. >>>> >>>> https://github.com/SquareBracketAssociates/Booklet-ManagingCode >>>> >>>> Stef and Guille >>>> >>>> -------------------------------------------- >>>> StÃ©phane Ducasse >>>> http://stephane.ducasse.free.fr >>>> http://www.synectique.eu / http://www.pharo.org >>>> 03 59 35 87 52 >>>> Assistant: Julie Jonas >>>> FAX 03 59 57 78 50 >>>> TEL 03 59 35 86 16 >>>> S. Ducasse - Inria >>>> 40, avenue Halley, >>>> Parc Scientifique de la Haute Borne, BÃ¢t.A, Park Plaza >>>> Villeneuve d'Ascq 59650 >>>> France >>>> >>> >>> -- >>> www.feenk.com >>> >>> "Presenting is storytelling." >>> >>> >> >> >> > > -- > www.feenk.com > > "Sometimes the best solution is not the best solution." > >

March 24, 2019

Re: [Pharo-dev] How to manage your code with Iceberg

by Tudor Girba

Weâd be happy to talk about it :) Doru > On Mar 24, 2019, at 4:40 PM, ducasse <stepharo(a)netcourrier.com> wrote: > > We will add patterns of management. > > I would like to discuss about releaser at Pharodays :) > > Stef > >> On 24 Mar 2019, at 15:21, Tudor Girba <tudor(a)tudorgirba.com> wrote: >> >> Nice work! And very useful for newcomers, too :) >> >> Doru >> >>> On Mar 24, 2019, at 10:22 AM, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: >>> >>> Hi >>> >>> I'm happy to announce a new booklet (soon to be released) on how to manage code with Iceberg. We plan to discuss management patterns in the future. >>> >>> https://github.com/SquareBracketAssociates/Booklet-ManagingCode >>> >>> Stef and Guille >>> >>> -------------------------------------------- >>> StÃ©phane Ducasse >>> http://stephane.ducasse.free.fr >>> http://www.synectique.eu / http://www.pharo.org >>> 03 59 35 87 52 >>> Assistant: Julie Jonas >>> FAX 03 59 57 78 50 >>> TEL 03 59 35 86 16 >>> S. Ducasse - Inria >>> 40, avenue Halley, >>> Parc Scientifique de la Haute Borne, BÃ¢t.A, Park Plaza >>> Villeneuve d'Ascq 59650 >>> France >>> >> >> -- >> www.feenk.com >> >> "Presenting is storytelling." >> >> > > > -- www.feenk.com "Sometimes the best solution is not the best solution."

March 24, 2019