- Pharo-dev - lists.pharo.org

Esteban's ChangeLog week of 2 April 2018
by estebanlm＠gmail.com April 9, 2018

April 9, 2018

Hello! This is my weekly ChangeLog, from 2 April 2018 to 8 April 2018. You can see it in a better format by going here: http://log.smallworks.eu/web/search?from=2/4/2018&to=8/4/2018 ChangeLog ========= 5 April 2018: ------------- * I closed [issue 593](https://github.com/pharo-vcs/iceberg/issues/593), revert a change is not refreshing changes list. * closed [issue 599](https://github.com/pharo-vcs/iceberg/issues/599), add fetch to remote entry in repository view. * fixed [case: 21676](https://pharo.fogbugz.com/f/cases/21676) (this is needed when using tabs). ... and made a backport for Pharo 6.1 [case: 21679](https://pharo.fogbugz.com/f/cases/21679) . * VM and CI : I made a pass to disable old projects still running in the Pharo Jenkins [http://ci.pharo.org](http://ci.pharo.org) . I don't know why they were still running, but that's wrong and they were consuming resources we need :) * I finished [issue 596](https://github.com/pharo-vcs/iceberg/issues/596) : Convert metacello plugin. * I created a github project to follow the work I'm doing with the new Iceberg UI (callled "Tip" :P). You can see it here: [https://github.com/pharo-vcs/iceberg/projects/2](https://github.com/pharo-v… I'm polishing (with the help of Guille and Pablo) the last details before "going public" in a test release. * I will resume posting actions here :) cheers! Esteban

1 0

Re: [Pharo-dev] pharo [vm-dev]
by StÃ©phane Ducasse April 8, 2018

April 8, 2018

Hello Armel The pharo board is not the list to ask questions and get some help. You can send the mail to Pharo Dev <pharo-dev(a)lists.pharo.org> or Pharo-users(a)lists.pharo.org You can also have direct discussion over discord http://discord.gg/Sj2rhxn <http://discord.gg/Sj2rhxn> Now if you want to have help describe clearly - Your OS - what you did? which version of Pharo, which version of the image Pharo 6.1? - did you use the PharoLauncher? Stef > On 8 Apr 2018, at 16:57, feav feav <feavfeav(a)gmail.com> wrote: > > Error. Could not determine platform's libc path for VM. > Try forcing $PLATFORMLIBDIR in /home/pi/pharo/pharo64/pharo/bin/pharo, based on LIBC_SO. > > Cordialement, Armel EMBOLO > <https://accounts.google.com/SignOutOptions?hl=fr&continue=https://mail.goog…> > IngÃ©nieur de travaux en Informatique de Gestion / Analyste programmeur > ElÃ¨ve IngÃ©nieur de Conception en GÃ©nie Logiciel > UniversitÃ© de Maroua, Ecole Nationale SupÃ©rieure Polytechnique de Maroua (ex ISS) > Facebook : Armel Embolo <https://www.facebook.com/armel.embolo> > Linkedin : armel embolo <https://www.linkedin.com/profile/view?id=AAMAABYswuMBn33mi4o_x8R49OxfxiIQVA…> > Tel : (+237) 650231339/698594740 -------------------------------------------- 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

2 1

[ann] gt diagrammer
by Tudor Girba April 7, 2018

April 7, 2018

