Not wanting to spoil the enthusiasm for the creation of new badges for runtimes (or for that matter any other feature request), but I think that getting the PSW (project-settings-webpage) synchronized with the new app_config -- may get more contribution* from existing crunchers with the possibility of also attracting new crunchers to the WCG fold -- by way of an easy-to-use, WYSIWYG, or otherwise an intuitive mechanism for ordering/requesting** WUs.

Notes:
*else minimize wastage from crunchers (existing or new) who may not have the time, nor want to invest in the time and the attendant effort and expense -- to understand how to order/request for WUs. For example, I have unavoidably, and much to my dislike -- thrown away a considerable amount of doneWUs attendant to my efforts to understand the intricacies of how the app_config (vis-a-vis the PSW) work together.
**The current mechanism for a cruncher to order/request WUs is by way of the PSW. How the WUs are scheduled/ordered to run on a client's machine is by way of the (new) mechanism in app_config. Crunchers who may not be aware of the app_config are left with the PSW to 'struggle' with. I say 'struggle' because a cruncher will have to go through a circuitous loop before getting exactly what that cruncher may have wanted. There should be no such issues if purely for-CPU-only WUs are involved; the 'struggle' only happens once that cruncher wants to involve for-the-GPU WUs. And where does the growth potential point to? GPUs, that's where! But the current form of the WU-ordering-mechanism (PSW vis-a-vis app_config) doesn't make it easy as much as possible for as wide and as many of the total-cruncher-population (exsisting, new, and potential) -- to get into the WCG GPU-computing game.
;
; andzgridPost#761
;

Fortunately there is. Via app_config.xml. We discussed this recently here.

Cheers

As far as I tested it, nope. The cache stays as it was prior to changes.

Just a bump here, folks... also a Happy New Year 2013 to all !
;
; andzgridPost#777
;