Fwd: Re: Ask for help about PopupApplet in PyKDE4

[Diego Casella ([Po]lentino)]

I'm forwarding the email to the mailing list for a couple of reasons,
explained below :)

2011/9/26 

> Yes, I just change to
> X-KDE-ServiceTypes=Plasma/PopupApplet
> and it works well . so thank you very much .
>

This is great,  you should've told this in the ml in the first place; in
this way, other people with your same issue will find out how to solve that
problem (reason #1) ;)


> but i still confuse that how the python applet works and why not use the
> PopupApplet
> class directly as we do in cpp ? it make me crazy .
>

Here we go with reason #2: I'm not a PyKDE guru, so you'd have better luck
if you asked in the mailing list.
Imho, the reason is because writing a plasmoid with python (or whatever else
scripted language) must be easier than doing it with cpp.
You simply change "X-KDE-ServiceTypes" entry  from "Plasma/Applet" to
"Plasma/PopupApplet" and bang!, you get a bunch of new properties and
methods to deal with a PopupApplet, instead of the more complex code you
would need to write with cpp in order to achieve the same result.


> and what's more , i find no documents
>  about Plasma.plasmascript at all .What is its  type ? Applet? PopupApplet
> ? or even appletscript ?
> that is so confusing.
>

I don't think you really need to know what plasmascript is, however here it
is the link [1].
Perhaps your confusion comes from the "lack" of documentation about python
bindings ... Actually those docs do exist, are extremely detailed  and very
well made but, unfortunately, they are not as visible as their
qml/javascript counterparts.
You can have a look here [2]  (of course change branch according to the KDE
version you are running in your pc) .
Good luck with your applet, and have fun :)
Cheers,

Diego


> --邮件发自网易手机邮--


P.S: and you _really_ are a lucky guy, because google put your email in my
spam folder, and I would never noticed it if I didn't pressed by mistake the
Spam button instead of the Draft one (reason #3) xD



[1]
https://projects.kde.org/projects/kde/kde-workspace/repository/revisions/master/entry/plasma/generic/scriptengines/python/plasmascript.py
[2]
https://projects.kde.org/projects/kde/kdebindings/pykde4/repository/revisions/master/show/docs/html/plasma

-- 
H: Who is Watson without Sherlock Holmes?
G: Watson was a genius in his own right.

My personal blog: http://polentino911.wordpress.com/

>> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<

Re: Allow users to donate money towards bugs

[Anne Wilson]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On 09/27/2011 04:12 PM, Felix Rohrbach wrote:
> If the money donated to a bug is not to motivate the developers,
> but a way for users to show that they care about a bug, then why
> don't donate the money to the KDE eV?

As far as I know that isn't an option, due to "non-profit-making
status".  I could be wrong though.

Anne
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAk6DPdoACgkQj93fyh4cnBfcywCfe3mSomRLqic66cWvKU4jmuFN
as8An3RqgZmg+TfsEVfBs4zgJ3mpFGCp
=Q64y
-END PGP SIGNATURE-

>> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<

Re: teacher needed for Ada Lovelace Day tutorial

[Tomaz Canabrava]

Must be a woman - teacher?
what about annma?

On Tue, Sep 27, 2011 at 3:00 PM, Lydia Pintscher  wrote:
> Heya folks :)
>
> Ada Lovelace Day is on 7th of October and I and a few other people
> would love to have a programming tutorial on IRC on that day. It'd be
> a "for women and their friends" event, meaning men are welcome if
> they're nice but the main focus are women). The goal of the tutorial
> would be writing a first small KDE application or fixing a bug. If we
> have teachers for both we could also do two tutorials.
> I'm looking for a teacher for this. I and others will help with
> promotion. Any takers?
>
>
> Cheers
> Lydia
>
> --
> Lydia Pintscher
> KDE Community Working Group member
> http://kde.org - http://about.me/lydia.pintscher
>

>> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<

Re: Getting started with KDE development

[Michael Pyne]

On Tuesday, September 27, 2011 21:07:40 Giorgos Tsiapaliwkas wrote:
> Hi and welcome.:)
> 
> On 27 September 2011 14:09, Picachu Nioto  wrote:
> > Okay, so current status is that I have decided to use kdesrc.
> > While executing kdesrc-build, I got the errors. Log is posted below but to
> > summarize there are 3 errors,
> > 1. Unable to configure qt-copy!
> 
> there is no qt-cory anymore.It is deprecated.

