[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]

Re: [PATCH master] Networking UI - integration of NM Applet



On 11/19/2010 01:40 AM, Brian C. Lane wrote:
On Thu, Nov 18, 2010 at 12:38:54PM +0100, Radek Vykydal wrote:
On 11/17/2010 11:18 PM, Brian C. Lane wrote:
The installer isn't the desktop, so to me panels and applets don't fit.

Yes, my first feeling was similar. But when I ask myself, why,
I can't say. It seems logical to me that network configuration
for installer environment is available all the time in the
environment. It also seems to allow to cope with one particularity
(due to using nm-c-e) - the same configuration wil be used
for target system.
Having the configuration available in UI all the way through
install we can for example suggest to change the configuration
before rebooting if it should be different from that used for
installer environment. And it also makes a lot of workarounds
easier, it gives user possibility of control without requiring to use it.

Another thing is that (in a very long term)
I feel (yes it is vague) convergence of DVD install and Live CD install
- I mean our installer (now even initrd) environment is
getting closer and closer to Live CD (the same order
of magnitude already;). Well, network configuration
has been pushing it this way (nm-c-e -> metacity, dbus) a lot.

Isn't it actually nice to have the same network configuration
UI in Live CD and DVD install?

I realize we have moved in a direction that requires us to use these,
but I don't think they fit. It seems to me that we're painting ourselves
into a corner by depending on NetworkManager during the install.

It is so. After commit to support full network configuration
in anaconda, I don't see a way to stop.

  Maybe
NM needs a better API to control these things without the need for the
applet?


We can talk to NM via dbus API just as NM Applet does,
I just don't want to duplicate its code and invent new
UI, not that I don't want to do it, but it would be our additional
code to be maintained and kept up to NM changes/added features.
I repeat myself, but the bugs and requirements would
make us basically duplicate it.

(NOTE: I do realize that I'm complaining without have any better
solutions, sorry about that).


That's ok.
One option that I can think of is to build alternative
(to systray applet) UI entry point upon lower layers of
NM applet code (note that both nm-c-e and NM Appled are in C),
but still I'd prefer using the applet.


Radek


[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]