Re: Review Request 119126: KMimeTypeChooser: hide Edit button if keditfiletype5 isn't found.

> On July 5, 2014, 9:44 p.m., Christoph Feck wrote: > > Alternatively, the button would get disabled, and the tooltip explains why. Yes, I thought about that too - but it's really not like this button is an important part of the KMimeTypeChooser functionality. You can use it all "readonly" (se

[OSX/Qt5/KF5/KDE CI system] - kate has problem with dynamic linking to phonon

When starting kate or kwrite one gets this error: --- Dyld Error Message: Library not loaded: lib/libphonon4qt5.4.dylib Referenced from: /opt/kde/install/darwin/mavericks/clang/kf5-qt5/frameworks/knotifications/inst/lib/libKF5Notifications.5.dylib Reason: image not found --- where it’s obvi

Re: Review Request 119126: KMimeTypeChooser: hide Edit button if keditfiletype5 isn't found.

--- This is an automatically generated e-mail. To reply, visit: https://git.reviewboard.kde.org/r/119126/#review61674 --- Alternatively, the button would get disabled, and the tooltip

[OSX/Qt5/KF5/KDE CI system] - libksysguard currently broken on master branch

When trying to build the current libksysguard (using the 'jenkins' branch) the CI system ran into this issue: --- [ 76%] Built target graphicssignalplotterbenchmark Undefined symbols for architecture x86_64: "KSysGuard::ProcessesLocal::ProcessesLocal()", referenced from: KSysGuard::Proce

Re: OSX/MacPorts KDE CI System: Asking for trouble due to installations outside the expected $DATA_INSTALL_DIR/kf5 directory for khtml and katepart5

Hi David, On 05 Jul 2014, at 20:04 , David Faure 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 Sup

Re: [OSX/Qt5/KF5/KDE CI system] - kdevplatform currently broken on frameworks branch

On Saturday 05 July 2014 17:47:05 Marko Käning wrote: > When trying to build the current kdevplatform (using the 'jenkins' branch) > the CI system ran into this issue: > Shall I post this on b.k.o.? Better just fix it directly. Should simply be a matter of replacing . [un]lockInline with .[un]l

Re: Review Request 119126: KMimeTypeChooser: hide Edit button if keditfiletype5 isn't found.

> On jul 5, 2014, 11:28 a.m., Mark Gaiser wrote: > > src/kmimetypechooser.cpp, line 64 > > > > > > static const QString s_keditfiletypeExecutable = > > QStringLiteral("keditfiletype5"); > > > > Then you

Re: OSX/MacPorts KDE CI System: Asking for trouble due to installations outside the expected $DATA_INSTALL_DIR/kf5 directory for khtml and katepart5

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 sub

Re: Review Request 119126: KMimeTypeChooser: hide Edit button if keditfiletype5 isn't found.

> On July 5, 2014, 11:28 a.m., Mark Gaiser wrote: > > src/kmimetypechooser.cpp, line 64 > > > > > > static const QString s_keditfiletypeExecutable = > > QStringLiteral("keditfiletype5"); > > > > Then you

Re: Review Request 119079: Add utility function for loading all plugins from a given dir + easy accessor for metadata

> On July 5, 2014, 9:33 a.m., David Faure wrote: > > src/lib/plugin/kpluginmetadata.h, lines 204-205 > > > > > > Make member vars private. > > > > It's not like deriving from a value class makes any sens

Re: Review Request 119079: Add utility function for loading all plugins from a given dir + easy accessor for metadata

> On July 5, 2014, 9:33 a.m., David Faure wrote: > > src/lib/plugin/kpluginmetadata.h, lines 204-205 > > > > > > Make member vars private. > > > > It's not like deriving from a value class makes any sens

Re: OSX/MacPorts KDE CI System: Asking for trouble due to installations outside the expected $DATA_INSTALL_DIR/kf5 directory for khtml and katepart5

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 sub

Re: OSX/MacPorts KDE CI System: Asking for trouble due to installations outside the expected $DATA_INSTALL_DIR/kf5 directory for khtml and katepart5

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 Support/

[OSX/Qt5/KF5/KDE CI system] - kdevplatform currently broken on frameworks branch

When trying to build the current kdevplatform (using the 'jenkins' branch) the CI system ran into this issue: --- Built target kcm_kdevprojectfilter_automoc [ 22%] Building CXX object util/dbus_socket_transformer/CMakeFiles/kdev_dbus_socket_transformer.dir/kdev_dbus_socket_transformer_automoc.c

Re: Review Request 119079: Add utility function for loading all plugins from a given dir + easy accessor for metadata

--- This is an automatically generated e-mail. To reply, visit: https://git.reviewboard.kde.org/r/119079/ --- (Updated Juli 5, 2014, 5:20 nachm.) Review request for KDE Frameworks.

Re: Review Request 119079: Add utility function for loading all plugins from a given dir + easy accessor for metadata

> On Juli 5, 2014, 11:33 vorm., David Faure wrote: > > I like the idea of having a method to list or load the plugins from a given > > subdir of the plugin path. > > > > The method that returns a QList could/should actually go into Qt > > at some point. The rest is tied to our specific metadat

Re: Deprecation warnings not showing on CMake 3

On Tuesday 03 June 2014 23:01:23 Anuj Pahuja wrote: > Hi, > > I am building libkdegames on KF5/Qt5 using CMake 3 but I'm not getting > deprecation warnings for KDELibs4Support classes (KDialog, KFileDialog > etc.). However, I get all the deprecation warnings when I use CMake 2.8. > Also, functions

