I would like to try (again) a wiki for Pharo. Problem is that they obsolete very fast, and information there become unusable⦠I suppose we need a âwiki overseerâ (or several) to ensure we keep it in track⦠anyway, I want to try a wiki for Pharo, because there is a lot of information that fits better there (like this and a lot other). Esteban On 31 May 2014, at 10:01, Hilaire Fernandes <hilaire.fernandes@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