Work-in-progress - Non real-time analyzer UI #25
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There's so much stuff that I want to be able to look at when debugging reactive applications. While the LiveView tool works decently for small apps or demo/training purposes it's simply not able to keep up with the amount of information from a highly reactive app such as GitHub for Windows. While talking with @ammeep about this she convinced me that there's some really cool things we could do if we dropped the real-time requirement. This doesn't mean dropping the real time app, I'd like to keep it alive but create a new non-realtime analyzer app that would address the performance problems of a real-time app (no ui thread contention etc).
Not only will this be good for the analysis part, it will also increase performance for apps being instrumented. Rather than communicating with a visualizing app we can now stream all events to disk with minimal overhead.
Design
I'm no where near finished here but one thought I had was to play with a tile-ish app, something like this
Diving deeper would allow for filtering in the timeline
Don't worry. I'll ask some actual designers for input before this is finalized.
Other things
I'd like to be able to detect common inadvisable patterns such as over eager/unnecessary scheduling on the UI thread etc.