MegaMol Project Concept

[geringsj]

Uses current lua script file path to determine a project directory, allowing FilePath Parameters to load files relative to that directory. The project directory is injected into file parameters of newly created graph modules.

TODO

• Should File Path Parameters automatically check for files beeing inside the project dir, and use relative paths for those?

• What happens when saving and loading the project again?
  • MegaMolGraph Serialization preserves relative file path (uses param->ValueString())
  • GUI Serialization preserves relative file path
• What happens when stacking project files? FilePathParams remember their respective project file
• Optional Lua Callback Arguments (optional project name argument)
• Do we really want to clear() the graph?

• vislib::sys::File and vislib::sys::File::Exists() must die Only FilePathParam knows about project, re-routing all file loading through project dir too intrusive
• Screenshots and other outputs go to project dir automatically? User configures screenshot output
• Unify UX: Configurator project open, project add, file load, file drop
• Adjust example projects for new file path structure

Test Instructions

The implementation works for all code paths going though the Project Loader Service, e.g. Drag & Drop of files into the window and "Load Project" in the GUI.
For example, modify the infovis.lua example to access the example data set relative to the examples directory.

-- snip --

-- old: mmSetParamValue("::CSVDataSource_1::filename",[=[../examples/sampledata/iris.csv]=])
mmSetParamValue("::CSVDataSource_1::filename",[=[sampledata/iris.csv]=])

[geringsj]

This might also be just a "prefix_path"

[github-actions]

Style check found formatting issues! Comment /format, to automatically commit the suggested changes.

[braunms]

/format