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

Optimizing the uploader layout & taking user configured sorting into account #5

Merged
merged 24 commits into from Jun 13, 2016

Conversation

AndyScherzinger
Copy link
Member

@AndyScherzinger AndyScherzinger commented Jun 11, 2016

NC version of @jancborchardt's original oC request 1193:

When uploading content from another app (like the Gallery), the uploader view looks strangely different from the normal file list.

It should have the same layout, with file/folder info below the folder names, and also the same sort order if one chose to sort by modified date.

pinging @tobiasKaminsky @przybylski for the 2-thumbs-up code review

could be put into a post 1.0.0 release since it is a rather small change and easy to test (already tested by me)


public class PreferenceManager {

public abstract class PreferenceManager {
Copy link
Member

Choose a reason for hiding this comment

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

To me this class name is super confusing, can you rename it to something like PreferenceHelpers ?

Copy link
Member

Choose a reason for hiding this comment

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

Also I don't understand why this is in db package

Copy link
Member Author

Choose a reason for hiding this comment

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

left this one open since it is a structural change

@AndyScherzinger
Copy link
Member Author

Very thorough review @przybylski thank you for that! 👍

I would like to start a discussion on this including @tobiasKaminsky in this. All the review comments are very legit and push for better code. The changes I made have been done with minimal changes in mind to be necessary to add the functionality but stay with the given/oC code structure to keep merges easy.

It's tricky since easy merges mean we are stuck with the code as it is when we forked which might slow us down here and there. Diverge right at the start will make merge rather hard and might lead to errors down the road due to mistakes made while manually merging/adapting changes.

Looking forward to your comments :)
...don't hit me 😉

@przybylski
Copy link
Member

So let's wait what will @tobiasKaminsky say

@AndyScherzinger
Copy link
Member Author

Sounds good to me. I am fine either way though but it should be a decision we all agree on :)

@tobiasKaminsky
Copy link
Member

Tricky one...
I would do a "middle way". In order to get all pending >50 PRs as quick as possible in Nextcloud we should stay very near to the original code.
After that we can and should refactor as much as we want. Of course this will make backports very time consumption...

@AndyScherzinger
Copy link
Member Author

Sounds good, thus I would propose the following steps:

  1. I fix the review comments which do not have a larger impact on the code structure
  2. We test and merge (I already tested it and it works)
  3. I open up an issue referring to this PR for refactoring aspects to be done after we are through which a larger part of the open PRs

Due to the possibility of differences in pace and future features the code base will diverge at some point anyways, but yes which should aim to get PRs merged and thus old branches removed and then move on from there.

Sounds good to you guys? @nextcloud/android developers epsecially @przybylski and @tobiasKaminsky ?

@tobiasKaminsky
Copy link
Member

The plan sounds fine! (I need to avoid everything that l g t m can think I like this PR ;))

@AndyScherzinger
Copy link
Member Author

Well we could remove the thumbs up pattern so only shipit and L g M T would trigger the approval 😃

@AndyScherzinger
Copy link
Member Author

Please review again. @tobiasKaminsky and @przybylski I incorporated all non-structural changes and also fixed some more layouting/data-display stuff so now all uploaders and the standard file list look exactly the same

android:layout_marginRight="4dp"
android:orientation="horizontal">

<TextView
Copy link
Member

Choose a reason for hiding this comment

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

Wouldn't it be better to have one text view and format string when inserting?

Copy link
Member Author

Choose a reason for hiding this comment

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

@przybylski I vote no since this would be the next change that doesn't add additional value but let's the code diverge from oC

@AndyScherzinger
Copy link
Member Author

opened an issue for the dimensions housekeeping: #12 to move stuff like this to dims.xml 😃

@AndyScherzinger
Copy link
Member Author

So are you fine with the changes @przybylski ?

@przybylski
Copy link
Member

aside some structural changes LGTM

@AndyScherzinger
Copy link
Member Author

AndyScherzinger commented Jun 13, 2016

Thanks a lot! Besides that looking forward to @tobiasKaminsky feedback especially on the matter on how (and when) to deal with technical debt and how to compile a list of PRs we want to integrate before we start larger refactorings.

@AndyScherzinger
Copy link
Member Author

Sidenote... just realised that I (as in the person who opened the PR) can't even have a 👍 in a comment at all without that being tracked as a positive code review feedback... 😣

@tobiasKaminsky
Copy link
Member

@AndyScherzinger of course it is. Just like LGTM needs it 👍

@AndyScherzinger
Copy link
Member Author

Sweet, so waiting for the build to finish and then I will merge :)

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

Successfully merging this pull request may close these issues.

None yet

3 participants