Miguel Petersen
Miguel Petersen
Code is great, when people can understand it. So, let's make an effort to improve documentation. The following list will be extended over time: - [ ] Instruction set exposed...
While extending unit tests / TDD is preferable, nothing quite beats mature applications. Automated testing of application suites has immense benefits, and reduces manual labor on change validation.
(First official bug report 🥳, filing on behalf of an external party) The connection dialogue row-wise styling can be confusing. Below, the first entry appears selected, upon clicking connect nothing...
Online documentation is great until you're not online, provide some kind of embedded documentation in the UI.
The settings menu desperately needs a styling pass, especially the application list.
Message counters as of themselves are not that interesting, what, however, is interesting is: - Messages per second - Messages per "frame" (would have to answer what a frame is)...
While the instrumentation may change quite often, the initial parsing rarely does. The prototype layer made use a global cache to speed up instrumentation times, we need something similar here.
Shader export data is typically a repeated stream of a few unique messages, there is a lot of benefit in rolling a custom compression scheme for it. Additionally, this would...
Dynamic message stream growth in the shader export streamer seems to be broken.