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

[Pharo 8.0] Build #677: [CI CLEANING] Fixing current test failures

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

There is a new Pharo build available! The status of the build #677 was: SUCCESS. The Pull Request #4436 was integrated: "[CI CLEANING] Fixing current test failures" Pull request url: https://github.com/pharo-project/pharo/pull/4436 Issue Url: https://github.com/pharo-project/pharo/issues/fixingCurrentTestFailures Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

Aug. 28, 2019

Re: [Pharo-dev] possible Windows Update "1903" Iceberg problem

by Tudor Girba

Hi, We just encountered this on two different machines. We got this after the update to Windows 1903. For us itâs a critical issue at this point. What can we do to help with this? Cheers, Doru > On Aug 17, 2019, at 12:50 PM, Ben Coman <btc(a)openInWorld.com> wrote: > > hi Stef, > I feel you missed my point. Probably I wasn't clear this has already been tested with latest Pharo 8 launched by PharoLauncher. > The problem occurs with Pharo 7.0.3(64 bit) and with Pharo8.0-SNAPSHOT-build.635(64 bit) > after Microsoft Windows Update 1903... > https://www.computerworld.com/article/3409621/microsoft-starts-windows-10s-… > > If indeed 1903 is the cause, with this update now being *forced* down on people, this will potentially soon impact more and more Windows users. > But my guess that 1903 is the culprit needs to be confirmed. > So I am requesting someone with access to multiple Windows machines directly compare a 1903 machine with a pre-1903 machine. > > cheers -ben > > On Sat, 17 Aug 2019 at 12:58, ducasse <stepharo(a)netcourrier.com> wrote: > Hi ben > > in the pharo launcher if you click on P8.0 (development version) you get access to all the builds. > > Stef > >> On 16 Aug 2019, at 16:02, Ben Coman <btc(a)openinworld.com> wrote: >> >> IThis morning the May 2019 Windows Update "1903" forced itself onto my computer and now 64-bits Pharo seems to have a problem with git_remote_fetch() FFI callout. I no longer have a non-1903 machine to directly compare behaviour before "1903". Can someone familiar with this area with both "pre-1903" and "1903" machines triage whether "1903" is indeed the cause? >> >> A few other recent reports are noted here... >> https://github.com/pharo-project/pharo/issues/3418 >> >> cheers -ben > -- feenk.com "Not knowing how to do something is not an argument for how it cannot be done."

Aug. 27, 2019

Re: [Pharo-dev] [Weekend Procastination] what the new minheadless opens as posibilities :D

by Guillermo Polito

> El 26 ago 2019, a las 14:08, ducasse <stepharo(a)netcourrier.com> escribiÃ³: > > Hi guille > >> Procastination 1: Render the world fully in athens (instead of a middling bitmap) to have an idea of the effort to get fast to hdpi >> <PastedGraphic-5.png> >> What you see here is a world drawn completely in athens in minheadless, where in red are the invalidated rectangles in the screen (Iâm using to debug a bit). >> Icons are broken because I broke them while playing, not because they do not work in athens :P. >> There is still work to do if we want to explore this direction. Mainly performance issues to make it at least usable, so it can be iterated easily. >> We have seen with Pablo that a lot of time is taken in the transformation of morphic/pharo form/bitmaps to athens ones, since they do not have the same format and right now it is done with a bit-per-bit copy. > > I do not get it. You are saying that it is slow while I have the impression that if we remove the bit-per-bit copy we should get faster. There are two different things in here :). First, in morphic we have bitmaps and forms representing for example icons and images. Those forms/bitmaps are stored in a format that is not cairo compatible, so every time we need to render an icon a super expensive transformation takes place. The other day we worked with Pablo in some caching of those transformations and it improves indeed a lot. Still we have to see if it makes sense to add those caches (where to put them how to invalidate them, are they shared or notâ¦), or if we change the internal representation of forms, or what :). Second, right now minheadless is drawing the morphic world into a form and then the form is copied (literally blitted usin bitblt) into the cairo context/sdl texture. What this first experiment is about is to render directly on the sdl texture without the extra copy. I donât think is will be necessary faster as this is just avoiding a couple of copies (blits) but the athens morphic renderer is far less optimized than the historical oneâ¦ The question to me is: can this be **as fast as the bitblt one** yet render better in hdpi?

Aug. 26, 2019

[MorphicUIManager] strange method onEventSensorStartup:

by ClÃ©ment Dutriez

