Frontend Improvements

[geringsj]

Feature requests, bugs and UX discussion for megamol.exe

• Failure to start some services (e.g. Lua) keeps megamol running
• On-the-fly adding/removing/restarting services (dont - services are static after startup)
• Handle Lua Config file correctly (CLI config parser feeds LuaAPI at startup)
• ZMQ context as resource
• Port cinematic, screenshooter
• On-the-fly requesting resources (new FBO, new GL context, new GLFW window)
• FBO-centered rendering => View redesign
• Multi-threaded rendering
• Rendering into multiple windows (e.g. one project per window)
• Modules should be able to check/require OpenGL capabilities OpenGL version check for modules (and calls) #496
• Streamline API policies (OpenGL-free core) #381
• New Camera Refactoring #323
• Remote / In-Situ design #252
• New Idea for Windows, APIs and CallRenders #245
• ScreenShooter improvements #442 and Allow window size larger than screen #692
• Sending fake input (key) events: how to handle press/release? They usually have a few frame between them
• Record+broadcast MegaMol events: Keyboard/Mouse, Camera, Lua, Graph, ...
• Add/Remove services on startup via CLI or Lua (Lua project, Lua remote)
• Project File Drag & Drop ignores configurator layout in GUI (drag&drop feeds into lua, gui knows nothing about it?)
• Screenshot Source: Frontbuffer is empty on Intel and AMD RDNA, need to switch to Backbuffer on demand (dont glClear after buffer swap in GL service)
• Project Concept, MegaMol UX: all projects (.lua files) end up in same megamol graph, or separate graph per project file?
• Services can (de)register Lua callbacks? E.g. Graph or GUI may provide their own mm Lua calls
• Eliminate CoreInstance: Module/Call description managers
• Better resource usability for Modules, e.g. Resource::ReqName, map lookup and template magic.
• Restructure logger for better usability and CLI parsing