D-Cubed Component Integration

The D-Cubed components are licensed by software development organizations for integration into their own end-user applications. Though the components provide advanced functionality, they are very simple from an application integration perspective. All of the components have similar interfaces and integration architectures.

The components are integrated into an application's existing user interface and file format environment. Written in highly standardized C++, comprising relatively small object libraries (static or dynamic), they can be used in just about any computer environment.

All components have been written specifically to be integrated into any geometry-based application. Target applications can be new or mature products.

Very few assumptions are made about the data structures used in the host system. The definitions of the geometry are held in the application and accessed by the components through a simple and compact interface. Use of the components does not require the application to redefine its geometric data structures.

This broad compatibility is illustrated by the wide range of released end-user applications listed on the D-Cubed Customers page.

Supported Platforms

All components are available for major platforms running Windows, Linux and OSX. Both 32 and 64-bit architectures are supported.

The components are coded in C++ and supplied with integral C++ and C interfaces. They are designed to be used with any application written in C++, C, or any other high level language which supports a C calling structure.

A managed interface for 2D DCM functions is available for .NET projects.

Integration Times

Great care has been taken in the design of the application programmer interfaces to ensure that integration into an end-user application is an efficient process. The following times are based on an initial integration of the component's data-structures with the application's data-structures and an implementation of the most important functionality – by one developer.

  • 2D DCM: 2–3 months
  • 3D DCM: 2–3 months
  • PGM: 2–3 months
  • AEM: 2–3 months
  • CDM: 1–2 months
  • HLM: 1–2 months

AEM applications must also integrate the 3D DCM.

The HLM, CDM and AEM use the same 3D data-structure. Having integrated any one of these components within an application, the time taken to integrate the other components is reduced by 3–4 weeks.

We have developed an interface for using the HLM, CDM and AEM with the Parasolid solid modelling component. This software, known as the Wrapper, is available free of charge to commercial Parasolid licensees. It reduces the time taken to integrate the HLM, CDM and AEM's 3D data-structures from 3–5 weeks to just 3 or 4 days.

We have also developed an interface between the 2D DCM and Teigha™ for .dwg files, enabling users of the Open Design Alliance (ODA) Teigha development platform to introduce the 2D DCM into their products more rapidly. For further information, please visit this page.

Close share layer

Share this page

Share this page through any of the following channels.

Bookmarking Sites



Blogs & Microblogs