| commit | 215de972f9e7a91a8f518158e14265a6aa18e24b | [log] [tgz] |
|---|---|---|
| author | susan101566 <hello@rive.app> | Mon Aug 19 21:03:29 2024 +0000 |
| committer | susan101566 <hello@rive.app> | Mon Aug 19 21:03:29 2024 +0000 |
| tree | 48d50a29067db4dd3f03c6a92e8c469c1a665c73 | |
| parent | 43d7f27b10c533ffba5b010a2eb6f0c9781c4014 [diff] |
editor: setting up the update callbacks for n-slicing I did some refactoring on image and mesh, where I created a 'deformer' that manages which mesh to show. I also abstracted out the parts in Mesh that deals with rendering specifically, called MeshDrawable. There's also a simple UI gated behind a feature flag that shows the N Slicing panel, where you can create, delete, update axis data (hold alt to show the remove axis button). The behavior is that when you create a mesh, the nslicer is deleted and vice versa. I mostly tested this manually. I added a print in the temp mesh's update, and made sure that when any axis gets deleted or updated, the print would trigger. I could add an auto test?! I need to look into that, but wanted to send this out to get some feedback on the approach. Next up: I'll add the algorithm for actually updating the render buffers in the temp mesh. doc: https://www.notion.so/rive-app/9-Slice-Tech-Proposal-Image-only-50b25ea8e79c4efabb681110e288f064#15f3a49ce3534baeafc31c37fb30cc0b Diffs= f99c93181 editor: setting up the update callbacks for n-slicing (#7869) Co-authored-by: Susan Wang <susan@rive.app>
Rive C++ is a runtime library for Rive, a real-time interactive design and animation tool.
The C++ runtime for Rive provides these runtime features:
We use premake5. The Rive dev team primarily works on MacOS. There is some work done by the community to also support Windows and Linux. PRs welcomed for specific platforms you wish to support! We encourage you to use premake as it's highly extensible and configurable for a variety of platforms.
In the rive-cpp directory, run build.sh to debug build and build.sh release for a release build.
If you've put the premake5 executable in the rive-cpp/build folder, you can run it with PATH=.:$PATH ./build.sh
Rive makes use of clang vector builtins, which are, as of 2022, still a work in progress. Please use clang and ensure you have the latest version.
cd skia/dependencies ./make_skia.sh // this will invoke get_skia.sh
To build viewer (plus you'll needed CMake installed)
./make_viewer_dependencies.sh
Uses the Catch2 testing framework.
cd dev ./test.sh
In the dev directory, run test.sh to compile and execute the tests.
(if you've installed premake5 in rive-cpp/build, you can run it with PATH=../../build:$PATH ./test.sh)
The tests live in rive/test. To add new tests, create a new xxx_test.cpp file here. The test harness will automatically pick up the new file.
There's a VSCode command provided to run tests from the Tasks: Run Task command palette.
rive-cpp uses clang-format, you can install it with brew on MacOS: brew install clang-format.
Note that if you‘re on MacOS you’ll want to install valgrind, which is somewhat complicated these days. This is the easiest solution (please PR a better one when it becomes available).
brew tap LouisBrunner/valgrind brew install --HEAD LouisBrunner/valgrind/valgrind
You can now run the all the tests through valgrind by running test.sh memory.
If you want to examine the generated assembly code per cpp file, install Disassembly Explorer in VSCode.
A disassemble task is provided to compile and preview the generated assembly. You can reach it via the Tasks: Run Task command palette or you can bind it to a shortcut by editing your VSCode keybindings.json:
[
{
"key": "cmd+d",
"command": "workbench.action.tasks.runTask",
"args": "disassemble"
}
]