Skip to content
This repository was archived by the owner on Feb 25, 2026. It is now read-only.

Linked ListDetails View #3284

Closed
Closed

Description

@oenarap

Maximize usage of available screen(s) real estate by allowing multiple master-details be displayed at a time.

I am wishing for a feature that is kind of similar to Fabian Sauter's MasterDetailsView PR but taken a little further.

Describe the solution

Imagine having all your displayable master-details view(s) rolled-out across your screen(s) with no wasted space whatsoever. But then, can be collapsed to fit in the size of a mobile phone's display without losing usability -- the crux of UWP apps!

Describe alternatives you've considered

I've considered using MasterDetailsView, BladeView and combination of both, but would require a daunting amount of workaround to get near the result i wish to achieve.

Additional context & Screenshots

I have been toying around with the idea for a while now. You might want to take a look at a rudimentary implementation i currently am working on: https://github.com/oenarap/CDLNPeople/tree/master/CustomControls.Controls/LinkedViewControl

i took inspiration from behavior of People app that shipped with Windows 8.1/10. I'm not sure, but definitely not the latest version.

screenshots:

compact (the most recent pane the user interacted with remains displayed)
image

optimal
image

full
image

extended
image

...etc.
...etc.

Activity

  1. Kyaa-dost commented on May 15, 2020

    @Kyaa-dost
    Contributor

    @oenarap looks like an interesting feature to have but not sure about the work it would require as you have emphasized the complexity 🤔

  2. skendrot commented on May 15, 2020

    @skendrot
    Contributor

    This does seem like a good use for the BladeView. In your "optimal" screenshot, wouldn't you want to view the the details of Mr. Potter and his personal information since that's currently selected?

  3. oenarap commented on May 15, 2020

    @oenarap
    Author

    @skendrot the second pane visible in "optimal" screenshot is some sort of quick view of a person's details most relevant to the user. the lower part serves as a navigation list.

    anyway, the content is not supposed to be the issue.

    as i've mentioned in the "alternatives", BladeView and MasterDetailsView are two closest to fit my scenario. it's just that i get lots of friction when i try to achieve a behavior like this:

    gif

    kudos to the watermark!

  4. michael-hawker commented on May 16, 2020

    @michael-hawker
    Member

    Thanks for this great suggestion @oenarap! I could almost definitely see this as an option on BladeView somehow. It really feel similar in layout/behavior to that (outside of this collapsing behavior).

    I mean the Master/Details vibe does show in your example, but I think that could still be left to the developer and manipulated via separate blades? Maybe we also need an option for BladeView to remove the header/controls on top of the blades to provide this more fluent look?

    I'll add this to our 7.0 milestone for now, is this something you want to take on yourself to implement & contribute or are you looking for assistance?

  5. added this to the 7.0 milestone on May 16, 2020
  6. oenarap commented on May 16, 2020

    @oenarap
    Author

    Thanks @michael-hawker!

    i'll be glad to go either way. if you let me take on it alone, fine. if you want me to collaborate, it's just the same coffee. so long as this idea gets "adopted and improved" by the community, it's a big win for me and perhaps, everybody.

  7. michael-hawker commented on May 17, 2020

    @michael-hawker
    Member

    Thanks @oenarap, it would be great to see what you come up with!

    Since we already have the TitleBarVisibility flag on BladeView, I see that this could be a combination of:

    1. Modernizing the BladeView style (@mdtauk & @niels9001 - fancy a gander? 🦙❤)
    2. Making it easier to have Blades adapt to their Content's sizing (I think they're pretty stiff currently).
    3. Adding a new BladeMode property for this new type of Stacking behavior of the panels.

    I think the Master/Details scenario part of it is probably secondary and either left up to the developer to manage, or maybe becomes some sort of separate navigation helper/tracker (I'm curious what @Sergio0694 does as he mentioned something like this once I think).

    One thing I wanted to clarify from your screenshots was if if the NavigationView bar was excluded from your vision or somehow integrated to the control??

    I'm also happy to point folks from the UWP Community Server onto this topic for more input from the community, or feel free to start a discussion there.

  8. mdtauk commented on May 17, 2020

    @mdtauk

    The only thing I would suggest, is to consider how this kind of control would work with the two pane view, and for dual screen scenarios.

    This kind of UI may be cumbersome for the user

  9. Sergio0694 commented on May 17, 2020

    @Sergio0694
    Member

    @michael-hawker Yeah you're correct, I do have something like this in both OneLocker and Legere. I wrote my own shell that I'm reusing across both apps (with some modifications), which includes two main panels (à la master-slave), and two additional side panels. The navigation system bounces back and forth between the two main panels and keeps a navigation history across them, so that when you shrink the UI down, the correct panel stays on top and the user doesn't lose track of the workflow. This also works well on mobile (OneLocker runs on W10M too), as the system completely hides the two main panels and the user only sees them as one. My shell in particular also includes some various animations/transitions for the various sidebars, as those are not considered on the same level as the two main panels, but more like accessories (the hamburger menu on the left, and the sidebar on the right).

    Here's a picture of the main visual states so that it's clearer to see what I'm talking about:

    image

    I have to say I'm a bit puzzled as to how something like this could work as a reusable control, as there are a lot of moving parts that need to come together, plus users might want to customize lots of different aspects to fit their needs. For instance, I couldn't just reuse my OneLocker shell, I forked my own shell and customized it again to perfecty fit my needs in Legere.

    What I mean is, the shell of the app is particularly important both for the UX as well as to define the brand, as different publishers might want to keep a distinct look and feel for all their apps (eg. like I'm doing with the same shell for OneLocker and Legere, see screenshot):

    image

    That is to say, we might probably want to think about how much customization to add so that it's enough for the majority of users that would be satisfied with just using a shared control from the toolkit with some light restyling, but also so that we don't waste time adding in too many customization features trying to appease devs who would not be using the control anyway, opting instead for their own custom shell. Just sharing my two cents here of course! 😄

  10. oenarap commented on May 17, 2020

    @oenarap
    Author

    @michael-hawker i agree the BladeView would offer the best springboard for this.

    with that said, i think we can dismiss any concern about reusability. anyone?

    @mdtauk if BladeView provides in-built functionality to split between two BladeViewItem to accommodate two-pane or multiple-screen scenario, then users should be able to focus their time and energy on the contents. and based on my understanding, that should always be the ultimate goal for an author. i would appreciate it if you can share something from your standpoint that guarantees this idea is doa.

    @Sergio0694 thanks for the input.

    @michael-hawker sorry if i got stuck with the "master-detail" thing. it has always been the way i imagine how "contents" will be presented. and as i said earlier in this thread, "contents" is not supposed to be the issue.

  11. oenarap commented on May 17, 2020

    @oenarap
    Author

    @michael-hawker i mean, i agree on all those points you enumerated. and by the way, the NavigationView in the screenshots just serves as a host. thanks!

  12. michael-hawker commented on Jul 27, 2020

    @michael-hawker
    Member

    Hey @oenarap just wanted to touch-base and see if improving BladeView for these scenarios was still something you were interested in taking on or not?

  13. oenarap commented on Aug 19, 2020

    @oenarap
    Author

    Hi @michael-hawker! Something unexpected came up and i lost the chance and free time to keep my hands on this. I definitely will get back on and push my idea. Stay safe.

  14. oenarap commented on Sep 18, 2020

    @oenarap
    Author

    @michael-hawker I can't go the BladeView route. I do not wish to break lots of stuffs.

  15. skendrot commented on Sep 24, 2020

    @skendrot
    Contributor

    Looking at the video again I wonder if this is best achieved through triggers based on the available size combined with a RelativePanel forbest display. You should also be able to put a MasterDetailsView as the Details of another MasterDetailsView

  16. modified the milestones: 7.0, 7.1 on Dec 9, 2020
  17. changed the title [-]Linked Master-Details View[/-] [+]Linked ListDetails View[/+] on Jun 29, 2021
  18. removed this from the 7.1 milestone on Jun 29, 2021
  19. oenarap commented on Jul 5, 2021

    @oenarap
    Author

    hi @michael-hawker
    it's been a while. i finally have some bit of free time.
    is anyone here working with the same idea?

    i'm doing some prototyping here.

    i'd be glad if you could give some guidance. thanks!

  20. locked and limited conversation to collaborators on Jul 29, 2022
  21. converted this issue into a discussionon Jul 29, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions