Hi Laurent. First, as Marcus said, there is no magic. You should really load the packages of seaside and all the minimal dependes. Just load what you need. Once you are done, evaluate ScriptLoader new cleanUpForRelease. But take a look to what that method does. Then, if you are sure you don't need certain packages from pharo core, thanks to the better modularization we have, you can remove it. Esteban did that for his images for iPhone.
There are also some shrink you can do. For example, "To put all all classes with the default category. Still can browse and recompile the whole image. Most production enviroments don't care about categories...this make sense when developing." Smalltalk allClassesAndTraitsDo: [:each | each zapOrganization ]. how much did it help? Fonts. Do you need al fonts? no...remove them. etc... On Wed, Aug 3, 2011 at 10:24 AM, Marcus Denker <[email protected]>wrote: > > On Aug 3, 2011, at 10:17 AM, laurent laffont wrote: > > > Hi, > > > > actually using PharoCore 1.3, loading ConfigurationOfSeaside30 Core, then > ScriptLoader>>cleanUpForProduction I have a 13MB image. Is it possible to > have it smaller ? (I know a next step is to be able to use PharoKernel). > > cleanUpForProduction should result in a Core image that is just 6.5MB... so > the ConfigurationOfSeaside30 seems to load *a lot* of stuff? Maybe be a bit > selective? > > Marcus > > > -- > Marcus Denker -- http://marcusdenker.de > > > -- Mariano http://marianopeck.wordpress.com
