-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On 2012-02-08 04:44, dmotd wrote:
as any other primitive, you can connectmultiple gemhead to a single gemvertexbuffer.
that's true, but i'm not sure it's a widely used feature, my sense is that people will create multiple gemvertexbuffer instead.
which could mean that the documentation is lacking.
i don't really see a strong interest splinting gemvertexbuffer in 2 different objects, but if you do so, and if you are ready to code it, then i have no objection, as long as you can provide a compatible abstraction that replace the current gemvertexbuffer object.
of course, i wouldn't want to break your current functionality.
no problems from my side. i don't especially like the _name_ [gemvertexbuffer] (it is too similar to [gemframebuffer] (which goes well with [gemwin]), but the functionality/usage is very different), and if it was made into an abstraction, all the better.
one could also use something like [pix_texture], that applies textures that it either generated itself (from a pix) or that was generated somehow else (by taking the texture id in it's 2nd inlet). but i'm not so sure that this scales well for the different VBO types.
fgmasdr IOhannes