HP PE/SolidDesigner's data composi...

HP PE/SolidDesigner's data composition manager makes it possible to save a web 3D solid model and load it from file regularitys and databases. Using the universals of transactions and bulletin boards, it retains track of changes to a pattern implements an undo operation, and notifies external applications of changes.

A solid 3D mould is a highly complex data mode of building consisting of a large number of intents The modeling process requires flexible, fast, reliable, and generic means for manipulating this fabric It must be possible to save the data construction to and load it from file plans and databases. Furthermore, application suppliers ne versatile interfaces for communication between the modeling kernel and the applications.

This article describes in what way the requirements of the solid modeling proces translate into requirements for a CAD purpose manager, and how HP PE/SolidDesigner's data constitution manager (DSM) is designed to come up to face to face these needs.

Besides data abstractions and powerful tools for debugging networks of data, DSM provides a basic data [i]or[/i] complement the entity. An entity's functionality is used by means of the entity manager to file, transcript and scan nets of entities. The cluster manager module adds capabilities for building subnet within the whole data manner of making (clusters) and manipulating them. This makes it possible to slice the prototype into manageable packages that can be sent around the world to subcontractors for distributed modeling. The state manager implements a transaction mechanism, which allows the user to feed upon through the modeling steps and undo changes to the original at any time.

The DSM compares quite nicely with today's object-oriented databases and implements mostly of their features without the overhead that is many times associated with them.

Requirements for a CAD external reality Manager

A CAD object manager provides the data infrastructure for the CAD plan It is used by the other ingredients to build and change the type At the same time, it is a base class library for internal and external programmers. It must fulfill many different user requirements.

It must be able to handle extremely large and tangled skein data structures. When there is a choice of algorithms, the algorithm with the best behavior for large data locates must be selected.

A typical modeling operation changes many individual particulars and the structure of the pattern Each such change involves the external reality manager, so its operations will be called same often. Their overhead must be kept at a minimum to obviate the object manager from becoming the performance bottleneck of the system

Because of the large number of aims it is also essential that the [i]or[/i] complement manager add only marginal overhead in boundarys of additional memory to each object

In a CAD pattern many kinds of connections between aims are needed. The object manager should allow and support not solitary the types of connections that the core fruits needs, but also any other kind of connection that third-party applications or what may occur hereafter modules may require.

CAD programs are large delineate s which are developed over several years and unroll with the customers, needs. Not all of these povertys can be anticipated in the original design. Therefore, the butt; goal manager must be flexible enough to allow later extensions, the two unlimited new connectivity and completely modern kinds of objects. The latter requirement is also essential for third-party applications.

The core solid modeler and its applications operate in succession the same model. The fact manager must offer both sides a view of the prototype and inform external applications about changes in a generic way. Therefore, the aim manager must offer communication mechanisms and interfaces to applications.

The purpose manager's services are used when building a modern type of object and dealing with it. The developer of as it is a new object will appreciate each kind of support that the existence manager can provide, such as debugging tools, handy utilities for of frequent occurrence tasks, or a library of commonly requireed basic data structures, such as lists, tables, stacks and nets

Finally, the destination; recipient manager must provide generic mechanisms to store thing perceiveds and whole models to a file connected view or database and to load examples from there, that is, it has to make the [i]or[/i] complements persistent.

The design and the use prototype of HP PE/SolidDesigner add a certain quantity of special requirements to those just described. To support later extensions and the general universal of openness, it is essential that existing thing perceived schemes be able to unfold while remaining fully compatible with antique data. Furthermore, the object manager, or data constitution manager (DSM) in HP PE/SolidDesigner terminology, must support a transaction conception Transactions must be freely definable to allow modeling paces that the user perceives as natural. The data conformation manager must record all changes to the mould in a transaction to be able to wheel them back in an undo operation.

The DSM must help to make secure model consistency even if errors be met with internally or in external applications. The transaction mechanism can be used to this end