Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Already on GitHub? Sign in to your account

Indicate whether or not the crawler is currently running in the app UI #1482

Open
ginatrapani opened this Issue Feb 7, 2013 · 2 comments

Comments

Projects
None yet
3 participants
Owner

ginatrapani commented Feb 7, 2013

Spin the "Update Data" button while crawl is in progress in the status bar.

To do this, let's set up a "heartbeat" page that returns the status of the crawler (running or not) in JSON. This file should check if the crawler mutex is set or not and return accordingly.

Then, use JavaScript to check the heartbeat every 5 seconds and change the spinner/button appropriately depending on state.

Perhaps when heartbeat indicates the crawl has completed, display "Refresh the page with new data" notification atop the stream.

su commented Feb 10, 2013

I don't think much needs to happen in terms of design; the current icon's standard enough. I'd just spin it if a crawl is active and use a bit of JS to temporarily strip the link. (No point letting the user click anyway and go to a page that's going to tell them again that they're wasting their time.) If animation's too obnoxious, maybe just switching to a disabled/grey appearance, though I'd think that would look like "unavailable" rather than "I'm already working on it."

Is this something that can only be tested on pageload, or is a JS-based "heartbeat" function feasible so as to catch crawls that start after I'm already viewing and/or stop the animation once done?

Owner

anildash commented Feb 11, 2013

Yeah, with the new Font Awesome setup, we can actually animate the refresh button to spin with just a CSS class change, so design-wise the impact is really minimal; It's all about implementing a simple way to tell the front-end to make that change.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment