- Pharo-dev - lists.pharo.org

[Pharo 7.0-dev] Build #1071: 22161-Add-more-log-to-bootstrap

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

There is a new Pharo build available! The status of the build #1071 was: FAILURE. The Pull Request #1570 was integrated: "22161-Add-more-log-to-bootstrap" Pull request url: https://github.com/pharo-project/pharo/pull/1570 Issue Url: https://pharo.fogbugz.com/f/cases/22161 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

June 18, 2018

[Pharo 7.0-dev] Build #1070: 22168-Integrate-Iceberg-111

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

There is a new Pharo build available! The status of the build #1070 was: SUCCESS. The Pull Request #1566 was integrated: "22168-Integrate-Iceberg-111" Pull request url: https://github.com/pharo-project/pharo/pull/1566 Issue Url: https://pharo.fogbugz.com/f/cases/22168 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

June 18, 2018

Re: [Pharo-dev] [Pharo-users] [Ann] Iceberg v1.1.1

by Norbert Hartl

Thanks again for the new things. Just a little maneuver critique. The amount of changes you did should be iceberg 1.2.0 and 1.1.1. Versions are cheap ;) and everything which is not really a hot-fix should be a new minor version. Norbert > Am 18.06.2018 um 17:47 schrieb Guillermo Polito <guillermopolito(a)gmail.com>: > > Hi everybody, > > This week we have a small patch release of Iceberg, version v1.1.1. > This version will be available in the next Pharo build. > > In summary, this release fixes two issues with the new credentials manager, and introduces a couple of other enhancements/bugfixes. > > Below you will find the detailed changes log. > Enjoy, > Guille > > Integrate Iceberg 1.1.1 > https://pharo.fogbugz.com/f/cases/22168/Integrate-Iceberg-1-1-1 <https://pharo.fogbugz.com/f/cases/22168/Integrate-Iceberg-1-1-1> > https://github.com/pharo-vcs/iceberg/releases/tag/v1.1.1 <https://github.com/pharo-vcs/iceberg/releases/tag/v1.1.1> > #864 <https://github.com/pharo-project/pharo/pull/864> Repairing Missing repositories lead to wrong source directory > #861 <https://github.com/pharo-project/pharo/pull/861> update tonel to v1.0.9 > #836 <https://github.com/pharo-project/pharo/pull/836> DefaultBackendType class variable is unused > #862 <https://github.com/pharo-project/pharo/pull/862> Iceberg tests are not running in Pharo 7 > #852 <https://github.com/pharo-project/pharo/pull/852> Make error dialogs copy-pastable > #858 <https://github.com/pharo-project/pharo/pull/858> IceTipReadOnlyTextMorph does not allow select and copy anymore > #850 <https://github.com/pharo-project/pharo/pull/850> Change Detached head status from error to warning if we are on a tag > #853 <https://github.com/pharo-project/pharo/pull/853> Clone dialog "username" is confusing > #860 <https://github.com/pharo-project/pharo/pull/860> CredentialStore API > #854 <https://github.com/pharo-project/pharo/pull/854> Error in History window > > > > -- > > Guille Polito > Research Engineer > > Centre de Recherche en Informatique, Signal et Automatique de Lille > CRIStAL - UMR 9189 > French National Center for Scientific Research - http://www.cnrs.fr <http://www.cnrs.fr/> > > Web: http://guillep.github.io <http://guillep.github.io/> > Phone: +33 06 52 70 66 13

June 18, 2018

[Ann] Iceberg v1.1.1

by Guillermo Polito

Hi everybody, This week we have a small patch release of Iceberg, version v1.1.1. This version will be available in the next Pharo build. In summary, this release fixes two issues with the new credentials manager, and introduces a couple of other enhancements/bugfixes. Below you will find the detailed changes log. Enjoy, Guille Integrate Iceberg 1.1.1 https://pharo.fogbugz.com/f/cases/22168/Integrate-Iceberg-1-1-1 https://github.com/pharo-vcs/iceberg/releases/tag/v1.1.1 #864 <https://github.com/pharo-project/pharo/pull/864> Repairing Missing repositories lead to wrong source directory #861 <https://github.com/pharo-project/pharo/pull/861> update tonel to v1.0.9 #836 <https://github.com/pharo-project/pharo/pull/836> DefaultBackendType class variable is unused #862 <https://github.com/pharo-project/pharo/pull/862> Iceberg tests are not running in Pharo 7 #852 <https://github.com/pharo-project/pharo/pull/852> Make error dialogs copy-pastable #858 <https://github.com/pharo-project/pharo/pull/858> IceTipReadOnlyTextMorph does not allow select and copy anymore #850 <https://github.com/pharo-project/pharo/pull/850> Change Detached head status from error to warning if we are on a tag #853 <https://github.com/pharo-project/pharo/pull/853> Clone dialog "username" is confusing #860 <https://github.com/pharo-project/pharo/pull/860> CredentialStore API #854 <https://github.com/pharo-project/pharo/pull/854> Error in History window -- Guille Polito Research Engineer Centre de Recherche en Informatique, Signal et Automatique de Lille CRIStAL - UMR 9189 French National Center for Scientific Research - *http://www.cnrs.fr <http://www.cnrs.fr>* *Web:* *http://guillep.github.io* <http://guillep.github.io> *Phone: *+33 06 52 70 66 13

