[KDE Dot News]
 faq
 flatforty
 contribute
 subscribe
 configure
 search
 rdf

 main


  The Pillars of KDE 4: Decibel
Feature Posted by Nathan Ogden on Wednesday 07/Feb/2007, @15:59
from the are-we-there-yet? dept.
The KDE development team is working hard on the KDE 4 platform. KDE 4 will include many exciting new technologies which will greatly enhance the functionality of KDE. One of these new technologies is Decibel. We would like to give you an idea of what Decibel is all about.

In putting this article together, the KDE promotional community was able to get most of the information from the lead developer of Decibel, Tobias Hunger. Tobias lives in Germany and studied Computer Engineering at the University of Kaiserslautern. Upon graduating, he found a job as a consultant for a small company specializing in systems management. Currently, he is employed as a software developer for basysKom GmbH.

This article is part one of a four part series about Decibel. In part one, we would like to provide a general overview of Decibel. Part two will define several terms related to Decibel. Benefits for developers will be covered in part three. Finally, part four will discuss benefits for users.

People use their computers to communicate with others. Usually, they want to communicate as close to real-time as possible. Email, instant messaging, and Voice over IP (VoIP), are some of the different ways people communicate using their computers. Each of these has its strengths and weaknesses. Ironically, each of these means of communication do not talk very well with other means of communication.

This is where Decibel comes in. Decibel is a service, not an application. The goal of Decibel is to create a bridge between different communication technologies. Decibel will make it easy to integrate real-time communication technologies into applications, Tobias says. Decibel provides a central storage place for settings of real-time communications. This will allow one communication application (say, email) to talk to another communication application (say, instant messaging) without having to learn a new language.

However, Decibel is not going to become yet another isolated box dealing only with communication. There are at least two ways Decibel will be able to connect to technologies and applications not normally associated with communication. Because Decibel allows programs in general to talk to each other in a more streamlined manner, programs that are not related to communication can also take advantage of this technology. For instance, document editors (such as word processors or graphics editors) could use this technology to allow better collaborative editing.

Also, Decibel is being developed to integrate with other KDE technologies. For instance, Phonon is a KDE technology that deals with integrating multimedia programs and services. It is possible for Decibel to work with Phonon in situations such as encoding and decoding voice data during a VoIP conversation.

In part two of this series on Decibel, we will define some terms to help further enhance your understanding of Decibel. In the final two sections, we describe potential benefits for both users and developers, and provide information on how to get involved with the Decibel project. The goals of the Decibel team are wide-ranging and forward-thinking. They have done an excellent job of specifying their vision. However, they are still in the beginning stages of reaching their goals. Much work needs to be done. The Decibel team would appreciate any help they can get.



<  |  >

 

  Related Links
 ·   Articles on Feature
 ·   Also by Nathan Ogden
 ·   Contact author

Thread Threshold:

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

