yes and we will have to also distribute icons into class resources.
> total memory consumption on old icons: 27258 > total memory consumption on new icons: 67234 > > so... is 40k more... I think we can live with that :) > > anyway, if you want to save memory, you can strip that and have no icons at > all (just remove *IconContents methods and reset icons class var). > > Esteban > > On Apr 24, 2012, at 11:44 AM, Norbert Hartl wrote: > >> >> Am 24.04.2012 um 11:35 schrieb Geert Claes: >> >>> >>> Norbert Hartl wrote >>>> >>>> Of course, if there is an ugly replacment that can be used if the system >>>> is minimised. Having two icon sets introduces the possibility to make the >>>> ugly one consume even less memory, e.g. make it black and white. >>>> >>> >>> I have no idea what you just tried to say :) When you say ugly replacement, >>> are you talking about the current ugly icons or do you find Esteban's >>> suggested icons not appealing enough? >>> >> It is just an addition to my first statement. If we call the current icon >> set medium in the sense of medium cutiness and medium memory consumption >> than there is a new situation with the new nice icons. Igor is right, if the >> vector world is coming to pharo then it is easy to make really good looking >> icons in the image. But the memory consumption and CPU intensity will be >> raised. That contradicts to usage of pharo in a server environment. So what >> I was saying is that I think that the new icons are great. But then there >> should be a replacement for it when the image is shrinked. The same happens >> with the fonts if you shrink. And if the icons are replaced they could even >> be replaced by something really basic that saves additional memory. On a >> server with VNC or the like the icons aren't that important and maybe can be >> removed completely. >> >> More clear now? >> >> Norbert >> >> > >
