mistercrunch edited a comment on issue #6774:
URL: https://github.com/apache/superset/issues/6774#issuecomment-931415864


   My take on "drill"-type interactions (drill down, drill through, drill 
across) is that we'll need a context-menu (or similar) since it's impossible to 
guess what the user expects or wants. Maybe there's a guessed interaction on a 
double-click, but we still need a context menu for the other interactions.
   
   Also I prefer a drill-across-first approach, since drill down requires 
upfront hierarchy semantics. Drill across allows to filter-and-pivot to any 
other dimension, which offers much more possibilities than the predefined 
hierarchies. 
   
   Also note that alternate hierarchies (multiple paths to drill down into, 
state->zipcode or state->city) are a real thing and we need to think about what 
we do when they exist. We also need to think about where and how these 
hierarchy semantics are defined, but I'm thinking most likely in the dataset 
editor.
   
   Some screenshots from google image search on "drill context menu" to show 
the kind of complexity we're dealing with:
   <img width="529" alt="Screen Shot 2021-09-30 at 8 28 15 AM" 
src="https://user-images.githubusercontent.com/487433/135485395-6bdeed9f-93d7-480a-a24a-b439d16a9d1d.png";>
   <img width="235" alt="Screen Shot 2021-09-30 at 8 28 02 AM" 
src="https://user-images.githubusercontent.com/487433/135485418-84563166-9103-433a-ba0b-d21d13fa6036.png";>
   <img width="284" alt="Screen Shot 2021-09-30 at 8 27 36 AM" 
src="https://user-images.githubusercontent.com/487433/135485427-cedddf04-8bfe-442c-93ac-d5753950e92f.png";>
   <img width="235" alt="Screen Shot 2021-09-30 at 8 27 24 AM" 
src="https://user-images.githubusercontent.com/487433/135485430-06a8dba6-a4a7-4c95-af58-01c47b65e305.png";>
   <img width="182" alt="Screen Shot 2021-09-30 at 8 27 19 AM" 
src="https://user-images.githubusercontent.com/487433/135485432-ed095247-c15d-449b-a54c-d5bd7cf91e65.png";>
   
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]



---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to