November 2019 - Pharo-dev - lists.pharo.org

[Pharo 8.0] Build #966: CompletionContextAndModelMerge

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

There is a new Pharo build available! The status of the build #966 was: SUCCESS. The Pull Request #5109 was integrated: "CompletionContextAndModelMerge" Pull request url: https://github.com/pharo-project/pharo/pull/5109 Issue Url: https://github.com/pharo-project/pharo/issues/CompletionContextAndModelMerge Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

Nov. 11, 2019

[Pharo 8.0] Build #965: 5093-Remove-Smart-Suggestions

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

There is a new Pharo build available! The status of the build #965 was: SUCCESS. The Pull Request #5094 was integrated: "5093-Remove-Smart-Suggestions" Pull request url: https://github.com/pharo-project/pharo/pull/5094 Issue Url: https://github.com/pharo-project/pharo/issues/5093 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

Nov. 9, 2019

[Pharo 8.0] Build #964: 5110-remove-smartSuggestions-classes

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

There is a new Pharo build available! The status of the build #964 was: FAILURE. The Pull Request #5111 was integrated: "5110-remove-smartSuggestions-classes" Pull request url: https://github.com/pharo-project/pharo/pull/5111 Issue Url: https://github.com/pharo-project/pharo/issues/5110 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

Nov. 8, 2019

[Pharo 8.0] Build #963: 3817-Unify-browseObsoleteMethodReferences--browseObsoleteReferences

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

There is a new Pharo build available! The status of the build #963 was: SUCCESS. The Pull Request #5100 was integrated: "3817-Unify-browseObsoleteMethodReferences--browseObsoleteReferences" Pull request url: https://github.com/pharo-project/pharo/pull/5100 Issue Url: https://github.com/pharo-project/pharo/issues/3817 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

Nov. 8, 2019

[Pharo 8.0] Build #962: Compiler: #parse should not do the doit wrapping

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

There is a new Pharo build available! The status of the build #962 was: SUCCESS. The Pull Request #5098 was integrated: "Compiler: #parse should not do the doit wrapping" Pull request url: https://github.com/pharo-project/pharo/pull/5098 Issue Url: https://github.com/pharo-project/pharo/issues/CompilerParseNoWrapDoit Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

Nov. 8, 2019

Re: [Pharo-dev] Moz2d Vs. Skia

by ducasse

