Note that there are some explanatory texts on larger screens.

plurals
  1. POInstrumenting a UI
    text
    copied!<p>How are you instrumenting your UI's? In the past I've read that people have instrumented their user interfaces, but what I haven't found is examples or tips on <em>how</em> to instrument a UI.</p> <p>By instrumenting, I mean collecting data regarding usage and performance of the system. A MSDN article on Instrumentation is <a href="http://msdn.microsoft.com/en-us/library/x5952w0c.aspx" rel="nofollow noreferrer" title="here">http://msdn.microsoft.com/en-us/library/x5952w0c.aspx</a>. I would like to capture which buttons users click on, what keyboard shortucts they use, what terms they use to search, etc.</p> <ul> <li>How are you instrumenting your UI?</li> <li>What format are you storing the instrumentation?</li> <li>How are you processing the instrumented data?</li> <li>How are you keeping your UI code clean with this instrumentation logic?</li> </ul> <p>Specifically, I am implementing my UI in WPF, so this will provide extra challenges compared to instrumenting a web-based application. (i.e. need to transfer the instrumented data back to a central location, etc). That said, I feel the technology may provide an easier implementation of instrumentation via concepts like attached properties.</p> <ul> <li>Have you instrumented a WPF application? Do you have any tips on how this can be achieved?</li> </ul> <hr /> <p>Edit: The following blog post presents an interesting solution: <a href="https://blog.pixelingene.com/2008/08/techniques-for-ui-auditing-on-wpf-apps/" rel="nofollow noreferrer">Pixel-In-Gene Blog: Techniques for UI Auditing on WPF apps</a></p>
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload