> On 24 Feb 2015, at 07:24, Jeremy Whiting <jpwhit...@kde.org> wrote: > > Hello list, > > I discussed a bit with Thiago and some others on irc this evening and have > realized that the QStandardPaths patch from [1] and discussion on [2] is > trying to solve too many problems at once. I'll list the problems here and > some possible solutions to these problems afterwards so we can discuss what > are appropriate/purposeful fixes to the problems and get these issues fixed. > > Thoughts, opinions, counterarguments, suggestions?
(Disclaimer: I know little about KDE frameworks internals) On OS X (and iOS): place the resources in he framework bundle for the component that owns them. Add public API to the component for accessing the resources. Installers and deployment utilities can then move the framework bundles as needed, for example to a shared location for a “system” installation, or to the applicaiton bundle to create a stand-alone, sandboxable app. Thanks for the writeup! I find sharing the "big picture" like this very useful. Morten _______________________________________________ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development
