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

Question: [Can we have mdi support for this?] #352

Closed
Shadowblitz16 opened this issue Dec 31, 2020 · 6 comments
Closed

Question: [Can we have mdi support for this?] #352

Shadowblitz16 opened this issue Dec 31, 2020 · 6 comments
Assignees
Labels
area-Win32 Support for Win32 packaged and non-packaged apps area-Windowing feature proposal

Comments

@Shadowblitz16
Copy link

Proposal: [MDI support]

Summary

Can we get mdi support even if its not recommended by Microsoft to use?
Its great for small screen resolutions or single monitor workspaces.

Rationale

  • {Win32 supports it}
  • {Multi monitor workspaces can be fixed by adding a pop out button to the mdi child title bar}
  • {We could also have the ability to drag the window back into the mdi container}
  • {Could support docking}
  • {Its still a good interface pattern for small or single monitor computers}
  • {Many companies still use it (like my dentist)}

Scope

Don't understand this part sorry.

Important Notes

I would think it should support treating windows as controls and adding mdi children is as easy as..

windowA.Controls =
{
    windowB,
    windowC.Controls =
    {
        windowD
    }
}

Open Questions

I searched and didn't see any issues on this

@lukeblevins
Copy link

@Shadowblitz16 If Win32 supports the Multiple-Document Interface specification, then why not continue to use it? Project Reunion isn't about completely replacing your existing technology, but gradually enhancing your applications where needed.

However, if you want to see this specification evaluated as a feature for WinUI: feel free to contribute your ideas, expectations, and opinions to open issues like this. Project Reunion is a family of components and WinUI is one of them.

If you're happy with the existing MDI support in Win32, then you can enhance your app in other ways.

@Shadowblitz16
Copy link
Author

Not sure what you mean.
I thought this interduces a common API for win32, winforms, wpf, and uwp and gets rid of them in the system in favor of this.

If so I was just wondering if mdi support could be added to the api

@mdtauk
Copy link

mdtauk commented Jan 2, 2021

Not sure what you mean.
I thought this interduces a common API for win32, winforms, wpf, and uwp and gets rid of them in the system in favor of this.

If so I was just wondering if mdi support could be added to the api

Reunion will be about introducing a common wrapper around existing APIs which can be used by UWP and Desktop applications. In time I am sure new APIs may be introduced.

One being discussed is replacing the Common File and Folder dialogs with a modern one. I would imagine apps running on Windows 8 may also be able to use this API, but it will probably just display the native Win32 one there.

@lukeblevins
Copy link

@Shadowblitz16 That's a common misconception. While Project Reunion aims to reduce differences in the features that the different application types can leverage, it is not a new app model.

@stevewri
Copy link
Contributor

stevewri commented Jan 4, 2021

@Shadowblitz16 does that answer your question? Please reactivate if you have a followup!

@stevewri stevewri closed this as completed Jan 4, 2021
@ghost ghost removed the needs-triage label Jan 4, 2021
@stevewri stevewri self-assigned this Jan 4, 2021
@stevewri stevewri added area-Win32 Support for Win32 packaged and non-packaged apps area-Windowing labels Jan 4, 2021
@stevewri stevewri assigned rkarman and unassigned stevewri Jan 4, 2021
@Shadowblitz16
Copy link
Author

It answers the question yes

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area-Win32 Support for Win32 packaged and non-packaged apps area-Windowing feature proposal
Projects
None yet
Development

No branches or pull requests

6 participants