KDE Commit-Digest for 29th October 2006

faq
flatforty
contribute
subscribe
configure
search
rdf

main

KDE Commit-Digest for 29th October 2006

Posted by Danny Allen on Sunday 29/Oct/2006, @18:19
from the it's-that-time-of-the-week dept.
In this week's KDE Commit-Digest: Work on Decibel and the KDE-based NEPOMUK components accelerates. The Unity web rendering engine experiment is removed from KDE SVN, due to a change in the circumstances that prompted its creation. KTabEdit, a guitar tablature editor is imported into the KDE SVN playground. A branch of kde-pim for improvements in future 3.5 releases shows promise with the introduction of several new features. QMA, an experimental email client, continues to mature and is renamed Mailody. Usability and file format support refinements in Amarok. Speed optimisations in KViewShell and KFTPGrabber. More improvements in the state of games in KDE 4.

< | >

Related Links

·   Articles on Developer
·   Also by Danny Allen
·   Contact author

The Fine Print: The following comments are owned by whomever posted them.
( Reply )

Over 40 comments listed. Printing out index only.

Status of khtml
by AC on Sunday 29/Oct/2006, @19:09

Is there anyone that can comment about the removal of the unity engine? Does this mean that the kde khml codebase has been resynced with webkit?

[ Reply To This | View ]

Re: Status of khtml by SadEagle on Sunday 29/Oct/2006, @19:55

Re: Status of khtml by Carewolf on Sunday 29/Oct/2006, @23:36

Re: Status of khtml by fred on Monday 30/Oct/2006, @02:36

Re: Status of khtml by SadEagle on Monday 30/Oct/2006, @06:39

Re: Status of khtml by fred on Monday 30/Oct/2006, @08:59
Re: Status of khtml by Andre Somers on Monday 30/Oct/2006, @09:41

Re: Status of khtml by cartman on Monday 30/Oct/2006, @11:40

Re: Status of khtml by Andre Somers on Monday 30/Oct/2006, @11:59

Re: Status of khtml by Thomas on Monday 30/Oct/2006, @10:07

Re: Status of khtml by Carewolf on Monday 30/Oct/2006, @13:54

Re: Status of khtml by germain on Tuesday 31/Oct/2006, @16:16

Re: Status of khtml by st. germain on Tuesday 31/Oct/2006, @18:31

Re: Status of khtml by germain on Tuesday 31/Oct/2006, @19:36

Re: Status of khtml by st. germain on Tuesday 31/Oct/2006, @19:37

Re: Status of khtml by Tuco on Sunday 12/Nov/2006, @11:48

Re: Status of khtml by romain on Tuesday 31/Oct/2006, @20:58

Re: Status of khtml by Mikun on Monday 30/Oct/2006, @00:53

Re: Status of khtml by Thorsten Schnebeck on Monday 30/Oct/2006, @02:18

Re: Status of khtml by Henning on Monday 30/Oct/2006, @00:06

Re: Status of khtml by Victor T. on Monday 30/Oct/2006, @04:39

Re: Status of khtml by Daniel "Suslik" D. on Tuesday 31/Oct/2006, @08:31

Re: Status of khtml by Sergio Cambra on Thursday 02/Nov/2006, @01:27

Over-zealous bug triage.
by mart on Monday 30/Oct/2006, @01:07

> The past weekend saw the second bug triage day, concentrating on the
> kde-pim module.

Great. They closed my bug. I wonder if they'll actually fix it next time.

[ Reply To This | View ]

Re: Over-zealous bug triage. by Leo S on Monday 30/Oct/2006, @01:11

Re: Over-zealous bug triage. by mart on Monday 30/Oct/2006, @01:13

Re: Over-zealous bug triage. by Robert Knight on Monday 30/Oct/2006, @03:51

KViewShell?
by Jan on Monday 30/Oct/2006, @02:13

Shouldn't it be replaced be oKular? Why is there still work on it?

[ Reply To This | View ]

Re: KViewShell? by AC on Monday 30/Oct/2006, @03:37

Re: KViewShell? by superstoned on Monday 30/Oct/2006, @04:50

Re: KViewShell? by Corbin on Monday 30/Oct/2006, @05:55

Re: KViewShell? by Albert Astals Cid on Monday 30/Oct/2006, @08:03

Re: KViewShell? by ac on Monday 30/Oct/2006, @11:24

Re: KViewShell? by Albert Astals Cid on Monday 30/Oct/2006, @13:58

Re: KViewShell? by Corbin on Monday 30/Oct/2006, @19:24

Re: KViewShell? by Andre on Tuesday 31/Oct/2006, @02:18

Mailody
by Hobbes on Monday 30/Oct/2006, @02:21

