network manager qt - how to get the passwords

2015-08-27 Thread Boettger, Heiko
Hi, I am currently developing a gui for our products to edit the network settings. One thing which I cannot figure out is how to get the passwords. Simply calling NetworkManager::Security8021xSetting::password() or any of the other password-methods doesn't seem to work. Is there somewhere a

Re: network manager qt - how to get the passwords

2015-08-27 Thread Jan Grulich
Hi, On Thursday 27 of August 2015 09:43:54 Boettger, Heiko wrote: Hi, I am currently developing a gui for our products to edit the network settings. One thing which I cannot figure out is how to get the passwords. Simply calling NetworkManager::Security8021xSetting::password() or any of

Re: Review Request 124698: KPasswordDialog: allow the user to show the password

2015-08-27 Thread David Faure
--- This is an automatically generated e-mail. To reply, visit: https://git.reviewboard.kde.org/r/124698/#review84491 --- Ship it! Ship It! - David Faure On Aug. 26, 2015, 10:36

Re: Review Request 124905: Win: Hide console window for binaries in LIBEXEC

2015-08-27 Thread Patrick Spendrin
--- This is an automatically generated e-mail. To reply, visit: https://git.reviewboard.kde.org/r/124905/#review84496 --- Wait, Wait, Wait. 1) The difference between console apps and

Re: Review Request 124698: KPasswordDialog: allow the user to show the password

2015-08-27 Thread Christoph Feck
On Aug. 27, 2015, 9:35 p.m., David Faure wrote: Ship It! Does it make sense to also have this feature in KNewPasswordDialog? - Christoph --- This is an automatically generated e-mail. To reply, visit:

Re: Review Request 124698: KPasswordDialog: allow the user to show the password

2015-08-27 Thread Elvis Angelaccio
On Ago. 27, 2015, 9:35 p.m., David Faure wrote: Ship It! Christoph Feck wrote: Does it make sense to also have this feature in KNewPasswordDialog? I have another RR ready to submit after this one. I'd like to add a new widget called `KNewPasswordWidget`, meant to be used in custom

Re: Paths to internal executables (c.f. libexec) hard-coded

2015-08-27 Thread David Faure
On Thursday 27 August 2015 00:14:50 Kevin Funk wrote: If we want to support this case, then we'd need to create a KSomething::libexecPaths() method returning the following search path (in order): - Windows: - Just QCA::applicationDirPath() (we control the install layout anyway) -

Re: Review Request 124905: Win: Hide console window for binaries in LIBEXEC

2015-08-27 Thread Kevin Funk
On Aug. 26, 2015, 7:24 a.m., David Faure wrote: It sounds to me like ecm_mark_non_gui_executable doesn't do the right thing then, and should be fixed, instead? These are non gui executables, so from an API point of view, using this function is correct. Would we ever want a

Re: Paths to internal executables (c.f. libexec) hard-coded

2015-08-27 Thread Volker Krause
On Thursday 27 August 2015 00:14:50 Kevin Funk wrote: On Wednesday 26 August 2015 13:40:20 Volker Krause wrote: On Wednesday 26 August 2015 13:15:15 Kevin Funk wrote: Heya, This is problem on Windows because the *final* installation location is not known at compile-time

Re: Review Request 124892: bug 342962: kdeclarative plugins should be built as a bundle plugin and not a shared library

2015-08-27 Thread Harald Sitter
On Aug. 25, 2015, 2:22 p.m., René J.V. Bertin wrote: When built as SHARED as in the current code, libdraganddropplugin.dylib gets installed to $PREFIX/share/qt5/qml/org/kde/draganddrop, but is given an OS X install_name of $PREFIX/lib/libdraganddropplugin.dylib. This mismatch can

Re: Review Request 124905: Win: Hide console window for binaries in LIBEXEC

2015-08-27 Thread David Faure
On Aug. 26, 2015, 7:24 a.m., David Faure wrote: It sounds to me like ecm_mark_non_gui_executable doesn't do the right thing then, and should be fixed, instead? These are non gui executables, so from an API point of view, using this function is correct. Would we ever want a

Re: Review Request 124905: Win: Hide console window for binaries in LIBEXEC

2015-08-27 Thread David Faure
On Aug. 26, 2015, 7:24 a.m., David Faure wrote: It sounds to me like ecm_mark_non_gui_executable doesn't do the right thing then, and should be fixed, instead? These are non gui executables, so from an API point of view, using this function is correct. Would we ever want a