Hello, I working on the first step of the migration of the UIManager. ```Smalltalk onEventSensorStartup: anEventSensor anEventSensor flushAllButDandDEvents ``` the problem is that the only class defining 'flushAllButDandDEvents' method do nothing. It's normal? what is the responsibility of this method? Thanks -- Dutriez ClÃ©ment dutriezcle(a)gmail.com 0605199489 [image: www.linkedin.com/in/clÃ©ment-dutriez-407275173] <http://www.linkedin.com/in/clÃ©ment-dutriez-407275173>

Aug. 26, 2019

[Pharo 8.0] Build #676: Add missing find and replace refactoring

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

There is a new Pharo build available! The status of the build #676 was: FAILURE. The Pull Request #4430 was integrated: "Add missing find and replace refactoring" Pull request url: https://github.com/pharo-project/pharo/pull/4430 Issue Url: https://github.com/pharo-project/pharo/issues/FindAndReplace Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

Aug. 26, 2019

[Pharo 8.0] Build #675: Add undo refactoring option

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

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

Aug. 26, 2019

Re: [Pharo-dev] [Weekend Procastination] what the new minheadless opens as posibilities :D

by ducasse

> On 26 Aug 2019, at 13:16, Ben Coman <btc(a)openinworld.com> wrote: > > Thanks for sharing Guille. > > Now what I was wondering is what possibilities minheadless opens up for running on IOS and Android tablets and phones. > IIUC one of the impediments was not being native-event-driven. Is the VM event handling now factored out to the degree necessary > to drive it from native-events, Not yet from pablo and esteban told me. > or what more work is required there? I do not know but I know that some work is needed. But this is in our roadmap. > On Mon, 26 Aug 2019 at 16:43, Guillermo Polito <guillermopolito(a)gmail.com <mailto:guillermopolito@gmail.com>> wrote: > Hi all, > > Over the weekend, instead of working on my ESUG presentations I procastinated a bit with some experiments that I would like to share ^^. > > Procastination 1: Render the world fully in athens (instead of a middling bitmap) to have an idea of the effort to get fast to hdpi > > What you see here is a world drawn completely in athens in minheadless, where in red are the invalidated rectangles in the screen (Iâm using to debug a bit). > Icons are broken because I broke them while playing, not because they do not work in athens :P. > There is still work to do if we want to explore this direction. Mainly performance issues to make it at least usable, so it can be iterated easily. > We have seen with Pablo that a lot of time is taken in the transformation of morphic/pharo form/bitmaps to athens ones, since they do not have the same format and right now it is done with a bit-per-bit copy. > > > Procastination 2: poping out morphs out of the world > > What you see here is that I can have different os windows with different worlds, giving a multi-window experience :). > There is also work to do in this direction if we want to push it: > - morphic support for multiple worlds/windows is not so good... > - the usage of the current world needs to be reviewed. The world has two distinct responsibilities right now > 1) it is the manager of the hands (required for drag n drop) > 2) it is the main container/pasteup for other morphs > > Imagine in the short term a Morphic Spec app can use a âexternal window rendering on athensâ strategy that mixes the two things above and each new window is popped up as a new window. :D > > For those @ESUG, Iâll be arriving this evening, Iâm going to show this in the show us your projects, and if you want to help, please contact me, you can learn a lot and its super fun :) > > cheers -ben > <PastedGraphic-4.png><PastedGraphic-5.png>

Aug. 26, 2019

Re: [Pharo-dev] [Weekend Procastination] what the new minheadless opens as posibilities :D

by Esteban Lorenzano

> On 26 Aug 2019, at 13:16, Ben Coman <btc(a)openinworld.com> wrote: > > Thanks for sharing Guille. > > Now what I was wondering is what possibilities minheadless opens up for running on IOS and Android tablets and phones. > IIUC one of the impediments was not being native-event-driven. Is the VM event handling now factored out to the degree necessary > to drive it from native-events, or what more work is required there? To be competitive in the mobile world, we need an idle vm. While moving the responsibility of showing the world to the image (and with that, removing the need of a UI cycle) is something needed, we still need to eliminate the heartbeat. And that is an effort of proportions. Esteban > > > On Mon, 26 Aug 2019 at 16:43, Guillermo Polito <guillermopolito(a)gmail.com <mailto:guillermopolito@gmail.com>> wrote: > Hi all, > > Over the weekend, instead of working on my ESUG presentations I procastinated a bit with some experiments that I would like to share ^^. > > Procastination 1: Render the world fully in athens (instead of a middling bitmap) to have an idea of the effort to get fast to hdpi > > What you see here is a world drawn completely in athens in minheadless, where in red are the invalidated rectangles in the screen (Iâm using to debug a bit). > Icons are broken because I broke them while playing, not because they do not work in athens :P. > There is still work to do if we want to explore this direction. Mainly performance issues to make it at least usable, so it can be iterated easily. > We have seen with Pablo that a lot of time is taken in the transformation of morphic/pharo form/bitmaps to athens ones, since they do not have the same format and right now it is done with a bit-per-bit copy. > > > Procastination 2: poping out morphs out of the world > > What you see here is that I can have different os windows with different worlds, giving a multi-window experience :). > There is also work to do in this direction if we want to push it: > - morphic support for multiple worlds/windows is not so good... > - the usage of the current world needs to be reviewed. The world has two distinct responsibilities right now > 1) it is the manager of the hands (required for drag n drop) > 2) it is the main container/pasteup for other morphs > > Imagine in the short term a Morphic Spec app can use a âexternal window rendering on athensâ strategy that mixes the two things above and each new window is popped up as a new window. :D > > For those @ESUG, Iâll be arriving this evening, Iâm going to show this in the show us your projects, and if you want to help, please contact me, you can learn a lot and its super fun :) > > cheers -ben > <PastedGraphic-4.png><PastedGraphic-5.png>

