<table><tr><td style="">rjvbb added a comment.
</td><a style="text-decoration: none; padding: 4px 8px; margin: 0 8px 8px; float: right; color: #464C5C; font-weight: bold; border-radius: 3px; background-color: #F7F7F9; background-image: linear-gradient(to bottom,#fff,#f1f0f1); display: inline-block; border: 1px solid rgba(71,87,120,.2);" href="https://phabricator.kde.org/D8211" rel="noreferrer">View Revision</a></tr></table><br /><div><div><p>KUIServerJobTracker documentation, here in a detached window on Mac using QTB:<br />
<a href="https://phabricator.kde.org/F5439007" style="background-color: #e7e7e7;
border-color: #e7e7e7;
border-radius: 3px;
padding: 0 4px;
font-weight: bold;
color: black;text-decoration: none;" rel="noreferrer">F5439007: Screen Shot 2017-10-19 at 23.46.14.png</a></p>
<p>Text is too large and layout too spacey for my taste, but that aside the documentation is perfectly usable.</p>
<p>And Christoph's feedback is exactly why this shouldn't be a one-man job: who'd have thought of testing with another colour palette? Now I understand why the original code imposes a simple B&W CSS sheet. Getting QTB to do the same shouldn't be hard: I just need to return the desired CSS from the loadResource() overload, instead of the actual CSS.</p></div></div><br /><div><strong>REPOSITORY</strong><div><div>R32 KDevelop</div></div></div><br /><div><strong>REVISION DETAIL</strong><div><a href="https://phabricator.kde.org/D8211" rel="noreferrer">https://phabricator.kde.org/D8211</a></div></div><br /><div><strong>To: </strong>rjvbb, KDevelop<br /><strong>Cc: </strong>croick, kossebau, aaronpuchert, flherne, arichardson, apol, kdevelop-devel, geetamc, Pilzschaf, akshaydeo, surgenight, arrowdodger<br /></div>