Hi,
On Tue, 2011-10-18 at 10:25 +0200, Daniel Wagner wrote:
> The thing my application wants to do is the have
> some status information towards the user what is happening.
I'm not sure applications actually want/need this. These state
transitions cause unnecessary wakeups for apps that just want to know
when they are connected to the 'net.
> So think of
> this: the user clicks on the connect button and you want to inform him
> that something is happening (drawing some animation).
I'm quite sure most of the apps don't have an UI like this. I do think
that in your area of implementation there might be a need for some
status in the application(s), since I might believe it to be fullscreen
or limited in other ways that there is no separate status area visible.
I'd move away the intermediate status update parts from the Session API
and add them to e.g. the Manager API (or Technology...?). In there there
already is a 'State' attribute which would make a really good UI spinner
modified with the states proposed here. Thus the applications only
caring about a Session would have a clean API, and the UI ones would
listen to the additional state information.
Cheers,
Patrik
_______________________________________________
connman mailing list
[email protected]
http://lists.connman.net/listinfo/connman