Tx doru! > On 8 Nov 2019, at 11:41, Tudor Girba <tudor(a)tudorgirba.com> wrote: > > Hi > > Thanks for following the development of Bloc :). > > We invest in multiple backends because of several reasons. For example, for window hosting we have SDL2 (which relies on polling) and Glutin (which relies on a push model), but we also have Morphic. And now, when it comes to rendering we have both Moz2D and Skia. These have different properties. > > When we started to work with Moz2D, it was the only cross-platform vector graphical framework with rich support of text rendering. We knew that we eventually need to move away from it, but it allowed us to bootstrap nicely. At that time Skia was actually one of the backends of Moz2D. In the meantime, Skia evolved significantly. It hasnât quite reach the level of Moz2D when it comes to text yet, but for our typical use cases, it is already good enough. > > While Moz2D works fine today, we now want to move to Skia because of maintenance and support for newer technologies. For example, both Moz2D and Skia are written in C++ which mean we can not directly use both of them via FFI and have to implement C ABI bindings anyway. However, for Skia, there exists a project (https://github.com/rust-skia/rust-skia) that provides an up-to-date Skia bindings in Rust. This provides a quick way to build and to integrate into CI, and it also looks memory safe. Skia also has support for Vulkan. > > Now, while we target Skia in the short term, we also consider and play with other combinations. In particular, WebRenderer looks interesting. For text, we could use Skia, or we could also consider using something like font-kit. > > I wanted to detail a bit how we work to show how we exercise the underlying architecture continuously. A similar story happens on the host side. We think it is critical to have as much flexibility as possible at that level, while also exposing all underlying abilities in the image. For example, an important piece when dealing with text is to have access to accurate measurements. So, those are available through Sparta. > > Cheers, > Doru > > >> On Nov 7, 2019, at 6:52 AM, ducasse <stepharo(a)netcourrier.com> wrote: >> >> Hi doru and alex >> >> Can you tell me why you drop Moz2D and switch to Skia (which to us looks a much safer path starting from the packaging :)? >> >> S >> >> >> > > -- > feenk.com > > "Quality cannot be an afterthought." > >

Nov. 8, 2019

[Pharo 8.0] Build #961: Fix-bug-in-MCClassTraitDefinition

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

There is a new Pharo build available! The status of the build #961 was: FAILURE. The Pull Request #5099 was integrated: "Fix-bug-in-MCClassTraitDefinition" Pull request url: https://github.com/pharo-project/pharo/pull/5099 Issue Url: https://github.com/pharo-project/pharo/issues/FIx Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

Nov. 8, 2019

[Pharo 8.0] Build #960: Compiler API: turn forSyntaxHighlighting into an option

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

There is a new Pharo build available! The status of the build #960 was: SUCCESS. The Pull Request #5082 was integrated: "Compiler API: turn forSyntaxHighlighting into an option" Pull request url: https://github.com/pharo-project/pharo/pull/5082 Issue Url: https://github.com/pharo-project/pharo/issues/CompilerAPICodeCompletion Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

Nov. 8, 2019

Re: [Pharo-dev] Moz2d Vs. Skia

by Tudor Girba

Hi Thanks for following the development of Bloc :). We invest in multiple backends because of several reasons. For example, for window hosting we have SDL2 (which relies on polling) and Glutin (which relies on a push model), but we also have Morphic. And now, when it comes to rendering we have both Moz2D and Skia. These have different properties. When we started to work with Moz2D, it was the only cross-platform vector graphical framework with rich support of text rendering. We knew that we eventually need to move away from it, but it allowed us to bootstrap nicely. At that time Skia was actually one of the backends of Moz2D. In the meantime, Skia evolved significantly. It hasnât quite reach the level of Moz2D when it comes to text yet, but for our typical use cases, it is already good enough. While Moz2D works fine today, we now want to move to Skia because of maintenance and support for newer technologies. For example, both Moz2D and Skia are written in C++ which mean we can not directly use both of them via FFI and have to implement C ABI bindings anyway. However, for Skia, there exists a project (https://github.com/rust-skia/rust-skia) that provides an up-to-date Skia bindings in Rust. This provides a quick way to build and to integrate into CI, and it also looks memory safe. Skia also has support for Vulkan. Now, while we target Skia in the short term, we also consider and play with other combinations. In particular, WebRenderer looks interesting. For text, we could use Skia, or we could also consider using something like font-kit. I wanted to detail a bit how we work to show how we exercise the underlying architecture continuously. A similar story happens on the host side. We think it is critical to have as much flexibility as possible at that level, while also exposing all underlying abilities in the image. For example, an important piece when dealing with text is to have access to accurate measurements. So, those are available through Sparta. Cheers, Doru > On Nov 7, 2019, at 6:52 AM, ducasse <stepharo(a)netcourrier.com> wrote: > > Hi doru and alex > > Can you tell me why you drop Moz2D and switch to Skia (which to us looks a much safer path starting from the packaging :)? > > S > > > -- feenk.com "Quality cannot be an afterthought."

Nov. 8, 2019

[Pharo 8.0] Build #959: Clean Display packages group dependencies

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

There is a new Pharo build available! The status of the build #959 was: SUCCESS. The Pull Request #5092 was integrated: "Clean Display packages group dependencies" Pull request url: https://github.com/pharo-project/pharo/pull/5092 Issue Url: https://github.com/pharo-project/pharo/issues/displayDependencies1 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

Nov. 7, 2019