Hi Esteban, Le lun. 7 oct. 2019 à 12:26, Esteban Maringolo <emaring...@gmail.com> a écrit : > > On Mon, Oct 7, 2019 at 12:07 PM Esteban Lorenzano <esteba...@gmail.com> wrote: > > > On 7 Oct 2019, at 11:55, Esteban Maringolo <emaring...@gmail.com> wrote: > > > >> So I’m wondering when the Pharo GUI will snap as well as VW. > > > > > > Maybe with native widgets there will be a significant speedup, > > > although I don't know whether the lag comes from rendering time or > > > from something else. > > > > Morphic + Glamour sometimes + bad UI/algorithms design put us in a bad > > place concerning UI speed. > > Pharo 5 was the turning point when it comes to that, and it correlates > with the introduction of the Glamour-based tools. > > > We are working to fix it, but this is not straightforward. > > I know, and the effort put into that is really appreciated. > > I haven't used your latest "native widgets" (GTK) build, but as long > as the UI isn't programmed to be as async as possible, then any non-UI > related event will slowdown or micro-block the UI, causing the noticed > latency. > > I know I'm speaking the obvious to you here, but if you look at things > like Android Architecture there is a lot to learn from, because mobile > users expect significantly faster, non-blocking UIs that desktop, and > not to mention web (although this is is changing too).
I would recommend that reference: https://danluu.com/input-lag/ to make sure we have a baseline to evaluate GUI responsiveness. In part because some objectives may be unrealistic, given the software and hardware layers involved. Thierry > Regards, > > Esteban A. Maringolo >
