Re: Plasma 5.2 bits for kdereview
El Divendres, 19 de desembre de 2014, a les 17:27:01, Jonathan Riddell va escriure: Plasma 5.2 is due out next month and there's a few KDE projects which would be good to be included. Please review these for inclusion in kde/workspace.. Can i ask this to never happen again? I'd very much prefer separate emails sent by the maintainers of the apps, it makes everything much easier to skim throught emails and realize i want to act if i see an email that says Touchpad KCM for Plasma 5.2 than if i see a Plasma 5.2 bits email. Cheers, Albert Bluedevil frameworks branch by David Rosca https://projects.kde.org/projects/extragear/base/bluedevil https://projects.kde.org/projects/playground/libs/libbluedevil User-manager frameworks port (it overlaps a little with account details kcm but is mostly an admin tool) https://projects.kde.org/projects/playground/base/user-manager kscreen and libkscreen maintained by Dan Vrátil. libkscreen is already released with Plasma but isn't in kde/workspace. https://projects.kde.org/projects/extragear/libs/libkscreen https://projects.kde.org/projects/extragear/base/kscreen ModemManagerQt, already released with Plasma, makes sense to move to kde/workspace (libnm-qt is moving to frameworks) https://projects.kde.org/projects/extragear/libs/libmm-qt Touchpad KCM, ported to KF5 by Rajeesh K Nambiar https://projects.kde.org/projects/playground/utils/kcm-touchpad sddm-kcm is already in http://thread.gmane.org/gmane.comp.kde.devel.core/84629 polkit-kde already requested on this list http://thread.gmane.org/gmane.comp.kde.devel.general/68224/focus=85357 It has also been suggested that ksshaskpass should moved to kde/workspace for release with Plasma (currently it has no home and is looking for one), anyone have an opinion on whether it should be part of the desktop or applications? http://thread.gmane.org/gmane.comp.kde.devel.core/85039 I'll ask for the ones in playground to be moved to kdereview now so URLs may change. Jonathan
Fwd: Plasma 5.2 bits for kdereview
On Thu, Jan 1, 2015 at 4:56 PM, Albert Astals Cid aa...@kde.org wrote: El Dimarts, 23 de desembre de 2014, a les 13:17:46, Daniel Vrátil va escriure: On Friday, December 19, 2014 06:46:11 PM Luigi Toscano wrote: Jonathan Riddell ha scritto: Plasma 5.2 is due out next month and there's a few KDE projects which would be good to be included. Please review these for inclusion in kde/workspace.. kscreen and libkscreen maintained by Dan Vrátil. libkscreen is already released with Plasma but isn't in kde/workspace. https://projects.kde.org/projects/extragear/libs/libkscreen https://projects.kde.org/projects/extragear/base/kscreen I disagree with moving libkscreen to kde/workspace. It is a dependency for at least one application (Okular), which has no Framework version for now but it will have it. It would make more sense to have libkscreen in Frameworks, like libnm* AFAIK Okular is using KScreen only to get DPI info, which was not provided by QScreen in Qt 4. In Qt 5 you already have DPI API in QScreen, so you should not need KScreen anymore. It is provided by QX11Info in Qt4, it's just wrong, does QScreen provide it correctly like kscreen does? Theoretically, yes it's correct. QScreen now reports DPI per monitor, not per each X screen which was the QX11Info problem. It's still subject to monitors reporting the wrong DPI, but so is kscreen. The API is a bit questionable. You'll might be told you're on QScreen 0, but will tell you have global co-ordinates that don't actually fit on that screen. You have to look up the correct QScreen, don't trust whatever QWindow will tell you. David Cheers, Albert Dan
Re: Dr Konqi still misbehaving - advice needed
El Dijous, 1 de gener de 2015, a les 16:48:59, Ian Wadham va escriure: Hi Thomas and others, My patch, based on Thomas' idea for handling the stale-cookies problem in Dr Konqi, has now been backported to the Applications/14.12 branch and forward-ported to master in KF5's plasma-workspace (thanks, Hrvoje). https://bugs.kde.org/show_bug.cgi?id=337742 has been closed and marked as Fixed in 14.12.1. If I understand correctly, this change will be tagged in Applications/14.12 on 8 January 2015 and released on 13 January 2015 in Applications/14.12.1. Please can someone confirm this, i.e. Have I done the pushes correctly? kde-runtime commit will yes; plasma-workspace is released separately from Applications/14.12 so it will be released a bit later Cheers, Albert Now that the holiday season is closing, please could somebody give the change a quick test on Linux and KDE 4? See details below. My own tests on Apple OS X were inconclusive. I was unable to reproduce the problem with stale cookies. On 29/12/2014, at 5:31 PM, Ian Wadham wrote: So could someone please do before-and-after tests of patch [1] on KDE 4 and Linux, using the bugstest.kde.org database? i.e. a) No patch [1], no cookies for bugstest.kde.org --- Dr K should succeed. b) No patch [1], cookies added --- Dr K should fail. c) Patch [1] added, cookies still present --- Dr K should succeed. See attachment [2] for a patch to set up Dr K to use the test database (cloned about 3 months ago). It should contain most of the accounts and data of the live bugs.kde.org database, but will send no embarrassing emails… Thanks in advance, Ian W. [1] DrKonqiSecurity_5.patch [2] DrK_bugstest.patch All the best, Ian W.
Re: Plasma 5.2 bits for kdereview
El Dimarts, 23 de desembre de 2014, a les 13:17:46, Daniel Vrátil va escriure: On Friday, December 19, 2014 06:46:11 PM Luigi Toscano wrote: Jonathan Riddell ha scritto: Plasma 5.2 is due out next month and there's a few KDE projects which would be good to be included. Please review these for inclusion in kde/workspace.. kscreen and libkscreen maintained by Dan Vrátil. libkscreen is already released with Plasma but isn't in kde/workspace. https://projects.kde.org/projects/extragear/libs/libkscreen https://projects.kde.org/projects/extragear/base/kscreen I disagree with moving libkscreen to kde/workspace. It is a dependency for at least one application (Okular), which has no Framework version for now but it will have it. It would make more sense to have libkscreen in Frameworks, like libnm* AFAIK Okular is using KScreen only to get DPI info, which was not provided by QScreen in Qt 4. In Qt 5 you already have DPI API in QScreen, so you should not need KScreen anymore. It is provided by QX11Info in Qt4, it's just wrong, does QScreen provide it correctly like kscreen does? Cheers, Albert Dan signature.asc Description: This is a digitally signed message part.
Re: Touchpad KCM - was - Re: Plasma 5.2 bits for kdereview
On Thu, Jan 1, 2015 at 4:50 PM, Albert Astals Cid aa...@kde.org wrote: El Divendres, 19 de desembre de 2014, a les 17:27:01, Jonathan Riddell va escriure: Touchpad KCM, ported to KF5 by Rajeesh K Nambiar https://projects.kde.org/projects/playground/utils/kcm-touchpad This is not a kcm, it's a kcm + a kded. The kded is partly conflicting with what ktouchpadenabler does (it's doing it worse though since the proper shortcuts are not set). I understand you guys have decided to remove ktouchpadenabler when merging this. FWIW, it's not merged yet. It's not going to be part of 5.2 unless the rest of my review comments (other thread) are addressed within the next few days. I have no time to try this, but can you please at least fix the shortcuts? Cheers, Albert
Touchpad KCM - was - Re: Plasma 5.2 bits for kdereview
El Divendres, 19 de desembre de 2014, a les 17:27:01, Jonathan Riddell va escriure: Touchpad KCM, ported to KF5 by Rajeesh K Nambiar https://projects.kde.org/projects/playground/utils/kcm-touchpad This is not a kcm, it's a kcm + a kded. The kded is partly conflicting with what ktouchpadenabler does (it's doing it worse though since the proper shortcuts are not set). I understand you guys have decided to remove ktouchpadenabler when merging this. I have no time to try this, but can you please at least fix the shortcuts? Cheers, Albert
Re: libkgeomap
El Dijous, 1 de gener de 2015, a les 23:23:16, Gilles Caulier va escriure: 2015-01-01 23:16 GMT+01:00 Albert Astals Cid aa...@kde.org: El Diumenge, 21 de desembre de 2014, a les 19:39:27, Tobias Leupold va escriure: Am Sonntag 21 Dezember 2014, 19:27:48 schrieb Albert Astals Cid: H, i understand you're the only user at the moment, but how is libkgeomap is a wrapper between marble for local map, OpenStreetMap, and GoogleMaps, to display geolocated items place over a world map. A widget is provided, and collection of tools to process : - Reverse Geocoding, - Tracks management, - Selection over map to process searches. * Photo Management related? We use it to display the location(s) where (a) photo(s) has/have been taken. It helps tagging photos, and later, you can simply see that place when viewing a photo. That's what you use it for, but can I use it to show the places my bank has offices? I'm not sure to understand... Typically, libkgeomap don't care about files to manage. It's item to geolocalize. Right, so it doesn't have much to do with graphics, right? That's what i'm saying. Cheers, Albert In digiKam we have a small interface to wrap libkgeomap with image geolocation stored in database. The real link between GPS info to display over the map and image/Video are done here. So, you can wrap your main data to geolocalize by the same way. libkgeompa do care about data which will store GPS info. Gilles Caulier
Re: libkgeomap
2015-01-01 23:16 GMT+01:00 Albert Astals Cid aa...@kde.org: El Diumenge, 21 de desembre de 2014, a les 19:39:27, Tobias Leupold va escriure: Am Sonntag 21 Dezember 2014, 19:27:48 schrieb Albert Astals Cid: H, i understand you're the only user at the moment, but how is libkgeomap is a wrapper between marble for local map, OpenStreetMap, and GoogleMaps, to display geolocated items place over a world map. A widget is provided, and collection of tools to process : - Reverse Geocoding, - Tracks management, - Selection over map to process searches. * Photo Management related? We use it to display the location(s) where (a) photo(s) has/have been taken. It helps tagging photos, and later, you can simply see that place when viewing a photo. That's what you use it for, but can I use it to show the places my bank has offices? I'm not sure to understand... Typically, libkgeomap don't care about files to manage. It's item to geolocalize. In digiKam we have a small interface to wrap libkgeomap with image geolocation stored in database. The real link between GPS info to display over the map and image/Video are done here. So, you can wrap your main data to geolocalize by the same way. libkgeompa do care about data which will store GPS info. Gilles Caulier
Re: libkgeomap
2015-01-01 23:40 GMT+01:00 Albert Astals Cid aa...@kde.org: El Dijous, 1 de gener de 2015, a les 23:23:16, Gilles Caulier va escriure: 2015-01-01 23:16 GMT+01:00 Albert Astals Cid aa...@kde.org: El Diumenge, 21 de desembre de 2014, a les 19:39:27, Tobias Leupold va escriure: Am Sonntag 21 Dezember 2014, 19:27:48 schrieb Albert Astals Cid: H, i understand you're the only user at the moment, but how is libkgeomap is a wrapper between marble for local map, OpenStreetMap, and GoogleMaps, to display geolocated items place over a world map. A widget is provided, and collection of tools to process : - Reverse Geocoding, - Tracks management, - Selection over map to process searches. * Photo Management related? We use it to display the location(s) where (a) photo(s) has/have been taken. It helps tagging photos, and later, you can simply see that place when viewing a photo. That's what you use it for, but can I use it to show the places my bank has offices? I'm not sure to understand... Typically, libkgeomap don't care about files to manage. It's item to geolocalize. Right, so it doesn't have much to do with graphics, right? That's what i'm saying. in theory, yes. Gilles
Re: libkgeomap
El Diumenge, 21 de desembre de 2014, a les 19:39:27, Tobias Leupold va escriure: Am Sonntag 21 Dezember 2014, 19:27:48 schrieb Albert Astals Cid: H, i understand you're the only user at the moment, but how is libkgeomap is a wrapper between marble for local map, OpenStreetMap, and GoogleMaps, to display geolocated items place over a world map. A widget is provided, and collection of tools to process : - Reverse Geocoding, - Tracks management, - Selection over map to process searches. * Photo Management related? We use it to display the location(s) where (a) photo(s) has/have been taken. It helps tagging photos, and later, you can simply see that place when viewing a photo. That's what you use it for, but can I use it to show the places my bank has offices? If so, I find it hard to justify such a thing living in kdegraphics/libs even though it's true I can't think of a better (nor worse) place. Any smart idea anyone? Cheers, Albert It's not strictly related to photo management, as it can display any coordinates. But that's what we (Digikam, kipi-plugins and KPhotoAlbum) use it for. Tobias Ps: Technically, there are at least two users ;-)
Re: Fwd: Plasma 5.2 bits for kdereview
On Donnerstag, 1. Januar 2015 22:01:11 CEST, David Edmundson wrote: You'll might be told you're on QScreen 0, but will tell you have global co-ordinates that don't actually fit on that screen. You have to look up the correct QScreen, don't trust whatever QWindow will tell you. Even after habing acquired a native window handle, resp. having the window mapped and managed? (The WM will usually position it, move it to the current screen etc.) Cheers, Thomas
Re: Plasma 5.2 bits for kdereview
Jonathan Riddell ha scritto: polkit-kde already requested on this list http://thread.gmane.org/gmane.comp.kde.devel.general/68224/focus=85357 This has been moved, but master is still kdelibs4-based. - Is it going to change? - Is there a final kdelibs4-based branch that can be tracked for the time being into the stable kdelibs4 l10n branch as extragear-base? Ciao and happy new year! -- Luigi