Why this new software? Is there anything wrong with KMail?! There is no explanation on Mailody website, except maybe the sentence "Supports Tabbed email reading" at the bottom.

Will it support IMAP only? I think this would be a mistake to support only one protocol.

Good luck anyway!

[ Reply To This | View ]

Re: Mailody by fred on Monday 30/Oct/2006, @02:55
Re: Mailody by AC on Monday 30/Oct/2006, @03:41

Re: Mailody by Hobbes on Monday 30/Oct/2006, @06:07

Re: Mailody by Stephen on Monday 30/Oct/2006, @11:25

Re: Mailody by Janne Ojaniemi on Monday 30/Oct/2006, @11:56

Re: Mailody by Hobbes on Tuesday 31/Oct/2006, @05:56

Re: Mailody by Janne on Tuesday 31/Oct/2006, @06:40

Re: Mailody by Janne on Monday 30/Oct/2006, @11:56

Unity? And fix KHTML.info
by liquidat on Monday 30/Oct/2006, @02:42

I have to admit that I'm a bit troubled about the current status of khtml vs Unity as well. What is the situation? And what will be the benefits and shortcomings?

Also, the khtml.info side is broken, can someone, please, fix that?

[ Reply To This | View ]

Pattern
by Gato on Monday 30/Oct/2006, @03:00

KHTML - Unity, KMail - Mailody, Okular - KViewShell, there seems to be a very strong pattern here. Some users would like all developers to work on the same project, some developers don't agree upon the path to take and write different apps. This is why there is Krita and not just the Gimp, this is why there is Amarok and not just XMMS ( for heaven's sake ;-) ). This is probably a good thing. The people who prefer to work on old KHTML don't want to work on Unity, I presume. The people who still develop KViewShell have some reason (it doesn't matter whether it's a good one) to not work on Okular. So they wouldn't work on Okular anyway.

Sure it's bad to split efforts when there's no serious reason, but on the other hand it's good (very good) to have two or three different apps with different philosophies for (approximately) the same job. KDE is just one development platform, but KDE apps are plenty, which is just a proof of the success of the platform.

[ Reply To This | View ]

Re: Pattern by Rick on Monday 30/Oct/2006, @04:21
Re: Pattern by illissius on Monday 30/Oct/2006, @05:33

Re: Pattern by Gato on Monday 30/Oct/2006, @06:16

Re: Pattern by Corbin on Monday 30/Oct/2006, @05:58
Re: Pattern by Louis on Monday 30/Oct/2006, @19:50

Nepomuk
by MM on Monday 30/Oct/2006, @04:17

Never heard about Nepomuk. Does this mean that work on Tenor is definitely stopped?

[ Reply To This | View ]

Re: Nepomuk by superstoned on Monday 30/Oct/2006, @04:54

NEOPUNK
by Jonathan Dietrich on Monday 30/Oct/2006, @04:44

OK, I know that NEPOMUK is a Networked Environment for Personalized, Ontology-based Management of Unified Knowledge, however every time I see "NEPOMUK" my inner voice says "NEO-PUNK".

[ Reply To This | View ]

Re: NEOPUNK by superstoned on Monday 30/Oct/2006, @04:55
Re: NEOPUNK by Corbin on Monday 30/Oct/2006, @05:59
Re: NEOPUNK by Poborskiii on Monday 30/Oct/2006, @10:59
Re: NEOPUNK by Tom Corbin on Monday 30/Oct/2006, @14:24

Technical Preview
by Felix on Monday 30/Oct/2006, @12:42

Maybe it is a little to optimistic, but the first technical preview should be out soon (from the "release plan"). Is there already a new official date ?

[ Reply To This | View ]

Re: Technical Preview by Gato on Monday 30/Oct/2006, @16:05

huuh? diplomatic layer alert
by Andre on Tuesday 31/Oct/2006, @02:12

"The Unity web rendering engine experiment is removed from KDE SVN, due to a change in the circumstances that prompted its creation."

Can someone please decode that message to me?

[ Reply To This | View ]

Re: huuh? diplomatic layer alert by Corbin on Tuesday 31/Oct/2006, @06:58

The Fine Print: The previous comments are owned by whomever posted them.
( Reply )


		"The trick is not to dream of adding a feature, but simply to do it." -- Stefan Westerfeld
KDE®, "K Desktop Environment", "KDE Dot News", "got the dot?" and the KDE Logo® are trademarks or registered trademarks of KDE e.V. in the European Union, the United States and other countries. All other trademarks and copyrights on this page are owned by their respective owners. Comments are owned by the poster. The rest: Copyright © 2000-2008 KDE e.V. for The KDE Project. For further information or comments on this site, please contact the Webmaster.