> You can use MVC, it works well on much slower computers... oh wait... :) Levente it was a good one. :) > Sorry, I couldn't resist. :)
:) I know the feeling. Now we removed MVC from pharo not because we did not value it but because we want a clean infrastructure (where several UI system could be loaded) and this was not with a isMorphic code everywhere that we could move. So sometimes you have to take decision so that you can get again agile so that you can reconsider your own decision. > Try getting rid of gradients, dropshadows, etc. Use a plain old strikefont > without anti-aliasing. If you can build a custom vm, make sure that you > optimize it for the platform and build all modules external, except for those > which are loaded when the image starts. You can also try using the new > StackVM. > And you can also run the following version of the browser test to see where > can you improve the performance: > > | savedMorphs | > savedMorphs := World submorphs. > World removeAllMorphs."heh, heh" > [ > [ > 10 timesRepeat: [ Browser fullOnClass: Object selector: > #yourself ]. > World submorphs do: [ :m | m delete. self currentWorld > doOneCycle] ] > ensure: [ World addAllMorphs: savedMorphs ] ] > timeProfile. > > > Levente > >> >> Thanks to share any thought, even random ones. >> >> >> Hilaire >> >> >> _______________________________________________ >> Pharo-project mailing list >> [email protected] >> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >> > > _______________________________________________ > Pharo-project mailing list > [email protected] > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project _______________________________________________ Pharo-project mailing list [email protected] http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
