How to use Solid Control (from kdebase/workspace/libs) and Solid (from KDELibs) in the same source

[Nicolas Ternisien]

Hi Will,

No problem, you finally answer me with some good news, so this is
great ! I will have a look into the next version of Solid of your
branch soon.

Thanks !

On Wed, Apr 23, 2008 at 2:42 PM, Will Stephenson <wstephenson at kde.org> wrote:
>
> On Wednesday 16 April 2008, Nicolas Ternisien said:
>  > I would like to implement In KInfocenter the Network information from
>  > Solid API, but there are two NetworkInterface classes that could be
>  >
>  > used :
>  > >From Kdelibs :
>  >
>  > http://api.kde.org/4.x-api/kdelibs-apidocs/solid/html/networkinterface_8h-s
>  >ource.html
>  > http://api.kde.org/4.x-api/kdelibs-apidocs/solid/html/classSolid_1_1Network
>  >Interface.html
>  >
>  > >From Kdebase Workspace :
>  >
>  > http://api.kde.org/4.x-api/kdebase-workspace-apidocs/libs/solid/html/classS
>  >olid_1_1Control_1_1NetworkInterface.html
>  > http://api.kde.org/4.x-api/kdebase-workspace-apidocs/libs/solid/html/networ
>  >kinterface_8h-source.html
>  >
>  > Unfortunately, Kdelibs implementation provides information about Mac
>  > address of the network, and Kdebase implementation other details like
>  > IP address, route, netmask,...
>  >
>  > I firstly have the problem that the two #include <networkinterface.h>
>  > could not be used at the same times because they have the same name
>  > and the same #ifdef SOLID_NETWORKINTERFACE_H variable.
>  >
>  > More over, I don't know if the device->as<NetworkInterface>() could
>  > work in the two cases.
>  >
>  > So I would like to know if I miss something, and if not, maybe change
>  > Solid from Kdebase headers name to a different name.
>
>  Hi Nicholas
>
>  Sorry for not responding sooner.  The Solid::Control API is being rewritten
>  and I hope to merge it this week.  I think the new API will provide all the
>  info you need.  Look in branches/~wstephens in SVN.
>
>  Will
>
>
>
>
>
>