Da*n, how many times should it be repeated again and again
Casio has its own politics, and it's very normal that they decide what features of their products they will offer to their users, and what will stay hidden. Don't forget that the ClassPad is a
commercial product, it is not an free or open source project! It is their
right to hide the internal structure of the CP if they don't want us (as simple users) to know how it works. And it is also their right to provide all the needed informations to their collaborators (like Saltire), and to forbid them to share it among the user community.
We already discussed many times about the buzzer support, and I think that things were clear: Casio does not want it to be supported simply because there is a possibility that the future ClassPad models won't have a buzzer anymore, and thus every programs using it would bring some boring incompatibilities among the different models.
Furthermore, Greg is a worker at Saltire, which is bound with Casio by contract, and you don't have to compare our position and his position. And about the secret menu: well, this is a secret menu, so it must remain secret, that's all. What's the point to have a secret menu if everybody has access to it?

I also would like Casio to provide us more information about the ClassPad's internal stuff, but we already have a nice SDK and support from Saltire; remember the case of the AFX for which we didn't have any support at all

Between a limited support and no support at all, I gladly choose the first solution. So stop complaining, and let's work hard all together to "complete" the SDK with some other interesting stuff

Edit: Consider my CPLua project. There are different things that are partly available, but about which I do not discuss for now, because it is possible that I will change it in the future versions or because it needs a lot of explanations to understand how it must be exactly used. Those things are hidden to protect reckless users from possible crashes or bugs due to an incorrect use of those features. Should I be blamed for that?

Therefore, if I would want to work with another collaborator, I would give him the details about some of those "hidden" features because I'm sure that he would use it in a correct manneer, and so he would be able to do some great things with it; but I would not want him to talk about that to any person whose not related to CPLua's development