June 18, 2018

[Pharo 7.0-dev] Build #1069: Revert "22161-Add-more-log-to-bootstrap"

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

There is a new Pharo build available! The status of the build #1069 was: SUCCESS. The Pull Request #1569 was integrated: "Revert "22161-Add-more-log-to-bootstrap"" Pull request url: https://github.com/pharo-project/pharo/pull/1569 Issue Url: https://pharo.fogbugz.com/f/cases/revert Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

June 18, 2018

Re: [Pharo-dev] [Moose-dev] [Pharo-users] [ann] gt documenter

by Tudor Girba

Hi, Thanks. About the next steps: We mostly think in terms of the overall goal, and the concrete next steps somehow happen. For us the end goal is a moldable environment that integrates all workflows related to development. Documentation is one of those development activities that are both pervasive and typically disliked, so it is only natural that we want to aim to create a full experience for it within the environment. What is more interesting to us is that we could create this experience without much effort due to the flexibility of the underlying framework. There is still engineering work to do, but I think the most difficult part is to rethink the way we approach UI given these new abilities. Cheers, Doru > On Jun 17, 2018, at 3:09 PM, Denis Kudriashov <dionisiydk(a)gmail.com> wrote: > > Hi Tudor. > > This is super impressive. > What's next? Do you plan to implement IDE for writing documents, navigation, refactorings? (senders, renames should find all places in documents) > > 2018-06-13 21:57 GMT+01:00 Tudor Girba <tudor(a)tudorgirba.com>: > Hi, > > We are happy to announce a new leap of GToolkit Documenter, the tool for manipulating live documents directly in the development environment: > https://github.com/feenkcom/gtoolkit-documenter > > Documenter is part of the second generation GToolkit project, it is based on Bloc and works with the latest Pillar. It is mainly developed by Juraj Kubelka. > > Attached you can see a preview of how documents look like: > > <gt-documenter.png> > > At its core it offers a live editor for manipulating Pillar documents. The interaction happens seamlessly directly in the text editor, and it can be combined with different types of previews to serve several classes of use cases: > â¢ code documentation > â¢ tutorials > â¢ interactive data notebook > > > Code documentation > ---- > Documenter complements the GToolkit Examples engine to redefine code documentation. When practicing example-driven development, examples get written as part of the typical development. Once examples exist, they can be quickly put together in a document to form documentation. For example, the linked picture shows the comment of a class containing a visual explanation: > https://twitter.com/feenkcom/status/973899862482866176 > > You can see a live example of documentation by inspecting the following snippet: > GtDocumenter editorForText: BrToggleExamples comment. > > > Tutorials: > ---- > Documenter offers a new experience of writing tutorials for Pharo by enabling the creation and embedding of Epicea change sessions directly in the document. For example, take a look at the following animation: > https://twitter.com/feenkcom/status/999975333972541440 > > The document shows a method on top, and a change preview at the bottom showing both the code and the associated diff to the state from the image. Applying the change updates both the change view (no more diff), and method preview. This speeds up significantly the process of going through a tutorial. Furthermore, given that now the document shows the diff to the current image, the reader can safely explore alternative scenario and come back to the tutorial at any time without losing the overview. > > The size of the preview can also be adjusted live: > https://twitter.com/feenkcom/status/1001152789874167808 > https://twitter.com/feenkcom/status/1001407762285375490 > > You can see a live tutorial by inspecting: > IceRepository repositoriesLocation / 'feenkcom'/ 'gtoolkit-examples' / 'doc' / 'tutorial' / 'examples-tutorial.pillarâ. > > > Interactive data notebook: > ---- > A Documenter document can also be used as an interactive notebook. Internally it essentially acts as a playground: > â¢ it supports defining variables in code snippets, and > â¢ the execution of code shows an embedded inspector. > > For example: > https://twitter.com/feenkcom/status/996310432225820672 > https://twitter.com/feenkcom/status/1002851190475026432 > > An example, can be seen by inspecting: > IceRepository repositoriesLocation / 'feenkcom'/ 'gtoolkit' / 'doc' / 'gtoolkit' / 'gtoolkit.pillar'. > > > As always, please do let us know what you think. > > Enjoy, > The feenk team > > > -- > www.tudorgirba.com > www.feenk.com > > "If you can't say why something is relevant, > it probably isn't." > > > _______________________________________________ > Moose-dev mailing list > Moose-dev(a)list.inf.unibe.ch > https://www.list.inf.unibe.ch/listinfo/moose-dev -- www.tudorgirba.com www.feenk.com "If you can't say why something is relevant, it probably isn't."