Careful with that one. ;)

There's no KDE copy of Qt+patches anymore, but KDE still does mirror Qt.

And the module kdesrc-build uses to build Qt must still be called qt-copy 
unfortunately.

> Can you tell us which kdesrc-build version do you use?
> 
> > 2. Unable to configure automoc with CMake! (Occurs for many packages)
> 
> probably some distro package is missing.we need to see the errors.

Make sure you have a recent enough CMake.

Regards,
 - Michael Pyne

signature.asc
Description: This is a digitally signed message part.

>> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<

Bug triage process needs help

[Bart Kelsey]

Hi folks,

I'd like to draw attention to the fact that KDE's bug triage process is lacking.

It's frustrating for users submitting bug reports when an easily
reproducible bug sits in the queue, without even a comment, for six
months.  For the record, I'm referring to this bug report here:

https://bugs.kde.org/show_bug.cgi?id=270105

I have, for the record, already posted a message to plasma-devel about
it, and I'm mentioning it here because I believe it's indicative of a
larger problem.

>From my understanding of C++ and Qt, this bug is most likely very easy
to fix for someone who knows the code base.  Even if it's not, though,
it would require a trivial amount of time to confirm it, leave a brief
comment, and mark the bug as new.

My question, ultimately, is do you really want users to report bugs?
If so, there ought to be a process in place to make sure the users who
report the bugs know that the bugs have at least been looked at by a
human being (and preferably triaged).  I realize this isn't exactly a
fun or interesting job, but for a large FOSS project like KDE, it's a
necessary one.

Regards,

Bart Kelsey


-- 
--

>> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<

Re: Allow users to donate money towards bugs

[Robert Klotzner]

Well the basic idea is to be able to make a living by writing free software.
But how can it be done, if you give it away for free?
Well it does not make any sense to sell copies, because copies are free (the
proprietary way), but it does make sense to pay for the development of free
software. The question is how? - This is exactly what I am thinking about, a
working model needs at least the following attributes:
- there must be an incentive to pay something
- it must be easy to give money
- what happens with the money must be transparent
- actual work is done with the money
- it must be as popular as possible, everyone knowing free software should
know the platform where he/she can invest in software
- clear goals for projects should be specified

These are at least the most important points. If it was possible to build
such a platform, it could be possible to pay a lot more developers for full
time work on free software, ideally it would make proprietary software
obsolete (I admit that's ambitious).

I know most of you do coding for fun, but in my personal opinion and
experience, getting money for fun is even better. The ones that simply don't
want money for their work, would not have to take money, the traditional
spare time coding is not abolished. The major goal is simply to make full
time development of free software more common place, in order to increase
quality, diversity and entering fields where free software is not that
prominent these days.

The question is whether it could work, at the moment I think "yes", if you
do it right. Projects like Ardour already show that there is potential.

That's just a few thoughts, of what I have in mind. What's your opinion?

Once again, thanks for your input, it helps a lot!

Best regards,

Robert

>> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<

Re: teacher needed for Ada Lovelace Day tutorial

[Lydia Pintscher]

On Wed, Sep 28, 2011 at 19:08, Tomaz Canabrava  wrote:
> Must be a woman - teacher?

Not necessarily but it would of course be nice.

> what about annma?

She said she can't promise she'll be available that day so can't do it.


Cheers
Lydia

-- 
Lydia Pintscher
KDE Community Working Group member
http://kde.org - http://about.me/lydia.pintscher

>> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<

Re: Getting started with KDE development

[Picachu Nioto]

Anyone got a chance to look at my earlier email.

Thanks,
Picachu

-- Forwarded message --
From: Picachu Nioto 
Date: Wed, Sep 28, 2011 at 4:18 AM
Subject: Re: Getting started with KDE development
To: kde-devel@kde.org


Hello everyone,

Thanks for the replies. Appreciate it!

I am using kdesrc 1.14.1
I have now checked the log files and it the error that I am getting is the
following: (they are different for different packages.

1) cmake_minimum_required(VERSION 2.8)
2)   include could not find load file:KDE4Defaults
3)   include could not find load file:MacroLibrary

I have kdelibs-dev installed.

Thanks!
Picachu

On Tue, Sep 27, 2011 at 11:07 AM, Giorgos Tsiapaliwkas
wrote:

