http://defect.opensolaris.org/bz/show_bug.cgi?id=11260
--- Comment #5 from Darren Kenny <dkenny at opensolaris.org> 2009-09-11 15:44:44 UTC --- There are quite a lot of states that can be represented, especially since this version of NWAM can have a lot more simultaneous active interfaces (the existing version can have only 1). I suppose the user really doesn't need to know the full state of the interfaces here, just a summary might suffice. If more information is needed the properties app can be run which has a status page with more information about active interfaces. I guess all that's need to know are things like: 1) Connected or not (i.e. if the expected set of i/f's are working), and could consist of things like: - Connected to wireless XXXXXXX - Connected to wired - both of the above? - Using Location XXXX and Profile XXXXX 2) If not connected, a reason why, this could be something like: - DHCP timeout - No cable connected - Need to select Wifi Network - Need to provide Wifi Key - No wireless APs visible 3) NWAM is not active Possibly these are the main states, but calculating the value could be expensive (and maybe prone to miscalculation). I'm starting to think that we could have two modes of operations for the tooltip - rich and text only, configured by a GConf key - some people might prefer a text summary... This would allow for a switchable mechanism, but I don't think that it should be based solely on whether a11y is enabled or not, since not a11y is reliant on the Atk name/description. -- Configure bugmail: http://defect.opensolaris.org/bz/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the QA contact for the bug. You are the assignee for the bug.
