Session 022: Migrate Lts/Tools (72 submodules) to Qt6

- Copied complete Lts/Tools directory from qt5-before to qt6-after
- Updated 32 CMakeLists.txt files (Qt5:: → Qt6::)
- Tools subdirectory already included in parent Lts/CMakeLists.txt
- All 72 tool submodules now present in qt6-migrated-legatus
- Includes: Adler, ArAssets, ConfigX, DBAdministration, DBUpdate,
  DdsView, InfrastructureManagement, and 67 more tools
- C++17 standard (RTI 7.7.0 compatibility maintained)
- Tests deferred until final validation phase

Migration progress:
✅ Lts/Application (68 files)
✅ Lts/DDS (verified Qt6-ready)
✅ Lts/Plugins (60 submodules, verified)
✅ Lts/Projects (5 submodules, verified)
✅ Lts/Proxies (13 submodules, verified)
✅ Lts/Services (47 submodules, verified)
✅ Lts/Tools (72 submodules, copied + CMake updated)
✅ Lts/Viewer (LtsFileDialog, LtsReportDisplay, SituationMap)
🟡 TetraIF (partial)
🟡 Z (partial: nglwidgets, QtSingleApplication, qsql_informix, WMS_Interface)
This commit is contained in:
torsten committed 2026-08-25 14:07:20 +02:00
1 parent 01dce5fe52
commit d5c13033e2
1792 files changed
+982018

No files matched your search

@@ -0,0 +1,18 @@
[Run TimelineParticipant]
To start the Timeline you just need to run the "TimelineParticipant.sh" file. (Run "./TimelineParticipant.sh" in this folder)
If you get an error try to run the "installNode.sh".(Run "./installNode.sh" in this folder)
[Stop TimelineParticipant]
The "TimelineParticipant.sh" starts a process in the background.
If you need to stop that process you can run "./KillTimelineParticipant.sh" or use pkill node from the console.
[Manually Run TimelineParticipant]
1. Nodejs has to be installed. If it is not, install it with "nvm install --lts".
2. If you want to use Nodemon run "npm install nodemon".
--If you start the Timeline with "node app.js" and you change any of the files you will have to stop the process with Crtl+C and then start it again.
--Nodemon will automaticly restart the nodeserver for you if there have been changes to the program files. (Great for Development and Debuging).
3. Now you just start the node server with "nodemon app.js" or "node app.js".
4. If the process is running successfully you can open any Web Browser and go on "localhost:3000".