> Hi and welcome.:)
>
>
> On 27 September 2011 14:09, Picachu Nioto  wrote:
>
>> Okay, so current status is that I have decided to use kdesrc.
>> While executing kdesrc-build, I got the errors. Log is posted below but to
>> summarize there are 3 errors,
>> 1. Unable to configure qt-copy!
>>
>
> there is no qt-cory anymore.It is deprecated.
> Can you tell us which kdesrc-build version do you use?
>
>
>> 2. Unable to configure automoc with CMake! (Occurs for many packages)
>>
>
> probably some distro package is missing.we need to see the errors.
>
>
>> 3. Can't checkout phonon: No such file or directory at ./kdesrc-build line
>> 2954. (Occurs for many packages)
>>
>
> Probably something is wrong with your .kdesrc-buildrc file.
>
> cheers
>
> --
> Tsiapaliwkas Giorgos (terietor)
> KDE Developer
>
> terietor.gr
>
>
> >> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to
> unsubscribe <<
>
>

>> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<

KPluginSelector: Problems with the configCommitted() signal

[José Expósito]

Hello list!!

I have a (probably very very simple) problem with the KPluginSelector
class. As I see in the documentation

the configCommitted() signal must be sent whenever the configuration
is save in disk... But I'm stucked because the configuration is
correctly saved on disk, but the signal is never emmited :S

This is my code:

-
// KRunnerForm inherits from KPluginSelector

KRunnerForm::KRunnerForm(QWidget *parent)
: KPluginSelector(parent)
{
connect(this, SIGNAL(configCommitted(const QByteArray&)),
this, SLOT(updateRunner(const QByteArray&)));

this->addPlugins(Plasma::RunnerManager::listRunnerInfo(),
KPluginSelector::ReadConfigFile, i18n("Available plugins"), "",
KSharedConfig::openConfig("takeoffrc"));
}

// This slot is called when the Accept button is pressed
void KRunnerForm::saveConfiguration()
{
this->save();
}

void KRunnerForm::updateRunner(const QByteArray &name)
{
// The slot is never called :(
qDebug() << "#";
}
-

Any help is welcome, and if you need more code only say me
Thanks in advance!!

>> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<

Seeking a starting point.

[Cecil]

Hello,

I just wrote a huge email asking about where to start to make some personal
changes to the kickoff and classic menus. Then I found the source and things
started becoming a little clearer.  However I would still love to have a
solid starting point in my reading, before I start beating up the code.

I have already figured out a fair amount of what I want from looking at the
kickoff code. The elements are a lot similar to the underlying code in vc++
or even Vb form files, but I am not finding size and location information
etc.

Everything I plan to mangle is for the kickoff and classic, and system tray.
So, where does a schmuck like me start?

 

Thanks, 

 

Cecil


>> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<

Re: Bug triage process needs help

[Christoph Feck]

On Wednesday 28 September 2011 19:46:14 Bart Kelsey wrote:
> I'd like to draw attention to the fact that KDE's bug triage
> process is lacking.

Thanks for your offer to help with bug triage. There are over 4 
bugs/wishes waiting for a comment, a confirmation, or a patch. You can 
also request more bugzilla rights, and resolve bugs accordingly. If 
you manage to resolve five bugs a day, we would be very happy.

Christoph Feck (kdepepo)
KDE Quality Team

>> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<

Re: Getting started with KDE development

[Milian Wolff]

Picachu Nioto, 29.09.2011:
> Anyone got a chance to look at my earlier email.

If you are on a debian based distro, you will need kdelibs5-dev.

bye

