Well, when I was in the process of writing (and still am), a hdd activity (I/O) applet, I ran into some crazy shit that it does.
For instance, did you know that on sourceRemoved or sourceAdded, it clears the entire connected sources, removes the applet layout entirely, then reloads all of the sources based on a Regular Expression, then recreates every visualization (== graph in the widget...and there can be n number of graphs in 1 widget). Anyone else find that silly? So I figured "okay, after I'm done with this...I'll have to rewrite the system monitor applets to do something sane". But then I couldn't get the idea out of my head of porting these applets to QML ;-) I noticed it's on the "To port to QML" wiki page, but do you guys recommend this? What benefits would it give me, other than being QML. Wonder how hard it'll be to get the graphing visualization...not sure on how to do that in QML... I'm so tempted to do so, after my other not-too-big projects..Thoughts? :) -- Shaun Reich, KDE Software Developer (kde.org) _______________________________________________ Plasma-devel mailing list Plasma-devel@kde.org https://mail.kde.org/mailman/listinfo/plasma-devel
