- Pharo-dev - lists.pharo.org

How to manage your code with Iceberg
by StÃ©phane Ducasse March 25, 2019

March 25, 2019

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 <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

6 11

[ANN] Pharo Days 2019 is online!
by Esteban Lorenzano March 25, 2019

March 25, 2019

Hi, We have finished the schedule for upcoming Pharo Days 2019, here a link for the google calendar: https://calendar.google.com/calendar?cid=MDIxdnExNjZpb2VqaWhyN25zYXQwcGpxaW… <https://calendar.google.com/calendar?cid=MDIxdnExNjZpb2VqaWhyN25zYXQwcGpxaW…> Do not forget to register! Esteban

2 2

[Pharo 8.0] Build #184: 3000-MailAddressParser---extend-to-parse-display-name-as-well-as-address
by ci-pharo-ci-jenkins2＠inria.fr March 25, 2019

March 25, 2019

There is a new Pharo build available! The status of the build #184 was: FAILURE. The Pull Request #3002 was integrated: "3000-MailAddressParser---extend-to-parse-display-name-as-well-as-address" Pull request url: https://github.com/pharo-project/pharo/pull/3002 Issue Url: https://github.com/pharo-project/pharo/issues/3000 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[ANN] 1 Tweet/day covering Lands features powered by Pharo: Follow, RT @npapoylias.
by Nick Papoylias March 25, 2019

March 25, 2019

I will be showcasing the *features *of Lands <https://npapoylias.gitlab.io/lands-project/>, in *espresso-sized form* for the next couple of months on twitter ;) *Please support the project by making some noise !* *On related news*: I am joining the LIG lab at <https://www.liglab.fr/en> Grenoble <https://www.liglab.fr/en> to work on *DSLs for the Linux kernel*, so stay tuned ! *Best*, Nick,

2 3

[Pharo 8.0] Build #183: SUCCESS
by ci-pharo-ci-jenkins2＠inria.fr March 25, 2019

March 25, 2019

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

1 0

updated CONTRIBUTING.md
by Marcus Denker March 25, 2019

March 25, 2019

Hi, I have simplified the CONTRIBUTING.md: https://github.com/pharo-project/pharo/blob/Pharo8.0/CONTRIBUTING.md - removed all the pre-git infos. - How to propose a bug fix or enhancement now points to https://github.com/pharo-project/pharo/wiki/Contribute-a-fix-to-Pharo I changed the âWelcomeâ ProBot message to now point to these links when someone opens their very first issue. Marcus

1 0

[Pharo 8.0] Build #182: SUCCESS
by ci-pharo-ci-jenkins2＠inria.fr March 25, 2019

March 25, 2019

There is a new Pharo build available! The status of the build #182 was: SUCCESS. Could not extract further issue information from commit message: Update config.yml welcome first issue: add link to https://github.com/pharo-project/pharo/wiki/Contribute-a-fix-to-Pharo Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 8.0] Build #181: 2813-Failing-tests-in-MorphicTextInputFieldAdapterTest
by ci-pharo-ci-jenkins2＠inria.fr March 25, 2019

March 25, 2019

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…

1 0

[Pharo 8.0] Build #180: 2996-test-failing-on-CI-GTSpotterExtensionsOnClassTesttestBasic
by ci-pharo-ci-jenkins2＠inria.fr March 25, 2019

March 25, 2019

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…

1 0

Esteban's ChangeLog week of 18 March 2019
by estebanlm＠gmail.com March 25, 2019

March 25, 2019

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

1 0