June 18, 2018

Promote new Pharo 7 VM?

by Alistair Grant

Hi Esteban, Would you consider promoting a new Pharo 7 VM? 140ff02 should finally solve an issue I've had with time zones and DST on Windows in the FileAttributesPlugin. Testing I've done on this VM: - Loaded up and used my normal dev environment. - Run the full automated test suite on: -- Linux 64 bit -- Linux 32 bit -- Win 32 bit In each case the set of failures in my environment roughly aligns with the current stable VM and the proposed one. I guess if anyone else has any objections they'll reply to this. :-) Of course, if you've got any questions or concerns, please let me know. In case it is useful for anyone, download links are: Linux 64 bit: http://files.pharo.org/vm/pharo-spur64/linux/pharo-linux-x86_64threaded-201… Linux 32 bit: http://files.pharo.org/vm/pharo-spur32/linux/pharo-linux-i386threaded-20180… Mac 64 bit: - http://files.pharo.org/vm/pharo-spur64/mac/pharo-mac-x86_64-201806171702-14… - http://files.pharo.org/vm/pharo-spur64/mac/pharo-mac-x86_64-201806171702-14… Mac 32 bit: - http://files.pharo.org/vm/pharo-spur32/mac/pharo-mac-i386-201806171702-140f… - http://files.pharo.org/vm/pharo-spur32/mac/pharo-mac-i386-201806171702-140f… Win 32 bit: http://files.pharo.org/vm/pharo-spur32/win/pharo-win-i386-201806171702-140f… Thanks! Alistair

June 18, 2018

[Pharo 7.0-dev] Build #1068: 22161-Add-more-log-to-bootstrap

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

There is a new Pharo build available! The status of the build #1068 was: FAILURE. The Pull Request #1559 was integrated: "22161-Add-more-log-to-bootstrap" Pull request url: https://github.com/pharo-project/pharo/pull/1559 Issue Url: https://pharo.fogbugz.com/f/cases/22161 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

June 18, 2018

Re: [Pharo-dev] Call for TechTalks

by Santiago Bragagnolo

Great! El 18 jun. 2018 13:53, "Marcus Denker" <marcus.denker(a)inria.fr> escribiÃ³: > That would be great! > > What date would be good? > > On 15 Jun 2018, at 12:44, Serge Stinckwich <serge.stinckwich(a)gmail.com> > wrote: > > > > On Fri, Jun 15, 2018 at 11:36 AM Marcus Denker <marcus.denker(a)inria.fr> > wrote: > >> Hi, >> >> As you might now, we organised âtech talksâ in the past: >> >> https://pharo.org/TechTalk >> >> We would like to continue the next half of 2018 with this series. >> >> The form itself is quite open: it can be a lecture, a demo, or just some >> âguidedâ discussion on Discord. >> >> If you have ideas â> send me a mail. >> >> > âI can do something about Machine Learning with TensorFlow and Pharo. > I already do a short presentation at the Pharo Club and another one will > be done during ESUG 2018. > > âA+ > -- > Serge Stinckwich > UMI UMMISCO 209 (SU/IRD/UY1) > "Programs must be written for people to read, and only incidentally for > machines to execute."http://www.doesnotunderstand.org/ > > >

June 18, 2018

Re: [Pharo-dev] Call for TechTalks

by Marcus Denker

That would be great! What date would be good? > On 15 Jun 2018, at 12:44, Serge Stinckwich <serge.stinckwich(a)gmail.com> wrote: > > > > On Fri, Jun 15, 2018 at 11:36 AM Marcus Denker <marcus.denker(a)inria.fr <mailto:marcus.denker@inria.fr>> wrote: > Hi, > > As you might now, we organised âtech talksâ in the past: > > https://pharo.org/TechTalk <https://pharo.org/TechTalk> > > We would like to continue the next half of 2018 with this series. > > The form itself is quite open: it can be a lecture, a demo, or just some âguidedâ discussion on Discord. > > If you have ideas â> send me a mail. > > > âI can do something about Machine Learning with TensorFlow and Pharo. > I already do a short presentation at the Pharo Club and another one will be done during ESUG 2018. > > âA+ > -- > Serge Stinckwich > UMI UMMISCO 209 (SU/IRD/UY1) > "Programs must be written for people to read, and only incidentally for machines to execute." > http://www.doesnotunderstand.org/ <http://www.doesnotunderstand.org/>

June 18, 2018