On 7 March 2016 at 14:45, René J.V. <rjvber...@gmail.com> wrote: > On Monday March 07 2016 12:41:52 Jaroslaw Staniek wrote: > > BTW, am I right that using a builtin binary rcc icon set could make you > lose in terms of memory (RAM) footprint overhead what you gain in terms of > disk space overhead? >
Dsk optimization is not the goal, that would be Enlightenment-like optimization :) The thing is, as an average Qt dev, if I had to develop and distribute a 5 cpp files-long lib or app, self-contained (not packaged), I wouldn't like to add 5970 (and counting) icon files to it to just display 3 icons or so. I would probably copy the needed icons into a subdir, maybe even rename them, move around, etc. Disclaimer: we're not 'average' Qt devs with all consequences but my dream is that the two extremes can be closer. I've been doing the copying myself for non-FOSS or non-mainstream FOSS code. So any improvement like having a single breeze.rcc file is more than good solution IMHO. In other words, we're not distributing movies in a form of N jpeg files, one per frame, we're using dedicated container. So here it is, a dedicated container for icons. -- regards, Jaroslaw Staniek KDE: : A world-wide network of software engineers, artists, writers, translators : and facilitators committed to Free Software development - http://kde.org Calligra Suite: : A graphic art and office suite - http://calligra.org Kexi: : A visual database apps builder - http://calligra.org/kexi Qt Certified Specialist: : http://www.linkedin.com/in/jstaniek
_______________________________________________ calligra-devel mailing list calligra-devel@kde.org https://mail.kde.org/mailman/listinfo/calligra-devel
