- Pharo-dev - lists.pharo.org

[Pharo 7.0] Build #66: 22819 Cleanup TestReviver
by ci-pharo-ci-jenkins2＠inria.fr Dec. 20, 2018

Dec. 20, 2018

There is a new Pharo build available! The status of the build #66 was: FAILURE. The Pull Request #2110 was integrated: "22819 Cleanup TestReviver" Pull request url: https://github.com/pharo-project/pharo/pull/2110 Issue Url: https://pharo.fogbugz.com/f/cases/22819 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

Re: [Pharo-dev] [Moose-dev] Re: glamorous toolkit: v0.4.0
by Tudor Girba Dec. 20, 2018

Dec. 20, 2018

Hi Luke, I am happy this looks exciting :). About the confusion part: The Glamorous Toolkit we are working on right now is a complete new world built on a complete new graphical stack that does is not based on the existing stack that ships with Pharo. It is not an evolution. It is a leap. The goal of the new GT is to propose a completely reshaped programming experience that enables moldable development. You will find the concepts from the old GT in the new world as well. For example, the Inspector is extensible in similar ways and the API is similar as well. But, in the new world, we are bringing the concept much further. For example, Documenter provides a whole new kind of a tool that can mold to unify multiple workflows (like data notebooks, code documentation, or tutorials) right in the IDE. Coder provides the infrastructure for manipulating code that can mold its shape as you type. Transcript allows you to embed various widgets to transform the otherwise dull experience of a console into a live one. Behind the scenes GT comes with several engines. The Examples engine enables example-driven development which also bridges the gap between testing and documentation effort, especially when combined with Documenter. Releaser is able to release deeply nested projects. Phlow offers an engine that shares similarities with Glamour. Completer provides moldable completion. Visualizer offers a couple of visualization engines such as Mondrian. All of these are possible because of the underlying graphical stack made of Sparta/Bloc/Brick. All in all, we believe that the new GT enables a new way of programming. Individual features can be attractive, but our goal is to reshape the development experience. Does this address the concern? Cheers, Doru > On Dec 19, 2018, at 2:09 PM, Luke Gorrie <luke(a)snabb.co> wrote: > > On Fri, 14 Dec 2018 at 05:13, Tudor Girba <tudor(a)tudorgirba.com> wrote: > Please do let us know what you think .. and, of course, what you feel. > > I'm feeling excited and confused :). > > Excited because I love seeing all these new demos streaming out and I'm itching to put new capabilities to work. > > Confused about the roadmap. How does this "new" Glamorous Toolkit relate to the "old" one that I learned about last year from the Moldable Tools thesis? Is this a new version or a complete rewrite? Is it backwards compatible or completely reimagined? Is adopting the new version a seamless process or is porting required? Are frameworks like Glamour still there behind the scenes or were they replaced? etc. > > > <gt-documenter-magic-markup.gif><gt-0-4-0.png>_______________________________________________ > Moose-dev mailing list > Moose-dev(a)list.inf.unibe.ch > https://www.list.inf.unibe.ch/listinfo/moose-dev -- www.feenk.com "Things happen when they happen, not when you talk about them happening."

1 0

[Pharo 7.0] Build #65: 22818 Cleanup Regex tests
by ci-pharo-ci-jenkins2＠inria.fr Dec. 20, 2018

Dec. 20, 2018

There is a new Pharo build available! The status of the build #65 was: FAILURE. The Pull Request #2109 was integrated: "22818 Cleanup Regex tests" Pull request url: https://github.com/pharo-project/pharo/pull/2109 Issue Url: https://pharo.fogbugz.com/f/cases/22818 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 7.0] Build #64: 22814-Broken-comments-on-Cursor
by ci-pharo-ci-jenkins2＠inria.fr Dec. 20, 2018

Dec. 20, 2018

There is a new Pharo build available! The status of the build #64 was: SUCCESS. The Pull Request #2106 was integrated: "22814-Broken-comments-on-Cursor" Pull request url: https://github.com/pharo-project/pharo/pull/2106 Issue Url: https://pharo.fogbugz.com/f/cases/22814 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 7.0] Build #63: 22811 Fix comment in ExternalBrowser
by ci-pharo-ci-jenkins2＠inria.fr Dec. 19, 2018

Dec. 19, 2018

There is a new Pharo build available! The status of the build #63 was: SUCCESS. The Pull Request #2102 was integrated: "22811 Fix comment in ExternalBrowser" Pull request url: https://github.com/pharo-project/pharo/pull/2102 Issue Url: https://pharo.fogbugz.com/f/cases/22811 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 7.0] Build #62: 22812 Clean the ImageCleaner
by ci-pharo-ci-jenkins2＠inria.fr Dec. 19, 2018

Dec. 19, 2018

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

1 0

[Pharo 7.0] Build #61: 22809 Cleanup MethodFinderTest and related sample classes
by ci-pharo-ci-jenkins2＠inria.fr Dec. 19, 2018

Dec. 19, 2018

There is a new Pharo build available! The status of the build #61 was: FAILURE. The Pull Request #2101 was integrated: "22809 Cleanup MethodFinderTest and related sample classes" Pull request url: https://github.com/pharo-project/pharo/pull/2101 Issue Url: https://pharo.fogbugz.com/f/cases/22809 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

Catalog Entries
by Sven Van Caekenberghe Dec. 19, 2018

Dec. 19, 2018

Hi, So we have the Catalog with version specific repositories for ConfigurationOfXYZ packages/classes. I am assuming that we will be keeping this system for at least Pharo 7 and possibly 8. Can one define Catalog entries using BaselineOfXYZ ? Is that recommended ? Or should a mostly empty ConfigurationOfXYZ be used that internally refers to the BaselineOfXYZ ? Sven

7 26

[Pharo 7.0] Build #60: 22777 ManifestMonticello and ManifestRingMonticello should be tagged with "Manifest"
by ci-pharo-ci-jenkins2＠inria.fr Dec. 19, 2018

Dec. 19, 2018

There is a new Pharo build available! The status of the build #60 was: SUCCESS. The Pull Request #2076 was integrated: "22777 ManifestMonticello and ManifestRingMonticello should be tagged with "Manifest"" Pull request url: https://github.com/pharo-project/pharo/pull/2076 Issue Url: https://pharo.fogbugz.com/f/cases/22777 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 7.0] Build #59: 22806 Small cleanups in EmbeddedFreeTypeFontInstallerTest
by ci-pharo-ci-jenkins2＠inria.fr Dec. 19, 2018

Dec. 19, 2018

There is a new Pharo build available! The status of the build #59 was: SUCCESS. The Pull Request #2099 was integrated: "22806 Small cleanups in EmbeddedFreeTypeFontInstallerTest" Pull request url: https://github.com/pharo-project/pharo/pull/2099 Issue Url: https://pharo.fogbugz.com/f/cases/22806 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0