Classes Introduction

This is only an introduction to libf3d classes. For the complete documentation, please consult the libf3d doxygen documentation..

Engine class

The engine class is the main class that needs to be instantiated. All other classes instance are provided by the engine using getters, getScene, getWindow, getInteractor, getOptions.

The engine constructor lets you choose the type of window in its constructor, NONE, NATIVE, NATIVE_OFFSCREEN, EXTERNAL. Default is NATIVE. See Window class documentation for more info. Please note that the engine will not provide a interactor with NONE and EXTERNAL.

A static function loadPlugin can also be called to load reader plugins. It must be called before loading any file. An internal plugin containing VTK native readers can be loaded by calling f3d::engine::loadPlugin("native");. Other plugins maintained by F3D team are available if their build is enabled: alembic, assimp, draco, exodus, occt and usd. If CMake option F3D_PLUGINS_STATIC_BUILD is enabled, the plugins listed above are also static just like native plugin. All static plugins can be loaded using f3d::engine::autoloadPlugins().

Scene class

The scene class is responsible to add file from the disk into the scene. It supports reading multiple files at the same time and even mesh from memory. It is possible to clear the scene and to check if the scene supports a file.

Window class

The window class is responsible for rendering the meshes. It supports multiple modes.

  • NONE: A window that will not render anything, very practical when only trying to recover meta-information about the data.

  • NATIVE: Default mode where a window is shown onscreen using native graphical capabilities.

  • NATIVE_OFFSCREEN: Use native graphical capabilities for rendering, but unto an offscreen window, which will not appear on screen, practical when generating screenshots.

  • EXTERNAL: A window where the OpenGL context is not created but assumed to have been created externally. To be used with other frameworks like Qt or GLFW.

Window lets you render, renderToImage and control other parameters of the window, like icon or windowName.

Interactor class

When provided by the engine, the interactor class lets you choose how to interact with the data.

It contains the animation API to start and stop animation.

Interactor also lets you set your interaction callbacks in order to modify how the interaction with the data is done.

Of course, you can use start and stop to control the interactor behavior.

Camera class

Provided by the window, this class lets you control the camera. You can either specify the camera position, target, and up direction directly, or specify movements relative to the current camera state.

Image class

A generic image class that can either be created from a window, from an image filepath or even from a data buffer. It supports comparison making it very practical in testing context.

Log class

A class to control logging in the libf3d. Simple using the different dedicated methods (print, debug, info, warn, error) and setVerboseLevel, you can easily control what to display. Please note that, on windows, a dedicated output window may be created.

Options class

This class lets you control the behavior of the libf3d. An option is basically a value that can be a optional or not. There is different API to access it, see the exhaustive doc.

Reader class

This class is used internally by the plugin SDK and is not intended to be used directly.

Plugin class

This class is used internally by the plugin SDK and is not intended to be used directly.