Credit the Hexa.NET libraries in the package READMEs - #353
Merged
Conversation
Every library in the suite renders through Hexa.NET's Dear ImGui bindings, but most package READMEs did not say so. Each README for a package that references a Hexa.NET package now has an Acknowledgments section linking the upstream repositories it actually uses: - New sections in ImGui.App.Testing, ImGui.Markdown, ImGui.Popups, ImGui.Probes and ImGui.SyntaxHighlighting. - ImGui.App's existing section gains the extension bindings it auto-detects (ImGuizmo, ImNodes, ImPlot), HexaGen behind them, and ImageSharp. - ImGui.Widgets' section listed only what the package was inspired by; it now leads with what it is built on, including Hexa.NET.ImGui.Widgets and Hexa.NET.Math. ocornut/imgui moves up out of the inspiration list, where it was duplicated. - ImGui.Styler gains Dear ImGui itself alongside the bindings. - The root README gains a suite-wide section covering the whole Hexa.NET stack, plus Silk.NET, ImageSharp and Markdig. Links come from each package's own repository metadata, except Hexa.NET.ImGui.Widgets, which keeps the URL the Widgets README already used. ImGui.Color and ImGuiNodeEditor also reference Hexa.NET packages but have no README of their own, so nothing was added for them. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_015qVmjxGLzVE2mZctNNjSJC
This was referenced Sep 8, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Every library in the suite renders through Hexa.NET's Dear ImGui bindings, but most package READMEs never said so. Each README belonging to a package that references a Hexa.NET package now carries an Acknowledgments section linking the upstream repositories it actually uses.
What changed
README.md(root)ImGui.AppImGui.Widgetsocornut/imguimoves up out of the inspiration list, where it was duplicatedImGui.StylerImGui.App.Testing,ImGui.Markdown,ImGui.Popups,ImGui.Probes,ImGui.SyntaxHighlightingEach list is scoped to the packages that README's project really has a
PackageReferenceto, so no README claims a dependency it does not have.Link provenance
Links come from each package's own
.nuspecrepository/projectUrlmetadata in the local NuGet cache, which is why the ImGuizmo, ImNodes, ImPlot and Widgets packages are described as part of theHexa.NET.ImGuiproject — that is the URL those packages publish. The one exception isHexa.NET.ImGui.Widgets, which keeps the dedicated repository URL the Widgets README was already using in its own prose.HexaGen.Runtimepoints atJunaMeinhold/HexaGen, per its package metadata.Note that github.com is not reachable from this container (the egress proxy returns 403), so the URLs were taken from package metadata and from links already present in the repo rather than fetched and confirmed live.
Not covered
ImGui.ColorandImGuiNodeEditoralso reference Hexa.NET packages but have no README of their own, so there was nothing to add a section to. Say the word if you want READMEs written for them.Docs only — no code, no build or test impact.
🤖 Generated with Claude Code
https://claude.ai/code/session_015qVmjxGLzVE2mZctNNjSJC
Generated by Claude Code