Hi,
It looks nice, and it is great you are tackling this, here are some display-related ideas.
(1) The immediate thing that stuck out cosmetically was the visual clutter. I'm guessing some of this was AI-generated, which tends to make things visually OTT. I find myself stating to the AI "Do it like Apple might", to try to restrain it. Maybe consider reducing colors for instance, see overview.png, which wasn't drawn for this purpose but still looks clearer I think. Also you've got detail at the bottom-left, but also settings for those at the top. I understand that's a status bar at the bottom, but still, it is extra clutter that could be removed if you find some of that detail can be represented in other ways or is unnecessary. For example, is the text Done needed, and if it is, the green indicator seems unusual, maybe it should be grayed out, or changed to a tick to indicate success?
(2) Consider ability to reorganize the signals and decodes, for instance, personally I think bottom-up looks better, with the decodes above the signals.
(3) Take a look at oscilloscopes as well, just in case you see any ideas you wish to build on. Also, take a look at Wireshark (a very different app for different use-cases, but there are a few ideas to glean from it perhaps).
(4) The individual characters in the decode could look bigger/clearer, and I didn't understand the need for the single-quote marks around them.
(5) The time values should improve, it's hard to count tiny zeros, so maybe the values should be in msec in your example, e.g. 2 msec instead of 2000 us, i.e. change automatically to suit.
(6) Consider ability to segment-ize, e.g. if there are long delays between bursts of data. Then, your decoded data could allow you to thumb through pages of the data. An example is in the overview png, where a burst might be a high-level file operation. You'd have to use your judgement what techniques your app could use and expose to the user, to control how bursts are determined.
(7) I have not run your app so I don't know what keys/mouse operations there are, but ability to easily page through, or pan, and zoom would be important of course, ideally with keyboard shortcuts, and also with mouse.
(8 ) You might want more than two cursors (and maybe an improved way of displaying their detail, since you'll run out of space if sticking to the current way you've got on the right side area) and also indicate where they are in the zoomed-out view at the top, just so users can quickly approximately see where a cursor is in the entire file (to me the word marker feels more intuitive than cursor by the way).
Home
Help
Search
Login
Register
