Re: QML device notifier
Hi all, it is merge now. the device notifier is now 100% qml. the feature set and the look should be a nearly exact replica... please test ;) Cheers, Marco Martin ___ Plasma-devel mailing list Plasma-devel@kde.org https://mail.kde.org/mailman/listinfo/plasma-devel
Re: QML device notifier
On Sun, Oct 30, 2011 at 10:03 PM, Marco Martin notm...@gmail.com wrote: the system kcms is the only detail still missing :p after this is in, i'll merge it's in! commit: http://commits.kde.org/kdelibs/f53ef3872b3755350ca5eb99eea8ef3b96dd8c74 pushed to kdelibs KDE/4.7 branch -- Marco Martin ___ Plasma-devel mailing list Plasma-devel@kde.org https://mail.kde.org/mailman/listinfo/plasma-devel ___ Plasma-devel mailing list Plasma-devel@kde.org https://mail.kde.org/mailman/listinfo/plasma-devel
Re: QML device notifier
On Tuesday 25 October 2011, Aaron J. Seigo wrote: On Tuesday, October 25, 2011 16:14:39 Marco Martin wrote: - scrollbar: for this it will depend from qtcomponents, they are in kde- runtime master for now, will still really rather move them in their own repository (and for me, they are 100% needed for active two) if they are in kde-runtime master, then they should be usable already for a plasmoid in kde-workspace master? so the repository location becomes a non- relevant detail for using them in the new plasmoid? - devices global kcm: aaron had a patch for this for enabling global kcms in qml plasmoids, it should really go in. ah, right. i'll have to find that one and put it into master... i'll do so asap (though not today) ok, now the device notifier is almost perfect and good to go (tm) almost pixel perfect identical but there are several little smoothness details that make it look and behave much better the system kcms is the only detail still missing :p after this is in, i'll merge -- Marco Martin ___ Plasma-devel mailing list Plasma-devel@kde.org https://mail.kde.org/mailman/listinfo/plasma-devel
Re: QML device notifier
On Tuesday, October 25, 2011 16:14:39 Marco Martin wrote: - scrollbar: for this it will depend from qtcomponents, they are in kde- runtime master for now, will still really rather move them in their own repository (and for me, they are 100% needed for active two) if they are in kde-runtime master, then they should be usable already for a plasmoid in kde-workspace master? so the repository location becomes a non- relevant detail for using them in the new plasmoid? - devices global kcm: aaron had a patch for this for enabling global kcms in qml plasmoids, it should really go in. ah, right. i'll have to find that one and put it into master... i'll do so asap (though not today) a reason is *very* important for me is the additions in the dataengine, that makes it actually usable from pure qml (mount/unmount service, tells if is removable or not) are they just additions, or did other things change which would make current users of the DataEngine potentially break with these changes applied? iow: is it backwards compatible? it is vital to have those functions for plasma active two since the image viewer now uses an horrible hack to actually list just the removable devices (and will be as well if a generic resource explorer will be started) so, that said, i would risk to merge it for 4.8 let's start with this one and see how it goes ... maybe attempting merging the battery applet as well ... and if it turns out well then lets target this one next. these are key pieces of the UI so i'm erring on the side of conservative here :) great to see these pieces coming together! -- Aaron J. Seigo humru othro a kohnu se GPG Fingerprint: 8B8B 2209 0C6F 7C47 B1EA EE75 D6B7 2EB1 A7F1 DB43 KDE core developer sponsored by Qt Development Frameworks signature.asc Description: This is a digitally signed message part. ___ Plasma-devel mailing list Plasma-devel@kde.org https://mail.kde.org/mailman/listinfo/plasma-devel
Re: QML device notifier
On Tuesday 25 October 2011, Aaron J. Seigo wrote: On Tuesday, October 25, 2011 16:14:39 Marco Martin wrote: - scrollbar: for this it will depend from qtcomponents, they are in kde- runtime master for now, will still really rather move them in their own repository (and for me, they are 100% needed for active two) if they are in kde-runtime master, then they should be usable already for a plasmoid in kde-workspace master? so the repository location becomes a non- relevant detail for using them in the new plasmoid? yep, it is the key question is, will be possible to use 4.8 for active two? for that perion it would be not released, but at elast frozen - devices global kcm: aaron had a patch for this for enabling global kcms in qml plasmoids, it should really go in. ah, right. i'll have to find that one and put it into master... i'll do so asap (though not today) :D a reason is *very* important for me is the additions in the dataengine, that makes it actually usable from pure qml (mount/unmount service, tells if is removable or not) are they just additions, or did other things change which would make current users of the DataEngine potentially break with these changes applied? iow: is it backwards compatible? yep, purely extra stuff, all the old keys are unchanged it is vital to have those functions for plasma active two since the image viewer now uses an horrible hack to actually list just the removable devices (and will be as well if a generic resource explorer will be started) so, that said, i would risk to merge it for 4.8 let's start with this one and see how it goes ... ok, after adding the last 2 missing things i'll merge and let's see how it goes maybe attempting merging the battery applet as well ... and if it turns out well then lets target this one next. these are key pieces of the UI so i'm erring on the side of conservative here :) great to see these pieces coming together! yeah, let's try with just this one for 4.8, the battery could be merged at the beginning of 4.9, so plenty of time to fix things up -- Marco Martin ___ Plasma-devel mailing list Plasma-devel@kde.org https://mail.kde.org/mailman/listinfo/plasma-devel
Re: QML device notifier
On Tuesday, October 25, 2011 18:54:34 Marco Martin wrote: On Tuesday 25 October 2011, Aaron J. Seigo wrote: On Tuesday, October 25, 2011 16:14:39 Marco Martin wrote: - scrollbar: for this it will depend from qtcomponents, they are in kde- runtime master for now, will still really rather move them in their own repository (and for me, they are 100% needed for active two) if they are in kde-runtime master, then they should be usable already for a plasmoid in kde-workspace master? so the repository location becomes a non- relevant detail for using them in the new plasmoid? yep, it is the key question is, will be possible to use 4.8 for active two? for that perion it would be not released, but at elast frozen Nope, not if we don't want to depend on a development snapshot. PA3 is the first version that can (without patching packages) depend on 4.8 :/ PA2 will be out before 4.8 ... -- sebas http://www.kde.org | http://vizZzion.org | GPG Key ID: 9119 0EF9 ___ Plasma-devel mailing list Plasma-devel@kde.org https://mail.kde.org/mailman/listinfo/plasma-devel
Re: QML device notifier
On Tuesday 25 October 2011, Sebastian Kügler wrote: Nope, not if we don't want to depend on a development snapshot. PA3 is the first version that can (without patching packages) depend on 4.8 :/ PA2 will be out before 4.8 ... hm, not sure what of those two things will cause more trouble... one thing i really want for active2 are the qtcomponents, is areeady an improvement so big compared to the old widgets, especially there and is a shame not being able to use them.. for the dataengine we can get around using yet another diff... for the components, what i was thinking is that since will probably be needed anyways to have a mobile specific version, said version could be done directly in the plasma-mobile repo and ship only that one for active2 Cheers, Marco Martin ___ Plasma-devel mailing list Plasma-devel@kde.org https://mail.kde.org/mailman/listinfo/plasma-devel
