Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Create low barrier to entry UIs for Geometry Central #205

Open
keenancrane opened this issue Jan 11, 2025 · 0 comments
Open

Create low barrier to entry UIs for Geometry Central #205

keenancrane opened this issue Jan 11, 2025 · 0 comments

Comments

@keenancrane
Copy link
Collaborator

There are a lot of great algorithms in GC, but it's sometimes annoying to have to build a whole C++ project, or hack on some "spaghetti" project, when you just want to do a few operations to a mesh, or a batch of meshes. (As you might want to do during, say, a paper deadline! :-P)

Doesn't seem like it would be too hard to hack together various ways of chaining together outputs and inputs:

  • a node-based interface for hooking up GC algorithms (e.g., via React Flow and Electron)
  • a collection of command line utilities for invoking GC algorithms, that support UNIX "piping" between utilities
  • and/or a command line REPL for processing meshes via GC (probably best implemented by just exposing more of Geometry Central through potpourri3d)

None of these utilities belong in the geometry-central repo itself, since they're effectively just apps built on top of GC. However, the question is: is there any software engineering we can do within GC to grease the wheels? I.e., to make it easier to chain inputs to outputs? Or are we basically already there?

[This issue is mostly just a note to myself.]

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant