Re: [Pharo-dev] GPU accelerated GUI

[Ben Coman]

Darrin Massena wrote: If nobody has time to curate the information then an issue tracker is probably the way to go. At least then tidbits of information would be gathered in one stream with timestamps so one can gauge relevance. For example, I'm doing some performance measurements and would post them to a GUI performance issue if there was one and others were following/contributing to it. When people ask about a topic in the forums they could be directed toward the relevant issue. Hi Darrin, I think the issue tracker is better for this, since the information will (hopefully) become redundant after code change, and this is tracked by issue open/closed status. Can you create an issue? Probably make a parent case to group smaller aspects of this.  (Note that slices submitted to a parent case don't get picked up by the CI monkey until all child cases are closed.) All, What might be useful as a wiki page would be a description of the defined fogbugz "projects", how any strategic plans for Pharo 4 are scoped for each, and who is working on these things - and anyone can add their name as interested in that area. btw, wasn't Trello used at some point for tracking the big picture?  How did that go? cheers -ben On Sat, May 31, 2014 at 6:01 AM, Hilaire Fernandes <hilaire.fernan...@gmail.com> wrote: Can we collect somewhere in the web the information you mentioned and other more accurate? Ideally a wiki. Is there a dedicated place for Pharo? The wiki bugtracker? I guess most of us does not know where to look at for improvement. Asking to a newbie to contribute does not really help if we can't provide direction. Hilaire Le 31/05/2014 10:48, Clément Bera a écrit : > One is that the Morphic-based UI is slow. You can see it by using the > old MVC instead of Morphic which goes faster. Recently Morphic got > slower on Pharo and it is now slower than in Squeak. It may be due to > refactoring on Morphic in order to get it better, it may not be. I guess > this is temporary. > > The second thing is that BitBlt is slow for 2 reasons: it is bit based > and not vector based and its implementation half in the VM half in the > image forces to copy a huge number of bits that could be avoided > > So the answer is that you need to contribute to the refactoring of > Morphic or to Athens. > -- Dr. Geo http://drgeo.eu