In this week's KDE CVS-Digest (all in one page):
amaroK and Kexi support KNewStuff for database examples, context themes and amaroK scripts.
amaroK adds support for Helix multimedia backend.
KMail filters now can be applied to messages from IMAP accounts.
KWifiManager implements switch network from GUI feature.
Dot Categories:
Comments
:-)
Always fun to read.
Fun to see kexi and amarok use knewstuff, although we might have to be careful about security since anyone can upload scripts.
Kexi has scripts disabled before 1.0 version, so don't worry. And we're planning to use a sandbox system for better security.
Good to see that the filters in kmail can now be applied on imap folders too.
Only two revisions behind schedule. 3.3, then 3.4 and now most likely what, 3.4.1?
I was thinking 3.5
Kay
Its no problem to apply filter to dIMAP folders - but stuff like filter incoming mails does not work if these mails are server side filtered by e.g. sieve. I hope the patch helps to solve this bug and will be backported to 3_4_BRANCH :-)
Bye
Thorsten
Which bug? Why should messages which have already been moved to the correct folder by the mail server be filtered again? That sounds like a pretty stupid idea, especially if you think of two differently configured email clients which ping-pong some messages between different folders.
For your information: Don's patch only filters new messages in the IMAP account's INBOX, just as with dIMAP.
Because, if a person wants filtering done on their imap mail, they very likely DONT have server side filtering to begin with. The only imapd that properly supports sieve is cyrus, which, in my experience is not all that common....
You misunderstood me. If a person doesn't use server side filtering then all his new mail will be in his IMAP account's INBOX and will thus be filtered. That's exactly what you want.
I use it for header rewriting cause this is easy with kmails filter engine.
But I can not apply this rule to new incomming mails into this folder. So I have to select new mails by hand and apply filter manually.
IIRC these rewrited headers are not synced back to the server.
Bye
Thorsten
There are two sections: "Development Tools" and "Development tools", of which the latter feels unnecessary. :-)
...and same for Kde-Base and Kde-base.
Ugh. Something about doing this at 1:30 am...
Derek
Has anyone started porting to Qt 4 or is that going to wait until Qt4 is final?
The KDE 4 branch is not open yet, as far as I know.
Some information about Qt4 here:
http://www.kdedevelopers.org/node/view/1005
This feature (which will hopefully be available in KDE 3.5) will greatly help new users coming from windows feeling more comfortable!
Olivier Goffart is coding the protocol part, and I started to send patches for the video capture support. I hope we'll have a working, useful code sooner than expected, at least for Linux (V4L and V4L2 APIs). Some help from BSD people will be very welcome.
While I am in the top 10 committers, no work from me is mentionned in the digest (I guess my logs should be longer) so there is a summary of what I did last week. I tested all KDE C++ KDevelop templates and made a doc about them.
http://women.kde.org/articles/tutorials/kdevelop_templates/index.php
In the process, I had fixed the ones that were broken and I updated the screenshots in the project wizard.
I also worked more on the new KHangMan design and used valgrind on KLettres -> fixed a memory leak.
Hey, thanks annma
the tutorial was quite useful for someone new to kde programming like me
how about adding a link to it on developer.kde.org?
And.. a little OT: i think here
http://developer.kde.org/documentation/misc/whatisscripty.php
someone forgot a (at the end of the page) ;)
Just took a quick look at the template doc. Very nice work. Thanks! :)
Could you PLEASE take some action regarding this bug. It's so silly and I think really many users suffer because of this:
http://bugs.kde.org/show_bug.cgi?id=91652
"...and I think really many users suffer because of this"
Standard phrase that everyone's using to promote his/her pet bug. Yawn. Posting this in an unrelated article gives bonus points, though.