Migrate to TGUI

.clang-format

@@ -0,0 +1,3 @@
+UseTab: Always
+IndentWidth: 4
+TabWidth: 4

.github/workflows/codeql.yml

@@ -0,0 +1,108 @@
+# For most projects, this workflow file will not need changing; you simply need
+# to commit it to your repository.
+#
+# You may wish to alter this file to override the set of languages analyzed,
+# or to provide custom queries or build logic.
+#
+# ******** NOTE ********
+# We have attempted to detect the languages in your repository. Please check
+# the `language` matrix defined below to confirm you have the correct set of
+# supported CodeQL languages.
+#
+name: "CodeQL Advanced"
+
+on:
+  push:
+    branches: ["main", "tgui-fresh"]
+  pull_request:
+    branches: ["main", "tgui-fresh"]
+  schedule:
+    - cron: "19 2 * * 1"
+
+jobs:
+  analyze:
+    name: Analyze (${{ matrix.language }})
+    # Runner size impacts CodeQL analysis time. To learn more, please see:
+    #   - https://gh.io/recommended-hardware-resources-for-running-codeql
+    #   - https://gh.io/supported-runners-and-hardware-resources
+    #   - https://gh.io/using-larger-runners (GitHub.com only)
+    # Consider using larger runners or machines with greater resources for possible analysis time improvements.
+    runs-on: ${{ (matrix.language == 'swift' && 'macos-latest') || 'ubuntu-latest' }}
+    permissions:
+      # required for all workflows
+      security-events: write
+
+      # required to fetch internal or private CodeQL packs
+      packages: read
+
+      # only required for workflows in private repositories
+      actions: read
+      contents: read
+
+    strategy:
+      fail-fast: false
+      matrix:
+        include:
+          - language: c-cpp
+            build-mode: manual
+        # CodeQL supports the following values keywords for 'language': 'actions', 'c-cpp', 'csharp', 'go', 'java-kotlin', 'javascript-typescript', 'python', 'ruby', 'rust', 'swift'
+        # Use `c-cpp` to analyze code written in C, C++ or both
+        # Use 'java-kotlin' to analyze code written in Java, Kotlin or both
+        # Use 'javascript-typescript' to analyze code written in JavaScript, TypeScript or both
+        # To learn more about changing the languages that are analyzed or customizing the build mode for your analysis,
+        # see https://docs.github.com/en/code-security/code-scanning/creating-an-advanced-setup-for-code-scanning/customizing-your-advanced-setup-for-code-scanning.
+        # If you are analyzing a compiled language, you can modify the 'build-mode' for that language to customize how
+        # your codebase is analyzed, see https://docs.github.com/en/code-security/code-scanning/creating-an-advanced-setup-for-code-scanning/codeql-code-scanning-for-compiled-languages
+    steps:
+      - name: Checkout repository
+        uses: actions/checkout@v4
+        with:
+          fetch-depth: 0
+          submodules: recursive
+
+      # Add any setup steps before running the `github/codeql-action/init` action.
+      # This includes steps like installing compilers or runtimes (`actions/setup-node`
+      # or others). This is typically only required for manual builds.
+      # - name: Setup runtime (example)
+      #   uses: actions/setup-example@v1
+
+      # Initializes the CodeQL tools for scanning.
+      - name: Initialize CodeQL
+        uses: github/codeql-action/init@v4
+        with:
+          languages: ${{ matrix.language }}
+          build-mode: ${{ matrix.build-mode }}
+          # If you wish to specify custom queries, you can do so here or in a config file.
+          # By default, queries listed here will override any specified in a config file.
+          # Prefix the list here with "+" to use these queries and those in the config file.
+
+          # For more details on CodeQL's query packs, refer to: https://docs.github.com/en/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/configuring-code-scanning#using-queries-in-ql-packs
+          # queries: security-extended,security-and-quality
+
+      # If the analyze step fails for one of the languages you are analyzing with
+      # "We were unable to automatically build your code", modify the matrix above
+      # to set the build mode to "manual" for that language. Then modify this step
+      # to build your code.
+      # ℹ️ Command-line programs to run using the OS shell.
+      # 📚 See https://docs.github.com/en/actions/using-workflows/workflow-syntax-for-github-actions#jobsjob_idstepsrun
+      - name: Run manual build steps
+        if: matrix.build-mode == 'manual'
+        shell: bash
+        run: |
+          sudo add-apt-repository ppa:xmake-io/xmake
+          sudo apt-get update
+          sudo apt-get install -y \
+            libx11-dev \
+            libxrandr-dev \
+            libxinerama-dev \
+            libxcursor-dev \
+            libxi-dev \
+            libgl1-mesa-dev \
+            mesa-common-dev \
+            xmake
+          xmake build --all -y
+
+      - name: Perform CodeQL Analysis
+        uses: github/codeql-action/analyze@v4
+        with:
+          category: "/language:${{matrix.language}}"

.gitignore

