[Info Bubble] Show telemetry values in info bubbles

[VWoeltjen]

Show telemetry values in info bubbles for domain objects which have associated telemetry. See UI docs linked from WTD-615

Migrated from: WTD-1240
Originally created: Fri, 5 Jun 2015 09:29:17 -0700
Updated: Thu, 14 Jan 2016 16:57:19 -0800

[hudsonfoo]

@VWoeltjen the UI docs link isn't working for me. Is it still up?

[VWoeltjen]

@charlesh88 - I looked through the UI docs to grab some relevant mockups, but I couldn't find the section that described info bubbles. Do you have these?

[charlesh88]

Info bubbles were in the older UI for WARP, v1.5.2.2. I pulled that page out and added it to the modern UI sketches (https://drive.google.com/open?id=0B0v27OM1JkSeR001RFJZMk43QVk) and added a bit more detail for Value. @hudsonfoo Let me know if you have issues getting to that link.

Note these important points:

• Value must ONLY be displayed for objects for which it's appropriate - this is important so that users can discern between objects for which "value" makes sense (telemetry, clocks, timers, etc.) and we do or don't have data, and those where it doesn't (Display Layouts, Timelines, Activities, Folders, etc.).
• There is a more complex case for containers that are able to hold multiple telemetry elements when they only happen to holding one element - should we show value? My preference would be no; let's keep this simple for now and define when Value appears or doesn't based on object type.

[VWoeltjen]

Open question: Should this telemetry value update live while the info bubble is showing, or should it be a timestamp/value pair frozen in time at the moment the hover occurred? Want to consult with @Costigan and @RCarvalhoNASA

[RCarvalhoNASA]

So I would like a mixed answer on this one, or perhaps there is a different feature which overlaps to resolve my split. For most uses of this bubble, show the current value, as it changes (unless the performance becomes an issue). However, if one is hovering over a plot or scrolling table, the bubble should show the value at that point, not the current value.

[Costigan]

I think the broad question is this:

What information about a telemetry point should be quickly accessible when the user has browsed to a point in the dictionary?

I think that the answer should include:

1. All static information in the dictionary, including its full name, type, doc string ...
2. Its current value in all encodings, e.g., raw, engineering and any others
3. A summary of its recent history (min, max, rate-of-change ...)
4. A plot of its recent history
5. Some way to monitor its value as it changes

How many of these things should be implemented with an info bubble is a design choice. Clearly, not all should be.

In ASIST, an info bubble is emulated via the user clicking on the name of a point seen on any page. This would create a small window that contains 1, 2 and 5. The window had buttons for 3 and 4. The window would remain until dismissed, even if other, similar windows were opened on other telemetry points. So these windows could be opened as tiny, temporary telemetry pages and kept open until they were no longer needed.

An info bubble is different in that it's ephemeral. For that reason, I think it's fine for the value(s) shown to not change after the bubble is created. If you want to monitor the value as it changes, your mouse is constrained to stay within the bubble. This can be awkward, and I think that implementing that function (temporary monitoring of a changing value) should be achieved in some other way.

•      Mark
  

From: RCarvalhoNASA [mailto:[email protected]]
Sent: Tuesday, October 25, 2016 11:38 AM
To: nasa/openmct
Cc: Shirley, Mark H. (ARC-TI); Mention
Subject: Re: [nasa/openmct] [Info Bubble] Show telemetry values in info bubbles (#542)

So I would like a mixed answer on this one, or perhaps there is a different feature which overlaps to resolve my split. For most uses of this bubble, show the current value, as it changes (unless the performance becomes an issue). However, if one is hovering over a plot or scrolling table, the bubble should show the value at that point, not the current value.

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://github.com//issues/542#issuecomment-256132387, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AH0ZVlL6ZjO3JtoySz9q_zOi_v2k8ZT2ks5q3kyYgaJpZM4HJ6An.

[charlesh88]

The scope of this issue should (as a Help Wanted) should address the behavior of integrating telem values in the current Info Bubble design as it applies to domain objects - there is a different approach for plot hovering in the current plot UX design in progress.