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 metherid@gmail.com To: The Spin Special Interest Group mailing list spins@lists.fedoraproject.org CC: Rex Dieter rdieter@fedoraproject.org
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