KDE CI: Frameworks » kio » kf5-qt5 FreeBSDQt5.15 - Build # 800 - Still Unstable!
BUILD UNSTABLE Build URL https://build.kde.org/job/Frameworks/job/kio/job/kf5-qt5%20FreeBSDQt5.15/800/ Project: kf5-qt5 FreeBSDQt5.15 Date of build: Thu, 20 May 2021 01:13:36 + Build duration: 9 min 54 sec and counting JUnit Tests Name: projectroot Failed: 1 test(s), Passed: 55 test(s), Skipped: 0 test(s), Total: 56 test(s)Failed: projectroot.autotests.applicationlauncherjob_servicetestName: projectroot.autotests Failed: 0 test(s), Passed: 6 test(s), Skipped: 0 test(s), Total: 6 test(s)Name: projectroot.src.ioslaves.trash Failed: 0 test(s), Passed: 1 test(s), Skipped: 0 test(s), Total: 1 test(s)Name: projectroot.src.kpasswdserver Failed: 0 test(s), Passed: 1 test(s), Skipped: 0 test(s), Total: 1 test(s)
Re: Any interest in a batch file renamer in KIO?
On Wednesday, May 19, 2021 10:10:32 A.M. CDT Nomen Luni wrote: > I can't remember if KRename comes pre-installed in Neon? It does not.
Re: Any interest in a batch file renamer in KIO?
On 5/19/21 9:10 AM, Nomen Luni wrote: I can't remember if KRename comes pre-installed in Neon? If not, doing so would increase discoverability- which may filter to other distributions. Also, the Dolphin service menu entry appears as 'Rename with KRename,' which IMO could do with changing. 'Batch rename,' or 'Bulk rename' would be much more aesthetic and meaningful to the average user, IMO. Absolutely agree. We should also not show the context menu item when there is only one file selected. :) Nate
Re: Any interest in a batch file renamer in KIO?
I can't remember if KRename comes pre-installed in Neon? If not, doing so would increase discoverability- which may filter to other distributions. Also, the Dolphin service menu entry appears as 'Rename with KRename,' which IMO could do with changing. 'Batch rename,' or 'Bulk rename' would be much more aesthetic and meaningful to the average user, IMO. On 19/05/2021 15:21, Nate Graham wrote: On 5/19/21 6:33 AM, Konstantin Kharlamov wrote: On Wed, 2021-05-19 at 15:29 +0300, Konstantin Kharlamov wrote: On Wed, 2021-05-19 at 13:30 +0200, Harald Sitter wrote: My point on discoverability was that a person more likely to question "Hmm, what plugins do I have in Dolphin" and find out this plugin, rather than "Hmm, what can I use to rename a bunch of files", in which case they need to use search engine, and after they did it, they'll most likely get a bunch of bash solutions. KRename won't be one of them unless they specifically search for "KDE file rename tools". So in that sense, discoverability of a plugin is higher than that of a stand- alone app. To clarify: this of course implies the plugin would be included by default with Dolphin. Otherwise indeed, there's no difference in discoverability compared to KRename Since installing KRename adds a relevant item to Dolphin's context menu automatically, maybe the real problem is simply that KRename isn't installed by default in the typical distros that our users use, so nobody ever finds this functionality unless they happened to already know about about and manually installed KRename. Nate
Re: Any interest in a batch file renamer in KIO?
On 5/19/21 6:33 AM, Konstantin Kharlamov wrote: On Wed, 2021-05-19 at 15:29 +0300, Konstantin Kharlamov wrote: On Wed, 2021-05-19 at 13:30 +0200, Harald Sitter wrote: My point on discoverability was that a person more likely to question "Hmm, what plugins do I have in Dolphin" and find out this plugin, rather than "Hmm, what can I use to rename a bunch of files", in which case they need to use search engine, and after they did it, they'll most likely get a bunch of bash solutions. KRename won't be one of them unless they specifically search for "KDE file rename tools". So in that sense, discoverability of a plugin is higher than that of a stand- alone app. To clarify: this of course implies the plugin would be included by default with Dolphin. Otherwise indeed, there's no difference in discoverability compared to KRename Since installing KRename adds a relevant item to Dolphin's context menu automatically, maybe the real problem is simply that KRename isn't installed by default in the typical distros that our users use, so nobody ever finds this functionality unless they happened to already know about about and manually installed KRename. Nate
KDE CI: Frameworks » kservice » kf5-qt5 FreeBSDQt5.15 - Build # 132 - Fixed!
BUILD SUCCESS Build URL https://build.kde.org/job/Frameworks/job/kservice/job/kf5-qt5%20FreeBSDQt5.15/132/ Project: kf5-qt5 FreeBSDQt5.15 Date of build: Wed, 19 May 2021 14:02:16 + Build duration: 1 min 26 sec and counting JUnit Tests Name: projectroot Failed: 0 test(s), Passed: 11 test(s), Skipped: 0 test(s), Total: 11 test(s)Name: projectroot.tests Failed: 0 test(s), Passed: 1 test(s), Skipped: 0 test(s), Total: 1 test(s)
T14471: Make Qt 5.15.0 to 5.15.2 for frameworks
ahmadsamir added a comment. Anything other than the methods that were added for "portability at the expense of performance", should be OK, famous last words™. :) I've been bitten twice by the QStringView API in Qt5, it has too many surprises, basically because upstream decided to make "code" portable any which way... but I digress. Since QStringRef is in a Qt6 compat module, I think QStringView should wait until we branch KF6; we also get QStrinTokenizer Qt6 (yes, it means we might scramble a bit between when we branch KF6 and the first release to fix affected public API's, but I think that's safer). TASK DETAIL https://phabricator.kde.org/T14471 To: ahmadsamir Cc: ahmadsamir, nicolasfella, kde-frameworks-devel, usta, LeGast00n, cblack, michaelh, ngraham, bruns
T14471: Make Qt 5.15.0 to 5.15.2 for frameworks
usta added a subscriber: ahmadsamir. usta added a comment. @ahmadsamir TASK DETAIL https://phabricator.kde.org/T14471 To: usta Cc: ahmadsamir, nicolasfella, kde-frameworks-devel, usta, LeGast00n, cblack, michaelh, ngraham, bruns
T14471: Make Qt 5.15.0 to 5.15.2 for frameworks
nicolasfella added a comment. Do we actually *want* to use the API that has been introduced in production? From QStringView:: toInt: Note: This method has been added in 5.15.2 to simplify writing code that is portable between Qt 5.15 and Qt 6. The implementation is not tuned for performance in Qt 5. TASK DETAIL https://phabricator.kde.org/T14471 To: nicolasfella Cc: nicolasfella, kde-frameworks-devel, usta, LeGast00n, cblack, michaelh, ngraham, bruns
Re: Any interest in a batch file renamer in KIO?
On Wed, 2021-05-19 at 15:29 +0300, Konstantin Kharlamov wrote: > On Wed, 2021-05-19 at 13:30 +0200, Harald Sitter wrote: > > On Mon, May 17, 2021 at 12:38 PM Nomen Luni wrote: > > > > > > Hi, > > > > > > I actually looked at KRename some time back and it wasn't quite what I > > > wanted. It does actually appear as a service menu option when installed, > > > so it has that base covered, however for my needs it's felt a little > > > unwieldy. My application, whilst no doubt a little less capable feels > > > smaller and more streamlined to operate and dare I say more at a level > > > consistent with the Dolphin ethos in terms of the simplicity of the GUI > > > - I realise this is subjective. If anyone has used the Thunar 'bulk > > > rename' plugin, mine is heavily influenced by the interface of that (but > > > implemented in Qt which was one of the prime reasons for its > > > creation)... so it wasn't a case of 'new code is more fun,' so much as > > > 'this is exactly what I want.' > > > > > > Since KRename already operates as a Dolphin plugin it shouldn't be too > > > much work to integrate it directly into Dolphin, or perhaps even just > > > ship it as a default plugin, however that isn't something I'm interested > > > in working on as I don't use it... benevolent self interest and all that. > > > > > > Dolphin could really benefit from a batch rename function in my opinion, > > > what form that functionality should take, pre-existing or new, is a > > > worthwhile conversation. In any case, Harald's point regarding > > > discoverability is a valid one, as I'm sure a large proportion of users > > > never take the time to investigate the service menu plugins. > > > > My point was more that all the "backendy" bits already exist in > > krename, the discoverability it lends is just bonus. And while I > > completely agree that the current UI is very... eh, advanced... you > > could simply stick another simplistic UI on top, or rework the default > > appearance of krename so it is simpler by default and powerful when > > needed. The way I see it krename could definitely become more > > appealing to potential users by being simpler, and at the same time if > > you invest UI engineering into krename you don't have to worry about > > any of the logic behind renaming in of itself since that already > > exists and is QA'd. > > > > HS > > My point on discoverability was that a person more likely to question "Hmm, > what plugins do I have in Dolphin" and find out this plugin, rather than "Hmm, > what can I use to rename a bunch of files", in which case they need to use > search engine, and after they did it, they'll most likely get a bunch of bash > solutions. KRename won't be one of them unless they specifically search for > "KDE file rename tools". > > So in that sense, discoverability of a plugin is higher than that of a stand- > alone app. To clarify: this of course implies the plugin would be included by default with Dolphin. Otherwise indeed, there's no difference in discoverability compared to KRename
Re: Any interest in a batch file renamer in KIO?
No worries! On Wed, 2021-05-19 at 13:27 +0100, Nomen Luni wrote: > P.S. Apologies - I believe the point regarding discoverability may have > been Konstantin's. > > On 19/05/2021 12:30, Harald Sitter wrote: > > On Mon, May 17, 2021 at 12:38 PM Nomen Luni wrote: > > > Hi, > > > > > > I actually looked at KRename some time back and it wasn't quite what I > > > wanted. It does actually appear as a service menu option when installed, > > > so it has that base covered, however for my needs it's felt a little > > > unwieldy. My application, whilst no doubt a little less capable feels > > > smaller and more streamlined to operate and dare I say more at a level > > > consistent with the Dolphin ethos in terms of the simplicity of the GUI > > > - I realise this is subjective. If anyone has used the Thunar 'bulk > > > rename' plugin, mine is heavily influenced by the interface of that (but > > > implemented in Qt which was one of the prime reasons for its > > > creation)... so it wasn't a case of 'new code is more fun,' so much as > > > 'this is exactly what I want.' > > > > > > Since KRename already operates as a Dolphin plugin it shouldn't be too > > > much work to integrate it directly into Dolphin, or perhaps even just > > > ship it as a default plugin, however that isn't something I'm interested > > > in working on as I don't use it... benevolent self interest and all that. > > > > > > Dolphin could really benefit from a batch rename function in my opinion, > > > what form that functionality should take, pre-existing or new, is a > > > worthwhile conversation. In any case, Harald's point regarding > > > discoverability is a valid one, as I'm sure a large proportion of users > > > never take the time to investigate the service menu plugins. > > My point was more that all the "backendy" bits already exist in > > krename, the discoverability it lends is just bonus. And while I > > completely agree that the current UI is very... eh, advanced... you > > could simply stick another simplistic UI on top, or rework the default > > appearance of krename so it is simpler by default and powerful when > > needed. The way I see it krename could definitely become more > > appealing to potential users by being simpler, and at the same time if > > you invest UI engineering into krename you don't have to worry about > > any of the logic behind renaming in of itself since that already > > exists and is QA'd. > > > > HS
Re: Any interest in a batch file renamer in KIO?
On Wed, 2021-05-19 at 13:30 +0200, Harald Sitter wrote: > On Mon, May 17, 2021 at 12:38 PM Nomen Luni wrote: > > > > Hi, > > > > I actually looked at KRename some time back and it wasn't quite what I > > wanted. It does actually appear as a service menu option when installed, > > so it has that base covered, however for my needs it's felt a little > > unwieldy. My application, whilst no doubt a little less capable feels > > smaller and more streamlined to operate and dare I say more at a level > > consistent with the Dolphin ethos in terms of the simplicity of the GUI > > - I realise this is subjective. If anyone has used the Thunar 'bulk > > rename' plugin, mine is heavily influenced by the interface of that (but > > implemented in Qt which was one of the prime reasons for its > > creation)... so it wasn't a case of 'new code is more fun,' so much as > > 'this is exactly what I want.' > > > > Since KRename already operates as a Dolphin plugin it shouldn't be too > > much work to integrate it directly into Dolphin, or perhaps even just > > ship it as a default plugin, however that isn't something I'm interested > > in working on as I don't use it... benevolent self interest and all that. > > > > Dolphin could really benefit from a batch rename function in my opinion, > > what form that functionality should take, pre-existing or new, is a > > worthwhile conversation. In any case, Harald's point regarding > > discoverability is a valid one, as I'm sure a large proportion of users > > never take the time to investigate the service menu plugins. > > My point was more that all the "backendy" bits already exist in > krename, the discoverability it lends is just bonus. And while I > completely agree that the current UI is very... eh, advanced... you > could simply stick another simplistic UI on top, or rework the default > appearance of krename so it is simpler by default and powerful when > needed. The way I see it krename could definitely become more > appealing to potential users by being simpler, and at the same time if > you invest UI engineering into krename you don't have to worry about > any of the logic behind renaming in of itself since that already > exists and is QA'd. > > HS My point on discoverability was that a person more likely to question "Hmm, what plugins do I have in Dolphin" and find out this plugin, rather than "Hmm, what can I use to rename a bunch of files", in which case they need to use search engine, and after they did it, they'll most likely get a bunch of bash solutions. KRename won't be one of them unless they specifically search for "KDE file rename tools". So in that sense, discoverability of a plugin is higher than that of a stand-alone app.
Re: Any interest in a batch file renamer in KIO?
P.S. Apologies - I believe the point regarding discoverability may have been Konstantin's. On 19/05/2021 12:30, Harald Sitter wrote: On Mon, May 17, 2021 at 12:38 PM Nomen Luni wrote: Hi, I actually looked at KRename some time back and it wasn't quite what I wanted. It does actually appear as a service menu option when installed, so it has that base covered, however for my needs it's felt a little unwieldy. My application, whilst no doubt a little less capable feels smaller and more streamlined to operate and dare I say more at a level consistent with the Dolphin ethos in terms of the simplicity of the GUI - I realise this is subjective. If anyone has used the Thunar 'bulk rename' plugin, mine is heavily influenced by the interface of that (but implemented in Qt which was one of the prime reasons for its creation)... so it wasn't a case of 'new code is more fun,' so much as 'this is exactly what I want.' Since KRename already operates as a Dolphin plugin it shouldn't be too much work to integrate it directly into Dolphin, or perhaps even just ship it as a default plugin, however that isn't something I'm interested in working on as I don't use it... benevolent self interest and all that. Dolphin could really benefit from a batch rename function in my opinion, what form that functionality should take, pre-existing or new, is a worthwhile conversation. In any case, Harald's point regarding discoverability is a valid one, as I'm sure a large proportion of users never take the time to investigate the service menu plugins. My point was more that all the "backendy" bits already exist in krename, the discoverability it lends is just bonus. And while I completely agree that the current UI is very... eh, advanced... you could simply stick another simplistic UI on top, or rework the default appearance of krename so it is simpler by default and powerful when needed. The way I see it krename could definitely become more appealing to potential users by being simpler, and at the same time if you invest UI engineering into krename you don't have to worry about any of the logic behind renaming in of itself since that already exists and is QA'd. HS
Re: Any interest in a batch file renamer in KIO?
Point taken. I guess the moral of the story here is I should have got in touch before building my application. On 19/05/2021 12:30, Harald Sitter wrote: other simplistic UI on top, or rework the default appearance of krename so it is simpler by default and powerful when needed. The way I see it krename could definitely become more appealing to potential users by being simpler, and at the same time if you invest UI engineering into krename you don't have to worry about any of the logic behind renaming in of itself since that already exists and is QA'd.
Re: Any interest in a batch file renamer in KIO?
On Mon, May 17, 2021 at 12:38 PM Nomen Luni wrote: > > Hi, > > I actually looked at KRename some time back and it wasn't quite what I > wanted. It does actually appear as a service menu option when installed, > so it has that base covered, however for my needs it's felt a little > unwieldy. My application, whilst no doubt a little less capable feels > smaller and more streamlined to operate and dare I say more at a level > consistent with the Dolphin ethos in terms of the simplicity of the GUI > - I realise this is subjective. If anyone has used the Thunar 'bulk > rename' plugin, mine is heavily influenced by the interface of that (but > implemented in Qt which was one of the prime reasons for its > creation)... so it wasn't a case of 'new code is more fun,' so much as > 'this is exactly what I want.' > > Since KRename already operates as a Dolphin plugin it shouldn't be too > much work to integrate it directly into Dolphin, or perhaps even just > ship it as a default plugin, however that isn't something I'm interested > in working on as I don't use it... benevolent self interest and all that. > > Dolphin could really benefit from a batch rename function in my opinion, > what form that functionality should take, pre-existing or new, is a > worthwhile conversation. In any case, Harald's point regarding > discoverability is a valid one, as I'm sure a large proportion of users > never take the time to investigate the service menu plugins. My point was more that all the "backendy" bits already exist in krename, the discoverability it lends is just bonus. And while I completely agree that the current UI is very... eh, advanced... you could simply stick another simplistic UI on top, or rework the default appearance of krename so it is simpler by default and powerful when needed. The way I see it krename could definitely become more appealing to potential users by being simpler, and at the same time if you invest UI engineering into krename you don't have to worry about any of the logic behind renaming in of itself since that already exists and is QA'd. HS
