From kde-hardware-devel  Mon Feb 22 12:00:56 2010
From: Alex Fiestas <alex () eyeos ! org>
Date: Mon, 22 Feb 2010 12:00:56 +0000
To: kde-hardware-devel
Subject: Re: [Kde-hardware-devel] bluetooth in kde
Message-Id: <201002221300.57122.alex () eyeos ! org>
X-MARC-Message: https://marc.info/?l=kde-hardware-devel&m=126684111706008

On Monday 22 February 2010 12:14:18 Will Stephenson wrote:
> FYI we had a meeting here at Tokamak (off-topic but most of the relevant
> people happened to be there) about refactoring around libsolid.   Sebas is
> going to give a more detailed summary here but I know you'll be working on
> solid/bluetooth soon so I am letting you know first.
> 
> The basic principle is to make libsolid more flexible, and make
> libsolidcontrol less flexible.
> 
> Libsolid: make it able to support multiple backends at the same time.  So
> whereas now libsolid supports one backend at a time, eg hal, and other
> backend technologies eg bluez and networkmanager live in their own Solid
> namespaces, this would incorporate each backend's Devices as branches in
> one tree.
> 
> This helps with the move from hal to udev+udisks+upower, since these are
> each independent interfaces and are subject to change.  It also adds the
> ability to make eg UPNP devices available via Solid.
> 
> Libsolidcontrol: currently has a frontend/backend abstraction like in
> libsolid.  We propose to move the functionality of libsolidcontrol into the
> single management apps that use it, removing the cost of maintaining
> frontend/backend.  We can do this because there is no binary compatibility
> guarantee in kdebase.
> 
Mueheh thanks for sharing that, seems that in the next days/weeks/month there 
will be a lot of activity in solid Land.

> So what does this mean from bluetooth?   The namespace will be Solid, and
> when Kevin publishes his draft of the new multi-backend libsolid there
> will be interfaces for it to add devices to the Solid device lists.  
> AFAIK the logic will remain the same.
> 
> Will
As we talked, at the moment we aren't adding features to *solid* instead we're 
creating a couple of libraries to handle the pairing stuff, which is the only 
part of the whole bluetooth that needs a shared library (you don't really want 
create a new agent or a new application to receive files).

Finally I was writing an email called "Bluetooth + Solid in 4.5" I'll hold it 
until Sebas gives the summary.
_______________________________________________
Kde-hardware-devel mailing list
Kde-hardware-devel@kde.org
https://mail.kde.org/mailman/listinfo/kde-hardware-devel