If we open a window using the WindowService and a custom component for the window content, there seems to be no easy way to disable the "minimize" action.

Example (pseudo code):

this.windowService.open({
                title: 'Execution Details',
                content: MyDetailsWindowComponent,
                width: 800,
                height: 600,
                minimizable: false, // < suggested feature
                maximizable: false  // < suggested feature
            });

Szenario: Esp. minify makes no sense in many situations (while we still don't want a "dialog like behavior" with backdrop and modal).

There are situations where we need to get a list of all windows, e.g. "close all" or "rearrange". While this can easily done manually when working with a single type of window, it's difficult if we have multiple windows using multiple components (we would have to ensure that we register them all in some kind of registry).

Feature request: Add something like a WindowManager that allows us to access all windows. Perhaps their WindowRefs? Perhaps an addition to WindowContainerService?

Please support out of the box support for modality. I know there is how to, but out of the box, for such basic feature seems reasonable.

Also suggested how to doesn't work for windows initialised through service.

This would also align Angular Window component with KendoUI Window component modality.

Requested feature:

A new options "stayInFront" / "alwaysTop" for WindowService > WindowSettings.

Example:

this._windowService.open({
                title: 'Details',
                content: MyDetailsWindowComponent,
                stayInFront: true // < requested feature
            });

Behavior:

• if true, the window is always "on top", that means if we open another window with "stayInFront=false" it will be behind the window with "stayInFront=true".
• if multiple windows are open with stayInFront=true they will keep the order in which they were opened

Szenario:

• We have a grid of records, where a record is a "pipeline configuration" that allows users to edit pipeline steps ("nodes").
• When the user clicks on a record, we open an "edit pipeline" window.
• Inside the "edit pipeline window" we have list of "nodes" and the user can click "edit" on each node. This will open a second window containing details to the selected node.

Current problem:

If both windows are open, the user can click on the first (a big one) and this will be moved to front and hide the "node details" window. That makes no sense but we cannot use a dialog because users should be able to select a different node (in the first window).