On 07 Jul 2014, at 00:09 , David Faure fa...@kde.org wrote:
I reinstalled ECM, kxmlgui and kate, but I don’t see a folder
/Library/Application Support/kxmlgui5 but instead this for kate’s install
root
I said if this goes in. It wasn't committed yet, as you can see in RR
119142. Patience :)
On Sunday 06 July 2014 20:20:08 Marko Käning wrote:
kwrite is now MISSING in that directory (it was there before the patching)!
Where did it go?
... to the kxmlgui5 subdir, which is the whole point of that change...
But you should probably look at kwrite/inst, not kate/inst.
--
David Faure,
On Monday 07 July 2014 21:31:06 Marko Käning wrote:
Hmm, kwrite gets installed as part of kate.
Ah oops I hadn't noticed. OK.
And this is where kxmlgui folder resides:
Irrelevant, that's the kxmlgui framework. Other things won't be writing into
that install root, that's for sure.
With my
On Monday 07 July 2014 23:16:43 Marko Käning wrote:
kde/applications/kate/inst/share/kxmlgui5/kwrite/kwriteui.rc
OK.
So, we’re with kxmlgui5 actually NOT below /Library/Application Support/,
but just like in Linux below /share lying parallel to /Library:
which is where the kwrite’s folder
On 07 Jul 2014, at 23:29 , David Faure fa...@kde.org wrote:
Urgh, don't confuse cmake and C++ code.
oh, you’re right!!!
:-/
1) Files get installed by cmake.
2) Files are looked up at runtime by C++ code using QStandardPaths.
Yep.
You can patch 2) all you want, it won't have any effect on 1).
Hi David,
On 07 Jul 2014, at 23:34 , Marko Käning mk-li...@email.de wrote:
Will reiterate this.
OK, so here we see the actual settings for the CI system:
---
MVM2:bin marko$ ./qtpaths --paths ConfigLocation
/opt/kde/install/darwin/mavericks/system/Library/Preferences
MVM2:bin marko$ ./qtpaths
On Saturday 05 July 2014 20:47:13 Marko Käning wrote:
This is the issue: there isn't just one vendor. Anyone can build apps on
top of Qt and KF5. So we can't hardcode a vendor in Qt or KF5 APIs.
Well, I thought, that the frameworks themselves have a vendor, namely KDE!
System-wide
Hi David,
On 06 Jul 2014, at 11:41 , David Faure fa...@kde.org wrote:
Framework-specific yes. But again, take the case of kxmlgui files as an
example. They are loaded by the kxmlgui framework itself, whether they got
installed by a kde framework, a kde app, a non-kde app (= an application
On 06 Jul 2014, at 11:41 , David Faure fa...@kde.org wrote:
Marko, if this goes in, can you port everything kf5-based to install .rc
files
in KXMLGUI_INSTALL_DIR just like kwrite.diff does for write?
I reinstalled ECM, kxmlgui and kate, but I don’t see a folder
/Library/Application
On Sunday 06 July 2014 20:20:08 Marko Käning wrote:
On 06 Jul 2014, at 11:41 , David Faure fa...@kde.org wrote:
Marko, if this goes in, can you port everything kf5-based to install .rc
files in KXMLGUI_INSTALL_DIR just like kwrite.diff does for write?
I reinstalled ECM, kxmlgui and kate,
khtml and katepart5 currently still ask for upcoming trouble when installing
the frameworks on OSX [1],
as they put files directly into
/Library/Application Support
instead of
/Library/Application Support/kf5
as all other frameworks do with
-DDATA_INSTALL_DIR=Library/Application
On Saturday 05 July 2014 11:20:28 Marko Käning wrote:
khtml and katepart5 currently still ask for upcoming trouble when installing
the frameworks on OSX [1], as they put files directly into
/Library/Application Support
instead of
/Library/Application Support/kf5
as all other
Hi David,
KXMLGUI files (called foo.rc) are found in
GenericDataLocation + '/' + componentName + '/' + fileName.
This is why KHTML installs its .rc files in DATA/khtml.
that's what I figured, but ...
Just like all KDE apps will install their rc files in DATA/appname.
I then spotted the
On Saturday 05 July 2014 12:30:05 Marko Käning wrote:
I then spotted the 13 framework applications shown below [1] getting
installed into the kf5 subfolder.
Yes but no *.rc files, right?
--
David Faure, fa...@kde.org, http://www.davidfaure.fr
Working on KDE Frameworks 5
On Saturday 05 July 2014 12:30:05 Marko Käning wrote:
I then spotted the 13 framework applications shown below [1] getting
installed into the kf5 subfolder.
Yes but no *.rc files, right?
Well, there are tons of files in those folders - of course - AND also these
three *.rc files:
---
$
On Saturday 05 July 2014 12:41:14 Marko Käning wrote:
On Saturday 05 July 2014 12:30:05 Marko Käning wrote:
I then spotted the 13 framework applications shown below [1] getting
installed into the kf5 subfolder.
Yes but no *.rc files, right?
Well, there are tons of files in those
No I mean in the frameworks which do install stuff under /kf5/.
Oh, ok.
But I looked now, and there aren't any. Which proves my point: .rc files
don't
go into the kf5 subfolder.
Yes.
Good that we've verified it. :)
___
Kde-frameworks-devel
Hi David and all,
Which proves my point: .rc files don't go into the kf5 subfolder.
I was pondering this again just now and came to the conclusion that
all the KF5/KDE frameworks and apps should install everything into
some subdir of the system's directory like
/Library/Application
On Saturday 05 July 2014 18:31:20 Marko Käning wrote:
Hi David and all,
Which proves my point: .rc files don't go into the kf5 subfolder.
I was pondering this again just now and came to the conclusion that
all the KF5/KDE frameworks and apps should install everything into
some subdir of
On Saturday 05 July 2014 18:31:20 Marko Käning wrote:
Hi David and all,
Which proves my point: .rc files don't go into the kf5 subfolder.
I was pondering this again just now and came to the conclusion that
all the KF5/KDE frameworks and apps should install everything into
some subdir of
Hi David,
On 05 Jul 2014, at 20:04 , David Faure fa...@kde.org wrote:
/Library/Application Support/KF5/
by which KF5 wouldn't clutter /Library/Application Support with
a ton of KF5-related files.
This doesn't fit with QStandardPaths::GenericDataLocation which points to
/Library/Application
21 matches
Mail list logo
