Skip to content
New issue

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

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Automatic refresh #295

Closed
dnrce opened this issue Jun 25, 2014 · 6 comments
Closed

Automatic refresh #295

dnrce opened this issue Jun 25, 2014 · 6 comments
Milestone

Comments

@dnrce
Copy link
Member

dnrce commented Jun 25, 2014

Migrated from the original issue at https://www.assembla.com/spaces/tracks-tickets/tickets/295

I'd love to see the ability to set a META HTTP-EQUIV=REFRESH value on the main page. It's necessary, in my opinion, now that we have an API that allows users to add new tasks via interfaces other than the web page itself. For instance, if I add a few new things via a Quicksilver command, and then later return to my main Tracks page, which has been sitting in the background somewhere, those new items won't be visible until I refresh the page. As a result, I sometimes forget that such items are there for quite a while. But if the page refreshed itself automatically at some pre-set interval, such items would eventually show back up.

I see this as being implemented by a new preference. By default, the refresh would be set to '0,' which would mean not to include a refresh tag on the main page. A user could enter a numeric value equal to the number of minutes between refreshes. (When implementing the tag, this numeric value would have to be multiplied by 60, as the refresh tag counts in seconds rather than minutes.)

Originally reported by Anonymous on May 5, 2006 at 23:19:53 (+0800)

@dnrce
Copy link
Member Author

dnrce commented Jun 25, 2014

On July 7, 2006 at 22:34:47 (+0800), Anonymous commented:

Fixed in [290]

@dnrce
Copy link
Member Author

dnrce commented Jun 25, 2014

On July 7, 2006 at 23:40:14 (+0800), bsag commented:

I worry a little about this approach. What if you're in the middle of filling in a new action form when the refresh hits? Also, what happens to any flash messages that have been shown? It seems that a javascript that can set timeout on idle might be a better implementation.

@dnrce dnrce added this to the Someday/Maybe milestone Jun 25, 2014
@dnrce
Copy link
Member Author

dnrce commented Jun 25, 2014

On July 7, 2006 at 02:01:27 (+0800), bsag commented:

I stupidly hadn't thought about that. Since I'm rubbish at javascript, can I assign it to you? At least the user.preferences part of it is done, at least ;-). And the default is zero, so people updating the trunk won't see any difference in behaviour by default.

Perhaps it could also be done by using a periodically_call_remote?

@dnrce
Copy link
Member Author

dnrce commented Jun 25, 2014

On July 7, 2006 at 03:17:11 (+0800), Anonymous commented:

Sure. I'll take it on.

@dnrce
Copy link
Member Author

dnrce commented Jun 25, 2014

On July 7, 2006 at 22:57:37 (+0800), Anonymous commented:

hasn't this been done in [290] and [291]?

@dnrce dnrce changed the title Meta Refresh Prefrence on Main Page? Automatic refresh Jul 2, 2014
@mattr-
Copy link
Member

mattr- commented Dec 1, 2018

If it's not already done (which it could be, based on the existing comments), I don't intend on implementing this.

@mattr- mattr- closed this as completed Dec 1, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants