Skip to content

Conversation

@okan35
Copy link
Contributor

@okan35 okan35 commented Nov 20, 2020

What is it?

  • Bugfix (user facing)
  • Feature (user facing)
  • Codebase improvement (dev facing)
  • Meta improvement to the project (dev facing)

Description of the changes in your PR

Currently when we refresh what's new, we see only loading screen on main screen with number of videos loading and at the same time we can see this on notification.
I removed loading screen from main screen so while app is loading new videos, we can also browse and watch videos.We should not be waiting for videos to finish loading so we can watch video or check what we have in list of videos, this definitely was not a good idea so I changed this.
While videos load we can still check the content. And if the someone wants to see number of videos that are loading, he/she can do so by checking the notification.

Fixes the following issue(s)

APK testing

app-debug.zip

Due diligence

@B0pol
Copy link
Member

B0pol commented Nov 21, 2020

I really dislike this behaviour.

The loading screen is there to show the user it's loading and it's not frozen.

Now you don't know the progress, it refreshes when it's loaded and really feels "wow it didn't work, I'm going to press refresh button again" with about 50 subs.

On top of that, it seems you didn't read contribution guidelines, because you don't follow them

Send PR that only cover one specific issue/solution/bug. Do not send PRs that are huge and consists of multiple
independent solutions

Then why do you send a PR with an unecessary dependency on a pull to refresh PR?

If you want to add a feature or change one, please open an issue describing your change. This gives the team and community a chance to give feedback before you spend any time on something that could be done differently or not done at all. It also prevents two contributors from working on the same thing and one being disappointed when only one user's code can be added.

@okan35
Copy link
Contributor Author

okan35 commented Nov 21, 2020

I now see where you are coming from because if you click to refresh the feed it shows like there is nothing going on. But if you pull to refresh it shows you a loading icon until the process is done and after click or pull to refresh videos still load.

We can also add that small icon so people who dont pull to refresh but click to refresh can see what is going on.

As to issue part, this actually was in #3329, you can see my comment and I don't know why it was closed as the requests in that issue were not done yet and only implemented small part of it which is pull to refresh.

Also instead of opening new issue I added mine in the same issue as it is covered under improvement of refresh.

@opusforlife2
Copy link
Collaborator

@okan35 We now strictly follow a policy of "one idea per issue/PR". So you can just open a new issue, describe the problem this PR is solving, and link it to this PR.

@okan35
Copy link
Contributor Author

okan35 commented Nov 21, 2020

@okan35 We now strictly follow a policy of "one idea per issue/PR". So you can just open a new issue, describe the problem this PR is solving, and link it to this PR.

I just did that and later will add the progress dialogue or icon whatever for click refresh, pull to refresh already does that.

@opusforlife2
Copy link
Collaborator

@okan35
Copy link
Contributor Author

okan35 commented Nov 21, 2020

@okan35 You can use keywords to link a PR to an issue. https://docs.github.com/en/free-pro-team@latest/github/managing-your-work-on-github/linking-a-pull-request-to-an-issue

Will do it next time, didn't know this existed.

@okan35
Copy link
Contributor Author

okan35 commented Nov 21, 2020

Added the necessary change for showing loading icon on click to refresh and updated the app. I believe the feature is done now.

Copy link
Member

@Stypox Stypox left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I like this, though I am not sure if it is a good idea not to show any progress indicator except for the hard-to-access notification. You could show the loading bar, which previously was shown at the center of the screen, just below the Feed last updated: ... bar at the top. Also, please remove all comments, they are not needed anymore. Thank you for this contribution that would decrease time waste :-D

animateView(refresh_root_view, false, 0)
animateView(items_list, false, 0)
animateView(refresh_root_view, true, 0)
animateView(items_list, true, 0)
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

There is no need for this, i.e. to show items_list, if you never hide it ;-)


private fun handleErrorState(errorState: FeedState.ErrorState): Boolean {
hideLoading()
swipeRefreshLayout.isRefreshing=false
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

No need for this, it is already inside hideLoading()

@okan35
Copy link
Contributor Author

okan35 commented Dec 13, 2020

I like this, though I am not sure if it is a good idea not to show any progress indicator except for the hard-to-access notification. You could show the loading bar, which previously was shown at the center of the screen, just below the Feed last updated: ... bar at the top. Also, please remove all comments, they are not needed anymore. Thank you for this contribution that would decrease time waste :-D

I pushed the changes for those reviews you left. I would suggest that we do that feature of showing progress of video fetching in another pull request. But it is a good idea to show it like that, below feed last updated when user refreshes video list, and when it finishes we can hide it back,

Copy link
Member

@Stypox Stypox left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I would suggest that we do that feature of showing progress of video fetching in another pull request.

Yeah, ok, but both PRs need to ship in the same release, otherwise we are taking away the progress indicator from users, which would be cumbersome. Are you willing to make another PR right after this one?

return feedFragment
}
}
}
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Add back the newline at the end of the file (checkstyle should have complained)

}
}

// /////////////////////////////////////////////////////////////////////////
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Bring back these comments.. sorry if I was unclear, I meant that old code shouldn't be commented-out but directly removed. But useful comments like this should be kept.

@okan35
Copy link
Contributor Author

okan35 commented Dec 14, 2020

I can make another pr but I will do it around this week as it is a matter of time :D

@okan35
Copy link
Contributor Author

okan35 commented Dec 19, 2020

I added that progress text below video last fetched and those comments are back as I went to that commit. Updated the apk. To me it looked nice as it shows up with progress and disappears when it is finished.

Copy link
Member

@Stypox Stypox left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Could you rebase?

}
}

// /////////////////////////////////////////////////////////////////////////
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Bring back these comments ;-)

@TobiGr TobiGr force-pushed the dev branch 2 times, most recently from 679bc75 to 2aeccc0 Compare March 16, 2021 08:24
@litetex litetex marked this pull request as draft October 1, 2021 17:39
@litetex
Copy link
Member

litetex commented Oct 1, 2021

Closing this for now:

  • no progress
  • no GitHub actions build
  • merge conflicts
  • Snyk Found vulnerabilities!
  • No feedback from the author

Feel free to reopen it when there is progress again.

@litetex litetex closed this Oct 1, 2021
@litetex litetex mentioned this pull request Oct 10, 2021
2 tasks
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

Successfully merging this pull request may close these issues.

Show/Don't hide feed items when updating feed

5 participants