@@ -40,7 +40,6 @@ game-src/*/lib/
 /game
 build/
 bin/
-libs/
 execs/**
 *.bin
 .cache/
@@ -58,3 +57,4 @@ imgui.ini
 clangd/
 game-src/
 compile_commands.json
+xmake-*.exe

.gitmodules

@@ -1,9 +0,0 @@
-[submodule "libs/luajit"]
-	path = libs/luajit
-	url = https://luajit.org/git/luajit.git
-[submodule "libs/raylib"]
-	path = libs/raylib
-	url = https://github.com/raysan5/raylib.git
-[submodule "rlImGui"]
-	path = rlImGui
-	url = https://github.com/raylib-extras/rlImGui

.zed/debug.json

@@ -0,0 +1,14 @@
+[
+  {
+    "label": "Debug RPG++ Editor (Linux)",
+    "build": {
+      "command": "xmake",
+      "args": ["build", "--all"],
+      "cwd": "${ZED_WORKTREE_ROOT}",
+    },
+    "program": "${ZED_WORKTREE_ROOT}/build/linux/x86_64/debug/editor",
+    "request": "launch",
+    "adapter": "CodeLLDB",
+    "cwd": "${ZED_WORKTREE_ROOT}/build/linux/x86_64/debug",
+  },
+]

.zed/settings.json

@@ -0,0 +1,11 @@
+{
+	"show_whitespaces": "selection",
+	"indent_guides": {
+		"active_line_width": 1,
+		"enabled": true,
+	},
+	"tab_size": 4,
+	"hard_tabs": true,
+	"show_wrap_guides": true,
+	"project_name": "RPG++",
+}

.zed/tasks.json

@@ -0,0 +1,17 @@
+// Project tasks configuration. See https://zed.dev/docs/tasks for documentation.
+//
+// Example:
+[
+	{
+		"label": "Run Editor",
+		"command": "xmake run editor",
+	},
+	{
+		"label": "Run translation checker",
+		"command": "xmake check_translation",
+	},
+	{
+		"label": "Build All",
+		"command": "xmake build --all",
+	},
+]

README.md

@@ -1,35 +1,87 @@
-# RPG++
-
 ![logo](docs/logo.png)
+---
 
 RPG++ is an experimental 2D RPG game engine written in C++. It is currently in early development, but contributions are welcome!
 
-## Building
+***This is a fresh restart, there are currently no RPG++ lua bindings, the engine hasn't been implemented in this branch yet.***
+
+<img src="docs/readme_img1.png" alt="screenshot of engine" width="640">
+
+Requirements
+---
+
+To build RPG++, you'll need to install the following tools/packages:
+- **For all platforms**:
+  - [xmake](https://xmake.io/) (follow the instructions on the website to install XMake on your system)
+  - [git](https://git-scm.com/)
+- Specifically for _Linux_:
+  - gcc, g++, make, and ninja (on Debian-based distros, you can install this via `sudo apt install build-essential`)
+  - libx11-dev, libxrandr-dev, libxinerama-dev, libxcursor-dev, libxi-dev, libgl1-mesa-dev, and mesa-common-dev (Debian-based distros can install this via `sudo apt install libx11-dev libxrandr-dev libxinerama-dev libxcursor-dev libxi-dev libgl1-mesa-dev mesa-common-dev`)
+- Specifically for _Windows_:
+  - Visual Studio 2019 or later with Desktop development with C++ (community edition will suffice)
+
+Building
+---
+
+Clone the project using git with
 
-This project uses [XMake](https://xmake.io/) so you may need to download it for your system.
+```bash
+git clone https://github.com/CDevv/rpgpp
+```
 
-First, you have to initialize the specified submodules. use `git submodule init` to initialize the paths. Then use, `git submodule update` to clone the submodules to your system.
+To build all targets, run
 
-After cloning the submodules to the paths, check your `/rlImGui` directory.
+```bash
+xmake build --all
+```
 
-Additional dependency is LuaJIT. After getting the luajit xmake package, you need to copy the luajit executable into the `execs/` directory.
+If xmake failed to build, try force reinstalling the packages with
+```bash
+xmake clean --all # remove build artifacts
+xmake require --clean # remove installed package cache for project
+xmake require --force # force install of package
+```
 
-Here are the xmake directories on different platforms:
+Running
+---
 
-Linux: `/home/name/.xmake/packages/l/luajitv2.1.0-beta3/aaeb029456e54f29b904a191c96508d2/bin/`
+To start the editor, run
 
-Windows: `AppData\Local\.xmake\packages\l\luajit\v2.1.0-beta3\7780bd1b1c8146cd984bf13d60e49407\bin`
+```bash
+xmake run editor
+```
 
-Mac: `/Users/nikodev/.xmake/packages/l/luajit/v2.1.0-beta3/bin`
+Translation
+---
 
-(Do not copy it blindly, the commit number might be different)
+Translation are located in `resources/translations`, containing JSON files with their names being the language code.
 
-Finally, use `xmake build --all` to build all targets.
+Each JSON files is structured as either flattened JSON:
+```json
+{
+	"language": "<name_of_language>",
+	"translation.key": "<translation_value>"
+}
+```
+or nested JSON:
+```json
+{
+	"language": "<name_of_language>",
+	"translation": {
+		"key": "<translation_value>"
+	}
+}
+```
+Both types are supported, though we recommend using nested JSON for better organization.
 
-## Running
+If you wish to improve an existing language, you can do so by modifying the language file of the language you know. Or if you want to add a new language, create a new JSON file within the folder, specify the language via the `language` key, and then translate the root translation file (en_us.json). The engine will automatically pick it up.
 
-Use `xmake run editor` to run the editor.
+To check for translation progress, you can do so via
+```
+xmake check_translation
+```
 
-## License
+License
+---
 
-This software uses the MIT License.
+This software is licensed under the MIT License.