Re: KDE MicroBlog (Twitter) update doesn't work
You're right, it works now again also for me. I didn't expect such a simple bug in the applet ;-) Thx. On Wednesday 29 July 2009 14:52:40 Ryan P. Bitanga wrote: It had nothing to do with the dataengine or anywhere in the service framework. Someone accidentally commented out a line in the applet. I committed the fix. checkout r1004151 of the applet. On Wed, Jul 29, 2009 at 8:01 PM, Ryan P. Bitangaryan.bita...@gmail.com wrote: On Wed, Jul 29, 2009 at 6:41 PM, Gerhard Gappmeiergerhard.gappme...@ascolab.com wrote: No, I'm directly connected to the Internet, no proxy. Receiving messages works. Have you tested with Twitter, or with identica? I tested both before but I svn up'd to 1003809 and compiled everything just now and I'm getting the same problem. Since the dataengine hasn't changed since I last successfully tested it, you could be right that it's a problem elsewhere. May there be any other side effects with changes in the service framework, twitter API, or just configuration files for twitter, that may corrupt things? If you tell me where the configuration is stored, I could delete this files, and recreate my µBlog configuration. - Ryan ___ Plasma-devel mailing list Plasma-devel@kde.org https://mail.kde.org/mailman/listinfo/plasma-devel 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: Issues with setupMatchSession/matchSessionComplete in RunnerManager
On Thu, Jul 30, 2009 at 9:28 AM, Aaron J. Seigoase...@kde.org wrote: On Wednesday 29 July 2009, Ryan P. Bitanga wrote: On Thu, Jul 30, 2009 at 2:04 AM, Aaron J. Seigoase...@kde.org wrote: On Wednesday 29 July 2009, Ryan P. Bitanga wrote: On Thu, Jul 30, 2009 at 12:43 AM, Aaron J. Seigoase...@kde.org wrote: On Wednesday 29 July 2009, Ryan P. Bitanga wrote: so I think the best place to do this would be in the destructor of FindMatchesJob. We'd check if the queue is empty, and if it is then we can emit the teardown signal. there'd be some corner cases there, such as if there are no FindMatchesJobs when teardown is requested ... how about in RunnerManagerPrivate::jobDone()? see attached patch... I like the fact that this keeps everything in RunnerManager instead of having the logic separated between files. Doesn't this suffer from the same problem though? If there are no jobs to begin with, the slot won't be called. that's why there's a call to checkTearDown() in RunnerManager::matchSessionComplete(). if there are no jobs running, checkTearDown() will run immediately. otherwise, it will wait until the jobs are all done. Oh right... :) In that case apart from not removing the checkTeardown call in reset I think the patch is good to go. Agreed, but the use case that came to mind while I was writing this e-mail is that of the window runner. It caches the data once a query is launched but the data may become invalid while the dialog is open (e.g. an application is launched/closed while the dialog is open). But this is an issue addressable in the runner implementation. yes; in this case the setup/teardown lets the runner know that it should start watching for those changes as well. if the data can't be trusted between runs (meaning that there is no way to detect changes and the data may change) then the runner will have to re-load the data in match no matter what we do :) Just for clarity I think we should put that in the apidocs. :) sure :) - Ryan ___ Plasma-devel mailing list Plasma-devel@kde.org https://mail.kde.org/mailman/listinfo/plasma-devel
Re: Issues with setupMatchSession/matchSessionComplete in RunnerManager
On Thu, Jul 30, 2009 at 11:29 PM, Ryan P. Bitangaryan.bita...@gmail.com wrote: On Thu, Jul 30, 2009 at 9:28 AM, Aaron J. Seigoase...@kde.org wrote: On Wednesday 29 July 2009, Ryan P. Bitanga wrote: On Thu, Jul 30, 2009 at 2:04 AM, Aaron J. Seigoase...@kde.org wrote: On Wednesday 29 July 2009, Ryan P. Bitanga wrote: On Thu, Jul 30, 2009 at 12:43 AM, Aaron J. Seigoase...@kde.org wrote: On Wednesday 29 July 2009, Ryan P. Bitanga wrote: so I think the best place to do this would be in the destructor of FindMatchesJob. We'd check if the queue is empty, and if it is then we can emit the teardown signal. there'd be some corner cases there, such as if there are no FindMatchesJobs when teardown is requested ... how about in RunnerManagerPrivate::jobDone()? see attached patch... I like the fact that this keeps everything in RunnerManager instead of having the logic separated between files. Doesn't this suffer from the same problem though? If there are no jobs to begin with, the slot won't be called. that's why there's a call to checkTearDown() in RunnerManager::matchSessionComplete(). if there are no jobs running, checkTearDown() will run immediately. otherwise, it will wait until the jobs are all done. Oh right... :) In that case apart from not removing the checkTeardown call in reset I think the patch is good to go. I mean removing the checkTeardown call in reset. - Ryan ___ Plasma-devel mailing list Plasma-devel@kde.org https://mail.kde.org/mailman/listinfo/plasma-devel
Review Request: kickoff: Always select Favorites tab when opened
--- This is an automatically generated e-mail. To reply, visit: http://reviewboard.kde.org/r/1164/ --- Review request for Plasma. Summary --- Fix bug 201998 by calling reset() after the launcher origin has been set (so the tabs are in the right order). This bugfix should also apply to trunk as there aren't any additional relevant changes. This addresses bug 201998. https://bugs.kde.org/show_bug.cgi?id=201998 Diffs - branches/KDE/4.3/kdebase/workspace/plasma/applets/kickoff/ui/launcher.cpp 1004485 Diff: http://reviewboard.kde.org/r/1164/diff Testing --- Tested all possible placements of the launcher button. Thanks, Felix ___ Plasma-devel mailing list Plasma-devel@kde.org https://mail.kde.org/mailman/listinfo/plasma-devel
Re: Review Request: kickoff: Always select Favorites tab when opened
--- This is an automatically generated e-mail. To reply, visit: http://reviewboard.kde.org/r/1164/#review1859 --- Ship it! good catch! i don't see your name in the svn commiter's list. do you need someone to commit this for you? - Aaron On 2009-07-30 12:49:11, Felix Geyer wrote: --- This is an automatically generated e-mail. To reply, visit: http://reviewboard.kde.org/r/1164/ --- (Updated 2009-07-30 12:49:11) Review request for Plasma. Summary --- Fix bug 201998 by calling reset() after the launcher origin has been set (so the tabs are in the right order). This bugfix should also apply to trunk as there aren't any additional relevant changes. This addresses bug 201998. https://bugs.kde.org/show_bug.cgi?id=201998 Diffs - branches/KDE/4.3/kdebase/workspace/plasma/applets/kickoff/ui/launcher.cpp 1004485 Diff: http://reviewboard.kde.org/r/1164/diff Testing --- Tested all possible placements of the launcher button. Thanks, Felix ___ Plasma-devel mailing list Plasma-devel@kde.org https://mail.kde.org/mailman/listinfo/plasma-devel
Re: Review Request: kickoff: Always select Favorites tab when opened
On 2009-07-30 18:57:09, Aaron Seigo wrote: good catch! i don't see your name in the svn commiter's list. do you need someone to commit this for you? Yes, I can't commit it myself. - Felix --- This is an automatically generated e-mail. To reply, visit: http://reviewboard.kde.org/r/1164/#review1859 --- On 2009-07-30 12:49:11, Felix Geyer wrote: --- This is an automatically generated e-mail. To reply, visit: http://reviewboard.kde.org/r/1164/ --- (Updated 2009-07-30 12:49:11) Review request for Plasma. Summary --- Fix bug 201998 by calling reset() after the launcher origin has been set (so the tabs are in the right order). This bugfix should also apply to trunk as there aren't any additional relevant changes. This addresses bug 201998. https://bugs.kde.org/show_bug.cgi?id=201998 Diffs - branches/KDE/4.3/kdebase/workspace/plasma/applets/kickoff/ui/launcher.cpp 1004485 Diff: http://reviewboard.kde.org/r/1164/diff Testing --- Tested all possible placements of the launcher button. Thanks, Felix ___ Plasma-devel mailing list Plasma-devel@kde.org https://mail.kde.org/mailman/listinfo/plasma-devel
tokamak planning
hi all .. with tokamak getting closer, i'd like to start working on the content part of the planning for it. on the T3 page on Techbase there's the Topics section: http://techbase.kde.org/Projects/Plasma/Tokamak3#Topics it would be good if every attendee could put down a presentation topic for our Day 1 Presentations. for the SoC students, that's probably very easy: present on your project ;) but you can present, really, on whatever you want. they aren't long presentations as we should fit them all into one day, leaving room for details like food and toilet breaks ;) below that there is the development topics list. i've added one there as an example, though it's a real example, to get us started. please add whatever you want to that list; think of it as a brain storm section. we may not get to everything that ends up on that list at T3, but that's ok. at T3 we will put the list of items up on a board and people can express interest in them and we will then try and put together a loose schedule around them. since we are in a really nice area of the world in terms of natural surroundings and we won't have to be travelling between hotel and hacking area, i'm going to try and structure the days similar to what we did in Trysil a couple years back. that means our days will look something like: * post-breakfast debrief: this is where anyone can bring up topics/issues from the previous day so everyone else is up to speed as well as announce what they will be working on that day (if they know ;) so others can coordinate. ~30 mins, gets the brain in gear post-breakfast * hacking until lunch * post-lunch walk outdoors, during which we can discuss design and implementation issues in natural surroundings. we're creating a more organic interface, what better way to do this than spend some time in the real organic interface: nature. also helps to get people away from the computer screen and thinking about things. depending on the day, we may end up with a group meeting outdoors before returning. 45 minutes - 1.5 hours, depending. * return and hack until we fall over in happy heaps of tired plasma people (with dinner somewhere in there ;) any/all of the components above will be flexible, of course. we don't need to do all parts every day, but that will be the general idea for most days. p.s. first home automated using plasma == awesome ;) -- 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 Software 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: tokamak planning
On Thursday 30 July 2009, 16:22 Aaron J. Seigo wrote: ...[snip]... Seems great to me. p.s. first home automated using plasma == awesome ;) Pictures + Detailsplz !? :) -- Artur Duque de Souza openBossa Research Labs 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: tokamak planning
Am Donnerstag, 30. Juli 2009 schrieb Artur Souza (MoRpHeUz): Morning On Thursday 30 July 2009, 16:22 Aaron J. Seigo wrote: ...[snip]... Seems great to me. Me thinks as well. And my organizational comments will follow tomorrow. p.s. first home automated using plasma == awesome ;) Pictures + Detailsplz !? :) I think Aaron means the thing I wrote at the end of the techbase page. A friend of mine is building a house which is automated to a certain way and didn't know the interface for the automation when I proposed Plasma. He's definitely interested and hopes to come for at least a day... More about this soon Mario ___ Plasma-devel mailing list Plasma-devel@kde.org https://mail.kde.org/mailman/listinfo/plasma-devel
Re: tokamak planning
* post-lunch walk outdoors, during which we can discuss design and implementation issues in natural surroundings. we're creating a more organic interface, what better way to do this than spend some time in the real organic interface: nature. also helps to get people away from the computer screen and thinking about things. depending on the day, we may end up with a group meeting outdoors before returning. 45 minutes - 1.5 hours, depending. +1 * return and hack until we fall over in happy heaps of tired plasma people (with dinner somewhere in there ;) :) any/all of the components above will be flexible, of course. we don't need to do all parts every day, but that will be the general idea for most days. p.s. first home automated using plasma == awesome ;) very awesome. -- 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
Tokamak 3 for those who won't be there
hi ... at the last tokamak we had a twitter group; this time it will be an identi.ca group ;) but beyond that, what can we do to make it better/easier/more transparent for the members of our plasma family who can't be with us in Randa? -- 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 Software 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: Tokamak 3 for those who won't be there
A Quinta, 30 de Julho de 2009 23:39:54 Aaron J. Seigo você escreveu: hi ... at the last tokamak we had a twitter group; this time it will be an identi.ca group ;) but beyond that, what can we do to make it better/easier/more transparent for the members of our plasma family who can't be with us in Randa? Please sort out meetings I can attend or should attend with skype or something like that. -- Oxygen coordinator ___ Plasma-devel mailing list Plasma-devel@kde.org https://mail.kde.org/mailman/listinfo/plasma-devel
Re: Tokamak 3 for those who won't be there
On Thursday 30 July 2009 19:28:53 Nuno Pinheiro wrote: A Quinta, 30 de Julho de 2009 23:39:54 Aaron J. Seigo você escreveu: hi ... at the last tokamak we had a twitter group; this time it will be an identi.ca group ;) but beyond that, what can we do to make it better/easier/more transparent for the members of our plasma family who can't be with us in Randa? Please sort out meetings I can attend or should attend with skype or something like that. This would be cool if we could have a Skype conference with Tokamak, I would certainly be able to attend this each day. Shawn. ___ Plasma-devel mailing list Plasma-devel@kde.org https://mail.kde.org/mailman/listinfo/plasma-devel
