An alternative that would not degrade startup performance is to ship one res bmp along with vector files. When an image is referenced initially, use the shipped bmp and start a background render job from the vector file. Once render completes, cache the result to disk and swap in the correct res image into the running instance. This would make Eclipse behave analogous to progressive resolution image loading.
Just a thought and I am certainly not in a position to volunteer to implement something like this. :) Konstantin On Sep 21, 2016, at 10:36, Antoine THOMAS <anto...@eclipse.org> wrote: >> >> Performance and footprint. > > Dani, performance, ok, I can understand that, even if many operating system > today are using SVG icons (or vector graphics in general). But footprint? > vector graphic files are very light compared to bitmap, especially if you > consider that you need to generate different sizes for different screen > resolutions. That would help to decrease the footprint of packages. > > __________________________ >> Antoine THOMAS aka ttoine >> Product Manager >> Eclipse Foundation >> antoine.tho...@eclipse.org >> +33663137906 >> @ttoine >> >> >> > _______________________________________________ > cross-project-issues-dev mailing list > cross-project-issues-dev@eclipse.org > To change your delivery options, retrieve your password, or unsubscribe from > this list, visit > https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
_______________________________________________ cross-project-issues-dev mailing list cross-project-issues-dev@eclipse.org To change your delivery options, retrieve your password, or unsubscribe from this list, visit https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
