3. Help
* Wiki. I realize that writing a good help is a big problem in itself, but with a wiki, we can all pitch in.
* Context F1-help like in VB. When you hit F1, you will be sent to the apropriate page in the wiki.
* Descriptions need to be better (especially with cryptically named stuff, like arg1, but also valid values (one should not have to plough forum posts to find the valid values for, say, SupportedOrientations, to find sensorLandscape)
* Examples. More examples are needed.
* Cookbooks, step by step for stuff like (much of this already exist in the forum, so it¨'s more a mattor of organizing it):
** How to do licensing
** How to do in-app payments
** How to deploy to Google Play
** How to do accelerated graphics
** How (and when) to save/load settings
** How to get app listed for tablets in Google Play
** How to make an app that can install to external storage
** ...
* Best practice-code (overlaps a lot with cookbooks). Showing by example to help people making better code.
* Wiki. I realize that writing a good help is a big problem in itself, but with a wiki, we can all pitch in.
* Context F1-help like in VB. When you hit F1, you will be sent to the apropriate page in the wiki.
* Descriptions need to be better (especially with cryptically named stuff, like arg1, but also valid values (one should not have to plough forum posts to find the valid values for, say, SupportedOrientations, to find sensorLandscape)
* Examples. More examples are needed.
* Cookbooks, step by step for stuff like (much of this already exist in the forum, so it¨'s more a mattor of organizing it):
** How to do licensing
** How to do in-app payments
** How to deploy to Google Play
** How to do accelerated graphics
** How (and when) to save/load settings
** How to get app listed for tablets in Google Play
** How to make an app that can install to external storage
** ...
* Best practice-code (overlaps a lot with cookbooks). Showing by example to help people making better code.