Over 40 comments listed. Printing out index only.
Integration (and KDE4)
by TMaster on Wednesday 07/Feb/2007, @23:47
Personally, I think Decibel sounds a bit scary. I'm not big on integration myself, and that's what it sounds like to me. That said, KDE appears to have a much better approach than Microsoft (sorry, but I'm both a KDE and Windows fanatic ;-) ). For example, Microsoft chose to integrate MSN Spaces, Microsoft's blogging site, with MSN Messenger. Now, I absolutely despise MSN Spaces, and have no official way of removing the 'functionality' from their Messenger, or associating with a different blogging site.

Either way, I'm still very interested to see it in action. You guys have proved to be capable of making some very cool stuff. I consider KDE 3.4 to already be superior to the Windows desktop environment, and that definitely says something to me (although some people might take it the wrong way).

On an unrelated note, how is KDE4 moving along, if I may ask? On Slashdot, I read a random commenter saying saying something along the lines of it being mostly ideas, but little code. Are you still on track for a final release in the first half of this year? That's what I read, anyway. 2007 looks like it'll be a great year for Linux-based OSes!

(Oh, and kudos to you for a commenting system that doesn't require an e-mail address. Nice CAPTCHA, too!)

~ random Kubuntu n00b
[ Reply To This | View ]
not like MS spaces & messenger
by Another Kubuntu n00b on Thursday 08/Feb/2007, @00:57
Well, if I understand the article correctly, this is an integration project only on service level, not application level, so programmers might make use of it to allow communication things to be seen in final application. For example, your amarok will still be that amarok and not become an application for chatting, you got kopete for that. But amarok can use decibel to easily program a new function that allows you to msg someone on MSN messenger as soon as a certain new song is playing for example.
Well I hope I made my point that it's on service level and not application level.
[ Reply To This | View ]
So is Decibel Hal/DBUS for software?
by Darkelve on Thursday 08/Feb/2007, @01:43
So, basically, Decibel is for software what HAL/DBUS is for hardware?

Is it only for audio or are there more applications for it?
[ Reply To This | View ]
hmmm...
by mikroos on Thursday 08/Feb/2007, @03:30
ok... i was generally absolutely for all of those changes in KDE4, they sounded ok and practical... but this time i just don't think this is gonna be ok for me. i strongly recommend allowing the user to totally turn off the usage of Decibel by apps.

cheers!
[ Reply To This | View ]
The name "Decibel"
by Lans on Thursday 08/Feb/2007, @03:54
I think this has been mentioned before, but I still find it odd: why "Decibel"?
To me it sounds like something to do with sound. Well, you might say that it is; you communicate by talking right? However, what I mean with "sound" is for example music.

If I've understood Decibel right, then something with both connection/communicating would be a more fitting name. Am I wrong?

By the way, thank you for the article.
[ Reply To This | View ]
Just some musing on potential.
by Alec Munro on Thursday 08/Feb/2007, @09:13
Ok, so I think I understand the idea of Decibel, and I think I understand Phonon, so I'll lay out what I think would be a neat scenario, and people who know better than me can say if it will or won't work.

Let's say Phonon and Decibel become relatively well integrated, with the idea that there is a coherent connection between your identity as someone who is communication, and the sounds you are listening to.

Could you:
- Use Decibel as an output for Phonon, allowing any audio application to stream music to any of your "contacts"?
- Use Decibel as an input for Phonon, allowing your contacts to effect what you are listening to?

(There is a gray area of authentication that would need to be addressed for these to become a reality)

In both of these cases, these are things that can be done today, but it seems to me that this would enable them to be done at a much higher level. So rather than audio applications having to deal with network protocols, or network applications having to deal with sound formats, you could have it all helpfully abstracted through Decibel and Phonon). If you wanted to have your audio networked, all you would need is this integration, rather than a plugin for your specific audio program.

I'm sure this isn't the primary focus of these libraries, but I would be very interested to hear how possible this would be.
Thanks.
[ Reply To This | View ]
KDE4
by Magar on Thursday 08/Feb/2007, @16:11
When will development versions of the next KDE be available?
[ Reply To This | View ]
Telepathy
by Henning on Thursday 08/Feb/2007, @17:22
How is Decibel related to Telepathy. Do these technologies compete or can they use each other?
[ Reply To This | View ]
Integration - how to do it right
by Will Stephenson on Friday 09/Feb/2007, @05:49
Some commenters are concerned that Decibel will result in bloat and the forced integration of unwanted apps. I'd like to clear that doubt up.

The distinguishing factor between bad and good integration is the degree of coupling.

The MSN integration mentioned above is an example of tight coupling. Tight coupling is good when you want to get something done quickly and flexibility be damned, but doesn't leave you many choices afterward.

The coupling which Decibel offers, like KIMProxy before it in KDE 3, is loose coupling. In this model no component is bound to a particular other component. Decibel defines interfaces, that allow any component that implements that interface to be replaced with any other component.

For example, with KIMProxy we were able to integrate Kopete and KAddressbook to show contact status in KAddressbook. However this was no tight coupling. As other applications implemented the KIMProxy interface, these could be used instead, for example, substitute Licq or Konversation for Kopete as the sources of contacts' online status. This is loose coupling, and this is what Decibel provides.
[ Reply To This | View ]
Compatibility
by FelixR on Friday 09/Feb/2007, @13:08
Maybe it's a bit offtopic - but are all the KDE projects Phonon, Decibel, ... compatible with Gnome technics?

In my point of view this is most important for Linux adoption on the desktop... choice is good but I think common specs for both Gnome and KDE are the MOST IMPORTANT thing.

It will be very bad if people cannot change colors, themes, audio backends for both environments in ONE configuration app... Hope that freedesktop will help in that direction.

It's too complicated at the moment - settings like themes, one/two mouse click behaviour, left/right hand mouse, fonts, colors etc. for Gnome apps in Gnome control center for KDE apps in KDE control center.

Too complicated and time consuming for beginners! And why should someone who uses Ubuntu only use Gnome apps because of better look and feel? It's a big limitation if a user shall not use KDE applications in Ubuntu or vice versa...

Integration of both DE's is the most important thing. Portland project is a very good step in the right direction. But KDE and Gnome should use same things for storing configuration (like gconf or sth. else) etc.
[ Reply To This | View ]
integration
by miro on Friday 09/Feb/2007, @15:06
I think that software should be about inteligent features not "inteligent" decisions. what I mean is that I don't want kopete to start kmail, but I love the smile in kmail as a notify for a user being online in icq/msn/jabber. a common communication history would be even more avesome. if a user is offline in icq maybe I would like to send her a email, but it shouldn't be automatic, a nice little icon for voip/mail would be more than enogh. the first step should be to find out patterns of user behavior, then provide actions that are likely for the use case.
[ Reply To This | View ]
Integration should be more integrative ;-)
by Roland Kaeser on Sunday 11/Feb/2007, @09:18
From my point of view, the whole thing goes to the right direction but not the whole way. Lets make a diffrent approach for application integration. I will call it "aspect oriented applications" (nothing to do with the Java thing). Instead of making the applications integrate theirselfs we should make document integration. In my environment a lot of small business companies have a lot of documents such as word excel access emails and a lot of other information. But the informations about its relation together is "stored" only in the brains of the employes. Who nows that the document Offer-2006-10-12-ProductA.swx has something to do with the email "Thanks of the Offer" replayed at 2006-10-20 sent to mr. Smith. And the spreadsheet "Caluculation-2006-10-11.swx" is the calulation for that offer. So, only the employe who was working on that business process knows the relation between all this informations. So if we want make a better application integration, we should find a efficient way to link all these informations together in a assotiative way such as a human does it. So lets think about a small and easy szenario: In the above case it whould be nice to have a central address store for all desktop and business apps. Attached at this address store a workflow engine should link all workflows (such as the above calulation, offer, acceptance of this offer etc) together with the address records of the customers, partners and supplirs etc. This is just one szenario, there might several others for developer companies, it integrators, universities and a lot more, but all have together that the assotiation of all those documents and informations can be stored in a defined and standard way. And at the end (as I hope so) we will no more work with files on a fileshare (nfs or smb or something else) we will rater have "documents" which are stored in assotiative database by which each of the attached workers (employes etc) can refind all infos to a worklow a other worker has made without having to use such helper programs as beagle or other search engines. All informations are pre se stored in a refindable way.
[ Reply To This | View ]

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

  "I tried to play with some toy applications and enjoyed it." -- Werner Trobin
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.
[ home | post article | flat forty | subscribe | search | rdf ]