QSP patch/activator
David Faure
faure at kde.org
Sat Jan 23 11:02:30 UTC 2016
On Monday 18 January 2016 12:48:34 René J.V. Bertin wrote:
> David,
>
> In your idea of a QSP::addStandardLocation() approach, would that always add to a "global" list (= affect all subsequent calls to standardLocations()), or would you also consider a variant that only affects the next call?
Global.
"next call" is horrible API (another library or another thread might snatch that from under you).
> Also, if you think we should avoid thinking of this as "providing an XDG-compliant mode", we should probably also find a different name for the KStandardPaths wrapper class we've been discussing. Thoughts (other than QMoreStandardPaths :))?
> FWIW, that wrapper class could implement the variant mentioned above that adds an element to standardLocations() transiently.
Seems like a mix of two ideas. If you route calls via a wrapper, then it can do the extra lookups itself, it doesn't need to add paths to QSP.
--
David Faure, faure at kde.org, http://www.davidfaure.fr
Working on KDE Frameworks 5
More information about the Kde-frameworks-devel
mailing list