Patchwatcher is now working well enough to depend on, I think, but doesn't send email yet.
You should see your patch appear at http://kegel.com/wine/patchwatcher/results under a minute after you post, and if your patch is simple, test results should show up about ten minutes later. (Long patch series take longer, since patchwatcher runs the test suite after each patch in the series.)
Today's changes (from http://code.google.com/p/winezeug/source/list ): - Update the dashboard immediately upon receiving patches. - Added qmgr timeout and winhttp:notification.c to blacklist.
Full blacklist at http://winezeug.googlecode.com/svn/trunk/patchwatcher/blacklist.txt Please fix your tests so I don't have to blacklist them. (The d3d tests should start passing once I move to the latest nvidia drivers, so don't worry about them.)
On Thu, 2008-11-06 at 08:32 -0800, Dan Kegel wrote:
You should see your patch appear at http://kegel.com/wine/patchwatcher/results
Very nice!
One suggestion that I have is changing the background color of the row on hover so you can easily match the result on the RHS to the Subject, right now that is a bit difficult to do visually on a wide-screen monitor.
On Thu, Nov 6, 2008 at 9:07 AM, Dimi Paun dimi@lattica.com wrote:
One suggestion that I have is changing the background color of the row on hover so you can easily match the result on the RHS to the Subject, right now that is a bit difficult to do visually on a wide-screen monitor.
Would you settle for static alternating colors? I'm kind of anti hover highlight.
On Thu, 2008-11-06 at 09:29 -0800, Dan Kegel wrote:
Would you settle for static alternating colors? I'm kind of anti hover highlight.
IIRC there was a recent study claiming that alternating row colors are not all that useful in practice, the on-hover has the advantage of focusing your attention only on the row that you care about.
But if you have a problem with that, static colors would be a step forward (and AFAIAC it would be fine).
-
Dan Kegel -
Dimi Paun