Added a basic RichText class (and added tests and an example).

Fixed LineWrap when using initial X offset and the word does not fit in the current line but it fits in the next.
Added basic agent rules.

.agent/rules/build-project.md

@@ -0,0 +1,11 @@
+---
+trigger: always_on
+---
+
+To build the project in debug mode you must run from the root project directory:
+
+`make -C make/linux -j$(nproc)`
+
+If any file has been added you should also run (previous to the make command):
+
+`premake4 --disable-static-build --with-mold-linker --with-debug-symbols --address-sanitizer gmake`

.agent/rules/project-introduction.md

@@ -0,0 +1,13 @@
+---
+trigger: always_on
+---
+
+[eepp](https://github.com/SpartanJ/eepp/) is an open source cross-platform game and application development framework heavily focused on the development of rich graphical user interfaces.
+
+Inside this repository also lives [ecode](https://github.com/SpartanJ/ecode/). ecode is a lightweight multi-platform code editor designed for modern hardware with a focus on responsiveness and performance. It has been developed with the hardware-accelerated eepp GUI, which provides the core technology for the editor. The project comes as the first serious project using the eepp GUI, and it's currently being developed to improve the eepp GUI library as part of one of its main objectives.
+
+Very basic eepp documentation can be found at `docs/articles`. Many class headers have Doxygen documentation, rely on that. eepp headers are at `include/eepp/`.
+
+A good amount of examples on how to use the library can be found in `src/examples`.
+
+The `README.md` at the root directory explains in more detail about the project.

.agent/rules/unit-tests.md

@@ -0,0 +1,18 @@
+---
+trigger: always_on
+---
+
+Project provide a good range of unit-tests that they must pass to guarantee that changes made do not break functionality.
+To run the tests you must execute the binary:
+`bin/unit_tests/eepp-unit_tests-debug`
+
+This path is from the root directory, you can run it from anywhere, current working directory is managed by the binary.
+
+If you need to run an specific test you can use the filter parameter, it supports glob patterns, for example:
+
+`bin/unit_tests/eepp-unit_tests-debug --filter="FontRendering.*Offset*"`
+
+Will run all tests with "Offset" in its name.
+It's expected that for *any* requested new functionality you must add new tests and also tests with previously existing ones. Initially always test with the most relevant to the change that's has been made.
+
+Tests can be found at: `src/tests/unit_tests`. Being `src/tests/unit_tests/fontrendering.cpp` the most complete set of tests related to text rendering.