Concepts of Fluent User Interface

Table of Contents

• Introduction
• Controls in Fluent UI
• Design Concept
• Cookbook to convert user interface to Fluent UI
• Reference Manual

Introduction

The Creo Elements/Direct Modeling Fluent User Interface replaces the previous Menu and Task Bar UI and includes these major components:

• Ribbon along with Quick Access Toolbar
• Status Bar
• Mini Toolbars

A ribbon is a command bar structured into tabs and groups. A group is a labeled set of commands which are closely related. In addition to tabs and groups a ribbon consists of:

• A Main Menu which is the first tab in the ribbon on the left hand side. In Creo Elements/Direct Modeling it is labeled "File" and contains a number of very often used actions generic for all applications and modules.
• Dialog box launchers are buttons to show specific commands. By default they are used to show settings user interface.
• A ribbon button can either call a dialog directly or open a ribbon button menu.
• Ribbon button menus consist of buttons, title, separator or further submenus.
• A split button keeps the information of the last called dialog from the ribbon button menu and calls it's action when the user presses on the left side of the icon. Pressing on the right side (the arrow) opens the ribbon button menu.
• A Quick Access Toolbar is a small user customizable toolbar which contains the most often used commands.

The status bar displays current prompt text and contains additional controls for certain actions like setting current part or workplane.

Mini toolbars are being displayed context depending on the current preselection. A mini toolbar fades away when you move the mouse cursor away from it. It is also displayed together with the context menu on a right mouse button click.

Controls in Fluent UI

A control in Fluent UI is a push button, toggle button, range control (combo box), separator or edit control.

The definition of the controls visible in the Fluent UI is based on available commands. The concept of available commands is described here. The action of a control is defined in the available command. It can be a dialog created via sd-defdialog, any existing command or a lisp form, for instance to display specific user interface. By default also the command name, description, icon and enable status is defined with the available command. These properties can be overwritten in the definition of a ribbon control.

Design Concept

Home Tab purpose

The goal is to minimize the need to switch between different tabs. Therefore the contents of the Home tab are dedicated to support a specific task. Examples are:

• Modeling: Creation and modification of 3D models
• Annotation: Creation and annotation of drawings from a 3D model
• Sheet Metal: Creation and modification of Sheet Metal parts

Focus on most important commands

Focus user's attention on important commands using large icons.

Adoption to user preferences

Split menu buttons give fast access to the last used command. (see above)

Rarely used commands

Rarely used commands are listed in a menu button at the end of a ribbon group named ... More to keep the UI overall small.

Common group layout and naming

Ribbon groups that have the same functions are ordered and named the same way in Modeling, Annotation and Drafting. Examples are "Draw" and "Annotate".

Static ribbon layout

The ribbon layout is only changed when switching between different applications. The visibility of ribbon controls is not changed during run time. Only the accessibility (enable/disable) might be changed depending on a certain context.

Fast access to Settings

User has fast access to group specific settings using the Dialog Box Launcher. All settings are accessible via the "File" tab.

Fast access to Utilities

User has fast access to "Utilities" ribbon group in all tabs (not View & Application). This group contains frequently used utility commands such as "Delete 2D".

File Tab and Database Integration

The File tab has 4 main purposes:

• Load and Save functionality
• Database Access (all Database Integrations add their contents to the File Tab in the same way)
• Print
• Customization & Tools (for example "Search")

Application switching and Modules

Applications exchange the ribbon contents and replace the Home tab tailored to the specific application.

Modules extend the functionality and append addon tab(s) to the Modeling ribbon behind the existing tabs. For each module a single addon-context should be created and used with every module specific addon tab. This way those addon-tabs are also visibly grouped together.

Common User Experience

• Skin
• Look & Feel
• Mouse Interaction
• Command Mini Toolbar
• Right Mouse Menu
• Function Keys (F1, F2, F9, F11, F12)