@scion/workbench 19.0.0-beta.2 → 19.0.0-beta.3

package/lib/workbench-config.d.ts

@@ -3,12 +3,105 @@ import { Signal, Type } from '@angular/core';
 import { LogAppender, LogLevel } from './logging';
 import { MicrofrontendPlatformConfig } from '@scion/microfrontend-platform';
 import { MicrofrontendPlatformConfigLoader } from './microfrontend-platform/microfrontend-platform-config-loader';
-import { WorkbenchLayoutFn, WorkbenchPerspectives } from './perspective/workbench-perspective.model';
+import { WorkbenchPerspectives } from './perspective/workbench-perspective.model';
 import { WorkbenchStorage } from './storage/workbench-storage';
+import { WorkbenchTextProviderFn } from './text/workbench-text-provider.model';
+import { WorkbenchIconProviderFn } from './icon/workbench-icon-provider.model';
+import { WorkbenchLayoutFn } from './layout/workbench-layout';
 /**
  * Configuration of the SCION Workbench.
  */
 export declare abstract class WorkbenchConfig {
+    /**
+     * Defines the layout(s) of the application. Defaults to a single layout with only a main area.
+     *
+     * An application can have multiple layouts, called perspectives. A perspective defines an arrangement of parts and views.
+     * Parts can be docked to the side or positioned relative to each other. Views are stacked in parts and can be dragged to other parts.
+     * Content can be displayed in both parts and views.
+     *
+     * A perspective typically has a main area part and other parts docked to the side, providing navigation and context-sensitive assistance to support
+     * the user's workflow. Initially empty or displaying a welcome page, the main area is where the workbench opens new views by default.
+     * Unlike any other part, the main area is shared between perspectives, and its layout is not reset when resetting perspectives.
+     *
+     * See {@link WorkbenchLayoutFn} for more information and an example.
+     */
+    abstract layout?: WorkbenchLayoutFn | WorkbenchPerspectives;
+    /**
+     * Provides texts to the SCION Workbench.
+     *
+     * A text provider is a function that returns the text for a translation key.
+     *
+     * Texts starting with the percent symbol (`%`) are passed to the text provider for translation, with the percent symbol omitted.
+     * Otherwise, the text is returned as is.
+     *
+     * The SCION Workbench uses the following translation keys for built-in texts:
+     * - workbench.clear.tooltip
+     * - workbench.close.action
+     * - workbench.close_all_tabs.action
+     * - workbench.close_other_tabs.action
+     * - workbench.close_tab.action
+     * - workbench.close_tab.tooltip
+     * - workbench.close_tabs_to_the_left.action
+     * - workbench.close_tabs_to_the_right.action
+     * - workbench.close.tooltip
+     * - workbench.dev_mode_only_hint.tooltip
+     * - workbench.minimize.tooltip
+     * - workbench.move_tab_down.action
+     * - workbench.move_tab_to_new_window.action
+     * - workbench.move_tab_to_the_left.action
+     * - workbench.move_tab_to_the_right.action
+     * - workbench.move_tab_up.action
+     * - workbench.null_content.message
+     * - workbench.null_view_developer_hint.message
+     * - workbench.ok.action
+     * - workbench.page_not_found.message
+     * - workbench.page_not_found.title
+     * - workbench.page_not_found_developer_hint.message
+     * - workbench.show_open_tabs.tooltip
+     *
+     * The function:
+     * - Can call `inject` to get any required dependencies.
+     * - Can call `toSignal` to convert an Observable to a Signal.
+     *
+     * @see WorkbenchTextProviderFn
+     */
+    abstract textProvider?: WorkbenchTextProviderFn;
+    /**
+     * Provides icons to the SCION Workbench.
+     *
+     * An icon provider is a function that returns a component for an icon. The component renders the icon.
+     *
+     * Defaults to a Material icon provider, interpreting the icon as a Material icon ligature.
+     *
+     * The default icon provider requires the application to include the Material icon font, for example in `styles.scss`, as follows:
+     * ```scss
+     * @import url('https://fonts.googleapis.com/css2?family=Material+Symbols+Rounded');
+     * ```
+     *
+     * The SCION Workbench uses the following icons:
+     * - `workbench.clear`: Clear button in input fields
+     * - `workbench.close`: Close button in views, dialogs and notifications
+     * - `workbench.dirty`: Visual indicator for view with unsaved content
+     * - `workbench.menu_down`: Menu button of drop down menus
+     * - `workbench.minimize`: Minimize button in docked parts
+     * - `workbench.pin`: Visual indicator for a pinned view
+     * - `workbench.search`: Visual indicator in search or filter fields
+     *
+     * To not replace built-in workbench icons, the icon provider can return `undefined` for icons starting with the `workbench.` prefix.
+     *
+     * The function can call `inject` to get any required dependencies.
+     *
+     * @see WorkbenchIconProviderFn
+     */
+    abstract iconProvider?: WorkbenchIconProviderFn;
+    /**
+     * Specifies the component to display in `<wb-workbench>` while the workbench is starting.
+     *
+     * Defaults to a splash showing a loading indicator (ellipsis throbber).
+     *
+     * Note: No splash screen is displayed if starting the workbench in an app initializer.
+     */
+    abstract splashComponent?: ComponentType<unknown>;
     /**
      * Specifies the component to display a view tab, enabling custom design or functionality.
      *
@@ -30,35 +123,38 @@ export declare abstract class WorkbenchConfig {
      */
     abstract viewMenuItems?: ViewMenuItemsConfig | false;
     /**
-     * Configures the workbench startup.
+     * Configures startup of the SCION Workbench.
+     *
+     * The SCION Workbench starts automatically when the `<wb-workbench>` component is added to the DOM. Alternatively,
+     * the workbench can be started manually using {@link WorkbenchLauncher.launch}, such as in an app initializer or a route guard.
      *
-     * The {@link WorkbenchLauncher} is used to start the workbench. During startup, it runs registered workbench initializers
-     * and waits for them to complete. You can inject {@link WorkbenchStartup} to get notified when the startup is complete.
+     * The application can hook into the startup process of the SCION Workbench by providing one or more initializers to {@link provideWorkbenchInitializer}.
+     * Initializers execute at defined points during startup, enabling the application's controlled initialization. The workbench is fully started once
+     * all initializers have completed.
      *
-     * Refer to {@link WorkbenchInitializer} to learn how to register a workbench initializer.
+     * The application can inject {@link WorkbenchStartup} to check if the workbench has completed startup.
      */
     abstract startup?: {
         /**
-         * Configures the workbench launching strategy. Defaults to `LAZY` if not specified.
-         *
-         *  - **APP_INITIALIZER**
-         *   Launches the workbench in an Angular `APP_INITIALIZER`, which is before bootstrapping the app component.
+         * Controls when to start the SCION Workbench. Defaults to `LAZY`.
          *
          * - **LAZY**
-         *   Launches the workbench at the latest when bootstrapping the workbench root component `<wb-workbench>`.
+         *   Starts the workbench when the `<wb-workbench>` component is added to the DOM or manually via {@link WorkbenchLauncher#launch},
+         *   e.g., from a route guard or app initializer.
          *
-         *   With this strategy, you are flexible when to start the workbench. You can start the workbench explicitly by
-         *   calling {@link WorkbenchLauncher#launch}, e.g., to launch the workbench from a route guard or app initializer,
-         *   or start it automatically when adding the workbench root component `<wb-workbench>` to the Angular component
-         *   tree.
+         *  - **APP_INITIALIZER**
+         *   Starts the workbench during application bootstrapping, blocking Angular's app startup until the workbench is ready.
+         *   No splash is displayed.
+         *
+         * @deprecated since version 19.0.0-beta.3. To start the workbench in an app initializer, use Angular's `provideAppInitializer()` function: `provideAppInitializer(() => inject(WorkbenchLauncher).launch())`. Otherwise, no migration is necessary. No replacement. API will be removed in version 21.
          */
-        launcher?: 'APP_INITIALIZER' | 'LAZY';
+        launcher?: 'LAZY' | 'APP_INITIALIZER';
         /**
-         * Specifies the component to display when mounting the workbench root component `<wb-workbench>` to the DOM before the
-         * workbench startup has finished.
+         * Specifies the component to display in `<wb-workbench>` while the workbench is starting.
+         *
+         * Note: No splash screen is displayed when using the app initializer strategy.
          *
-         * Note that when launching the workbench in an Angular `APP_INITIALIZER`, no splash will display since the workbench
-         * will start upfront.
+         * @deprecated since version 19.0.0-beta.3. Property has been moved. Configure the splash in `WorkbenchConfig.splashComponent`. Property will be removed in version 21.
          */
         splash?: ComponentType<unknown>;
     };
@@ -85,13 +181,6 @@ export declare abstract class WorkbenchConfig {
      * under the DI token {@link MICROFRONTEND_PLATFORM_POST_STARTUP}.
      */
     abstract microfrontendPlatform?: MicrofrontendPlatformConfig | Type<MicrofrontendPlatformConfigLoader>;
-    /**
-     * Defines the workbench layout. Multiple layouts can be defined in the form of perspectives.
-     * If not set, defaults to a layout with only a main area.
-     *
-     * See {@link WorkbenchLayoutFn} for more information and an example.
-     */
-    abstract layout?: WorkbenchLayoutFn | WorkbenchPerspectives;
     /**
      * Provides persistent storage to the SCION Workbench.
      *
@@ -130,20 +219,100 @@ export declare abstract class WorkbenchConfig {
 /**
  * Configuration of built-in menu items in the view's context menu.
  *
- * Each property represents a menu item, allowing customization of visibility, text, accelerators, and more.
+ * Each property represents a menu item, allowing customization of visibility, accelerators, and more.
  *
- * Set a built-in menu item to `false` to exclude it.
+ * Texts can be changed or localized using a {@link WorkbenchTextProviderFn text provider} passed to {@link provideWorkbench} via the workbench config object.
  */
 export interface ViewMenuItemsConfig {
+    /**
+     * Configures the menu item for closing a view tab.
+     *
+     * Set to `false` to exclude it.
+     *
+     * The menu item text can be changed or localized using a {@link WorkbenchTextProviderFn}.
+     * Translation key: `workbench.close_tab.action`
+     */
     close?: MenuItemConfig | false;
+    /**
+     * Configures the menu item for closing other view tabs.
+     *
+     * Set to `false` to exclude it.
+     *
+     * The menu item text can be changed or localized using a {@link WorkbenchTextProviderFn}.
+     * Translation key: `workbench.close_other_tabs.action`
+     */
     closeOthers?: MenuItemConfig | false;
+    /**
+     * Configures the menu item for closing all view tabs.
+     *
+     * Set to `false` to exclude it.
+     *
+     * The menu item text can be changed or localized using a {@link WorkbenchTextProviderFn}.
+     * Translation key: `workbench.close_all_tabs.action`
+     */
     closeAll?: MenuItemConfig | false;
+    /**
+     * Configures the menu item for closing view tabs to the right.
+     *
+     * Set to `false` to exclude it.
+     *
+     * The menu item text can be changed or localized using a {@link WorkbenchTextProviderFn}.
+     * Translation key: `workbench.close_tabs_to_the_right.action`
+     */
     closeToTheRight?: MenuItemConfig | false;
+    /**
+     * Configures the menu item for closing view tabs to the left.
+     *
+     * Set to `false` to exclude it.
+     *
+     * The menu item text can be changed or localized using a {@link WorkbenchTextProviderFn}.
+     * Translation key: `workbench.close_tabs_to_the_left.action`
+     */
     closeToTheLeft?: MenuItemConfig | false;
+    /**
+     * Configures the menu item for moving a view up.
+     *
+     * Set to `false` to exclude it.
+     *
+     * The menu item text can be changed or localized using a {@link WorkbenchTextProviderFn}.
+     * Translation key: `workbench.move_tab_up.action`
+     */
     moveUp?: MenuItemConfig | false;
+    /**
+     * Configures the menu item for moving a view to the right.
+     *
+     * Set to `false` to exclude it.
+     *
+     * The menu item text can be changed or localized using a {@link WorkbenchTextProviderFn}.
+     * Translation key: `workbench.move_tab_to_the_right.action`
+     */
     moveRight?: MenuItemConfig | false;
+    /**
+     * Configures the menu item for moving a view down.
+     *
+     * Set to `false` to exclude it.
+     *
+     * The menu item text can be changed or localized using a {@link WorkbenchTextProviderFn}.
+     * Translation key: `workbenchworkbench.move_tab_down.action`
+     */
     moveDown?: MenuItemConfig | false;
+    /**
+     * Configures the menu item for moving a view to the left.
+     *
+     * Set to `false` to exclude it.
+     *
+     * The menu item text can be changed or localized using a {@link WorkbenchTextProviderFn}.
+     * Translation key: `workbench.move_tab_to_the_left.action`
+     */
     moveLeft?: MenuItemConfig | false;
+    /**
+     * Configures the menu item for moving a view to a new window.
+     *
+     * Set to `false` to exclude it.
+     *
+     * The menu item text can be changed or localized using a {@link WorkbenchTextProviderFn}.
+     * Translation key: `workbench.move_tab_to_new_window.action`
+     */
     moveToNewWindow?: MenuItemConfig | false;
 }
 /**
@@ -160,6 +329,8 @@ export interface MenuItemConfig {
      * Can be a string or a function that returns a string or a {@link Signal}.
      *
      * The function can call `inject` to get any required dependencies, or use `toSignal` to convert an observable to a signal.
+     *
+     * @deprecated since version 19.0.0-beta.3. Register a text provider to change or localize menu item texts. Register the text provider via workbench configuration passed to the `provideWorkbench` function. API will be removed in version 21.
      */
     text?: string | (() => string | Signal<string>);
     accelerator?: string[];

package/lib/workbench.component.d.ts

@@ -1,4 +1,5 @@
-import { WorkbenchStartup } from './startup/workbench-launcher.service';
+import { WorkbenchStartup } from './startup/workbench-startup.service';
+import { ɵWorkbenchService } from './ɵworkbench.service';
 import * as i0 from "@angular/core";
 /**
  * Main entry point component of the SCION Workbench.
@@ -6,12 +7,18 @@ import * as i0 from "@angular/core";
 export declare class WorkbenchComponent {
     private _workbenchLauncher;
     private _logger;
+    private readonly _workbenchRouter;
     private _iframeOverlayHost;
     private _viewDropZoneOverlayHost;
     /** Splash to display during workbench startup. */
     protected splash: import("@angular/cdk/portal").ComponentType<unknown>;
     protected workbenchStartup: WorkbenchStartup;
+    protected workbenchService: ɵWorkbenchService;
     constructor();
+    /**
+     * Toggles layout maximization by pressing Ctrl+Shift+F12.
+     */
+    private installMaximizeShortcutListener;
     /**
      * Starts the SCION Workbench. Has no effect if already started, e.g., in an app initializer or route guard.
      */

package/lib/workbench.constants.d.ts

@@ -11,6 +11,10 @@ export declare const PART_ID_PREFIX = "part.";
  * @see ViewId
  */
 export declare const VIEW_ID_PREFIX = "view.";
+/**
+ * Represents the id prefix of activities.
+ */
+export declare const ACTIVITY_ID_PREFIX = "activity.";
 /**
  * Represents the id prefix of popups.
  */

package/lib/workbench.model.d.ts

@@ -205,6 +205,8 @@ export type WorkbenchPartActionFn = (part: WorkbenchPart) => WorkbenchPartAction
 export type WorkbenchViewMenuItemFn = (view: WorkbenchView) => WorkbenchMenuItem | null;
 /**
  * Information about a workbench theme.
+ *
+ * @deprecated since version 19.0.0-beta.3. Read the theme from `WorkbenchService.settings.theme` signal, and the color scheme from 'getComputedStyle(inject(DOCUMENT).documentElement).colorScheme'. API will be removed in version 21.
  */
 export interface WorkbenchTheme {
     /**

package/lib/workbench.provider.d.ts

@@ -1,36 +1,87 @@
 import { EnvironmentProviders } from '@angular/core';
 import { WorkbenchConfig } from './workbench-config';
 /**
- * Enables and configures the SCION Workbench in an application, returning a set of dependency-injection providers to be registered in Angular.
+ * Enables and configures the SCION Workbench, returning a set of dependency-injection providers to be registered in Angular.
  *
- * SCION Workbench enables the creation of Angular web applications that require a flexible layout to arrange content side-by-side
+ * ### About
+ * SCION Workbench enables the creation of Angular web applications that require a flexible layout to display content side-by-side
  * or stacked, all personalizable by the user via drag & drop. This type of layout is ideal for applications with non-linear workflows,
  * enabling users to work on content in parallel.
  *
- * The workbench layout is a grid of parts. Parts are aligned relative to each other. Each part is a stack of views. Content is displayed in views or parts.
+ * An application can have multiple layouts, called perspectives. A perspective defines an arrangement of parts and views.
+ * Parts can be docked to the side or positioned relative to each other. Views are stacked in parts and can be dragged to other parts.
+ * Content can be displayed in both parts and views.
  *
- * The layout can be divided into a main and a peripheral area, with the main area as the primary place for opening views.
- * The peripheral area arranges parts around the main area to provide navigation or context-sensitive assistance to support
- * the user's workflow. Defining a main area is optional and recommended for applications requiring a dedicated and maximizable
- * area for user interaction.
+ * Users can personalize the layout of a perspective and switch between perspectives. The workbench remembers the last layout of each perspective,
+ * restoring it the next time it is activated.
  *
- * Multiple layouts, called perspectives, are supported. Perspectives can be switched. Only one perspective is active at a time.
- * Perspectives share the same main area, if any.
+ * A perspective typically has a main area part and other parts docked to the side, providing navigation and context-sensitive assistance to support
+ * the user's workflow. Initially empty or displaying a welcome page, the main area is where the workbench opens new views by default. Users can split
+ * the main area (or any other part) by dragging views side-by-side, vertically and horizontally, even across windows.
  *
- * ---
- * Usage:
+ * Unlike any other part, the main area is shared between perspectives, and its layout is not reset when resetting perspectives. Having a main area and
+ * multiple perspectives is optional.
  *
+ * ### Usage
  * ```ts
- * import {bootstrapApplication} from '@angular/platform-browser';
+ * import {MAIN_AREA, provideWorkbench, WorkbenchLayoutFactory} from '@scion/workbench';
  * import {provideRouter} from '@angular/router';
  * import {provideAnimations} from '@angular/platform-browser/animations';
- * import {provideWorkbench} from '@scion/workbench';
+ * import {bootstrapApplication} from '@angular/platform-browser';
+ *
+ * bootstrapApplication(AppComponent, {
+ *   providers: [
+ *     provideWorkbench({
+ *       layout: (factory: WorkbenchLayoutFactory) => factory
+ *         .addPart(MAIN_AREA)
+ *         .addPart('todos', {dockTo: 'left-top'}, {label: 'Todos', icon: 'checklist'})
+ *         .navigatePart(MAIN_AREA, ['overview'])
+ *         .navigatePart('todos', ['todos'])
+ *         .activatePart('todos'),
+ *     }),
+ *     provideRouter([
+ *       {path: 'overview', loadComponent: () => import('./overview/overview.component')},
+ *       {path: 'todos', loadComponent: () => import('./todos/todos.component')},
+ *     ]),
+ *     provideAnimations(),
+ *   ],
+ * });
+ * ```
+ *
+ * ### Startup
+ * The SCION Workbench starts automatically when the `<wb-workbench>` component is added to the DOM. Alternatively, the workbench can be
+ * started manually using the {@link WorkbenchLauncher}, such as in an app initializer or a route guard.
+ *
+ * Example of starting the workbench in an app initializer:
+ *
+ * ```ts
+ * import {provideWorkbench, WorkbenchLauncher} from '@scion/workbench';
+ * import {bootstrapApplication} from '@angular/platform-browser';
+ * import {inject, provideAppInitializer} from '@angular/core';
+ *
+ * bootstrapApplication(AppComponent, {
+ *   providers: [
+ *     provideWorkbench(),
+ *     provideAppInitializer(() => inject(WorkbenchLauncher).launch())
+ *   ]
+ * });
+ * ```
+ *
+ * Starting the workbench in an app initializer will block Angular's app startup until the workbench is ready.
+ *
+ * ### Startup Hooks
+ * The application can hook into the startup process of the SCION Workbench by providing one or more initializers to the `provideWorkbenchInitializer()` function.
+ * Initializers execute at defined points during startup, enabling the application's controlled initialization.
+ *
+ * ```ts
+ * import {provideWorkbench, provideWorkbenchInitializer} from '@scion/workbench';
+ * import {bootstrapApplication} from '@angular/platform-browser';
+ * import {inject} from '@angular/core';
  *
  * bootstrapApplication(AppComponent, {
  *   providers: [
  *     provideWorkbench(),
- *     provideRouter([]), // required by the SCION Workbench
- *     provideAnimations(), // required by the SCION Workbench
+ *     provideWorkbenchInitializer(() => inject(SomeService).init()),
  *   ],
  * });
  * ```

package/lib/workbench.service.d.ts

@@ -3,29 +3,33 @@ import { WorkbenchPartActionFn, WorkbenchTheme, WorkbenchViewMenuItemFn } from '
 import { ViewId, WorkbenchView } from './view/workbench-view.model';
 import { WorkbenchPerspective, WorkbenchPerspectiveDefinition } from './perspective/workbench-perspective.model';
 import { PartId, WorkbenchPart } from './part/workbench-part.model';
-import { Signal } from '@angular/core';
+import { Signal, WritableSignal } from '@angular/core';
 import { WorkbenchLayout } from './layout/workbench-layout';
 import * as i0 from "@angular/core";
 /**
  * The central class of the SCION Workbench.
  *
- * SCION Workbench enables the creation of Angular web applications that require a flexible layout to arrange content side-by-side
+ * SCION Workbench enables the creation of Angular web applications that require a flexible layout to display content side-by-side
  * or stacked, all personalizable by the user via drag & drop. This type of layout is ideal for applications with non-linear workflows,
  * enabling users to work on content in parallel.
  *
- * The workbench layout is a grid of parts. Parts are aligned relative to each other. Each part is a stack of views. Content is displayed in views or parts.
+ * An application can have multiple layouts, called perspectives. A perspective defines an arrangement of parts and views.
+ * Parts can be docked to the side or positioned relative to each other. Views are stacked in parts and can be dragged to other parts.
+ * Content can be displayed in both parts and views.
  *
- * The layout can be divided into a main and a peripheral area, with the main area as the primary place for opening views.
- * The peripheral area arranges parts around the main area to provide navigation or context-sensitive assistance to support
- * the user's workflow. Defining a main area is optional and recommended for applications requiring a dedicated and maximizable
- * area for user interaction.
+ * Users can personalize the layout of a perspective and switch between perspectives. The workbench remembers the last layout of each perspective,
+ * restoring it the next time it is activated.
  *
- * Multiple layouts, called perspectives, are supported. Perspectives can be switched. Only one perspective is active at a time.
- * Perspectives share the same main area, if any.
+ * A perspective typically has a main area part and other parts docked to the side, providing navigation and context-sensitive assistance to support
+ * the user's workflow. Initially empty or displaying a welcome page, the main area is where the workbench opens new views by default. Users can split
+ * the main area (or any other part) by dragging views side-by-side, vertically and horizontally, even across windows.
+ *
+ * Unlike any other part, the main area is shared between perspectives, and its layout is not reset when resetting perspectives. Having a main area and
+ * multiple perspectives is optional.
  */
 export declare abstract class WorkbenchService {
     /**
-     * Provides the snapshot of the current workbench layout.
+     * Provides the layout of the workbench.
      *
      * The layout is an immutable object. Modifications have no side effects. The layout can be modified using {@link WorkbenchRouter.navigate}.
      */
@@ -147,10 +151,41 @@ export declare abstract class WorkbenchService {
      * See the documentation of `@scion/workbench` SCSS module for more information.
      *
      * @param theme - The name of the theme to switch to.
+     *
+     * @deprecated since version 19.0.0-beta.3. Switch theme using `WorkbenchService.settings.theme` signal. API will be removed in version 21.
      */
     abstract switchTheme(theme: string): Promise<void>;
+    /**
+     * Defines settings to adapt the workbench to personal preferences and working styles.
+     *
+     * Settings are stored in {@link WorkbenchConfig.storage} (defaults to local storage).
+     */
+    abstract readonly settings: {
+        /**
+         * Specifies the workbench theme.
+         *
+         * Defaults to the `sci-theme` attribute set on the HTML root element, or to the user's OS color scheme preference if not set.
+         *
+         * Built-in themes: `scion-light` and `scion-dark`.
+         */
+        theme: WritableSignal<string | null>;
+        /**
+         * Controls the alignment of the bottom docked panel.
+         *
+         * Defaults to the `--sci-workbench-layout-panel-align` design token, or `justify` if not set.
+         */
+        panelAlignment: WritableSignal<'left' | 'right' | 'center' | 'justify'>;
+        /**
+         * Controls animation of docked panels.
+         *
+         * Defaults to the `--sci-workbench-layout-panel-animate` design token, or `true` if not set.
+         */
+        panelAnimation: WritableSignal<boolean>;
+    };
     /**
      * Provides the current workbench theme, if any.
+     *
+     * @deprecated since version 19.0.0-beta.3. Read the theme from `WorkbenchService.settings.theme` signal, and the color scheme from 'getComputedStyle(inject(DOCUMENT).documentElement).colorScheme'. API will be removed in version 21.
      */
     abstract readonly theme: Signal<WorkbenchTheme | null>;
     static ɵfac: i0.ɵɵFactoryDeclaration<WorkbenchService, never>;

package/lib//311/265workbench.service.d.ts

@@ -2,12 +2,11 @@ import { Signal } from '@angular/core';
 import { WorkbenchPartActionFn, WorkbenchTheme, WorkbenchViewMenuItemFn } from './workbench.model';
 import { Disposable } from './common/disposable';
 import { WorkbenchService } from './workbench.service';
-import { WorkbenchPerspective, WorkbenchPerspectiveDefinition } from './perspective/workbench-perspective.model';
+import { WorkbenchPerspectiveDefinition } from './perspective/workbench-perspective.model';
 import { ɵWorkbenchView } from './view/ɵworkbench-view.model';
 import { ɵWorkbenchPart } from './part/ɵworkbench-part.model';
 import { ɵWorkbenchPerspective } from './perspective/ɵworkbench-perspective.model';
 import { ViewId } from './view/workbench-view.model';
-import { ɵWorkbenchLayout } from './layout/ɵworkbench-layout';
 import { PartId } from './part/workbench-part.model';
 import * as i0 from "@angular/core";
 export declare class ɵWorkbenchService implements WorkbenchService {
@@ -18,15 +17,17 @@ export declare class ɵWorkbenchService implements WorkbenchService {
     private readonly _viewMenuItemRegistry;
     private readonly _viewRegistry;
     private readonly _perspectiveService;
-    private readonly _layoutService;
-    private readonly _workbenchThemeSwitcher;
-    readonly layout: Signal<ɵWorkbenchLayout>;
+    readonly layout: Signal<import("./layout/\u0275workbench-layout").ɵWorkbenchLayout>;
     readonly perspectives: Signal<ɵWorkbenchPerspective[]>;
     readonly parts: Signal<ɵWorkbenchPart[]>;
     readonly views: Signal<ɵWorkbenchView[]>;
+    readonly activePerspective: Signal<ɵWorkbenchPerspective | undefined>;
     readonly theme: Signal<WorkbenchTheme | null>;
-    readonly activePerspective: Signal<WorkbenchPerspective | undefined>;
-    constructor();
+    readonly settings: {
+        theme: import("@angular/core").WritableSignal<string | null>;
+        panelAlignment: import("@angular/core").WritableSignal<"justify">;
+        panelAnimation: import("@angular/core").WritableSignal<true>;
+    };
     /** @inheritDoc */
     getPerspective(perspectiveId: string): ɵWorkbenchPerspective | null;
     /** @inheritDoc */
@@ -47,6 +48,7 @@ export declare class ɵWorkbenchService implements WorkbenchService {
     registerViewMenuItem(fn: WorkbenchViewMenuItemFn): Disposable;
     /** @inheritDoc */
     switchTheme(theme: string): Promise<void>;
+    private computeLegacyThemeObject;
     static ɵfac: i0.ɵɵFactoryDeclaration<ɵWorkbenchService, never>;
     static ɵprov: i0.ɵɵInjectableDeclaration<ɵWorkbenchService>;
 }

package/package.json

@@ -1,7 +1,7 @@
 {
   "name": "@scion/workbench",
-  "version": "19.0.0-beta.2",
-  "description": "SCION Workbench enables the creation of Angular web applications that require a flexible layout to arrange content side-by-side or stacked, all personalizable by the user via drag & drop.",
+  "version": "19.0.0-beta.3",
+  "description": "SCION Workbench enables the creation of Angular web applications that require a flexible layout to display content side-by-side or stacked, all personalizable by the user via drag & drop. This type of layout is ideal for applications with non-linear workflows, enabling users to work on content in parallel.",
   "license": "EPL-2.0",
   "private": false,
   "publishConfig": {
@@ -34,7 +34,7 @@
     "@angular/animations": "^19.0.0",
     "@angular/forms": "^19.0.0",
     "@angular/router": "^19.0.0",
-    "@scion/components": "^19.0.0",
+    "@scion/components": "^19.2.0",
     "@scion/toolkit": "^1.6.0",
     "@scion/microfrontend-platform": "^1.3.0",
     "@scion/workbench-client": "^1.0.0-beta.26",

package/lib/common/grid-element-if-visible.pipe.d.ts

@@ -1,13 +0,0 @@
-import { PipeTransform } from '@angular/core';
-import { MPart, MTreeNode } from '../layout/workbench-layout.model';
-import * as i0 from "@angular/core";
-/**
- * Returns given grid element, but only if visible.
- *
- * @see isGridElementVisible
- */
-export declare class GridElementIfVisiblePipe implements PipeTransform {
-    transform(gridElement: MTreeNode | MPart | null | undefined): MTreeNode | MPart | null;
-    static ɵfac: i0.ɵɵFactoryDeclaration<GridElementIfVisiblePipe, never>;
-    static ɵpipe: i0.ɵɵPipeDeclaration<GridElementIfVisiblePipe, "wbGridElementIfVisible", true>;
-}

package/lib/layout/migration/workbench-layout-migration-v7.service.d.ts

@@ -1,10 +0,0 @@
-import { WorkbenchMigration } from '../../migration/workbench-migration';
-import * as i0 from "@angular/core";
-/**
- * Migrates the workbench layout from version 6 to version 7.
- */
-export declare class WorkbenchLayoutMigrationV7 implements WorkbenchMigration {
-    migrate(json: string): string;
-    static ɵfac: i0.ɵɵFactoryDeclaration<WorkbenchLayoutMigrationV7, never>;
-    static ɵprov: i0.ɵɵInjectableDeclaration<WorkbenchLayoutMigrationV7>;
-}

package/lib/microfrontend-platform/microfrontend-notification/microfrontend-notification-intent-handler.service.d.ts

@@ -1,17 +0,0 @@
-import { IntentClient } from '@scion/microfrontend-platform';
-import { Logger } from '../../logging';
-import { NotificationService } from '../../notification/notification.service';
-import * as i0 from "@angular/core";
-/**
- * Handles intents that refer to the built-in notification capability, allowing microfrontends to display simple text notifications.
- *
- * This class is constructed after connected to the SCION Microfrontend Platform via {@link MICROFRONTEND_PLATFORM_POST_STARTUP} DI token.
- *
- * @see WorkbenchHostManifestInterceptor
- * @see MICROFRONTEND_PLATFORM_POST_STARTUP
- */
-export declare class MicrofrontendNotificationIntentHandler {
-    constructor(intentClient: IntentClient, notificationService: NotificationService, logger: Logger);
-    static ɵfac: i0.ɵɵFactoryDeclaration<MicrofrontendNotificationIntentHandler, never>;
-    static ɵprov: i0.ɵɵInjectableDeclaration<MicrofrontendNotificationIntentHandler>;
-}