Aug. 26, 2019

Re: [Pharo-dev] [Weekend Procastination] what the new minheadless opens as posibilities :D

by ducasse

Hi guille > Procastination 1: Render the world fully in athens (instead of a middling bitmap) to have an idea of the effort to get fast to hdpi > <PastedGraphic-5.png> > What you see here is a world drawn completely in athens in minheadless, where in red are the invalidated rectangles in the screen (Iâm using to debug a bit). > Icons are broken because I broke them while playing, not because they do not work in athens :P. > There is still work to do if we want to explore this direction. Mainly performance issues to make it at least usable, so it can be iterated easily. > We have seen with Pablo that a lot of time is taken in the transformation of morphic/pharo form/bitmaps to athens ones, since they do not have the same format and right now it is done with a bit-per-bit copy. I do not get it. You are saying that it is slow while I have the impression that if we remove the bit-per-bit copy we should get faster. > > > Procastination 2: poping out morphs out of the world > > <PastedGraphic-4.png> > > What you see here is that I can have different os windows with different worlds, giving a multi-window experience :). > There is also work to do in this direction if we want to push it: > - morphic support for multiple worlds/windows is not so good... > - the usage of the current world needs to be reviewed. The world has two distinct responsibilities right now > 1) it is the manager of the hands (required for drag n drop) > 2) it is the main container/pasteup for other morphs > > Imagine in the short term a Morphic Spec app can use a âexternal window rendering on athensâ strategy that mixes the two things above and each new window is popped up as a new window. :D > > For those @ESUG, Iâll be arriving this evening, Iâm going to show this in the show us your projects, and if you want to help, please contact me, you can learn a lot and its super fun :)

Aug. 26, 2019

Re: [Pharo-dev] [Weekend Procastination] what the new minheadless opens as posibilities :D

by Ben Coman

Thanks for sharing Guille. Now what I was wondering is what possibilities minheadless opens up for running on IOS and Android tablets and phones. IIUC one of the impediments was not being native-event-driven. Is the VM event handling now factored out to the degree necessary to drive it from native-events, or what more work is required there? On Mon, 26 Aug 2019 at 16:43, Guillermo Polito <guillermopolito(a)gmail.com> wrote: > Hi all, > > Over the weekend, instead of working on my ESUG presentations I > procastinated a bit with some experiments that I would like to share ^^. > > *Procastination 1:* Render the world fully in athens (instead of a > middling bitmap) to have an idea of the effort to get fast to hdpi > > What you see here is a world drawn completely in athens in minheadless, > where in red are the invalidated rectangles in the screen (Iâm using to > debug a bit). > Icons are broken because I broke them while playing, not because they do > not work in athens :P. > There is still work to do if we want to explore this direction. Mainly > performance issues to make it at least usable, so it can be iterated easily. > We have seen with Pablo that a lot of time is taken in the > transformation of morphic/pharo form/bitmaps to athens ones, since they do > not have the same format and right now it is done with a bit-per-bit copy. > > > *Procastination 2*: poping out morphs out of the world > > What you see here is that I can have different os windows with different > worlds, giving a multi-window experience :). > There is also work to do in this direction if we want to push it: > - morphic support for multiple worlds/windows is not so good... > - the usage of the current world needs to be reviewed. The world has two > distinct responsibilities right now > 1) it is the manager of the hands (required for drag n drop) > 2) it is the main container/pasteup for other morphs > > Imagine in the short term a Morphic Spec app can use a âexternal window > rendering on athensâ strategy that mixes the two things above and each new > window is popped up as a new window. :D > > For those @ESUG, Iâll be arriving this evening, Iâm going to show this in > the show us your projects, and if you want to help, please contact me, you > can learn a lot and its super fun :) > cheers -ben

Aug. 26, 2019