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

Using mittsu without graphics #115

Open
Floppy opened this issue Apr 15, 2023 · 2 comments · May be fixed by #125
Open

Using mittsu without graphics #115

Floppy opened this issue Apr 15, 2023 · 2 comments · May be fixed by #125
Milestone

Comments

@Floppy
Copy link
Contributor

Floppy commented Apr 15, 2023

For my use case, I want to manipulate some 3d object files in Ruby, but I don't need to render them; instead I'm using THREE.js in the browser for that. So, in the interests of minimising dependencies would it be possible to make the library work without pulling in OpenGL unless a rendering context is created? I tried to use it without glfw3 installed just to see if it would cope, but it wouldn't start up.

This could perhaps either be done by adapting the code in the library as-is, or for a more extreme solution, splitting the non-graphical stuff out into a separate gem, something like mittsu-core. Do you think either are possible? I'm happy to try this, but it would be good to know what approach you'd prefer I investigate before I do so!

@danini-the-panini
Copy link
Owner

I've definitely thought about splitting the code out. It was adapted from THREE.js directly, which supports swapping out renderers. The idea would be to have mittsu-core and separate renderers, e.g. mittsu-renderer-[name] e.g. mittsu-renderer-opengl and mittsu-renderer-direct3d etc.

@Floppy
Copy link
Contributor Author

Floppy commented Apr 17, 2023

I was going to suggest exactly that renderer split too, but thought I'd keep it simple to start with :)

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

Successfully merging a pull request may close this issue.

2 participants