Re: Plasmoid activation signal
On Monday 19 October 2009 21:23:13 Aaron J. Seigo wrote: hi Matteo .. please keep plasma issues on this list; cross-posting to kde-devel will just make it more confusing to follow the resulting thread(s) :) On October 19, 2009, Matteo Agostinelli wrote: So my question is if there already is a signal that is emitted when either of the previously stated action is triggered. Or should I override some protected method (in that case, please give me a hint). A possible candidate seems this signal: void newStatus (Plasma::ItemStatus status) but this has been introduced in 4.4 and I would like to make this work also in 4.3 if possible. Any suggestions? focusInEvent? Yep, this partially solved the problem. Partially because if the plasmoid is activated by the keyboard shortcut it seems that this function is not called. I had to add a connect to the activate() signal of the plasmoid to solve this problem. Now everything is working fine. Thanks, Matteo ___ Plasma-devel mailing list Plasma-devel@kde.org https://mail.kde.org/mailman/listinfo/plasma-devel
Re: Mini Usability Testing Ideas?
On Monday 19 October 2009, 16:08 Celeste Lyn Paul wrote: I am looking for ideas of small tasks or processes we could test, such as the playlist editing task we did for Amarok. Any ideas are welcome! Maybe do some usability tests with the new Plasma's Add Widgets would be a nice idea ? Cheers, -- Artur Duque de Souza openBossa INdT - Instituto Nokia de Tecnologia -- Blog: http://blog.morpheuz.cc PGP: 0xDBEEAAC3 @ wwwkeys.pgp.net -- 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: Mini Usability Testing Ideas?
On Tue, Oct 20, 2009 at 7:27 AM, Artur Souza (MoRpHeUz) morph...@openbossa.org wrote: On Monday 19 October 2009, 16:08 Celeste Lyn Paul wrote: I am looking for ideas of small tasks or processes we could test, such as the playlist editing task we did for Amarok. Any ideas are welcome! Maybe do some usability tests with the new Plasma's Add Widgets would be a nice idea ? Yes, AnnieC mentioned this on IRC yesterday. It could be part of a Customize Your Desktop activity. Although we wouldnt be able to get any feedback done in time for 4.4, we should be able to test before the February Tokamak. Cheers, -- Artur Duque de Souza openBossa INdT - Instituto Nokia de Tecnologia -- Blog: http://blog.morpheuz.cc PGP: 0xDBEEAAC3 @ wwwkeys.pgp.net -- -- Celeste Lyn Paul KDE Usability Project KDE e.V. Board of Directors www.kde.org ___ Plasma-devel mailing list Plasma-devel@kde.org https://mail.kde.org/mailman/listinfo/plasma-devel
Re: Moved runner Amarok to kdereview
Hello, I would prefer to make it more generic. Done that in the code. If you say that it is ok, I'll change the runner's description and the name (maybe to Control Audio Player?). Does anybody know some MRPIS players so I can add them to the combo box? I made the box editable but I would like to add the most famous players. Thanks. * the runner is not setting any syntaxes; this prevents runtime help from working for this runner. this should be done in reloadConfiguration() Done, too. * amarokRunning() shouldn't be called in every match(); it should be checked once in a method connected to the prepare() signal, probably setting a bool member that can then be checked for in match(). That's done. * caching the values of songsInPlaylist, prevSongAvailable and nextSongAvailable would be a good idea instead of calling them repeatedly in match() I tried this, I'm not sure if I've done it correctly. So one question to this: When is the signal prepare() emitted? * there is this line in match(): searchCollection = config().readEntry(searchCollection, true); //resets searchCollection is it really needed? My memory played a trick on me. It isn't needed, I deleted it. Thanks for your help :) -- Jan Gerrit Marker (jangmarker) ___ Plasma-devel mailing list Plasma-devel@kde.org https://mail.kde.org/mailman/listinfo/plasma-devel
Re: Mini Usability Testing Ideas?
On Monday 19 October 2009, Celeste Lyn Paul wrote: Hi Everyone, I would like to plan another community-based usability test similar to the one I did for Amarok last spring [1]. This time, I am trying to involve my university's LUG and will have access to a usability lab. Depending on how well I can organize this new group, we would like to try a test later this year (end of November/beg Dec) or early next year (~ Feb). I am looking for ideas of small tasks or processes we could test, such as the playlist editing task we did for Amarok. Any ideas are welcome! ~ Celeste [1] http://www.obso1337.org/2009/amarok-playlist-usability-testing/ something on the netbook thing? (basic operations like starting apps, adding widget, switching windows, since they are quite different from the usual..) -- Marco Martin ___ Plasma-devel mailing list Plasma-devel@kde.org https://mail.kde.org/mailman/listinfo/plasma-devel
Re: Moved runner Amarok to kdereview
On October 20, 2009, Jan Gerrit Marker wrote: Hello, I would prefer to make it more generic. Done that in the code. If you say that it is ok, I'll change the runner's description and the name (maybe to Control Audio Player?). sure. Does anybody know some MRPIS players so I can add them to the combo box? I made the box editable but I would like to add the most famous players. http://wiki.xmms2.xmms.se/wiki/Media_Player_Interfaces#Projects_involved seems there's an add-on for Songbird as well. * caching the values of songsInPlaylist, prevSongAvailable and nextSongAvailable would be a good idea instead of calling them repeatedly in match() I tried this, I'm not sure if I've done it correctly. So one question to this: When is the signal prepare() emitted? before calls to match() start happening (apidox is your friend! :) and yes, looks like you did it correctly ... cool. -- 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: Plasmoid activation signal
On October 20, 2009, Matteo Agostinelli wrote: On Monday 19 October 2009 21:23:13 Aaron J. Seigo wrote: hi Matteo .. please keep plasma issues on this list; cross-posting to kde-devel will just make it more confusing to follow the resulting thread(s) :) On October 19, 2009, Matteo Agostinelli wrote: So my question is if there already is a signal that is emitted when either of the previously stated action is triggered. Or should I override some protected method (in that case, please give me a hint). A possible candidate seems this signal: void newStatus (Plasma::ItemStatus status) but this has been introduced in 4.4 and I would like to make this work also in 4.3 if possible. Any suggestions? focusInEvent? Yep, this partially solved the problem. Partially because if the plasmoid is activated by the keyboard shortcut it seems that this function is not called. I had to add a connect to the activate() signal of the plasmoid to solve this problem. Now everything is working fine. did you implement focusInEvent on your applet, or on the graphicsWidget()? in a popup applet, all the fun actually happens in the graphicsWidget(), not the Applet itself. -- 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: Mini Usability Testing Ideas?
Am Dienstag 20 Oktober 2009 16:30:02 schrieb Parker Coates: Of course, this may be a PITA to test as one wouldn't want to have to wait for the computer to restart between every test. If you kill the X session before it terminates itself, the shutdown will be aborted. Greetings Stefan -- Die Zukunft wird nicht gemeistert von denen, die an der Vergangenheit kleben. 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: Review Request: use QGraphicsOpacityEffect in FadeAnimation
--- This is an automatically generated e-mail. To reply, visit: http://reviewboard.kde.org/r/1860/ --- (Updated 2009-10-20 17:15:16.202552) Review request for Plasma and Adenilson Cavalcanti. Changes --- deletes private class in destructor updated to the last rev AbstractAnimation::AbstractAnimation() sets d-animObject to 0 Summary --- This little patch makes the FadeAnimation use QGraphicsOpacityEffect instead of setting the opacity directly on the widget. This solves a graphical glitch with Plasma::Label. Diffs (updated) - /trunk/KDE/kdelibs/plasma/animations/abstractanimation.cpp 1038071 /trunk/KDE/kdelibs/plasma/animations/fade.h 1038071 /trunk/KDE/kdelibs/plasma/animations/fade.cpp 1038071 Diff: http://reviewboard.kde.org/r/1860/diff Testing --- tested, works Thanks, Giulio ___ Plasma-devel mailing list Plasma-devel@kde.org https://mail.kde.org/mailman/listinfo/plasma-devel
Grouping support in containments
Hi plasma devs! Some of you may know recently i've tried in many ways to group applets visually inside the containment. I tried to embed applets in applets but it brought many problems, then containment in qgraphicsproxywidget in applet in containment but it brought other problems. Then i started working with an other approach: i wrote a subclass of Plasma::Applet, AbstractGroup, that is the base class for all the GroupApplets. it has some functions such as - assignApplet(Plasma::Applet) - layoutApplet(Plasma::Applet) - saveAppletLayoutInfo(Plasma::Applet *applet, const KConfigGroup group) - restoreAppletLayoutInfo(Plasma::Applet *applet, const KConfigGroup group) Then i created a desktop containment and reimplemented some things: - when an applet is added it checks if its pos() is contained in some group geometry() and in the case it calls group-assignApplet(applet) - reimplemented saveContents so that for each applet if it is managed by a group it saves an entry Group=group_id in the applet's config and calls group-saveAppletLayoutInfo(applet, kconfiggroup) - reimplemented restoreContents so that it reads the Group entry and calls group-assignAppelt(applet) and group-restoreAppletLayoutInfo(applet, kconfiggroup) in saveAppletLayoutInfo the group creates a KConfigGroup (that is [Applets][id] [GroupInformation]) and inside it it writes config specified to that one group. so, e.g, i wrote a grid group so it saves row and column, but one could write a stack group so it saves the index. restoreAppletLayoutInfo obviously does the contrary. the configuration of a group is saved under [Containment][id][Groups][id], so that the containment doesn't risk to confuse between groups and simple applets. Now i hope i've explained myself and i'm asking you: what should i do with this? I was thinking between two possibilities: should i merge this with Plasma::Containment? Please note that the containment doesn't know *anything* about how the groups manage the applets inside them. it knows only if they are grouped and, in the case, the id of their group. nor the applets knows anything about how they are arranged. It is all done internally in the groups. Or should i write a subclass of Containment that has group support so one could use this to write a desktop or panel with grouping support? I'd aim at the first one choice, because it would add little more complexity in the containment code but, on the other hand, all the containments would have this support for free. you can find the code in playground/base/plasma/containments/groupingdesktop/ What do you think? Giulio. ___ Plasma-devel mailing list Plasma-devel@kde.org https://mail.kde.org/mailman/listinfo/plasma-devel
Re: Moved runner Amarok to kdereview
Am Dienstag 20 Oktober 2009 18:26:32 schrieb Aaron J. Seigo: Done that in the code. If you say that it is ok, I'll change the runner's description and the name (maybe to Control Audio Player?). sure. Ok, I changed everything. I would be very pleased if you would have a look at it cause I did a mistake (rm -rf ~ instead of rm -rf ~) which made me very confused therefore I don't know how many other mistakes I did :( Does anybody know some MRPIS players so I can add them to the combo box? I made the box editable but I would like to add the most famous players. http://wiki.xmms2.xmms.se/wiki/Media_Player_Interfaces#Projects_involved seems there's an add-on for Songbird as well. Mh, my VLC (which is listed there) doesn't provide a D-Bus module :(. I didn't add another application now. Thanks for the link. before calls to match() start happening (apidox is your friend! :) Didn't thought of the API doc, sorry and yes, looks like you did it correctly ... cool. Great :) Thanks a lot for the help again :) -- Jan Gerrit Marker (jangmarker) ___ Plasma-devel mailing list Plasma-devel@kde.org https://mail.kde.org/mailman/listinfo/plasma-devel
Re: OT: Thanks!
On 20/10-2009 20:16 Chani chan...@gmail.com wrote: About the name confusion: are there any reasons for Plasmoids also being referred to as Applets and Widgets? Widgets is a specially confusing term as at least I think of Qt Widgets when used. Widget = any sort of little doodad you can add to your desktop. plasmoids, google gadgets, osx dashboard widgets, etc... that group of things seemed to already have widget as the most common name before plasma came along. Plasmoid = a plasma-specific widget. Applet = the class within libplasma that all plasmoids inherit. Thanks Chani. I think I wasn't being clear in what I wrote. What I meant was that reading through documentation, tutorials etc. about creating *Plasmoids* the terms seems to be used rather randomly. -- Best Regards / Med venlig hilsen Thomas Olsen ___ Plasma-devel mailing list Plasma-devel@kde.org https://mail.kde.org/mailman/listinfo/plasma-devel
Re: OT: Thanks!
Thanks Chani. I think I wasn't being clear in what I wrote. What I meant was that reading through documentation, tutorials etc. about creating *Plasmoids* the terms seems to be used rather randomly. they're on the techbase wiki, right? you could fix them :) -- This message brought to you by eevil bananas and the number 3. www.chani3.com 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: OT: Thanks!
On 20/10-2009 22:03 Chani chan...@gmail.com wrote: Thanks Chani. I think I wasn't being clear in what I wrote. What I meant was that reading through documentation, tutorials etc. about creating *Plasmoids* the terms seems to be used rather randomly. they're on the techbase wiki, right? you could fix them :) You're right. I just struck my self out :-) I'll try to be better at contributing to techbase. My only excuse is that I'm still in an early learning phase and a bit careful about not writing anything faulty. And my English is bad ;-) -- Best Regards / Med venlig hilsen Thomas Olsen ___ Plasma-devel mailing list Plasma-devel@kde.org https://mail.kde.org/mailman/listinfo/plasma-devel