Hi, We are happy to announce an initial version of GT Diagrammer, an engine for constructing diagrams interactively. This is the newest addition to the next generation GT built on Bloc. It looks like this: https://twitter.com/feenkcom/status/976341449267531776 We chose to work on Diagrammer for multiple reasons. First, developers often need to create hand built diagrams to communicate intentions, and an integrated experience should not require us to leave our environment to create them. At the same time, Diagrammer is an application that requires a widgets and interactions, and thus it is a nice exercise for Bloc and Brick. One requirement we had from the beginning was to make it work with any Bloc element. This means that the editing part had to be reasonably generic. To this end, we now have elements that can define visual editors. This is somewhat a combination between Magritte descriptions, and inspector extensions. An interesting side effect is that now we can edit visual properties when inspecting any element. In other words, we got the basic infrastructure of a UI painter. It looks like this: https://twitter.com/feenkcom/status/982656456968241152 The user interface essentially relies on two widgets: scrollable list and toggle button. While the visual look of the toggle button is inspired from material design, the most interesting part is that now we have an implementation for controlling looks per element instance. A key issue here is that looks can react to events coming from the element and inject visual attributes and possible even change behavior (for example, changing an icon while pressing a button). We will post more about looks soon. We now also have a nice solution for overlays. For example, we have an overlay showing selection and an overlay for resizing elements. Perhaps less obvious, Diagrammer also offers a basic infrastructure for the area of visual languages. As Diagrammer works with any Bloc elements, we can simply create dedicated visual elements. As an example, Diagrammer comes with an implementation of a UML class figure. Furthermore, as the functionality does not impose a specific model, custom language semantics can be mapped on visual actions. There are several things to do still for it to become a mature solution. An important next step is to serialize a diagram scene in a reproducible manner. Currently, the diagram (or any element) can be exported as pdf (https://twitter.com/feenkcom/status/976580153802358786) svg (https://twitter.com/feenkcom/status/976578060429484032) png, gif or jpeg by directly using the low level canvas. However, for the diagram to be truly useful we need to store the result in either code or another reloadable form such as STON. Other future directions are related to figure controlling (for example, custom anchors or line bending points) and to enhanced editors. To play with it, the easiest way is to download the new GT in a Pharo 6.1 image: Metacello new baseline: 'GToolkit'; repository: 'github://feenkcom/gtoolkit/src'; load. And then inspect: GtDiagrammerElement new Cheers, The feenk team -- www.tudorgirba.com www.feenk.com "Presenting is storytelling."

2 1

Grafoscopio Questions
by Sean P. DeNigris April 5, 2018

April 5, 2018

I just loaded 1.3.9 into Pharo 6.1 latest (IIRC 540). Two questions: - I got an error on load about updating the docs. Is this known? If not, I'll go back and get more details - How does one contribute to the docs? I found a typo, but if I edit the STON file the PDF will not be in sync and also where/how do I upload? ----- Cheers, Sean -- Sent from: http://forum.world.st/Pharo-Smalltalk-Developers-f1294837.html

1 0

[Pharo 7.0-dev] Build #756: 21678-Improve-the-Diff-Morph-with-a-title-bar-showing-each-of-the-version-compared
by ci-pharo-ci-jenkins2＠inria.fr April 5, 2018

April 5, 2018

There is a new Pharo build available! The status of the build #756 was: SUCCESS. The Pull Request #1183 was integrated: "21678-Improve-the-Diff-Morph-with-a-title-bar-showing-each-of-the-version-compared" Pull request url: https://github.com/pharo-project/pharo/pull/1183 Issue Url: https://pharo.fogbugz.com/f/cases/21678 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 7.0-dev] Build #755: 21676-TabMorph-throw-an-error-when-the-theme-change
by ci-pharo-ci-jenkins2＠inria.fr April 4, 2018

April 4, 2018

There is a new Pharo build available! The status of the build #755 was: SUCCESS. The Pull Request #1181 was integrated: "21676-TabMorph-throw-an-error-when-the-theme-change" Pull request url: https://github.com/pharo-project/pharo/pull/1181 Issue Url: https://pharo.fogbugz.com/f/cases/21676 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 7.0-dev] Build #754: 21674-Move-AbstractFileReferencehexDumponmax-to-ByteArray
by ci-pharo-ci-jenkins2＠inria.fr April 4, 2018

April 4, 2018

There is a new Pharo build available! The status of the build #754 was: SUCCESS. The Pull Request #1179 was integrated: "21674-Move-AbstractFileReferencehexDumponmax-to-ByteArray" Pull request url: https://github.com/pharo-project/pharo/pull/1179 Issue Url: https://pharo.fogbugz.com/f/cases/21674 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 7.0-dev] Build #753: 21638-Implementing-FT2Plugin-with-FFI-calls-in-the-image-side
by ci-pharo-ci-jenkins2＠inria.fr April 4, 2018

