On 07/07/2009 02:32 PM, James Cammarata wrote:
Ok, I want to play with this so if I get anything /non-sucking/ I might check it in, if not, tis ok.
I will probably try to get it all packaged (for us, not Fedora) and spend most of my time seeing that this works.
--Michael
Yeah basically I've got it reading the files, sourcing the .js/.css files, and it pops up an alert with onload() and that's about it. We'll need to create a timer to check for alerts periodically, and come up with some way of storing alerts we've already gotten in a cookie or in the session so it doesn't constantly popup the same alerts. That shouldn't be too difficult though.
Ok, think I'm very close to having that.
I think a XMLRPC call on a timer to say "get alerts since ___" would work perfectly. (Would not need auth, so pretty simple, I think)
Maybe even we could say something like (in remote.py)
get_changes_from_hash(old_task_info) -> (new_task_info, array_of_alerts)
I'll see what I can get done.
If that happens, we can also make another system in the daemon for notifications, both global and to the user, to also be checked on the same timer.
Things like getting notifications when systems finish installing would be /slick/.
I'm excited about this.
--Michael