Projects/Kbluetooth/Development - Revision history

Odysseus: moved Kbluetooth devel to Projects/Kbluetooth/Development

2011-03-19T16:54:55Z

moved Kbluetooth devel to Projects/Kbluetooth/Development

Afiestas: /* Dates, dates! give me dates! */

2009-09-16T22:30:20Z

‎Dates, dates! give me dates!

Afiestas: /* Solid development in detail: */

2009-09-16T22:29:47Z

‎Solid development in detail:

Afiestas: Created page with '=Current situation:= Right now the bluetooth support in KDE is not the best in any side, no user (kbluetooth) nor developer (solid) so we've to trace a roadmap to fix all of them...'

2009-09-16T11:30:27Z

Created page with '=Current situation:= Right now the bluetooth support in KDE is not the best in any side, no user (kbluetooth) nor developer (solid) so we've to trace a roadmap to fix all of them...'

New page

=Current situation:=
Right now the bluetooth support in KDE is not the best in any side, no user (kbluetooth) nor developer (solid) so we've to trace a roadmap to fix all of them.

=What are the steps to follow:=
The most urgent thing to do is fill the user gap. To do it we'll focus our work/time in the user applications like kbluetooth and a possible kioslave.
Once the user stuff is in a good shape, we'll start to "move" all the development we made for the user applications to solid/bluetooth and solid/bluez, so everybody will benefit of it.

=kbluetooth development in detail:=
Before 0.4 version, kbluetooth was thought as a framework and is because of it that kbluetooth is divided in 3 programs, kbluetooth, kbluetooth-devicemanger and kbluetooth-inputwizard. Everything will be merged in kbluetooth.

Then, all classes will be refactored/revised, and the new features which are not in solid will be totally rewritten from scratch (if needed), so we can move it easily to solid in the future (send, receive files for example).

Finally, we've to implement basic features like a2dp/modem pairing.

=Solid development in detail:=
The current bluetooth code is messed because the last development was stopped in the middle of a big refactoring. Despite it, everything is working quite well.
While we're working on user stuff, we'll maintain solid as it is, but once finish it, the plan is design a perfect API to introduce a real bluetooth support in kde.

=And what will happen once the previous points are reached?=
We'll talk with the usability team to design the perfect bluetooth integration.

=Dates, dates! give me dates!=
We don't have dates, we've objective. The objectives are:
*For KDE 4.4 all suer gaps must be fixed.
*For KDE 4.5 everything should be done.

@@ Line 21: / Line 21: @@
 =Dates, dates! give me dates!=
-We don't have dates, we've objective. The objectives are:
+We don't have dates, we've objectives. The objectives are:
-*For KDE 4.4 all suer gaps must be fixed.
+*For KDE 4.4 all user gaps must be fixed.
 *For KDE 4.5 everything should be done.

@@ Line 15: / Line 15: @@
 =Solid development in detail:=
 The current bluetooth code is messed because the last development was stopped in the middle of a big refactoring. Despite it, everything is working quite well.
-While we're working on user stuff, we'll maintain solid as it is, but once finish it, the plan is design a perfect API to introduce a real bluetooth support in kde.
+While we're working on user stuff, we'll maintain solid as it is, but once finish it, the plan is design a good API to introduce a real bluetooth integration in kde.
 =And what will happen once the previous points are reached?=