On Thu, Jun 17, 2010 at 9:19 AM, <[email protected]> wrote: [...] >> * does it work with qt 4.6.2 + qt-mobility 1.0.0? > > I have not completed the back-port to mobility.
Is it planned or in general distros should we wait for qt 4.7 to land? >> * is it possible to create a complete/standalone wifi manager with it? >> (create new networks, asking for psk or EAP parameters and so on?) [...] > There is qconnmanservice_linux.cpp that you can use in your own projects. > It's a wrapper around connman that uses QDbus. I have also written a tray > icon app that can create connections using it. Good I'll give it a try too. On Thu, Jun 17, 2010 at 10:14 AM, Thiago Macieira <[email protected]> wrote: > Em Quinta-feira 17 Junho 2010, às 09:19:21, [email protected] escreveu: [...] >> Not necessarily with this plugin. Bearermanagement can only start and stop >> already configured connections. > > It's also not the objective of the Bearer Management API to do system > configuration. The objective is for applications to declare that they would > like a network connection to be set up, and also to find out about changes to > it. Some applications may modify their networking behaviour depending on > whether you're on GPRS/3G or WiFi. Others also do that accoring to power > state. > > System configuration belongs to the system and that includes whether the > requests for bringing network bearers up or down will be honoured. Why not? such type of abstraction should be perfect for the qt/qt-mobility objective and bearer plugins may declare or not, with a particular capability, if they are able to create/modify network configurations (simply my suggestion is write system dialogs or a "super connection manager gui" with qt-mobility too and reuse them everywhere). Regards Niko _______________________________________________ MeeGo-dev mailing list [email protected] http://lists.meego.com/listinfo/meego-dev
