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

Should pressing the refresh button on recordings or upcoming trigger a fresh download whether or not the stored etag returns a HTTP 304? #122

Closed
dmfrey opened this issue Feb 27, 2013 · 6 comments

Comments

@dmfrey
Copy link
Contributor

dmfrey commented Feb 27, 2013

Just wondering what the app should do in thus case.

@pot8oe
Copy link
Contributor

pot8oe commented Feb 27, 2013

How about leaving refresh as it stands and add a reset menu item. Reset
would clear and repull everything. does that make sense?

@dmfrey
Copy link
Contributor Author

dmfrey commented Feb 27, 2013

That would work. Is reset the appropriate term here?
On Feb 26, 2013 10:21 PM, "Thomas G. Kenny Jr" [email protected]
wrote:

How about leaving refresh as it stands and add a reset menu item. Reset
would clear and repull everything. does that make sense?


Reply to this email directly or view it on GitHubhttps://github.com//issues/122#issuecomment-14154157
.

@pot8oe
Copy link
Contributor

pot8oe commented Feb 27, 2013

I don't know. Reset was the first thing that came to mind. Clear data?
On Feb 26, 2013 10:25 PM, "Daniel Frey" [email protected] wrote:

That would work. Is reset the appropriate term here?
On Feb 26, 2013 10:21 PM, "Thomas G. Kenny Jr" [email protected]
wrote:

How about leaving refresh as it stands and add a reset menu item. Reset
would clear and repull everything. does that make sense?


Reply to this email directly or view it on GitHub<
https://github.com/MythTV-Clients/MythTV-Android-Frontend/issues/122#issuecomment-14154157>

.


Reply to this email directly or view it on GitHubhttps://github.com//issues/122#issuecomment-14154412
.

@billmeek
Copy link
Contributor

Need an update from the developers. I'd suggest making the Refresh icon trigger a
fresh download. As opposed to adding another menu item. There should be no
need to refresh unless there's something's missing in the current display or if the
user knows that something has changed in Upcoming/Recordings.

@pot8oe
Copy link
Contributor

pot8oe commented Sep 13, 2013

I agree. Fresh download!

-Tom

On Fri, Sep 13, 2013 at 4:50 PM, billmeek [email protected] wrote:

Need an update from the developers. I'd suggest making the Refresh icon
trigger a
fresh download. As opposed to adding another menu item. There should be no
need to refresh unless there's something's missing in the current display
or if the
user knows that something has changes in Upcoming/Recordings.


Reply to this email directly or view it on GitHubhttps://github.com//issues/122#issuecomment-24423632
.

@dmfrey
Copy link
Contributor Author

dmfrey commented Sep 13, 2013

This will be pretty easy to fix. Just delete the etag for the respective
service endpoint when the refresh button is pressed.

I will take a look tonight.
On Sep 13, 2013 4:55 PM, "Thomas G. Kenny Jr" [email protected]
wrote:

I agree. Fresh download!

-Tom

On Fri, Sep 13, 2013 at 4:50 PM, billmeek [email protected]
wrote:

Need an update from the developers. I'd suggest making the Refresh icon
trigger a
fresh download. As opposed to adding another menu item. There should be
no
need to refresh unless there's something's missing in the current
display
or if the
user knows that something has changes in Upcoming/Recordings.


Reply to this email directly or view it on GitHub<
https://github.com/MythTV-Clients/MythTV-Android-Frontend/issues/122#issuecomment-24423632>

.


Reply to this email directly or view it on GitHubhttps://github.com//issues/122#issuecomment-24423955
.

@dmfrey dmfrey closed this as completed in 609e482 Sep 14, 2013
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants