Excerpts from Jerry Vonau's message of Mon Mar 07 09:51:30 +0100 2011: > Yes, think that would be a good idea, with this method connections.cfg > can be empty. Perhaps network.py can just use/create the needed file > for /etc/NetworkManager/system-connections/ or make that an option > available in control panel.
Using system instead of user settings in Sugar has been planned for some time now [1], but I didn't get around to working on it. The first beta of NetworkManager 0.9 has been released [2] a few days ago. As of that version, the distinction between system and user settings is gone for good [3], so it makes more sense to migrate [4] to 0.9 right away instead of moving to system settings first. As part of the 0.9 migration I'd like us to show configured connections in addition to the currently visible access points. This should help users working in less-than-perfect environments (disabled beacons, VPNs, access points on different sites that need different credentials but have the same SSID, etc.). We should also try to move our Ad Hoc auto-connect logic into NetworkManager. Not only would it make our code simpler and easier to debug, but non-Sugar users would benefit from the automatic "under the tree" networking as well. Even Mac OS X seems to have something similar to automatic Ad Hoc networking + link-local collaboration now (called AirDrop [5]). Sascha [1] https://bugs.sugarlabs.org/ticket/1884 [2] http://mail.gnome.org/archives/networkmanager-list/2011-March/msg00020.html [3] http://live.gnome.org/NetworkManager/ApiSimplify [4] http://projects.gnome.org/NetworkManager/developers/migrating-to-09/ [5] http://www.apple.com/macosx/lion/ -- http://sascha.silbe.org/ http://www.infra-silbe.de/
signature.asc
Description: PGP signature
_______________________________________________ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel