System-wide wireless connection bug

[Andrey Borzenkov]

On Fri, Mar 11, 2011 at 1:37 PM, Sebastian Kügler <sebas at kde.org> wrote:
> Hey guys,
>
> On Thursday, March 10, 2011 21:45:11 Lamarque Vieira Souza wrote:
>> Em Thursday 10 March 2011, Andrey Borzenkov escreveu:
>> > >> > We still need user settings support for those who are not going to
>> > >> > upgrade to NM 0.9 soon. Have you tested that branch against a NM 0.9
>> > >> > snapshot?
>> > >>
>> > >> No. It is very unlikely to work due to D-Bus API changes, secrets
>> > >> handling changes, ...
>> > >>
>> > >> I do not know if it possible at all to have support for both NM 0.8
>> > >> and NM 0.9 in a single program. For a start, all NM lib major were
>> > >> increased so it is not clear how to even compile such binary.
>> > >>
>> > >> I thought more about current KNM 0.9 support NM 0.8 and move forward
>> > >> to 0.10 (or whatever) with NM 0.9 support.
>> > >>
>> > >> > I
>> > >> > still need to figure out what kind of changes we will need to do in
>> > >> > Solid::Control::NetworkManager (or its successor) to accomodate NM
>> > >> > 0.9 specification. Maybe it is a good idea to create a new
>> > >> > networkmanager-0.9 backend in kde://kde-workspace/solid/
>> > >>
>> > >> Does it help?
>> > >>
>> > >> http://projects.gnome.org/NetworkManager/developers/migrating-to-09/
>> > >
>> > > Hi guys,
>> > >
>> > > yeah, NM 0.9 changes the API a bit, so it is not compatible with 0.8.
>> > > Basicaly the API is simplified and applets can save a ton of code,
>> > > because they don't have to deal with user connections.
>> > >
>> > > Moreover, Dan would like to release NM 0.9 very soon (16th of March):
>> > > http://blogs.gnome.org/dcbw/2011/02/24/networkmanager-0-8-4-beta1-gets-
>> > > al l-up- in-there/
>>
>>       That is too soon for KDE :-/
>
> Well, we won't have it supported at release time, but having NM 0.9 out if
> important for us so we can start the transition.
>

I think, the most smooth transition can be achieved by factoring out
current local connection handling code in separate (kded?) module and
making applet talk to it via D-Bus. Then minimal changes would be
necessary in applet to transition to NM 0.9, because it will handle
connection only via D-Bus anyway; and connection module could be
transitioned to secrets agent for NM 0.9. Depending on amount of
changes, it may even be possible to conditionally use NM 0.8/0.9 code
in the same binary.

Comments?

Any pointers or short introduction to sources structure to achieve
this split (besides readme in KNM tree)?