> -- Forwarded message --
> From: Picachu Nioto 
> Date: Wed, Sep 28, 2011 at 4:18 AM
> Subject: Re: Getting started with KDE development
> To: kde-devel@kde.org
> 
> 
> Hello everyone,
> 
> Thanks for the replies. Appreciate it!
> 
> I am using kdesrc 1.14.1
> I have now checked the log files and it the error that I am getting is the
> following: (they are different for different packages.
> 
> 1) cmake_minimum_required(VERSION 2.8)
> 2)   include could not find load file:KDE4Defaults
> 3)   include could not find load file:MacroLibrary
> 
> I have kdelibs-dev installed.
> 
> Thanks!
> Picachu
> 
> On Tue, Sep 27, 2011 at 11:07 AM, Giorgos Tsiapaliwkas
> 
> wrote:
> > Hi and welcome.:)
> > 
> > On 27 September 2011 14:09, Picachu Nioto  wrote:
> >> Okay, so current status is that I have decided to use kdesrc.
> >> While executing kdesrc-build, I got the errors. Log is posted below but
> >> to summarize there are 3 errors,
> >> 1. Unable to configure qt-copy!
> > 
> > there is no qt-cory anymore.It is deprecated.
> > Can you tell us which kdesrc-build version do you use?
> > 
> >> 2. Unable to configure automoc with CMake! (Occurs for many packages)
> > 
> > probably some distro package is missing.we need to see the errors.
> > 
> >> 3. Can't checkout phonon: No such file or directory at ./kdesrc-build
> >> line 2954. (Occurs for many packages)
> > 
> > Probably something is wrong with your .kdesrc-buildrc file.
> > 
> > cheers
> > 
> > --
> > Tsiapaliwkas Giorgos (terietor)
> > KDE Developer
> > 
> > terietor.gr
> > 
> > >> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to
> > 
> > unsubscribe <<


-- 
Milian Wolff
m...@milianw.de
http://milianw.de


signature.asc
Description: This is a digitally signed message part.

>> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<

Re: Bug triage process needs help

[Sune Vuorela]

On 2011-09-28, Bart Kelsey  wrote:
> Hi folks,
>
> I'd like to draw attention to the fact that KDE's bug triage process is 
> lacking.

Hi Bart

You are absolutely right that we get more bug reports to any component
than we can currently handle, as you have noticed yourself.

I haven't looked at the bug report in question, so this is a generic
comment on bug reports.

Many bug reports are 'low quality', as in 'hard to figure out what the
submitter means'.
There are really many bug reports in general.
This leads to a fact that finding the 'high quality' bug reports is the
classic of finding a needle in a haystack.

I'm sure that if you want to help triage the bugs reports and finding
the actual high quality ones, I'm sure it would be most welcomed. If you
could just spare  a couple of hours pr week, it would actually make a
difference.

I think the plasma product gets several hundred bugs a week, and there
is only a handful of people actually working on plasma, and not only on
bugfixing but also doing new or missing features, so there is clearly
room for helping here, as well as in any other product.

Thanks for your interest in KDE

/Sune


>> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<

Re: Bug triage process needs help

[Giovanni Venturi]

On Wednesday 28 September 2011 13:46:14 Bart Kelsey wrote:
> Hi folks,
> 
> I'd like to draw attention to the fact that KDE's bug triage process is
> lacking.
> 
> It's frustrating for users submitting bug reports when an easily
> reproducible bug sits in the queue, without even a comment, for six
> months.  For the record, I'm referring to this bug report here:
> 
> https://bugs.kde.org/show_bug.cgi?id=270105
> 
> I have, for the record, already posted a message to plasma-devel about
> it, and I'm mentioning it here because I believe it's indicative of a
> larger problem.
> 
Yes. I think so. Maybe developers have different priorities when they are few 
people on the specific project.

Also these bugs are in queue:

https://bugs.kde.org/show_bug.cgi?id=183143
https://bugs.kde.org/show_bug.cgi?id=251056
https://bugs.kde.org/show_bug.cgi?id=240716

>> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<

Re: invest money in free software?

[Sven Burmeister]

Am Donnerstag, 22. September 2011, 17:33:59 schrieb Sam S.:
> On Thu, Sep 22, 2011 at 4:13 PM, David Narvaez
> 
>  wrote:
> > Hi, just wanted to add this link with an interesting (and valid?) point
> > of view
> > 
> > http://threatpost.com/en_us/blogs/how-bug-bounties-are-rat-farming-09201
> > 1
> 
> Yes, allowing uncontrolled personal bug bounties would
>   a) open the door to various moral hazards:
> - incentive for "rat farming" (as you mentioned)

How? People introducing bugs to fix them later? Code is reviewed now and will 
be then.

> - incentive for working alone (or even in secret) rather that
> collaborating

Who cares if you work in secret on a few lines patch to fix a bug? Do you 
think people gather in groups to for most bug fixes?

> - etc., and
>   b) introduce lots of destructive petty conflicts of interest into an
> environment otherwise based on mutual constructive collaboration:
> - Who gets the money, the one who completes the last 1% of the work?

