Gwen
8bca6ac62a
I feel a little conflicted about how I should be doing this. I think it could save a lot of code to do away with the `FrameData` which amalgamates the buffers into a single buffer, or at least remove the frame data as a separate concept, and let all of that functionality get folded into the primitive buffer. My idea was, as I was implementing things in bevy I realized having double-buffered primitive buffers could be _super_ useful; however, it's kind of silly to have 2 copies of everything just to copy it again to another buffer (the Vec<u8> in the RawBuffer) only to copy that buffer _again_ onto the GPU. Why not just have the RawBuffer act as the second buffer, so there's a sort of like "double buffering" still? Honestly I feel like I might be overthinking things a little bit here. I expect to revisit this at some point in the future, for now I am sort of happy, definitely some code improvements here! But maybe there just doesn't need to be so much code or complexity. |
||
---|---|---|
.hooks | ||
dev | ||
doc | ||
src | ||
.gitignore | ||
.rustfmt.toml | ||
Cargo.toml | ||
LICENSE | ||
README.md |
README.md
An immediate mode graphical user interface library.
Immediate mode started as a port of Dear ImGui, but was influenced by many other frameworks and applications along the way. Most notably, Our Machinery's IMGUI implementation and the Nom parser combinator library.