Hi circular,
and I’m very happy that I didn’t bother but rather met an already existing interest. This is nice to hear!
Just tried the update.
The simple test project has:
2.887.680 project1_without_bgra.exe
4.397.056 project1_full-version.exe
4.070.912 project1_previous_core-version.exe
3.981.824 project1_recent_core-version.exe
For another/real program where I tried to apply, I’d have the following data:
4.748.288 anApp_without_bgra.exe
6.192.640 anApp_bgra_full-version.exe
5.888.000 anApp_core_previous-version.exe
5.799.424 anApp_core_today-version.exe
In sum:
- an app (against the not-bgra-using original) would grow around 1 or 1,1 MB now.
- the recent core version, against the full version, will win approx. 400 KB.
The overhead drops by a third, if I see right.
I’d think that are numbers that sound far better than at the beginning and makes it far easier to apply also when used only for punctual tasks!
![Smiley :)](/Smileys/ExcellentSmileys1/smile.gif)
in particular image readers/writers (BMP, PNG), polygon and path rendering. Not sure if it would make sense not import them.
I’d vote
Not to exclude them from the core version. The loss of widespread functionality, seen against the benefit, would be surely to high imo. And it would discourage users from using the core version, I’d guess.