Am 07.10.2014 um 15:58 schrieb Jürgen Spitzmüller <sp...@lyx.org>: > 2014-10-07 15:44 GMT+02:00 Jean-Marc Lasgouttes: > Le 07/10/2014 13:10, Jürgen Spitzmüller a écrit : > In that case, we could probably set up a script that generates those @2x > icons (as well as icons of diverse size) from the SVG. This could also > be used in order to generate bigger icons for other purposes (think > tablet UI). > > Why not use directly the svg versions? Is it bad in terms of performance? > > If this is possible with the Qt HDPI approach (i.e., if it does not requires > those @2x icon bitmap files). I have not checked that, but if I understand > this correctly, it should be possible: > http://blog.qt.digia.com/blog/2013/04/25/retina-display-support-for-mac-os-ios-and-x11/ > > Quote: > > "As we have seen, raster content won’t look nice when scaled and > high-resolution content should be provided. As an app developer you have two > options: (ignoring the “do-nothing” option) > • Replace existing raster content with a high-resolution version > • Provide separate high-resolution content > The first option is convenient since there is only one version of each > resource. However, you may find (or your designer will tell you) that > resources like icons look best when created for a specific resolution. To > facilitate this, Qt as adopted the “@2x” convention for image filenames:" > > SVG would be "first option", no?
Yes, I think so. The nice effect of using the “@2x” convention is the assignment of the correct devicePixelRation to the images Qt creates that way. Stephan
