Re: KDEReview: Nepomuk-Controller QML
I guess which icons are shown in the system tray is a setting of the system tray applet, no? Yes but I have now a proper plasma update script, so this issue should be solved now. The script will be installed by default so any user should be updated correctly
Re: KDEReview: Nepomuk-Controller QML
I'd say the Messages.sh pot filename are wrong for both the dataengine and the applet. Please confirm with the plasma developers what's the catalog name that will be loaded but yours doesn't seem to follow the pattern. I see, the i18n techbase article says every qml app needs plasma_applet_ infront of the pot filename same for DataEngine and plasma_engine. I've changed the Messages.sh and some related problems. Thanks for the Hint.
Re: KDEReview: Nepomuk-Controller QML
On Wednesday, 2013-03-27, Jörg Ehrichs wrote: Assuming this setting is stored in some KConfig based file, wouldn't it be possible to migrate it using kconf_update? Good question. The config is saved in plasma-desktop-appletsrc and I need to add: [Containments][3][Applets][25][Configuration][Applets][36] geometry=0,0,24,24 immutability=1 plugin=nepomukcontroller-qml zvalue=0 it seems the old nepomuk controller did not save to this file instead if this program will be removed from the system it won't start. Have to explicitly start it via $ nepomukcontroller to start it here I guess which icons are shown in the system tray is a setting of the system tray applet, no? Cheers, Kevin -- Kevin Krammer, KDE developer, xdg-utils developer KDE user support, developer mentoring signature.asc Description: This is a digitally signed message part.
Re: KDEReview: Nepomuk-Controller QML
Assuming this setting is stored in some KConfig based file, wouldn't it be possible to migrate it using kconf_update? Good question. The config is saved in plasma-desktop-appletsrc and I need to add: [Containments][3][Applets][25][Configuration][Applets][36] geometry=0,0,24,24 immutability=1 plugin=nepomukcontroller-qml zvalue=0 it seems the old nepomuk controller did not save to this file instead if this program will be removed from the system it won't start. Have to explicitly start it via $ nepomukcontroller to start it here
Re: KDEReview: Nepomuk-Controller QML
The minor version upgrade process all throughout the KDE/Plasma 4 releases started off as a fairly steady source of minor nits and irritants for users. The Nepomuk controls themselves are already fairly well-known so it's even more important IMO that if they are deprecated that they don't simply disappear completely the first time a new KDE 4.11 user logs in. That is true, I do hope though to increase the awareness of what Nepomuk does in the background by exposing not just the fileindexer but also especially the workload the pim indexer is doing. While the look and feel of the systray will be completely different it is mostly an improvement of the currently rather hidden dialog that comes up. One detail though is missing, the old systray was able give a number of indexer file resources. This number is missing from my QML approach. Not sure how important this number is, as it isn't really a good measure or even a measure at all how big the Nepomuk database is at all. Likewise it would be a good idea to ensure our Release Notes for 4.11 (if any are started) reflect the migration so that our packagers can ensure they change package dependencies if deemed appropriate. I would write a blogpost about this, as soon as this goes into SC. IS there any other action I need to do to ensure packagers are aware of the change? The current nepomukcontroller is enabled in the systray (right click on the systray-settings-enable additional entries) this step must be done for the new nepomuk controller to allow a seamingless transition. Not trying to discourage, but just some things to think about. Don't worry, exactly these kind of thoughts are why the review process exist. I'd rather have overly worrying reviewers than being responsible for an unpleasant transition due to my change. Kind Regards, Joerg
Re: KDEReview: Nepomuk-Controller QML
On Tuesday, March 26, 2013 11:42:46 Jörg Ehrichs wrote: One detail though is missing, the old systray was able give a number of indexer file resources. This number is missing from my QML approach. Not sure how important this number is, as it isn't really a good measure or even a measure at all how big the Nepomuk database is at all. Well we rearrange U/I even across point releases (if it fixes bugs) so merely removing a useless stat is not a big concern, as long as the overall functionality is still comparable to what was present before. Removing the number might even be judged as a U/I improvement (why show something neither the user nor developer will need except possibly for bug triage?). Likewise it would be a good idea to ensure our Release Notes for 4.11 (if any are started) reflect the migration so that our packagers can ensure they change package dependencies if deemed appropriate. I would write a blogpost about this, as soon as this goes into SC. IS there any other action I need to do to ensure packagers are aware of the change? The release notes is the big thing, I would expect packagers are tracking that Wiki page or web page as they are put together during the release series so that they can make preparations ahead-of-time. The only other thing you'd want to do is to send an email to the kde-packager mailing list informing them of the change and any action that might be needed or desirable on their part to ensure a smooth transition for their users. The mailing list is moderated so expect that; your message will make it through regardless for this topic. Regards, - Michael Pyne signature.asc Description: This is a digitally signed message part.
Re: KDEReview: Nepomuk-Controller QML
On Sat, Mar 23, 2013 at 8:12 PM, Jörg Ehrichs joerg.ehri...@gmx.de wrote: So after a first introduction in plasma, I like to get this thing into SC. The Nepomuk-Controller aims to replace the current system tray Nepomuk applet. This one allows to suspend/resume and show information for all the indexers, thus this gives any user a small hint what happens in the background and allow them to suspend it, if they need to. For the review I have pushed the branch nepomukcontroller-qml into kde-workspace. You can find the important parts at plasma/generic/dataengines/nepomuk plasma/generic/applet/nepomuk-controller The dataengine as well as the applet is only installed if Nepomuk-Core/Soprano is found as build dependency. This would deprecate: kde-runtime/nepomuk/controller/ Deprecate or remove? Cause I would like to remove it. and need current nepomuk-core master For an easy to install version there is also: http://quickgit.kde.org/?p=scratch/jehrichs/nepomukcontroller-qml.git Some Pictures: http://wstaw.org/m/2013/03/20/nepomukcontroller-qml1.jpg http://wstaw.org/m/2013/03/20/nepomukcontroller-qml2.jpg http://wstaw.org/m/2013/03/20/nepomukcontroller-qml3.jpg http://wstaw.org/m/2013/03/20/nepomukcontroller-qml4.jpg Any help/comments are welcome. Since my first mail on the plasma devel list, the dbus calls are asynchrone now, the FileWatch service is not shown on default, but can be enabled if the user wants, and the licence should be fine now. Kind Regards Joerg -- Vishesh Handa
Re: KDEReview: Nepomuk-Controller QML
On Monday, March 25, 2013 16:46:10 Vishesh Handa wrote: On Sat, Mar 23, 2013 at 8:12 PM, Jörg Ehrichs joerg.ehri...@gmx.de wrote: The dataengine as well as the applet is only installed if Nepomuk-Core/Soprano is found as build dependency. This would deprecate: kde-runtime/nepomuk/controller/ Deprecate or remove? Cause I would like to remove it. What will the provision be to automatically replace the old systray program with the applet (or at least let the user know where to add the new applet from)? The minor version upgrade process all throughout the KDE/Plasma 4 releases started off as a fairly steady source of minor nits and irritants for users. The Nepomuk controls themselves are already fairly well-known so it's even more important IMO that if they are deprecated that they don't simply disappear completely the first time a new KDE 4.11 user logs in. Likewise it would be a good idea to ensure our Release Notes for 4.11 (if any are started) reflect the migration so that our packagers can ensure they change package dependencies if deemed appropriate. Not trying to discourage, but just some things to think about. Regards, - Michael Pyne signature.asc Description: This is a digitally signed message part.
KDEReview: Nepomuk-Controller QML
So after a first introduction in plasma, I like to get this thing into SC. The Nepomuk-Controller aims to replace the current system tray Nepomuk applet. This one allows to suspend/resume and show information for all the indexers, thus this gives any user a small hint what happens in the background and allow them to suspend it, if they need to. For the review I have pushed the branch nepomukcontroller-qml into kde-workspace. You can find the important parts at plasma/generic/dataengines/nepomuk plasma/generic/applet/nepomuk-controller The dataengine as well as the applet is only installed if Nepomuk-Core/Soprano is found as build dependency. This would deprecate: kde-runtime/nepomuk/controller/ and need current nepomuk-core master For an easy to install version there is also: http://quickgit.kde.org/?p=scratch/jehrichs/nepomukcontroller-qml.git Some Pictures: http://wstaw.org/m/2013/03/20/nepomukcontroller-qml1.jpg http://wstaw.org/m/2013/03/20/nepomukcontroller-qml2.jpg http://wstaw.org/m/2013/03/20/nepomukcontroller-qml3.jpg http://wstaw.org/m/2013/03/20/nepomukcontroller-qml4.jpg Any help/comments are welcome. Since my first mail on the plasma devel list, the dbus calls are asynchrone now, the FileWatch service is not shown on default, but can be enabled if the user wants, and the licence should be fine now. Kind Regards Joerg
Re: KDEReview: Nepomuk-Controller QML
El Dissabte, 23 de març de 2013, a les 15:42:33, Jörg Ehrichs va escriure: So after a first introduction in plasma, I like to get this thing into SC. The Nepomuk-Controller aims to replace the current system tray Nepomuk applet. This one allows to suspend/resume and show information for all the indexers, thus this gives any user a small hint what happens in the background and allow them to suspend it, if they need to. For the review I have pushed the branch nepomukcontroller-qml into kde-workspace. Why workspace when you are deprecating something in runtime? Cheers, Albert
Re: KDEReview: Nepomuk-Controller QML
Why workspace when you are deprecating something in runtime? All other Plasma::DataEngines and applets (battery, network) are in workspace too. While runtime/plasma has only some generic stuff. So in general it felt like the better place. In addition I think this service info tool is not a runtime dependency, like the KCM, kioslaves for nepomuk and the systray seemed to have ended in runtime only, because it got added there all together. Regards, Joerg
