Detailed dependencies of frameworks on external resources like icons

[Nicolás Alvarez]

2014-09-17 18:44 GMT-03:00 Friedrich W. H. Kossebau <kossebau at kde.org>:
> Two years ago, to fight the number of "unknown" icons appearing in the UI and
> reducing duplicated icons in the Calligra repo itself, some macros have been
> introduced in Calligra, to tag all icon name ids being used in the program, so
> automatic extraction and processing is possible, using gettext:
> https://projects.kde.org/projects/calligra/repository/revisions/master/entry/KoIcon.h
>
> Using these macros needs discipline, because nothing (as in: compiler)
> enforces the use of them. But so far it worked out, unkwown icons are seldomly
> seen now, and lots of icons duplicated from the Oxygen iconset could be
> removed. The script for checking duplicates, unused or unknown icons is
> https://projects.kde.org/projects/calligra/repository/revisions/master/entry/devtools/iconcheck/iconcheck.py
>
> Just, this did not help with finding those icons used directly from kdelibs.
> So the single installer Windows packages created for Krita have been larger
> then needed, due to playing safe and shipping more or less also the complete
> Oxygen icons.
>
> For mobile platforms with limited resources in bandwith and storage size not
> really acceptable.
>
>
> Has this been discussed before? What would you propose how to deal with this
> problem? Would such macros make sense for frameworks for the described
> problem? How to collect the info which sizes of the icons might be only
> needed?

I was thinking of complicated scripts to extract calls to
QIcon::fromTheme and such, I never thought of using a macro to
annotate icon names, that's a great idea.

One minor problem I just noticed: where would the macro be defined?
Would each framework define its own?

-- 
Nicolás