You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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 forRenderer
is perhaps justDevice
which implies you're talking to the graphics device.The text was updated successfully, but these errors were encountered: