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

New Activity View #4083

Merged
merged 32 commits into from
Nov 16, 2015
Merged

New Activity View #4083

merged 32 commits into from
Nov 16, 2015

Conversation

dragotin
Copy link
Contributor

@dragotin dragotin commented Nov 6, 2015

I'd like to create this pull request already to discuss the changes done here as early as possible.

This branch changes the way we display the sync activity in the former client releases and adds three new views to the Activity-tab in the client.

  1. Server Activiity
    This displays the server activity list. Currently it is pulled from the server and displayed if the server is reachable.
  2. Sync Protocol
    Very similar to the former list of synced files, but without the ignored and error files in between. It's a plain positive list now.
  3. Not Synced
    A list of files that were not successfully synced because they were ignored (by user intention or because of other reasons) Later on we can also handle the blacklisting here more user friendly.

Some Screenshots:

server_activity

sync_proto

not_synced

Please give me your feedback on this changes and if you think they help to improve user experience. Nothing is set in stone yet, please do not stumble above details. @MTRichards @moscicki @jancborchardt @DeepDiver1975 @karlitschek

Thanks

This a first step to integrate the server activity view, see #3732
Keep one instance for the lifetime of the generalsettings widget.
Currently, this one only replaces colons by / on Mac platform. This makes
the function resuseable.
This is the new widget to display server activity.
It is better to create the tabs from the code in SettingsDialog.
Do not use it via a smart pointer class.
Now it can be used to be set on the other two treeviews.
So there are three views now: One displaying the server activities, one for
the sync protocol and a third one for ignored files and issues.
@guruz guruz added this to the 2.1-current milestone Nov 6, 2015
@jancborchardt
Copy link
Member

Isn’t the goal still to make it similar to the web-app activity view? As in, similarly simple to see what happened, with nice profile images of other people who shared stuff with you, file thumbnails, ability to share files from there / open them locally etc.? Keep in mind those are just plans and we should of course do this step-by-step, but this 3-tab view is more complicated than the current view.

One problem it solves is that errors drown in the log – but the proposal for that from me since long ago was to just keep them at the top. See: In »Activity«, keep errors at the top #1745 (from May last year without reply from anyone of you).

@dragotin
Copy link
Contributor Author

dragotin commented Nov 9, 2015

About "similar to the web-app": Yes, we want to make more useful. However, the current available API does not allow more than what I have implemented so far. The needed data is not available.

A new API is in discussion here: owncloud/activity#405

About the "three tab solution": It is better for the user to have the three tabs. The main focus is on the default tab which is the server activity, as @karlitschek wanted. In Berlin we agreed to combine the server api and the client sync protocol, however, that is currently not possible due to missing API capabilities. So we want to keep the sync protocol as people are using it to verify their syncs.

I will answer on why I think it makes sense to have a separate tab with "bugs" in #1745

@jancborchardt
Copy link
Member

It is better for the user to have the three tabs. The main focus is on the default tab which is the server activity

Why is it better to have three?
The most important thing here is to know when there have been issues, and being able to solve them. That’s why the errors (files not synced, because of illegal chars or whatever) should show up top in the list.

I also answered in #1745 (comment)
I’m not happy with this solution and think that splitting it up into 3 separate views overcomplicates this view even more than it already is. cc @karlitschek @DeepDiver1975 @owncloud/designers

@dragotin
Copy link
Contributor Author

dragotin commented Nov 9, 2015

I tried to explain this. If there are real issues, they are displayed more prominent at the account settings anyway. So this is for people who want to dig deeper anyway.

We are talking here about files that were not synced. That is only in rare cases an error condition. Mostly it's intentional by ignore patterns. Note that we are away from literally syncing everything, and do not want to go there with our selective sync and ignore patterns.

So what we are talking here is mainly a list of ignored files. That must be available somewhere.

> Why is it better to have three?
Because we need two anyway (Server Activity and Sync Protocol), and because of the arguments I gave in #1745 we do not want to clutter the sync protocol any more.

@jancborchardt before talking down the practical solution I was coming up here with (also based on a very difficult API) please take the time to really dig into the nifty details and come up with proposals for better solutions which take the given circumstances into consideration.

@guruz
Copy link
Contributor

guruz commented Nov 9, 2015

I think it is fine for the 2.1
Better to have that out of the door earlier than later.
We can then wait for feedback and iterate in 2.2

@guruz
Copy link
Contributor

guruz commented Nov 9, 2015

Could "Not synced" be renamed to "Issues" and you also list created conflict files there? This was requested at several other points here on github.

@jancborchardt
Copy link
Member

I think it is fine for the 2.1

I’m not sure, as I said. It’s more complicated.

please take the time to really dig into the nifty details and come up with proposals for better solutions which take the given circumstances into consideration.

We did that at the conf. It seems like all of that was forgotten? See also the email I just sent for a recounting of what we talked about. I can mock this up, if needed, but I guess coming to Nürnberg and working face-to-face on a whiteboard seems to be the correct way to settle this without another misunderstanding.

@jancborchardt
Copy link
Member

Maybe cc @ogoffart whom I specifically talked to about the redesign of this.

@MegaV0lt
Copy link

Maybe add symbols in the Aktion row for Up and Download?

It uses the Account displayName to destinguish.
Display the activity entries in a different mode if the account is not
longer connected.
This gives a visual indication of the account not being connected
and as a result maybe outdated activity data.
Note that the activity has also entries of files that are not synced so
that not every activity entry has to have a local pendant.

Also, one activity entry can reference multiple files, so only the first
one is shown.
the original text might be elided.
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.

4 participants