-
-
Notifications
You must be signed in to change notification settings - Fork 7
Config files and folder structure
Stanislav Vasilev edited this page Nov 15, 2022
·
10 revisions
Here we will detail the different folder and config file locations and their purpose
The core framework directory, a.k.a. the one you see first on the github web interface contains the following folders and files
-
.github- For github and git specific data, github actions workflows, issue and pr templates -
Config- The default config folder containing the default config files- Core - Contains core configs
- Translations - Translation configs for the locale module
-
Content- The default content folder, contains example images and icons -
Framework- Contains the entire source code and dependencies for the framework, for more info for framework developers scroll to the bottom of the page -
Projects- Contains your projects -
UVKBuildTool- Contains theUVKBuildTooland its source code -
create-project.sh- Used to create a project -
export.sh- Used to export your application for production distribution -
install.sh- The framework installation script -
update.sh- An automated script to update your project and framework to a new version
Additionally every project contains those additional files and folders:
-
Exported- For storing your final production builds -
Generated- For generated files and sources -
Source- For your application's source code -
CMakeLists.txt- The CMake project file -
uvproj.yaml- Your project's config
The config files are located under the Config folder, which itself contains 2 directories, Core and Translation.
The Core directory stores the following files:
DefaultLayout.iniFallbackLayout.ini-
Keybindings.yaml- For custom keybindings, detailed in later wiki entries -
Modules.yaml- The modules
This project is supported by all the people who joined our discord server and became beta testers. If you want to join the discord you can click here.
- Home
- Beginner content
- Install guide
- Creating and using the UI components
- The Instance
- The Init Info struct
- Building better titlebar menus
- Textures
- Logging
- Unicode support
- Additional features
- Client-side bar
- Custom type definitions
- Memory management
- C API development
- Config files and Folders
- Interfaces
- Internal Event safety
- Customising the build system
- Modules system
- Collaborating with others
- Advanced content
- Loading dynamic libraries at runtime
- Understanding the library layout
- Compilation mode modifiers
- Supporting plugins
- Production export and deployment
- OS integration tips
- Targeting WASM
- Using a custom rendering engine:
- Using a custom windowing backend:
- Developer and contributor resources
- Misc