On Sun, Dec 7, 2014 at 10:33 AM, Alejandro Exojo <s...@badopi.org> wrote:
> That's the opposite of what most people are trying to do. > > If the overhead is negligible, you may not care much of shipping all the > assets in one binary package, of which the user will only see a part, but > other applications might prefer to save some space if they contain many > assets. > The problem is that this model does not scale. Now there is one device using SailfishOS, next June there will be two... Hopefully there will be more in one year. So you want to make one build for each model that will use SailfishOS in the future? I think Jolla hopes to license the OS to other vendors. If they succeed, optimization s targeted to single devices will not be practical. The best option is to build the asset in a scalable format (or ship it at high res) and then render it at install time... Like what has been proposed for the icon scaling. > However, the main thing that motivated me to dig into the issue and send the > mail was libsailfishapp. That library is, AFAIK, only relevant on Sailfish, > and also requires one to add special code in main(). That can't be done at > runtime (well, you could do it I think, but you really don't want to, given > that you already have to set a special binary name, for example, and it > complicates things for no reason). > Well, I think the easiest thing to do is do out-of source builds, and since the target configuration qmake -config sailfishos qmake -config blackberry etc. Then if you want to have different assets, you can do this as well... But it makes no sense to ask for a generic way to do that. In the end, the Qt platform for sailfish os is indeed simply Linux, or if you want Linux+Wayland. The rest of the dependencies should be checked package for package: So on linux, check if there is libsailfishapp, and build the sailfish version. Check for... Mir, and build for Ubuntu. Or build for a desktop Linux if you do not find mobile specific libraries. > Other features like screen size, language, etc. Of course you want to do it at > runtime. But note that the default +android, +blackberry directories that are > different anyway, do something like for the sailfish > QFileSelector knows about should work out of the box with plain Qt. See for > example: > > https://github.com/qtproject/qtbase/blob/8ee7aa78afd3d3dee6e333953d51aa72cb227441/src/corelib/io/qfileselector.cpp#L349-386 > > This can still be added to the QQmlFileSelector of the engine through > libsailfishapp, so I think I'll send a pull request anyways. > > -- > Alex (a.k.a. suy) | GPG ID 0x0B8B0BC2 > http://barnacity.net/ | http://disperso.net > _______________________________________________ > SailfishOS.org Devel mailing list > To unsubscribe, please send a mail to devel-unsubscr...@lists.sailfishos.org -- Luciano Montanaro Anyone who is capable of getting themselves made President should on no account be allowed to do the job. -- Douglas Adams _______________________________________________ SailfishOS.org Devel mailing list To unsubscribe, please send a mail to devel-unsubscr...@lists.sailfishos.org
