Docking/MDI vNext - How Should We Improve MVVM Support?

by Avatar Bill Henning (Actipro) - 5 comments
Thursday, August 20, 2015 at 2:20pm

PostBannerWPFControlsDevNotes

As mentioned in this previous post, we've been looking for ideas to further improve our WPF Docking/MDI product, which already is the market leader for docking tool window and MDI functionality.  We've committed to working on a complete internal restructuring of the product that we will call Docking/MDI vNext.  We're doing our best to keep the same general API surface, while providing even more advanced features in every area of the product.  We've collected suggestions from our customers over the past several years and are working to meet them as best we can with Docking/MDI vNext.

Our current production version of Docking/MDI fully supports the optional MVVM pattern for managing both tool and document windows.  The design generally follows that of a standard ItemsControl.

We are revisiting all of this right now in our vNext implementation and want to hear from you, our customers, on what improvements or feature additions would help you out when working with MVVM-based docking windows.

  • What API additions/changes would you like to see?
  • What MVVM-related functionality would you like to see added?
  • What are any pain points you've encountered with MVVM support in the current version?
  • What MVVM framework, if any, do you use within your app that you'd like to integrate docking windows with?

If you could reply to the above questions in the comments or email our support address, it would be most welcome.  Now is the time to send your feedback as we are currently working in this area.  Thanks!

Docking/MDI vNext - Tabbed MDI New Tab Button

by Avatar Bill Henning (Actipro)
Tuesday, July 14, 2015 at 7:54pm

PostBannerWPFControlsDevNotes

As mentioned in this previous post, we've been looking for ideas to further improve our WPF Docking/MDI product, which already is the market leader for docking tool window and MDI functionality.  We've committed to working on a complete internal restructuring of the product that we will call Docking/MDI vNext.  We're doing our best to keep the same general API surface, while providing even more advanced features in every area of the product.  We've collected suggestions from our customers over the past several years and are working to meet them as best we can with Docking/MDI vNext.

In our previous post, we showed several new tabbed MDI features including read-only glyphs, tab layout kinds, and context menu options.  In today's post we'll show another new feature coming to tabbed MDI, which is the optional new tab button.

Feature Description

When the new tab button is enabled, a button shows up at the end of the tab list.  This tab button is best used when the tab overflow mode is set to shrink tabs.  Upon clicking the new tab button, an event fires allowing you to be notified that the end user is requesting a new tab.

Here's a small demo we made with tabs that look like a Chrome browser.  The animation sequence shows how tabs can be dragged around in an animated fashion and then when the new tab button is clicked, new tabs are added.

ChromeBrowser

The sample above is using a completely custom tab and new tab button chrome.  Default styling of a new tab button has a plus button glyph.

Summary

New tab buttons are great for use in certain application scenarios such as browsers.  vNext easily brings the option of using them to your own apps.

Docking/MDI vNext is currently still in mid-development stages but is progressing very well.  Please contact us via email if you are an existing customer and would like to sign up as a beta tester for vNext.  If you have any other suggestions for improving Docking/MDI, now is the time to get them in.  We'll post more updates on our vNext improvements soon.

In the meantime, please download our current Docking/MDI control product and give it a spin.

TaskDownload TaskLiveDemo TaskBuyNow

Docking/MDI vNext - New Tabbed MDI Features

by Avatar Bill Henning (Actipro) - 4 comments
Monday, July 6, 2015 at 5:23pm

PostBannerWPFControlsDevNotes

As mentioned in this previous post, we've been looking for ideas to further improve our WPF Docking/MDI product, which already is the market leader for docking tool window and MDI functionality.  We've committed to working on a complete internal restructuring of the product that we will call Docking/MDI vNext.  We're doing our best to keep the same general API surface, while providing even more advanced features in every area of the product.  We've collected suggestions from our customers over the past several years and are working to meet them as best we can with Docking/MDI vNext.

In the last post, we showed how vNext will support full-featured tabbed MDI with docked tool windows in a floating container.  In today's post, we will focus on several other new features coming to tabbed MDI.

Feature Description

First, we have a new built-in read-only glyph that shows in a tab when the document window is marked read-only.  You can see it at the beginning of the animation sequence below.

TabbedMdiTabKinds

Second, we've added the ability to designate the kind of layout a tab will use when in tabbed MDI mode.  The default option is Normal.  There also is a Pinned layout kind.  Pinned tabs appear to the left of normal tabs and have an unpin button on them.  When unpinned, a pinned tab returns back to Normal state.  A third state is a Preview state where the tab appears on the right side of the container using an alternate appearance, and has a Keep Tab Open button on it, also available on the context menu.  Clicking that button returns the tab to a Normal state.  A preview tab is generally used as a temporary tab that can disappear when no longer needed.

Third, we've added more menu items to the context menu that shows for tabbed MDI.  In the animation sequence, you can see new Close Others and Close All Documents menu items.  Close Others will close all other tabs in the same container.  Close All Documents will close all tabs in any tabbed MDI container.

