examples/gkurve: initial commit for resizable_label #327
No reviewers
Labels
No labels
CI
all
basisu
blog
bug
build
contributor-friendly
core
correctness
deferred
dev
direct3d-headers
docs
driver-os-issue
duplicate
dxcompiler
editor
examples
experiment
feature-idea
feedback
flac
freetype
gamemode
gkurve
glfw
gpu
gpu-dawn
harfbuzz
help welcome
in-progress
infrastructure
invalid
libmach
linux-audio-headers
long-term
mach
mach.gfx
mach.math
mach.physics
mach.testing
model3d
needs-triage
object
opengl-headers
opus
os/linux
os/macos
os/wasm
os/windows
package-manager
priority
proposal
proposal-accepted
question
roadmap
slipped
stability
sysaudio
sysgpu
sysjs
validating-fix
vulkan-zig-generated
wayland-headers
website
wontfix
wrench
www
x11-headers
xcode-frameworks
zig-update
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
hexops/mach!327
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "main"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
About the tessellator code, the tessellator.zig and data_structures come from https://github.com/fubark/cosmic, the tracy code from the zig compiler
@ -0,0 +1 @@TODO: add license, the tesselator implementation comes from https://github.com/fubark/cosmic/blob/master/graphics/src/tessellator.zig@fubark We're using your Cosmic tesselator implementation, and plan to continue doing so in the future. For now @PiergiorgioZagaria has extracted it from Cosmic so we can use it here, I'm curious how you'd feel about having this live in a separate repository/library proper?
(if that's just more work for you, no worries, just figured I'd ask!)
This is super cool @PiergiorgioZagaria - I'm planning to review later in the week (probably in 2-3 days)
Is it ok if I make small commits to the PR for removing some bugs I found?
Oh absolutely, push whatever improvements you like. I'll check them all out in a few days time.
LGTM, there's definitely code cleanup I'd like to do here but it's fine - the solution looks great overall and I'm excited to have this.
Next up for me is (1) sorting out the ECS and (2) moving this logic into an ECS-backed solution