I think you miss the point. How many lines do most bug fixes have? Ever 
thought about not everything being about adding huge features but rather bugs 
that nobody fixes for weeks?

> - How are disagreements handled about by whom, when or if a bug was fixed?

How are disagreements currently handled if two devs have different approaches? 
You must really think that people just wait to start attacking each other over 
money and will crowd to fix bugs they would not have touched in weeks if there 
was no bounty.

> - etc.
> To handle all those possible issues, lots of bureaucracy and
> conflict-management would be needed, which would probably do the
> project more harm than good.

Not at all. Common sense and a working community, including reviews as they 
are already done.

[snip]

IMHO you think far too negative and complicated.

Sven

>> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<

Re: Bug triage process needs help

[Sebastian Kügler]

Hi,

On Wednesday, September 28, 2011 19:46:14 Bart Kelsey wrote:
> I'd like to draw attention to the fact that KDE's bug triage process is
> lacking.

Did you get in contact with the bugsquad, they'll probably appreciate your 
help.

> It's frustrating for users submitting bug reports when an easily
> reproducible bug sits in the queue, without even a comment, for six
> months.  For the record, I'm referring to this bug report here:

This posting of bugreports to mailinglists is often seen as unnecessary, and 
unfair since you're bringing attention to your pet bugs, which disadvantages 
others' pet bugs. Please don't do it, your bug likely ends up lower on 
developers' priority lists, and it sometimes causes bad blood (as can be seen 
in recent history).

Even if you word it carefully, essentially your message is still saying that a 
trivial to triage bug doesn't get the attention you think it should get. That, 
however, is true for many bugs, sending reminders about them to mailinglists 
is no solution, since it doesn't scale, nor does it give any useful 
prioritization to developers.

FWIW, I tend to other bugs, when I encounter this behaviour.

Cheers,
-- 
sebas

http://www.kde.org | http://vizZzion.org | GPG Key ID: 9119 0EF9

>> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<

Re: Allow users to donate money towards bugs

[Sven Burmeister]

Am Sonntag, 25. September 2011, 10:56:21 schrieb Lydia Pintscher:
> I'd like to recommend watching Stormy Peter's excellent talk titled
> "Would you do it again for free". It has some very enlightening points
> about this topic.

To quote from her blog:

http://stormyscorner.com/2008/11/does-money-kill-good-motivations.html

"The short answer is, it [the studies] applies, but money is not as 
demotivating as you’d first think for a number of other reasons."

So as with everything it can be done wrong or right and it's not a proved fact 
that it demotivates per se.

> It changes the game and the motivation change is not restricted to
> that work no-one else wants to do. I also don't believe the train of
> thought that we have a lot of areas that no-one wants to touch. Most
> of these areas lack from exposure to people who would love to work on
> them. That's the first thing we need to fix and the CWG has been
> working on that with Finding the Unloved but I am sure there is a lot
> more that can be done.

I do not understand how one can not believe that the bug tracker contains lots 
and lots of bugs that are unfixed although they are part of an active project, 
e.g. plasma. Rather than spending time on building a list of those bugs one 
should leave it to the users to "mark" them with whatever a fix is worth to 
them. This does in fact already happen with votes – but votes don't seem to 
change much regarding the motivation to fix a bug. Some bugs seem to even get 
unnoticed for weeks although they have a lot of votes. If votes are ignored I 
do not think that one can state that devs suddenly would like to fix a bug if 
it was pointed out as unloved.

However, if pointing out the "unloved" bugs helps I can do so in the future – 
but I do not think that anyone will suddenly start coding on a bug just 
because I point out that it is a few weeks old and valid. But who knows.

Sven

>> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<

Re: Seeking a starting point.

[Stefan Majewsky]

On Thu, Sep 29, 2011 at 6:50 PM, Cecil  wrote:
> The elements are a lot similar to the underlying code in vc++ or even Vb
> form files, but I am not finding size and location information etc.

You mean "size and location" of the widgets inside the menu applets?
Without actually looking at the code, I suspect that these should be
QGraphicsWidgets. Look for QGraphicsLayout instances: These are
calculating size and location of the widgets automatically as the
applet is resized.

In any case, a very good read with many examples and the like is the
Qt documentation at http://doc.qt.nokia.com. And the KDE API
documentation you can find at http://api.kde.org (paste the name of
the class in question into the search box at the bottom left).

Greetings
Stefan

>> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<