Summary

These are all advanced features that have been requested by our customers and are coming to Docking/MDI vNext.

Docking/MDI vNext is currently still in mid-development stages but is progressing very well.  Please contact us via email if you are an existing customer and would like to sign up as a beta tester for vNext.  If you have any other suggestions for improving Docking/MDI, now is the time to get them in.  We'll post more updates on our vNext improvements soon.

In the meantime, please download our current Docking/MDI control product and give it a spin.

TaskDownload TaskLiveDemo TaskBuyNow

Docking/MDI vNext - Floating MDI

by Avatar Bill Henning (Actipro)
Friday, June 5, 2015 at 7:18pm

PostBannerWPFControlsDevNotes

As mentioned in this previous post, we've been looking for ideas to further improve our WPF Docking/MDI product, which already is the market leader for docking tool window and MDI functionality.  We've committed to working on a complete internal restructuring of the product that we will call Docking/MDI vNext.  We're doing our best to keep the same general API surface, while providing even more advanced features in every area of the product.  We've collected suggestions from our customers over the past several years and are working to meet them as best we can with Docking/MDI vNext.

In our previous post, we discussed some new features coming to standard MDI.  In today's post we'll get into one of the largest new features coming in vNext, which is the ability to have a full-featured MDI with docked tool window support in a floating container.

Feature Description

In the current 2015.1 version, you can float document and tool windows.  Each document window goes into its own floating container, while tool windows can be combined in floating containers.  Many customers have requested that we allow a full MDI in floating containers and that's what we're bringing to vNext.  Let's have a first look at how this will work.

Here we have a main window that contains two tabbed documents (docked next to each other) and tool windows in various locations docked around the MDI area.

FloatingMdi1

Next I drag the Document1.txt tab into its own floating container.  Then I drag Document2.txt and using dock guides, attach it to the first document.  This is a new feature that couldn't be done before.

FloatingMdi2

Finally I drag the Solution Explorer and dock it next to the MDI in the floating container.  Again, this is a new feature that couldn't be done before.  The end result is a single DockSite that has two fully-functional DockHosts in it, one that is primary (within the DockSite) and one that is in a floating container.

Summary

Floating MDI features have been requested by a number of customers and we're very happy to deliver them in vNext.  This feature set allows your single app to have multiple MDI areas that can be most effectively used in multiple monitor scenarios.  Your end users will love it!

Docking/MDI vNext is currently still in mid-development stages but is progressing very well.  Please contact us via email if you are an existing customer and would like to sign up as a beta tester for vNext.  If you have any other suggestions for improving Docking/MDI, now is the time to get them in.  We'll post more updates on our vNext improvements soon.

In the meantime, please download our current Docking/MDI control product and give it a spin.

TaskDownload TaskLiveDemo TaskBuyNow

Docking/MDI vNext - Standard MDI Dock Target and Context Menus

by Avatar Bill Henning (Actipro)
Friday, May 29, 2015 at 7:37pm

PostBannerWPFControlsDevNotes

As mentioned in this previous post, we've been looking for ideas to further improve our WPF Docking/MDI product, which already is the market leader for docking tool window and MDI functionality.  We've committed to working on a complete internal restructuring of the product that we will call Docking/MDI vNext.  We're doing our best to keep the same general API surface, while providing even more advanced features in every area of the product.  We've collected suggestions from our customers over the past several years and are working to meet them as best we can with Docking/MDI vNext.

In yesterday's post, we talked about a new optional size-to-content feature coming to standard MDI.  In today's post we'll get into some other new features:  standard MDI dock target and context menus.

Feature Description

One new addition is that now standard MDI can accept an "attach" (center dock guide) when dragging tool windows around.  If the tool windows are dropped on the center dock guide, they immediately become documents in the standard MDI.

Another new feature is the ability to right-click on a standard MDI window's title bar or click its icon (if any) to see a context menu.  We'll be expanding the options on the context menu further in the future.

Let's see all of this in action!

StandardMdiDocking

In this animation, we drag the Solution Explorer and Class View tool windows around.  You can see the dock guides displayed for the standard MDI area.  At first, we dock the tool windows to the left of MDI, keeping them still in a Docked state.  Then we "attach" (center) dock them into the standard MDI and they become documents.

You can see the context menu that comes up when the title bar is right-clicked.

Summary

These great new features will be part of Docking/MDI vNext, with plenty more on the way!

Docking/MDI vNext is currently still in mid-development stages but is progressing very well.  Please contact us via email if you are an existing customer and would like to sign up as a beta tester for vNext.  If you have any other suggestions for improving Docking/MDI, now is the time to get them in.  We'll post more updates on our vNext improvements soon.

In the meantime, please download our current Docking/MDI control product and give it a spin.

TaskDownload TaskLiveDemo TaskBuyNow