I sent the modified widget to you yesterday.

This widget is awesome. I tend to forget to check woot daily, having this widget means I never miss a good item!

That being said, I've noticed this widget takes an inordinately large amount of CPU time. I'm talking like anywhere from 10-20+% at ALL TIMES. Is there any reason it would be doing this? I've tested it on multiple computers, changed the settings of the widget, and tinkered with the widget engine itself, all to try bringing the cpu usage down some, to no avail.

Thanks… for any advice you've got, I really like the widget -- enough that even with the resources it uses it's always running anyway! More

E-mail me your version of the widget. I haven't had much of a chance to fool with the widget in a while, but I'll work on it.

Send to scoot241 AT gmail DOT com

Inspired by today/yesterday's Woot-Off, I spent some time playing around with this widget. I've made the following changes: Use the XMLHttpRequest object to get and read the woot RSS feed, added a request header to force it to always give a non-cached answer, made the request asynchronous so it doesn't hang the gui waiting for an answer, and tried to make the sold out logic work durring a Woot-Off (used the % sold). I also verified that the RSS feed is not updating the sold out st…atus correctly, so we will have to wait for woot to fix that. Not quite sure how to get this back into the published version or if Scott is even interested. I'll check back occasionally to see if Scott answers. More

"Sold out" has stopped for me as well -- but this is a very good and useful Widget.