April 4, 2018

There is a new Pharo build available! The status of the build #753 was: SUCCESS. The Pull Request #1142 was integrated: "21638-Implementing-FT2Plugin-with-FFI-calls-in-the-image-side" Pull request url: https://github.com/pharo-project/pharo/pull/1142 Issue Url: https://pharo.fogbugz.com/f/cases/21638 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 7.0-dev] Build #752: 21672-Package-deprecation-based-on-deprecated-manifest-class
by ci-pharo-ci-jenkins2＠inria.fr April 4, 2018

April 4, 2018

There is a new Pharo build available! The status of the build #752 was: SUCCESS. The Pull Request #1178 was integrated: "21672-Package-deprecation-based-on-deprecated-manifest-class" Pull request url: https://github.com/pharo-project/pharo/pull/1178 Issue Url: https://pharo.fogbugz.com/f/cases/21672 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

CFP - IWST 2018 - International Workshop on Smalltalk Technologies
by Anne Etien April 4, 2018

April 4, 2018

CFP - IWST 2018 - International Workshop on Smalltalk Technologies [Please accept our apologies if you receive multiple copies of this call] [Please send to interested colleagues / mailing-lists] ************************************************************************************************************ CALL FOR PAPERS IWST 2018 â International Workshop on Smalltalk Technologies http://esug.org/wiki/pier/Conferences/2018/International-Workshop-IWST_18 <http://www.esug.org/wiki/pier/Conferences/2017/International-Workshop-IWST_…> Cagliari, Italy; Between September 10th and 14th, 2018 ************************************************************************************************************ ------------------- Goals and scopes ------------------- The goals of the workshop is to create a forum around advances or experience in Smalltalk and to trigger discussions and exchanges of ideas. The topics of your paper can be on all aspect of Smalltalk, theoretical as well as practical. Participants are invited to submit research articles or industrial papers. This year we want to open two different tracks: one research track and one industrial track with less scientific constraints. We expect papers of three kinds: Short position papers describing emerging ideas Long research papers with deeper description of experiments and of research results. Industrial papers with presentation of real and innovative Smalltalk applications; this kind of paper should enlighten why Smalltalk is really appropriate for your application. We will not enforce any length restriction. -------------------- Important Dates -------------------- Submission deadline: June 15th, 2018 Notification deadline: July 20th, 2018 Workshop : between September 10th and 14th, 2018 All accepted papers will be published in ACM DL (To be confirmed) ------------------- Topics ------------------- We welcome contributions on all aspects, theoretical as well as practical, of Smalltalk related topics such as: -Aspect-oriented programming, -Design patterns, -Experience reports, -Frameworks, -Implementation, new dialects or languages implemented in Smalltalk, -Interaction with other languages, -Meta-programming and Meta-modeling, -Tools ------------------- Best Paper Award ------------------- To encourage the submission of high-quality papers, the IWST organizing committee is very proud to announce a Best Paper Award for this edition of IWST. We thank the Lam Research Corporation for its financial contribution which makes it possible for prizes for the three best papers: 1000 USD for first place, 600 USD for second place and 400 USD for third place. The ranking will be decided by the program committee during the review process. The awards will be given during the ESUG conference social event. The Best Paper Award will take place only with a minimum of six submissions. Notice also that to be illegible, a paper must be presented at the workshop by one of the author and that the presenting author must be registered at the ESUG conference. ------------------- Publication ------------------- Both submissions and final papers must be prepared using the ACM SIGPLAN 10 point format. Templates for Word and LaTeX are available at http://www.acm.org/sigs/sigplan/authorInformation.htm <http://www.acm.org/sigs/sigplan/authorInformation.htm>. This site also contains links to useful informations on how to write effective submissions. ------------------- Submission ------------------- All submissions must be sent via easychair: https://easychair.org/conferences/?conf=iwst18 <https://easychair.org/conferences/?conf=iwst18> ------------------- Program chairs ------------------- Anne Etien (UniversitÃ© de Lille, France) Loic Lagadec (Ensta Bretagne, France)

1 0