From: Jason M. <ko...@gm...> - 2008-08-24 18:07:25
|
Henri Häkkinen wrote: > > I see your point. At the correct point, we can crack open the shape > functions and to show the user what's inside, but there's no need > to bog > down e.g. a lighting tutorial with vertex uploading. > > On the other hand, having a "standardized" format for communicating > vertex attributes to the user could be useful. That way, a future > model > loader would be able to provide data in the same way as the shape > functions do. But that's not really pertinent right now (just > expressing > an idea oft-discussed at the OpenTK forums). > > > Yes, I see the idea. If we declare the GLSshape struct as open, we can > allow third party geometry importers and have the geometry drawn with > DrawShape. However, we could also just provide accessor functions to get at those attributes. The internal structure of GLSshape does not need to be exposed to user to be able to provide loading support. If we need to expose the ability to create a GLSshape from arbitrary data, we can add a function to do that. In short, we do not /need/ to make it a public struct in order to provide this functionality. |