[Glsdk-devel] [GLm] api

[H. H. <hen...@gm...>]

The GLM API seems at this moment to use two sets of naming styles. Compare
these two for example:

glmVecSub2f
glmVecLength2f

The first function is using a short form for the operation ('sub' as from
'substract') while the other is using long form. Should we simplify the API
to look like this:

glmVecSub2f
glmVecLen2f

Althought on the other hand, how do we shorten such stuff as Normalize,
Transform, Identity, Inverse? This does not necessary look good:

glmVecNorm
glmVecTrans
glmMatTrans
glmMatInv
glmMatIdent

Is this even a big issue? Comments?

If we decide to keep the API as it is now, I think we should lock it in and
begin to outline the API reference for it. For later versions, I would like
to implement such stuff as colors, quaternions and maybe planes and matrix
stacks but this can wait. Bigger priority is to get the current version
working and tested for.

For Korval: I outlined some API ref in a plain text format. You may find it
in 'docs/sdk_reference/glm-apiref' in the latest revision. You may use this
as ideas for the DocBook API ref and this file needs to get removed once you
migrate it into DocBook.

-- 
Henri 'henux' Häkkinen