will take some work and come later, but I love the idea. here is my note on it:
embed webbrowser control options:
• to website, or local html inside dSS client window, maybe do a default to local if not online.
• custom header area (above systeminfo frame) and possibly lower left details area.
• custom button action (to take over entire right display area: systeminfo frame + header)
• consider embedding full browser, explore options to use default (at least Chrome/FF) vs. just IE
• usage: promotions/purchase info/button (on free copies)/social media buttons/etc. via updating a page on their website
Of course there is one slight issue. the way I present a browser inside the app is by using a control that accesses a single IE .dll for the rendering functionality. The intent being that there is zero bloat and no chance of pre-loaded extensions/add-ons or even any real browser technologies being utilized, so malicious software or just plain broken components cannot ruin the experience. The side effect of not allowing most web stuff to 'work' is that of course, most web stuff won't work, so chances are you may get some site display issues, but surely the odds are some "script errors" and other things will pop up.
Ideally I need to investigate at least stopping the script error prompts. That is my preference. If not, I have seen methods of embedding a fully functional browser inside an application window, and maybe that is a better option at least for certain usage cases, like this one.