[GEM-dev] gemvertexbuffer (prev.. vertex operations / vertex_* (prev.. gem port to opengl-es - initial developments..))

[IOhannes m zmoelnig]

-----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
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAk8yMy0ACgkQkX2Xpv6ydvTSEgCeOrsIy34fUJO0K7K1yxxZ0+Tz
d5sAnigbwBE47x3mq7zrhxkYlo7sUI+7
=0fBX
-----END PGP SIGNATURE-----

-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 3636 bytes
Desc: S/MIME Cryptographic Signature
URL: <http://lists.puredata.info/pipermail/gem-dev/attachments/20120208/7e851c05/attachment.bin>