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

Improving Data only view of query page #3087

Open
kocsmy opened this issue Nov 16, 2018 · 11 comments
Open

Improving Data only view of query page #3087

kocsmy opened this issue Nov 16, 2018 · 11 comments

Comments

@kocsmy
Copy link
Collaborator

kocsmy commented Nov 16, 2018

I've played a bit with the query data only view to further improve this view.

Just throwing in a couple of ideas, including iterative improvements and new concepts as well.

@kocsmy
Copy link
Collaborator Author

kocsmy commented Nov 16, 2018

Bringing meta data to the top more in place:

query view only
query view only 2

@kocsmy
Copy link
Collaborator Author

kocsmy commented Nov 16, 2018

Hide left sidebar entirely

query view only 3
query view only 3 fixed

@kocsmy
Copy link
Collaborator Author

kocsmy commented Nov 16, 2018

Card layout

This design approaches the data only query page as a mini dashboard where the data is presented in similar card like layouts we use on the dashboards.

query view only 4 card view

@arikfr
Copy link
Member

arikfr commented Nov 18, 2018

Screenshot 3 is the one that makes the most sense:

  • Get rid of the sidebar.
  • Give the data full width.

But I also like the look of the cards version. I don't think we should show all visualizations in a single view, but I do like the rest.

Maybe we can try merging screenshot 3 with the cards version:

  • Cards based sections.
  • The data section will retain tabs and be full width?

@kocsmy
Copy link
Collaborator Author

kocsmy commented Nov 20, 2018

Here's the merged version:
query view only 4 card view copy

I'm not 100% sure this is the right direction, the mixed fixed and fluid elements feels a bit strange to me. I'm also not 100% convinced that a so much different view/edit pages is the right direction.

@arikfr
Copy link
Member

arikfr commented Nov 20, 2018

How about all sections will be full width?

@kocsmy
Copy link
Collaborator Author

kocsmy commented Nov 21, 2018

Yes, full width works much better.

query view only 4 card view copy

@arikfr
Copy link
Member

arikfr commented Nov 25, 2018

Yes, I agree this is better. Some notes:

  1. The results & parameters sections should be similar to how they look like in query source view.
  2. Instead of the "Datasource" label we can use the database icon. Also why is it in a different row than the other metadata details?
  3. There is no Execute button...

@kocsmy
Copy link
Collaborator Author

kocsmy commented Dec 12, 2018

I've refined this as requested:

  • Results & Params are now in the same section.
  • For the datasource icon, I used the specific database icon which is a really nice addition.
  • Execute btn added.

query view only 4 card view copy

I explored how it would look like if we go with the sticky bottom section; I think this might even work better.

query view only 4 card view copy 2

@arikfr
Copy link
Member

arikfr commented Nov 18, 2019

We're hoping to address this as part of the React migration (#3071) of the Query Results and Editor pages. For this end, we're going to do some preliminary work with a UI/UX designer to define the new views. As a first step before finding such person, I created a short description of the project:

https://docs.google.com/document/d/1zX2NJz22ExBTKzpRnP10u8qwMaWhKIE2jEoEr8tkRNo/edit?usp=sharing

Y'all welcome to comment and add your thoughts in the doc.

@arikfr
Copy link
Member

arikfr commented Jan 6, 2020

Updated designs from @mohitpanjwani for the results only view. (@gabrieldutra, @kravets-levko, @susodapop FYI)

Everyone are welcome to share thoughts and comments.

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

2 participants