Fixing bugs before putting it into svn? what a novel idea! ;)<br><br>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.<br>
<br>Anyway, best of luck and thanks for answering, and making such a useful plasmoid.<br>Jeremy<br><br><div class="gmail_quote">On Tue, Aug 31, 2010 at 11:02 AM, Martin <span dir="ltr"><<a href="mailto:darklight.xdarklight@googlemail.com">darklight.xdarklight@googlemail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">Hi Jeremy,<br>
<div class="im"><br>
> I have tried and found your keystate plasmoid to be very useful and<br>
> wondered if you'd be interested in getting it into main kde itself.<br></div></blockquote><div><br>plasma-devel: note the keystate plasmoid is hosted on gitorious at git://<a href="http://gitorious.org/keystate/keystate.git">gitorious.org/keystate/keystate.git</a><br>
<br></div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><div class="im">
</div>indeed, I'm thinking of getting this into KDE itself :)<br>
<div class="im"><br>
> I noticed your TODO lists just that ;) Anyway, let me know and we can see<br>
> what to do to get it into kde's svn (or if you want to wait for the git<br>
> migration that's ok too I guess, though I think users would like having<br>
> this sooner than later.<br>
</div>There are still two things I'd like to do before releasing it (one of them is<br>
already in the TODO-list):<br>
-fix the bug which makes plasma-desktop use up to 80% cpu if "prefer size" is<br>
enabled (I just started debugging this in my VM, it might be a QtScript bug<br>
:/)<br>
-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 ;)<br>
It's a bit difficult to change this the "clean" way (I know a "dirty"<br>
workaround, but I'd rather "fix" this the clean way). The clean way would be<br>
extending plasma so it can handle code-generated default values.<br>
<br>
I'll probably start implementing the functionality for issue #2 soon, so that<br>
might be fixed in KDE 4.7<br>
As for bug #1: I'm not sure what's causing this, I can reproduce this in my VM<br>
and on my main desktop - but I probably need to recompile Qt to get more<br>
information about this.<br>
<br>
Greeting from Germany ;)<br>
Regards,<br>
<font color="#888888">Martin<br>
</font></blockquote></div><br>