Marcel Holtmann <[email protected]> writes: > Hi Aapo,
Hi Marcel and Aapo, >> We are working at Nokia on porting existing (MeeGo Touch based) Internet >> connectivity UIs to support Connman. Previously our Internet UI has >> supported Maemo specific connection daemon called ICd2. >> >> Most parts of the Connman API look good and clear, but couple of >> questions popped up today when going through our own worklist: >> >> * Is there indication when scanning starts or ends in Connman? I'm >> looking for something similar to Bluez Adapter API >> "Discovering" property (but of course for e.g. WLAN scan instead of >> BT discovery). I could not find anything similar when reading the >> API docs myself. > > there used to be an indication, but we removed that one. I also would need support for showing scanning status. > The question really is why do you want something like this for WiFi. In > the future we will have wpa_supplicant doing proper background scanning > for nice roaming capabilities. So essentially ConnMan should not ever > trigger a scan again. My plan is to use scanning indication to warn the user that the available network list in a dialog will be updated soon. Showing some scanning animation would do that. >> * Is there any possibility to rename a service? Currently Service >> "Name" property has been marked as [readonly] in the API >> documentation. In this case I would expect to find e.g. "Alias" >> property (like in Bluez Device API), but I was unable to find one. I >> know at least some cases when the end user can receive a WLAN AP >> from ISP having semi-random SSID. In this cases it IMHO would be >> nice to provide way for the user to rename or assign an alias for >> the WLAN service. > > There is no such feature right now. Do you really wanna expose that in > the user interface. I definitely see the use for this. > It makes only sense to add such a thing if the UI and then in the end > the user really wants to use this feature. > > Even with BlueZ I always question myself if it was a good idea. But then > for BlueZ the device name is shown in a few more places, so I can argue > for it. However with WiFi, why bother, that access point name should > never really be presented to the user in any other application than the > settings/selector UI. Like Aapo said, a cryptic SSID is one good example. Also there's a case if there are two networks with same SSID but different encryption settings. I have this case already with my n900: one is open network, the other one uses WPA-PSK and both have the same SSID. It would be really nice to have different names for these two networks. -- Kalle Valo _______________________________________________ connman mailing list [email protected] http://lists.connman.net/listinfo/connman
