Fwd: Re: [Fedora-spins] [spin-kickstarts] +nm-applet

[Rex Dieter]

Rahul shared some of the same concern that Kevin did about this recent 
change I made.

I have to admit, I share some of the same pragmatic sentiments that 
Rahul does (esp in areas where stability/features are even wider, like 
with kpackagekit).

Comments?

-- Rex

-------- Original Message --------
Subject: Re: [Fedora-spins] [spin-kickstarts] +nm-applet
Date: Mon, 19 Jul 2010 02:33:52 +0530
From: Rahul Sundaram 
To: The Spin Special Interest Group mailing list 

CC: Rex Dieter

On 07/19/2010 01:18 AM, Rex Dieter wrote:
> +# provide nm-applet as fallback in cases where knm/nm-plasmoid fails
> +NetworkManager-gnome

I assume this requires manual reconfiguration by the user.  Couldn't knm
or nm-plasmoid whichever one is the future for KDE just be fixed to
support everything nm-applet does?  If you don't have feature parity,
you should just bite the bullet and continue to include nm-applet by
default and ignore the purity angle.   Including both is not the right
approach IMO.

Rahul

[Fedora-spins] [spin-kickstarts] +nm-applet

[Anoop]

On Mon, Jul 19, 2010 at 7:13 PM, Rex Dieter  wrote:
> Rahul shared some of the same concern that Kevin did about this recent
> change I made.
>
> I have to admit, I share some of the same pragmatic sentiments that
> Rahul does (esp in areas where stability/features are even wider, like
> with kpackagekit).
>
> Comments?

I am using NM plasmoid and so for it has worked wonderfully well for
me. I use mobile, wireless and Wired connections with different
profiles.

Thanks,
Anoop
> -- Rex
>
> -------- Original Message --------
> Subject: Re: [Fedora-spins] [spin-kickstarts] +nm-applet
> Date: Mon, 19 Jul 2010 02:33:52 +0530
> From: Rahul Sundaram 
> To: The Spin Special Interest Group mailing list
>
> CC: Rex Dieter
>
> On 07/19/2010 01:18 AM, Rex Dieter wrote:
> > +# provide nm-applet as fallback in cases where knm/nm-plasmoid fails
> > +NetworkManager-gnome
>
> I assume this requires manual reconfiguration by the user.  Couldn't knm
> or nm-plasmoid whichever one is the future for KDE just be fixed to
> support everything nm-applet does?  If you don't have feature parity,
> you should just bite the bullet and continue to include nm-applet by
> default and ignore the purity angle.   Including both is not the right
> approach IMO.
>
> Rahul
> _______________________________________________
> kde mailing list
> [e-mail]
> https://admin.fedoraproject.org/mailman/listinfo/kde
> New to KDE4? - get help from http://userbase.kde.org

[Michal Hlavinka]

On Monday, July 19, 2010 15:43:14 Rex Dieter wrote:
> Rahul shared some of the same concern that Kevin did about this recent
> change I made.
>
> I have to admit, I share some of the same pragmatic sentiments that
> Rahul does (esp in areas where stability/features are even wider, like
> with kpackagekit).
>
> Comments?

my gf uses knetworkmanager and she does not care, because does not need to 
know there is something like that at all, so knm is enough for her

on the other hand I'm using nm because knm-vpnc bug for askpass and more 
importantly because knm vpn is missing feature "ipv4 : routes: [ ] Use this 
connection only for resources on its network" which is very important for me 
because I don't wont to have "local" internet radio routed twice over the 
ocean.

