Bentley Systems, Inc.

Barry J Bentley

Keith A Bentley

Raymond B Bentley

Gino Cortesi

John Gooding

Samuel W Wilson

R Brien Bastings

Sam Wilson

William Steinbock

In one embodiment, techniques are used to create a customized 3-D menu for controlling an application (e.g., a CAD application) leveraging the application's native storage format to describe the menu's appearance and function. The menu is defined using elements of a model to which commands are associated within the storage format. The elements, upon later display, operate as menu items, whose selection activates the associated command. The application's (e.g., the CAD application's) visualization capabilities may be used to rotate, zoom, or otherwise manipulated the model in in 3-D space to create a desired appearance. A view of the model is then stored within the storage format to defined an initial appearance of the 3-D menu. Upon later display, the view of the 3-D menu is loaded to provide the defined initial appearance.

3-D screen menus

An element template system allowing users to define a named set of element symbology properties to be associated with a graphic element is provided. When the element template is active, it sets the active drawing settings to match the template and associates newly created elements with the active template. Once elements are associated with an element template, the template can be used for checking for compliance with a graphics standards for that project. The element templates technology can be used to update elements and existing files to match a specific set of template properties. The element templates defining a particular graphic element are stored in the same design file as that graphic element so that when the graphic element design file is transported the element templates are also transported with the file, thereby eliminating a need to be coupled to a database or other form of external data.

System and method for visually representing a project using graphic elements

Conventional file-based engineering design data for an engineering model are represented by a plurality of components. The plurality of components are kept in stores, which reside on servers. Each store contains the components that correspond to the elements of one design file. The stores also maintain a history of changes made to the components. A plurality of client computers are bidirectionally connected to the servers. Each client computer may obtain the current version of the components and may send locally edited versions of the components back to the servers to replace the current versions in the stores. At the client computer, the user interacts with the components using conventional file-based software. Before the locally edited versions of the components are committed to the servers to replace the current versions, a synchronization and merging process occurs whereby the latest version of the components are downloaded to the client computer and are compared to the locally edited version of the components to detect resolvable (compatible) and unresolvable (incompatible) conflicts. The commit process is performed only if no unresolvable conflicts exist between the two versions of the components. To facilitate translation between file-based data and components, a schema is written to 'wrap' each of the engineering file formats. Each schema is a set of classes that capture all of the information in the file-based data.

System, method and computer program product for collaborative engineering using component and file oriented tools

Conventional file-based engineering design data for an engineering model are represented by a plurality of components. Each component has a unique identifier, a set of fields, each field having a data type and a data value, and a program which interprets and modifies the fields. The plurality of components are stored in a repository of a server. The repository also stores a history of any changes made to the components. A plurality of client computers are bidirectionally connected to the server. Each client computer may obtain the current version of the components and may send locally edited versions of the components back to the server to replace the current versions in the repository. At the client computer, the user interacts with the components using conventional file-based software. Before locally edited versions of the components are committed to the server to replace the current versions, a synchronization and merging process occurs whereby the latest version of the components are downloaded to the client computer and are compared to the locally edited version of the components to detect resolvable (compatible) and unresolvable (incompatible) conflicts therebetween. The commit process is performed only if no unresolvable conflicts exist between the two versions of the components. To facilitate translation between file-based data and components, a schema is written to &ldquo;wrap&rdquo; each of the engineering file formats. Each schema is a set of classes that capture all of the information in the file-based data.

Growing community of inventors

Elverson, PA, United States of America

Barry J Bentley