| SCION Workbench | Projects Overview | Changelog | Contributing | Sponsoring |
|---|
SCION Workbench > Feature Overview
This page gives you an overview of existing and planned main workbench features. Development is mainly driven by requirements of projects at SBB building a Traffic Management System and others. Many other features are imaginable. If a feature you need is not listed here or needs to be prioritized, please file a GitHub issue.
Done
In Progress
Planned
Deprecated
| Feature | Category | Status | Note |
|---|---|---|---|
| Workbench Layout | layout | |
Layout to display content side-by-side or stacked, all personalizable by the user via drag & drop. |
| Docked Parts DnD | layout | |
Allow dragging docked parts to other docking areas. |
| Docked Parts Menu | layout | |
Control which docked parts to display in the sidebar. |
| Perspective | layout | |
Multiple layouts, called perspectives, can be created. Users can switch between perspectives. Perspectives share the same main area, if any. |
| Part | layout | |
Visual workbench element used to create the workbench layout. Parts can be docked to the side or positioned relative to each other. A part can display content or stack views. |
| View | layout | |
Visual workbench element for displaying content stacked or side-by-side in the workbench layout. |
| Pin View | layout | |
Allow pinning views. Pinned views are not target of new navigations and not closed when closing other views. |
| Multi-Window | layout | |
Views can be moved between browser windows. |
| Part Actions | layout | |
Actions that are displayed in the tabbar of a part. Actions can stick to a view, so they are only visible if the view is active. |
| View Context Menu | layout | |
A view tab has a context menu. By default, the workbench adds some workbench-specific menu items to the context menu, such as for closing other views. Custom menu items can be added to the context menu as well. |
| Persistent Navigation | navigation | |
The arrangement of the views is added to the browser URL or local storage, enabling persistent navigation. |
| Desktop | layout | |
The workbench displays a desktop when the layout is empty (no view and no navigated part). |
| Microfrontend Support | microfrontend | |
Microfrontends can be opened in views. Embedded microfrontends can interact with the workbench using a framework-angostic workbench API. The documentation is still missing. |
| Theming | customization | |
An application can define a custom theme to change the default look of the SCION Workbench. |
| Selection Propagation | layout | |
The active view or part can propagate its current "selection" for other views to present context-sensitive content. #486 |
| Keyboard Navigation | navigation | |
Support for keyboard navigation between views #496 |
| Responsive Design | layout | |
The workbench adapts its layout to the current display size and device. #112 |
| Electron/Edge Webview 2 | env | |
The workbench can be used in desktop applications built with Electron and/or Microsoft Edge WebView2 to support window arrangements. #306 |
| Localization (l10n) | env | |
The SCION Workbench supports translation of built-in texts and application-specific texts used in the layout. |
| Browser Support | env | |
The workbench works with most modern browsers. As of now, the workbench is optimized and tested on browsers based on the Chromium rendering engine (Google Chrome, Microsoft Edge). However, the workbench should work fine on other modern browsers as well. #111 |
| Dialog | control | |
Content can be displayed in a modal dialog. A dialog can be view or application modal. Multiple dialogs are stacked. |
| Message Box | control | |
Content can be displayed in a modal message box. A message box can be view or application modal. Multiple message boxes are stacked. |
| Notification Ribbon | control | |
Notifications can be displayed to the user. Notifications slide in in the upper-right corner. Multiple notifications are displayed one below the other. |
| Popup | control | |
Content can be displayed in a popup overlay. A popup does not block the application. |
| Tab | customization | |
The built-in tab can be replaced with a custom tab implementation, e.g., to add additional functionality. |
| Optional Microfrontend Support | dependency | |
Move built-in microfrontend support to a separate plugin, reducing the minimal required dependencies and allowing for other microfrontend strategies/implementors. #312 |