Re: Review Request 119126: KMimeTypeChooser: hide Edit button if keditfiletype5 isn't found.

--- This is an automatically generated e-mail. To reply, visit: https://git.reviewboard.kde.org/r/119126/#review61641 --- src/kmimetypechooser.cpp

Fwd: [Kde-hardware-devel] [Patch included] Re: OSX/MacPorts KDE CI System: Build failed for framework solid

Sent it only to kde-hardware-devel by mistake - Weitergeleitete Nachricht von k...@privat.broulik.de - Datum: Thu, 03 Jul 2014 10:32:40 +0200 Von: k...@privat.broulik.de Antwort an: kde-hardware-de...@kde.org Betreff: [Kde-hardware-devel] [Patch included] Re: OSX/MacPorts

Re: OSX/MacPorts KDE CI System: Asking for trouble due to installations outside the expected $DATA_INSTALL_DIR/kf5 directory for khtml and katepart5

> 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

Re: OSX/MacPorts KDE CI System: Asking for trouble due to installations outside the expected $DATA_INSTALL_DIR/kf5 directory for khtml and katepart5

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 file

Re: OSX/MacPorts KDE CI System: Asking for trouble due to installations outside the expected $DATA_INSTALL_DIR/kf5 directory for khtml and katepart5

> 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:

Re: OSX/MacPorts KDE CI System: Asking for trouble due to installations outside the expected $DATA_INSTALL_DIR/kf5 directory for khtml and katepart5

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

Review Request 119126: KMimeTypeChooser: hide Edit button if keditfiletype5 isn't found.

--- This is an automatically generated e-mail. To reply, visit: https://git.reviewboard.kde.org/r/119126/ --- Review request for KDE Frameworks, Christoph Feck and Jonathan Riddell. R

Re: OSX/MacPorts KDE CI System: Asking for trouble due to installations outside the expected $DATA_INSTALL_DIR/kf5 directory for khtml and katepart5

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

Re: keditfiletype binary

On Tuesday 29 April 2014 17:19:20 Jonathan Riddell wrote: > keditfiletype is in kde-cli-tools in workspace category and used to be in > kde-runtime. I've submitted a review to rename it for coinstallability and > noticed that it gets used in frameworks in a couple of places > > frameworks/kio/sr

Re: keditfiletype binary

Hi, sorry for not getting around to replying to this earlier. On Tuesday 29 April 2014 17:19:20 Jonathan Riddell wrote: > keditfiletype is in kde-cli-tools in workspace category and used to be in > kde-runtime. I've submitted a review to rename it for coinstallability and > noticed that it gets us

Re: Deprecation warnings not showing on CMake 3

On Tuesday 03 June 2014 23:01:23 Anuj Pahuja wrote: > Hi, > > I am building libkdegames on KF5/Qt5 using CMake 3 but I'm not getting > deprecation warnings for KDELibs4Support classes (KDialog, KFileDialog > etc.). However, I get all the deprecation warnings when I use CMake 2.8. > Also, functions

Re: OSX/MacPorts KDE CI System: Installs not into configured CMAKE_INSTALL_BUNDLEDIR on OSX - specifically for frameworks kauth & kjsembed

On Saturday 05 July 2014 11:30:57 Marko Käning wrote: > There are 6 app packages to be found on OSX which are NOT in the configured > bundle dir. > > This is understandable for libexec/kf5/kconfig_compiler_kf5.app since it was > specifically configured to land in there. > > Probably also all other

Re: OSX/MacPorts KDE CI System: Asking for trouble due to installations outside the expected $DATA_INSTALL_DIR/kf5 directory for khtml and katepart5

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

Re: Review Request 119079: Add utility function for loading all plugins from a given dir + easy accessor for metadata

--- This is an automatically generated e-mail. To reply, visit: https://git.reviewboard.kde.org/r/119079/#review61635 --- I like the idea of having a method to list or load the plugins

OSX/MacPorts KDE CI System: Installs not into configured CMAKE_INSTALL_BUNDLEDIR on OSX - specifically for frameworks kauth & kjsembed

There are 6 app packages to be found on OSX which are NOT in the configured bundle dir. This is understandable for libexec/kf5/kconfig_compiler_kf5.app since it was specifically configured to land in there. Probably also all other app packages below libexec shall indeed go there, but: 1) Why

OSX/MacPorts KDE CI System: Asking for trouble due to installations outside the expected $DATA_INSTALL_DIR/kf5 directory for khtml and katepart5

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 Su

Re: [Kde-hardware-devel] OSX/MacPorts KDE CI System: Build failed for framework solid

Hi David, > Done (v5.0.0-rc2 tag) thanks. I'll re-run the whole build later, just to make sure that nothing else got broken in the meantime. Greets, Marko ___ Kde-frameworks-devel mailing list Kde-frameworks-devel@kde.org https://mail.kde.org/mailman

Re: [kde-promo] KDE Frameworks 5 promo

On Wednesday 02 July 2014 19:00:49 Kevin Ottens wrote: > Hello, > > On Wednesday 02 July 2014 10:48:58 David Faure wrote: > > On Wednesday 02 July 2014 10:35:29 Jos Poortvliet wrote: > > > On Tuesday 01 July 2014 23:13:24 David Faure wrote: > > > > On Tuesday 01 July 2014 16:16:48 Jonathan Riddell