Re: Questions about the toolbox & panels
On Saturday 06 December 2008 10:52:36 Aaron J. Seigo wrote: > On Saturday 06 December 2008, Jesse L. Zamora wrote: > > > availableScreenRegion is done, i didn't get much work done on tasks, > > > but managed a few commits to libtaskmanager. will be working more on > > > that today again. > > > > Sweet! I like that code, however simple it may be. There is one catch > > though. Right now, it just returns all the available screen rects in the > > order which it reads them. But, I think it should return the main screen > > area FIRST so that the toolbox code can know which one it is. Otherwise, > > there is no sane way to do that. What do you think? > > i think i don't undertand what you are asking for ;) > > what do you mean by "main screen area" and "firt"? Actually, Forget it. I guess in my crazy thinking state I thought that would be necessary; but in fact, the current implementation rocks and will work for what needs to get done (which is, keep the toolbox from hitting the panel). Thanks for writing that code, it really really helps!!! :-) :-) Xtreme Kommander ___ Plasma-devel mailing list Plasma-devel@kde.org https://mail.kde.org/mailman/listinfo/plasma-devel
Review Request: simplifying the bookkeeping in TaskGroupItem
--- This is an automatically generated e-mail. To reply, visit: http://reviewboard.vidsolbach.de/r/295/ --- Review request for Plasma and Aaron Seigo. Summary --- All bookkeeping is done with AbstractTaskItems. Further i removed all special bookkeeping for startup tasks since the accocciated TaskItem of a WindowTaskItem automatically becomes a full taskItem (what a greatly understandable sentece ;-). Diffs - trunk/KDE/kdebase/workspace/plasma/applets/tasks/taskgroupitem.h trunk/KDE/kdebase/workspace/plasma/applets/tasks/taskgroupitem.cpp trunk/KDE/kdebase/workspace/plasma/applets/tasks/windowtaskitem.h trunk/KDE/kdebase/workspace/plasma/applets/tasks/windowtaskitem.cpp Diff: http://reviewboard.vidsolbach.de/r/295/diff Testing --- Thanks, Christian ___ Plasma-devel mailing list Plasma-devel@kde.org https://mail.kde.org/mailman/listinfo/plasma-devel
Re: multi-screen fixathon
On December 6, 2008, Aaron J. Seigo wrote: > On Saturday 06 December 2008, Thomas Fjellstrom wrote: > > On December 6, 2008, Aaron J. Seigo wrote: > > > hi all.. > > > > > > we have a "healthy" number of multiscreen bugs on bugs.kde.org for > > > plasma: > > > > > > http://bugs.kde.org/buglist.cgi?product=plasma&component=multiscreen&bu > > >g_ st > > > atus=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED > > >&b ug_ severity=normal > > > > > > and that's with the multi-head bugs separated out! i'd like to work in > > > the next week on these bugs, but i lack the hardware to test with =( > > > > You don't have a spare monitor sitting around? Just about every graphics > > card and many new mobos have two display ports. > > ... but not all can do xinerama, i'm not running all drivers/x versions, > etc. all drivers support Xinerama in some way. Now XRandR is a different story, anyone with nvidia drivers just cant test xrandr 1.2 till nvidia gets its xrandr support finished. But I see your point :) -- Thomas Fjellstrom [EMAIL PROTECTED] ___ Plasma-devel mailing list Plasma-devel@kde.org https://mail.kde.org/mailman/listinfo/plasma-devel
Re: multi-screen fixathon
On Saturday 06 December 2008, Aaron J. Seigo wrote: > can we arrange some time with people who do have such hardware available to > them to test and fix? ok ... can we do this on wednesday/thursday of this coming week? come find me on irc when you are around and we'll start triaging the bugs. =) -- 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: multi-screen fixathon
On Saturday 06 December 2008, Thomas Fjellstrom wrote: > On December 6, 2008, Aaron J. Seigo wrote: > > hi all.. > > > > we have a "healthy" number of multiscreen bugs on bugs.kde.org for > > plasma: > > > > http://bugs.kde.org/buglist.cgi?product=plasma&component=multiscreen&bug_ > >st > > atus=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&b > >ug_ severity=normal > > > > and that's with the multi-head bugs separated out! i'd like to work in > > the next week on these bugs, but i lack the hardware to test with =( > > You don't have a spare monitor sitting around? Just about every graphics > card and many new mobos have two display ports. ... but not all can do xinerama, i'm not running all drivers/x versions, etc. -- 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: multi-screen fixathon
On Saturday 06 December 2008 17:34:55 Aaron J. Seigo wrote: > can we arrange some time with people who do have such hardware available to > them to test and fix? i'm happy to throw patches at people in return for > debug output, backtraces, descriptions of problems, etc. I can help with testing twinview / dualhead bugs. (NVidia 7600GS, latest drivers, recent trunk available). Feel free to harrass me whenever my personal timezone and travel plans make it possible. -- 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: multi-screen fixathon
On Samstag 06 Dezember 2008 17:34:55 Aaron J. Seigo wrote: > hi all.. > > we have a "healthy" number of multiscreen bugs on bugs.kde.org for plasma: > > http://bugs.kde.org/buglist.cgi?product=plasma&component=multiscreen&bug_st >atus=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_ >severity=normal > > and that's with the multi-head bugs separated out! i'd like to work in the > next week on these bugs, but i lack the hardware to test with =( > > can we arrange some time with people who do have such hardware available to > them to test and fix? i'm happy to throw patches at people in return for > debug output, backtraces, descriptions of problems, etc. Hey! I have a NVidia-Twinview here, latest X.org, Archlinux... so I can test :) Lukas ___ Plasma-devel mailing list Plasma-devel@kde.org https://mail.kde.org/mailman/listinfo/plasma-devel
Re: multi-screen fixathon
On December 6, 2008, Aaron J. Seigo wrote: > hi all.. > > we have a "healthy" number of multiscreen bugs on bugs.kde.org for plasma: > > http://bugs.kde.org/buglist.cgi?product=plasma&component=multiscreen&bug_st >atus=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_ >severity=normal > > and that's with the multi-head bugs separated out! i'd like to work in the > next week on these bugs, but i lack the hardware to test with =( You don't have a spare monitor sitting around? Just about every graphics card and many new mobos have two display ports. > can we arrange some time with people who do have such hardware available to > them to test and fix? i'm happy to throw patches at people in return for > debug output, backtraces, descriptions of problems, etc. Sure, I'm willing to help. I have two 21" CRTs setup with kde running on the nvidia beta drivers. I could test on ATI (integrated HD3200) as well if I had a DVI-D or HDMI enabled display. :( -- Thomas Fjellstrom [EMAIL PROTECTED] ___ Plasma-devel mailing list Plasma-devel@kde.org https://mail.kde.org/mailman/listinfo/plasma-devel
multi-screen fixathon
hi all.. we have a "healthy" number of multiscreen bugs on bugs.kde.org for plasma: http://bugs.kde.org/buglist.cgi?product=plasma&component=multiscreen&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=normal and that's with the multi-head bugs separated out! i'd like to work in the next week on these bugs, but i lack the hardware to test with =( can we arrange some time with people who do have such hardware available to them to test and fix? i'm happy to throw patches at people in return for debug output, backtraces, descriptions of problems, etc. -- 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: Questions about the toolbox & panels
On Saturday 06 December 2008, Jesse L. Zamora wrote: > > availableScreenRegion is done, i didn't get much work done on tasks, but > > managed a few commits to libtaskmanager. will be working more on that > > today again. > > Sweet! I like that code, however simple it may be. There is one catch > though. Right now, it just returns all the available screen rects in the > order which it reads them. But, I think it should return the main screen > area FIRST so that the toolbox code can know which one it is. Otherwise, > there is no sane way to do that. What do you think? i think i don't undertand what you are asking for ;) what do you mean by "main screen area" and "firt"? -- 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: Questions about the toolbox & panels
On Friday 05 December 2008 09:23:15 Aaron J. Seigo wrote:
> On Friday 05 December 2008, Jesse L. Zamora wrote:
> > On Wednesday 03 December 2008 22:06:34 Aaron J. Seigo wrote:
> > > On Wednesday 03 December 2008, Guillaume Pothier wrote:
> > > > 2008/12/3 Aaron J. Seigo <[EMAIL PROTECTED]>:
> > > > > On Wednesday 03 December 2008, Jesse L. Zamora wrote:
> > > > >> How can I let the toolbox know where the panels are? Are there any
> > > > >
> > > > > if (containment->screen() > -1) {
> > > > > QRegion usableArea =
> > > > > containment->corona()->availableScreenRegion(containment->screen())
> > > > >; }
> > > >
> > > > Oh then it's probably time to properly implement this API :-) (see
> > > > eg. desktopcorona.cpp:106).
> > > > As far as I'm concerned I probably won't be able to do this this
> > > > week, though, so if someone else feels like to do it, please go
> > > > ahead.
> > >
> > > yeah, i can do that easily.
> > >
> > > tomorrow i will work on:
> > >
> > > * implementing availableScreenRegion
> > > * tasks widget, building on chrigi's good work.
> >
> > Yup, thanks alot guys! Today is Friday, is it done yet? Yesterday I had
> > to go to work so I couldn't see my emails.
>
> availableScreenRegion is done, i didn't get much work done on tasks, but
> managed a few commits to libtaskmanager. will be working more on that today
> again.
Sweet! I like that code, however simple it may be. There is one catch though.
Right now, it just returns all the available screen rects in the order which
it reads them. But, I think it should return the main screen area FIRST so
that the toolbox code can know which one it is. Otherwise, there is no sane
way to do that. What do you think?
Xtreme Kommander
___
Plasma-devel mailing list
Plasma-devel@kde.org
https://mail.kde.org/mailman/listinfo/plasma-devel
