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

Remove support for RevisionGrid layouts #5026

Closed
drewnoakes opened this issue Jun 4, 2018 · 23 comments
Closed

Remove support for RevisionGrid layouts #5026

drewnoakes opened this issue Jun 4, 2018 · 23 comments

Comments

@drewnoakes
Copy link
Member

The RevisionGrid control supports multiple layouts.

I strongly suspect that most users don't know this, and use the default layout.

I kinda wonder whether anyone uses a non-default layout. Does anyone reading this do so?

Layouts

Many of the layouts look completely broken. Here's what they look like in 2.51.02, and they look much the same on master.

You can cycle layouts by pressing Ctrl+Shift+L, or via the "View" menu.

image

image

image

image

image

image

image

image

Proposal

Remove the ability to change the layout. Have one good layout. Reduce the volume of code considerably. No one will notice :)

I've got a branch going with some tidying of RevisionGrid. That's such a huge class, with over 300 members (excluding the designer file). If this proposal gains support, I will do the necessary surgery on that branch and create a PR.


Environment

GitExtensions version: 2.51.02, master
OS version: Windows 10

@vbjay
Copy link
Contributor

vbjay commented Jun 4, 2018 via email

@vbjay
Copy link
Contributor

vbjay commented Jun 4, 2018 via email

@drewnoakes
Copy link
Member Author

Which layout do you use? Do they look this broken for you? To me the non-broken layouts look pretty much the same.

@vbjay
Copy link
Contributor

vbjay commented Jun 5, 2018

Some of them you have to force a refresh before it looks right.

@vbjay
Copy link
Contributor

vbjay commented Jun 5, 2018

image I submitted an issue for this one for the selected commit text not being visible.

I also use this one

image

@RussKie
Copy link
Member

RussKie commented Jun 5, 2018 via email

@jbialobr
Copy link
Member

jbialobr commented Jun 5, 2018

I also support single layout, especially taking into account switching from WinForms to sth else.

@gerhardol
Copy link
Member

Single layout.
A colleague got one of the semi-broken layouts somehow and did not know how to get it back. This can of course occur for any customization, but there is not much point in delivering broken layouts.

@drewnoakes
Copy link
Member Author

I should have time today to experiment with this. Will report back with findings.

@drewnoakes
Copy link
Member Author

@vbjay could you explain some more about what the tile view gives you? Then we can explore whether there's a way of bringing some of that into a single layout. To me it looks nice enough aesthetically, but I wouldn't use it due to its low information density.

@vbjay
Copy link
Contributor

vbjay commented Jun 5, 2018 via email

@pmiossec
Copy link
Member

pmiossec commented Jun 5, 2018

I'm Ok to remove too.
Also, under high dpi all others are either:

  • completely broken
  • nearly the same than the default one
  • display not clear data and could induce comprehension errors

For example, this all flat layout :

image
We can't understand which commit belong to which branch. Using the option "Show current branch only" make a lot more sense...

@vbjay
Copy link
Contributor

vbjay commented Jun 5, 2018 via email

@pmiossec
Copy link
Member

pmiossec commented Jun 5, 2018

@vbjay I did it once I read your previous comment and that don't change a lot of things.
There are mostly broken even after a refresh under high dpi screen :(

@vbjay
Copy link
Contributor

vbjay commented Jun 5, 2018 via email

@drewnoakes
Copy link
Member Author

@pmiossec thanks for pointing out that we would remove a large bunch of high DPI bugs.

@vbjay

It lets me focus on each commit instead of seeing a ton of them.

Perhaps we can introduce a density setting to let the user choose how visually dense the revision grid is. Would that help achieve what you're after.

In a similar spirit, moving to a single grid presentation style allows us to focus on making it as great to use as possible, while resisting adding too many user options. This will be easier to realise if we have less code to consider.

I have some progress on this but it's blocked a bit behind #5029. I'll fix that first.

@drewnoakes
Copy link
Member Author

The only issue I face with the layouts is the selected commit font color. White against that gradient causes the commit text to disappear.

This is a problem with many of the non-default layouts. The default layout works well with selections.

@vbjay
Copy link
Contributor

vbjay commented Jun 5, 2018 via email

@drewnoakes
Copy link
Member Author

I also like the gravatar image on the commits

We could add it as a column to the grid, and still have only one layout. There are existing settings that toggle column visibilities, so we can add one more.

Such a column would probably only look decent if the density was turned down.

@pmiossec
Copy link
Member

pmiossec commented Jun 5, 2018

I also like the gravatar image on the commits

We could add it as a column to the grid

I also think that it should be a column displayed for example just before the Author column...

@drewnoakes
Copy link
Member Author

Thinking longer term we could add a column chooser, where you can control which columns are visible and their order in the grid.

@vbjay
Copy link
Contributor

vbjay commented Jun 5, 2018 via email

@RussKie
Copy link
Member

RussKie commented Jun 5, 2018 via email

@drewnoakes drewnoakes added this to the 3.00 milestone Jun 24, 2018
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

6 participants