Using the Nimbus Driver Designer
The Nimbus user interface is completely integrated with the Visual Studio IDE. Nimbus offers a variety of tool windows, document windows, menus, and commands for manipulating every aspect of the driver project. Driver developers can quickly navigate between Nimbus-supplied commands and windows and native Visual Studio windows with which they are already familiar, such as code editors and Solution Explorer. This topic presents an overview of the Nimbus user interface within Visual Studio and introduces UI terminology used throughout the Nimbus documentation.
The images presented in this topic show the user interface elements for an IVI.NET driver with a linked IVI-C driver. However, the same user interface elements exist for IVI-COM and stand-alone IVI-C drivers. The IVI.NET user interface is presented here for illustration purposes.
The image below shows an example of a Nimbus IVI.NET driver project in Visual Studio. Each of the Nimbus-supplied items are labeled and discussed in the sections below.
A Nimbus driver solution is simply a container for the Nimbus driver project and all of its supporting projects -- such as the unit test project, the help project, and the setup project. As with any Visual Studio solution, a Nimbus driver solution is managed from the Solution Explorer window shown on the right side of Figure 1. The node that appears at the top of Solution Explorer is the referred to as the Nimbus node -- (the node with the Nimbus icon). It is used to access project-wide features. For instance, the Driver Designer and the Driver Settings Editor are accessed by right-clicking the Nimbus node and choosing from the context menu, or by expanding the Nimbus node and double-clicking one of its child nodes.
The projects that appear in Solution Explorer beneath the Nimbus node are Nimbus Driver Help, Nimbus Driver Setup, and standard unit test project types. Though Nimbus automatically generates and manages much of the code in these projects, they can be accessed just as typical Visual Studio projects.
Most of the tasks involved in IVI driver developer are performed within a special document window -- the Driver Designer. The image in Figure 1 shows how the Driver Designer appears as a tabbed document window alongside other Visual Studio document windows -- such as code editor windows and project property pages. This makes it easy to move between the Driver Designer and other areas within the IDE.
The Driver Designer can be accessed from Solution Explorer by double-clicking the Driver Designer node. The designer is divided into three regions -- a tree view that occupies the left portion of the window, an Item Editor in the right portion of the window, and a yellow Info Panel appearing along the bottom of the window.
The tree view is used to navigate the hierarchy of types, methods and properties in the driver. Right-clicking the various nodes in the tree, reveals context menu commands for performing the most common Nimbus tasks, such as adding methods, properties, and parameters. The tree fully supports standard copy/paste functionality as well as drag and drop for quickly arranging the driver hierarchy as desired.
The right portion of the Driver Designer window is occupied by a series of Item Editors. The Item editors are used to manipulate various aspects of the method, property, parameter or other item selected in the tree view. In Figure 1, a property is selected -- making five different Item Editors available via the row of five buttons along the bottom. These are labeled "General", "Help", "Simulation", "Range Checking", and "State Caching".
The bottom portion of the Driver Designer window is occupied by a yellow window called the Info Panel. This read-only window provides useful "at-a-glance" summary information about the item selected in the tree view. For instance, when a method is selected in the tree view, the Info Panel displays the full signature of the method or property. In addition, the help summary information for the method or property is display.
If a method or property uses a type that also exists in the tree view, such as enums or interfaces defiend by the driver itself, then the Info Panel displays that type as a hyperlink. Clicking the hyperlink navigates to the type where details about the specific type can be reviewed.
Download a complete CHM version of this documentation here.