As posted in forum:
  <http://forum.jogamp.org/Improvements-API-Support-td4031509.html>

This bug entry shall envelop all subsequent bug entries
reflecting the task of validating 'API semantics, implementation and more'.

+++

Dear all,

being reminded by a chat we just had on IRC about improving our API,
I like to pass this onto the forum for all to read.

Whenever we see something odd in our API,
especially when approaching it the 1st time,
please report it in the forum and/or IRC
and finally via an 'enhancement' bug report.

Otherwise we will not be able to see it and hence won't fix it.

Long term users usually don't see other people's use-cases
or - even worse - live with it by using a workaround.

Further more I like to encourage all of you to
openly criticize things in a constructive manner.
Whether it be my or other people's 'behavior',
JogAmp's usability in general (documentation, web pages, ...),
or it's implementation.
Please keep in mind that our resources are limited
and hence we cannot change the world in a finger snap.

Hence the 'constructive' part of your criticism could be performed
in providing a proposal (git patch/pull-request, wiki edit, etc)
which we are able to discuss and hopefully can merge later on.

Thx to the free software notion of JogAmp, this is not only possible,
but very much encouraged!

Thank you all and have a great time.

~Sven