On Tue, Jul 13, 2010 at 9:58 AM, Hilaire Fernandes < hilaire.fernandes@gmail.com> wrote:
Le 13/07/2010 09:42, Mariano Martinez Peck a écrit :
Hilarie: first question, do you want to make faster what? The
development there or the deploy of a particular application?
I want first to improve the user experience under this 12 years old CPU power technology (XO-1): make UI more responsive is the first and only issue.
I am compiling tips and suggestion on DrGeo Todo list: http://community.ofset.org/index.php/DrGeo_Todo
Next of course the deployment is another aspect related to configuration, see my other post.
Ok ok ok. What I would to is to: - Start from PharoCore, of course. Not dev. Take a core and load what you need. To script such loads, you can use Gofer. If you want to use Metacello, you can take your conf and load it. It will bootstrap metacello, and then, once you have installed it, with ConfigurationOfMetacello >> unload you con can remove Metacello from the system. - Do some cleaning to the image. Check the stuff done in ScriptLoader >> cleanUpForProduction. There are a lot of interesting things there - Use standard fonts and as they said, without antialaising - For the VM you can also compile a minimal VM. I did that with MacOS where I compiled only the 4 or 5 plugins that were needed. I am not sure if you win something, thus. - Check and try this email: http://forum.world.st/Are-random-refactorings-welcome-td2283957.html#a228395... - Of course, try Cog. - I would use the SystemBrowser that comes with the Core. Not OB neither O2. - Enable fastDragWindowForMorphic - Don't use annotation panes. CHeck also issues 2403 - Use Pharo 1.1 that is much faster than 1.0 That's all that came to my mind. Not sure what could help. Good luck and let us know. Cheers Mariano
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project