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

Rename Renderer -> Device #115

Closed
azul3d-bot opened this issue Mar 6, 2016 · 2 comments
Closed

Rename Renderer -> Device #115

azul3d-bot opened this issue Mar 6, 2016 · 2 comments

Comments

@azul3d-bot
Copy link

Issue by slimsag
Tuesday Dec 09, 2014 at 13:45 GMT
Originally opened as azul3d-legacy/gfx#60


In an effort to help the gfx package be less ambiguous -- it would probably help if we tried to stick to our roots of making the package just a single Go interface to modern rendering API's as it's supposed to be.

Renderer is a somewhat abstract term and as such it may confuse people into thinking that this package restricts in some way how your objects look. This isn't the case and it's up to the user to define how things look completely, so a better name for Renderer is perhaps just Device which implies you're talking to the graphics device.

@azul3d-bot
Copy link
Author

Comment by slimsag
Tuesday Dec 09, 2014 at 13:56 GMT


It might also make sense to rename GPUInfo -> DeviceInfo if this is the case.

And also hence Renderer.GPUInfo -> Device.Info

@emidoots
Copy link
Member

emidoots commented Mar 6, 2016

Fixed/merged as part of #1

@emidoots emidoots closed this as completed Mar 6, 2016
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

2 participants