Since MeeGo uses Connman instead of Networkmanager to handle network connections, that means there is not (yet 😉 an user interface to control in right from the KDE workspaces.
If you happen to have one of the Desktop summit Exopc with the Contour user interface that there has been installed on several devices, here are some easy steps to get the MeeGo tablet Connman ui installed and be able to connect to a wireless network.
Ingredients
- A device running the Contour MeeGo ui
- An USB keyboard
- Either an USB ethernet adaptor (preferred) or a thumbdrive
recipe
- Open a konsole
- vim /etc/zypp/repos.d/ and replace the urls there with http://download.meego.com/MeeGo/snapshots/stable/1.2.0.90/latest/repos/oss/ia32/packages/ (unfortunately repos url changed since the image was built, with newer releases should be smoother)
- If you have the ethernet usb adaptor: zypper install meego-ux-settings
- If you don’t have it, download from the url above the following files on a thumbdrive:
- bluetooth-qt
- connman-qt
- connman-qt-declarative
- libofono-qt
- meego-ux-settings
- meego-ux-settings-libsettings
- mobile-broadband-provider-info
- syncevolution-qt-dbus
- From the device, as root, rpm -Uvh /media/whatever/*.rpm
After having installed everything on the device, start the settings application with meego-qml-launcher –app meego-ux-settings. After it connects to your access point, it will automatically reconnect on next startup, so no need to launch the settings app again until you want to change access point.
Don’t forget the two getting started IRC session that will be held this week, where we can help on this and other issues
A plasmoid that can manage connections using Connman is planned shortly 😉
Is there any plan for a Connman Solid backend making it manageable from Plasma?
If I understand it correctly, a solid backend would also be necessary for apps to know whether the computer is online or offline.