Restructure 3D Part

[TMink]

Over the last development period the 3D Part was adjusted many times, often more sporadicly, because of the direct demand. This lead to an unhealthy layering of code, which was often not optimized performance wise . In order to provide a stabel Enviroment wich enables the user to use different data types of 3D-Models, functions to manipulate Objects or simply view multiple 3D-Objects at once, the whole 3D-Part will be restructured.

This means:

• outsourcing and simplyfing to prevent redundancy
• make functions like loaders more universaly usable, like outside of the 3D-Part
• create an overall more stable enviroment wich isn't subsceptible to bugs
• support future development processes
• make it easier to create a proper class hierarchy diagram for the code documentation
• zoom on objects

[TMink]

Updated: Zoom on Objects: Now the zoom is based on the cursor position, rather than the center of the place-object as it was before

[TMink]

Update: Outsourcing and simplyfing to prevent redundandcy: Most of the functions, like object loaders and garbage collection, has been outsourced. These functions were grouped in classes. In addition a parameter list was implemented to centralize them.

3DView:

• HTML part
• vue life cycle
• almost no import of libraries
• imports every outsourced class an uses instances of them
• central part of the 3D-part
• distributes data from parameter list

CameraSetting (file):

• CameraSettings (class)
  • Includes functions to modify the camera state in the scene

ControlSetting (file):

• ControlSettings (class)
  • Includes functions to modify the control settings and attach/detach them to/from certain objects

GarbageCollection (file):

• GarbageCollection (class)
  • The process that will happen, wenn ever the 3DView is closed and the scenes and assets are not used anymore. This should help with cache problems and keeps the canvas space clean of data remains.

Initialisations (file):

• Initialisations (class)
  • A collection of initialisation functions, which will be called in the mounted function in 3DView.js. This includes the creation of the main/sub scene and various tools.

ObjectFilter (file):

• ObjectFilter (class)
  • A filter algorithmen to search for an object to modify.

ObjectLoaders (file):

• ObjectLoaders
  • A Collection of loader functions which are used to determines, distributes and modify the 3D objects which will be loaded in main or sub scene.

Tools (file):

• A collection of all created tools. The initialisation of each tool takes place in Initialisations.js. These classes contain the logic behind each tool and can be imported inside 3DView.js for further usage.
  • LineTool (class)
  • AnnotationTool (class)
  • ModelInteraktion (class)
  • SegmentationTool (class)

UpdateIndexedDB (file):

• UpdateIndexedDB (class)
  • A Collection of functions to update saved data in IndexedDB.

UpdateLoaclVariables (file):

• UpdateLocalVariables (class)
  • Functions to update the local parameter list to reduce the amount of IndexedDb accesses.

Utilities (file):

• Utilities (class)
  • A Collections of various functions that are used all over the 3DPart in many different situations for minor changes or generell maintenence.

[TMink]

Update: Make functions like loaders more universaly usable. like outside of the 3D-Part The new class Objectloaders inside Objectloaders.js, includes the load function, which will do exactly that. Through the utialization of the different loader types provided by three.js, it is possible to process different postfixes. The differences between the usage of these loaders are often minor, but still so impactfull, that they differ. Beside that, the loader function can now be implemented in every part of the code and used the same way, like places and positions, where models can be loaded in the system.

This image shows the minor impactful difference between both loaders, as an example.

[TMink]

Update: Create an overall more stable enviroment wich isn't subsceptible to bugs All knowen bugs are fixed and the new, more structured, layout of the code can be tested and maintained more easily.

[TMink]

Update: support future development processes By choosing simple, easy-to-understand names for variables and functions, in addition to a detailed dokumentation, new features can be implemented musch faster.

[TMink]

Update: Make it easier to create a proper class hierarchy diagram for the code documentation

[TMink]

Update: Zoom on objects The new zoom function lets the user zoom on the cursor position. This should support the interaction.

[TMink]

Every task was processed and documented.