From kde-panel-devel Tue Aug 31 18:16:58 2010 From: Jeremy Whiting Date: Tue, 31 Aug 2010 18:16:58 +0000 To: kde-panel-devel Subject: Re: keystate plasmoid Message-Id: X-MARC-Message: https://marc.info/?l=kde-panel-devel&m=128327872225801 MIME-Version: 1 Content-Type: multipart/mixed; boundary="--===============1122702318==" --===============1122702318== Content-Type: multipart/alternative; boundary=001517576cb6331535048f22966a --001517576cb6331535048f22966a Content-Type: text/plain; charset=ISO-8859-1 Fixing bugs before putting it into svn? what a novel idea! ;) Anyway, that's awesome that you have plans for it. I've never dealt with javascript plasmoids (or much with c++ plasmoids either tbh) yet, but I bet if someone asked on irc in #plasma, these issues could get solved pretty quickly. There are many plasma experts in that channel. Actually, I'll cc this to plasma-devel and see if they have any ideas. Hope you don't mind. Anyway, best of luck and thanks for answering, and making such a useful plasmoid. Jeremy On Tue, Aug 31, 2010 at 11:02 AM, Martin < darklight.xdarklight@googlemail.com> wrote: > Hi Jeremy, > > > I have tried and found your keystate plasmoid to be very useful and > > wondered if you'd be interested in getting it into main kde itself. > plasma-devel: note the keystate plasmoid is hosted on gitorious at git:// gitorious.org/keystate/keystate.git > indeed, I'm thinking of getting this into KDE itself :) > > > I noticed your TODO lists just that ;) Anyway, let me know and we can > see > > what to do to get it into kde's svn (or if you want to wait for the git > > migration that's ok too I guess, though I think users would like having > > this sooner than later. > There are still two things I'd like to do before releasing it (one of them > is > already in the TODO-list): > -fix the bug which makes plasma-desktop use up to 80% cpu if "prefer size" > is > enabled (I just started debugging this in my VM, it might be a QtScript bug > :/) > -there's an issue with the color selection: currently I use hard-coded > default-values. As in 99% of the cases: hard-coded values are not nice ;) > It's a bit difficult to change this the "clean" way (I know a "dirty" > workaround, but I'd rather "fix" this the clean way). The clean way would > be > extending plasma so it can handle code-generated default values. > > I'll probably start implementing the functionality for issue #2 soon, so > that > might be fixed in KDE 4.7 > As for bug #1: I'm not sure what's causing this, I can reproduce this in my > VM > and on my main desktop - but I probably need to recompile Qt to get more > information about this. > > Greeting from Germany ;) > Regards, > Martin > --001517576cb6331535048f22966a Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Fixing bugs before putting it into svn? what a novel idea! ;)

Anyway= , that's awesome that you have plans for it.=A0 I've never dealt wi= th javascript plasmoids (or much with c++ plasmoids either tbh) yet, but I = bet if someone asked on irc in #plasma, these issues could get solved prett= y quickly.=A0 There are many plasma experts in that channel.=A0 Actually, I= 'll cc this to plasma-devel and see if they have any ideas. Hope you do= n't mind.

Anyway, best of luck and thanks for answering, and making such a useful= plasmoid.
Jeremy

On Tue, Aug 31, 2010= at 11:02 AM, Martin <darklight.xdarklight@googlemail.com> w= rote:
Hi Jeremy,

> I have tried and found your keystate plasmoid to be very useful and > wondered if you'd be interested in getting it into main kde itself= .

plasma-devel: note the keystate plasmoid i= s hosted on gitorious at git://gitorious.org/keystate/keystate.git
=A0
indeed, I'm thinking of getting this into KDE itself :)

> I noticed your TODO lists just that ;) =A0Anyway, let me know and we c= an see
> what to do to get it into kde's svn (or if you want to wait for th= e git
> migration that's ok too I guess, though I think users would like h= aving
> this sooner than later.
There are still two things I'd like to do before releasing it (on= e of them is
already in the TODO-list):
-fix the bug which makes plasma-desktop use up to 80% cpu if "prefer s= ize" is
enabled (I just started debugging this in my VM, it might be a QtScript bug=
:/)
-there's an issue with the color selection: currently I use hard-coded<= br> default-values. As in 99% of the cases: hard-coded values are not nice ;) It's a bit difficult to change this the "clean" way (I know a= "dirty"
workaround, but I'd rather "fix" this the clean way). The cle= an way would be
extending plasma so it can handle code-generated default values.

I'll probably start implementing the functionality for issue #2 soon, s= o that
might be fixed in KDE 4.7
As for bug #1: I'm not sure what's causing this, I can reproduce th= is in my VM
and on my main desktop - but I probably need to recompile Qt to get more information about this.

Greeting from Germany ;)
Regards,
Martin

--001517576cb6331535048f22966a-- --===============1122702318== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Plasma-devel mailing list Plasma-devel@kde.org https://mail.kde.org/mailman/listinfo/plasma-devel --===============1122702318==--