On 17 Jan 2013, at 14:35, Sorvig Morten <[email protected]> wrote:
> > On Jan 16, 2013, at 5:16 PM, Attila Csipa <[email protected]> wrote: > >> On 16/01/13 17:36, Mohamed Fawzi wrote: >>> I am certainly not against the idea of a faster/more efficient static way >>> of choosing resources but it cannot depend on a predetermined directory >>> ordering. I believe we should rather focus the immediate efforts on a >>> subset of the problem, like handling multiple image resolutions within .qrc >>> files. >>> that could be handled nicely in the current proposal by adding -highres for >>> example to the images. >>> I se no reason why this "new" URL handler should not look into .qrc files. >>> >>> >> >> It also wouldn't hurt to check how other platforms are doing it for >> inspiration, as there are some precedents/prior art addressing this for >> several years now. iOS has the @2x and -568h naming conventions ( >> http://www.vigorouscoding.com/2012/03/naming-conventions-for-image-resources-in-ios/ >> ), Android has >> http://developer.android.com/guide/practices/screens_support.html , etc >> > > I've already adopted the "@2x" convention for the high-dpi/retina support so > I suggest we go for that. if we use @ as selector separator (which I think gives even less clashes than "-") then this could be implemented using what was discussed in the Platfoem Content Selection. Fawzi > > Morten > > _______________________________________________ > Development mailing list > [email protected] > http://lists.qt-project.org/mailman/listinfo/development _______________________________________________ Development mailing list [email protected] http://lists.qt-project.org/mailman/listinfo/development
