5cdfe62e2d
- factor out own class for the iadsnetwork within the conflicttheater - This class will handle all Skynet related things - no specific group_name handling necessary in future - make iadsbuilding own TGO class because SAM & EWRs are Vehicle Groups. IADS Elements dont have any groups attached. - added command center, connection node and power source as Ground objects which can be added by the campaign designer - adjust lua generator to support new iads units - parse the campaign yaml to get the iads network information - use the range as fallback if no yaml information was found - complete rewrite of the skynet lua script - allow destruction of iads network to be persistent over all rounds - modified the presetlocation handling: the wrapper PresetLocation for PointWithHeading now stores the original name from the campaign miz to have the ability to process campaign yaml configurations based on the ground unit - Implementation of the UI representation for the IADS Network - Give user the option to enable or disable advanced iads - Extended the layout system: Implement Sub task handling to support PD
DCS Liberation Client
This is a React app for the front-end of DCS Liberation. It is a work in progress that just barely implements the map. This is not useful for players yet.
For development, set the following environment variables when launching DCS Liberation (the Qt UI):
-
CORS_ALLOW_DEBUG_SERVER=trueThis will allow the front-end to make requests to the server, as long as the front-end is running on http://localhost:3000.
Then, run npm start to start the development server. Launch the Qt UI with
--new-map --dev to connect the webview to the development server, or navigate
to http://localhost:3000 in your browser.
Regenerating the API stubs
The backend uses FastAPI which exposes /openapi.json. This is consumed by
@rtk-query/codegen-openapi to automatically generate the API stubs in
src/api/liberationApi.ts.
If you make a change to the API surface the typescript API will need to be regenerated. To do this, first launch Liberation (to start the backend) and run
npm run regenerate-api
See https://redux-toolkit.js.org/rtk-query/usage/code-generation for more information.
Available Scripts
In the project directory, you can run:
npm start
Runs the app in the development mode.
Open http://localhost:3000 to view it in the browser.
The page will reload if you make edits.
You will also see any lint errors in the console.
npm test
Launches the test runner in the interactive watch mode.
See the section about running tests for more information.
npm run build
Builds the app for production to the build folder.
It correctly bundles React in production mode and optimizes the build for the best performance.
The build is minified and the filenames include the hashes.
Your app is ready to be deployed!
See the section about deployment for more information.
npm run eject
Note: this is a one-way operation. Once you eject, you can’t go back!
If you aren’t satisfied with the build tool and configuration choices, you can eject at any time. This command will remove the single build dependency from your project.
Instead, it will copy all the configuration files and the transitive dependencies (webpack, Babel, ESLint, etc) right into your project so you have full control over them. All of the commands except eject will still work, but they will point to the copied scripts so you can tweak them. At this point you’re on your own.
You don’t have to ever use eject. The curated feature set is suitable for small and middle deployments, and you shouldn’t feel obligated to use this feature. However we understand that this tool wouldn’t be useful if you couldn’t customize it when you are ready for it.
Learn More
You can learn more in the Create React App documentation.
To learn React, check out the React documentation.