Michal
> -- Rex
>
> -------- Original Message --------
> Subject: Re: [Fedora-spins] [spin-kickstarts] +nm-applet
> Date: Mon, 19 Jul 2010 02:33:52 +0530
> From: Rahul Sundaram 
> To: The Spin Special Interest Group mailing list
>
> CC: Rex Dieter
>
> On 07/19/2010 01:18 AM, Rex Dieter wrote:
> > +# provide nm-applet as fallback in cases where knm/nm-plasmoid fails
> > +NetworkManager-gnome
>
> I assume this requires manual reconfiguration by the user.  Couldn't knm
> or nm-plasmoid whichever one is the future for KDE just be fixed to
> support everything nm-applet does?  If you don't have feature parity,
> you should just bite the bullet and continue to include nm-applet by
> default and ignore the purity angle.   Including both is not the right
> approach IMO.
>
> Rahul
> _______________________________________________
> kde mailing list
> [e-mail]
> https://admin.fedoraproject.org/mailman/listinfo/kde
> New to KDE4? - get help from http://userbase.kde.org

[Markus Slopianka]

I had no major problems with KNM4, but I keep using nm-applet, because it can 
import CiscoVPN config files and I'm too lazy to enter the settings by hand.

Markus

On Monday 19 July 2010 15:43:14 Rex Dieter wrote:
> Rahul shared some of the same concern that Kevin did about this recent
> change I made.
>
> I have to admit, I share some of the same pragmatic sentiments that
> Rahul does (esp in areas where stability/features are even wider, like
> with kpackagekit).
>
> Comments?
>
> -- Rex
>
> -------- Original Message --------
> Subject: Re: [Fedora-spins] [spin-kickstarts] +nm-applet
> Date: Mon, 19 Jul 2010 02:33:52 +0530
> From: Rahul Sundaram 
> To: The Spin Special Interest Group mailing list
>
> CC: Rex Dieter
>
> On 07/19/2010 01:18 AM, Rex Dieter wrote:
> > +# provide nm-applet as fallback in cases where knm/nm-plasmoid fails
> > +NetworkManager-gnome
>
> I assume this requires manual reconfiguration by the user.  Couldn't knm
> or nm-plasmoid whichever one is the future for KDE just be fixed to
> support everything nm-applet does?  If you don't have feature parity,
> you should just bite the bullet and continue to include nm-applet by
> default and ignore the purity angle.   Including both is not the right
> approach IMO.
>
> Rahul
> _______________________________________________
> kde mailing list
> [e-mail]
> https://admin.fedoraproject.org/mailman/listinfo/kde
> New to KDE4? - get help from http://userbase.kde.org

[Dennis Gilmore]

On Monday, July 19, 2010 08:43:14 am Rex Dieter wrote:
> Rahul shared some of the same concern that Kevin did about this recent
> change I made.
>
> I have to admit, I share some of the same pragmatic sentiments that
> Rahul does (esp in areas where stability/features are even wider, like
> with kpackagekit).
>
> Comments?
>
> -- Rex
>
> -------- Original Message --------
> Subject: Re: [Fedora-spins] [spin-kickstarts] +nm-applet
> Date: Mon, 19 Jul 2010 02:33:52 +0530
> From: Rahul Sundaram 
> To: The Spin Special Interest Group mailing list
>
> CC: Rex Dieter
>
> On 07/19/2010 01:18 AM, Rex Dieter wrote:
> > +# provide nm-applet as fallback in cases where knm/nm-plasmoid fails
> > +NetworkManager-gnome
>
> I assume this requires manual reconfiguration by the user.  Couldn't knm
> or nm-plasmoid whichever one is the future for KDE just be fixed to
> support everything nm-applet does?  If you don't have feature parity,
> you should just bite the bullet and continue to include nm-applet by
> default and ignore the purity angle.   Including both is not the right
> approach IMO.
>
> Rahul

While travelling at the moment. im realising again how horrible the user 
experience of KNM is. Connecting to a new wireless network is way more work 
that it should be. At least for me clicking on a network in the plasmoid does 
not correctly bring up the new network configuration dialog.  though really it 
should just prompt  for the password and offer to save in kwallet or not.  but 
i guess that comes back to the bug that knetworkmanager just doesnt know how 
to give you a dialog to prompt for a password. even though the ui says it can.

My recomendation is to use nm-applet only.  Im currently running the plasmoid 
on rawhide.

Dennis