Difference between revisions of "Development/Tutorials/Phonon/Introduction"

Jump to: navigation, search
(Introduction)
(Introduction)
Line 13: Line 13:
 
[http://www.englishbreakfastnetwork.org/apidocs/apidox-kde-4.0/kdelibs-apidocs/phonon/html/index.html Phonon API].
 
[http://www.englishbreakfastnetwork.org/apidocs/apidox-kde-4.0/kdelibs-apidocs/phonon/html/index.html Phonon API].
  
Getting involved with Phonon consists in three different main tasks.
+
By getting involved with Phonon, you can choose between three different main tasks.
* '''Using the Phonon API''', which allows you to develop your own multimedia application.  
+
* '''Using the Phonon API''', which allows you to develop your own multimedia application. In fact any application that needs sound can take benefits form the phonon API.
  
 
* '''Hacking the Phonon library''', (try to develop more this topic).
 
* '''Hacking the Phonon library''', (try to develop more this topic).

Revision as of 14:05, 1 March 2007

These tutorials are now under construction, please be patient. This document has born the 28th of February 2007. In order to make the revision process clear, I introduce a confident index, 0 means that nobody except me had reviews the text. I please the reviewers to increment the counter to prove the validity of the tutorials.

If you are a Phonon developer and you realize errors, you're missing some details or a whole chapter. Please feel free to complete the followings.


Introduction

Confident Index =0

The following is based on the documentation available here Phonon API.

By getting involved with Phonon, you can choose between three different main tasks.

  • Using the Phonon API, which allows you to develop your own multimedia application. In fact any application that needs sound can take benefits form the phonon API.
  • Hacking the Phonon library, (try to develop more this topic).
  • Writing Phonon backend, this consists in writing interfaces that allows Phonon to use different sound/video engine. This usually requires good skills and knowledge of the engine you interface.

By the way the beginners will probably be interested by the first task.


KDE® and the K Desktop Environment® logo are registered trademarks of KDE e.V.Legal