
Hello, I don't think any of the tooltips is needed, see comments inline. Same arguments go for bonds on the left side of the dialog, which so far seem to have been overlooked. On 20/09/13 23:18, Malini Rao wrote:
Hi,
Here is a solution recommendation for Bug 984737 - usability: webadmin difficulty in assigning client ip, no gateway possible". Please provide any feedback. Here is a brief flow and description -
Host Network- Normal.png represents the Host network as it displays regularly - i.e, when the user is not interacting with it in any way. User may roll over any of the blocks in the network diagram
Host Network- Non-specific roll over v2.png - When the user mouses over any given block/entity in the network diagram in a non-specific area ( i.e within the box but not on the gear icon), details about that entity are available. Also a Gear icon displays next to the name of the entity to indicate some actions are available.
In the original thread it was all but settled that the information displayed in this tooltip is useless. I think one tooltip is enough over a single GUI item. That being said, since I think the other tooltip should be dropped as well (see comment below), if any tooltip is kept it should be this one, perhaps with other fields (e.g. IP address).
Host Network- Actions menu.png - When the user mouses over the gear icon, the action menu displays and any other rollover display is replaced with this menu.
Why an actions menu? The only action we needed here was edit. There already exists an action menu upon right-click. The original problem was the visibility/comprehensibility of the pencil icon. If the assumption is that the gear icon attracts enough attention to hover over, then it definitely attracts enough attention to be clicked and might as well just serve as an edit button with a different icon.
Rationale: The basic view is kept uncluttered so that the user can focus on the relationships. Upon mouseover, the details show up as it does today but the action (gear) icon is located prominently next to the name of the entity and it remains in view for the entire time the mouse is over the entity block or the details panel to maximize discoverability. A more specific mouse over event is designed to present the menu of actions available in a more sizable widget upon demand.
Thoughts?
Thanks Malini
Lior.