but you have to admit that most examples are actually snippets of code that are hard to read for someone who just enters the community. especially because they are really "quick and dirty" solutions.
They are not quick and dirty, they are simple
EXAMPLES. What's so wrong with that? The approach of writing this kind of examples served the community well so far IMHO. You'll always find somebody who thinks different...and this person is free to contribute other kinds of examples.
Besides this, from a software technical perspective jPCT-AE seems (for me) to be a quick and dirty solution anyway (please excuse me for beeing that honest).
You don't have to like it nor do you have to use it. It's not quick and dirty. Granted, it's not packed with interfaces, packages and whatnot and it's pretty monolithic in design. But that's the way it's supposed to be and that's what works really well on Android.
Its too bad jPCT-AE is not open source, it's really good work you did up to now, considered that there are no other comparable free 3D engines for android out there right now. but it will change really quickly when google improves the android market payment possibilities (and it will happen, google already announced). wouldn't it be a good idea to re-release (at least) jPCT-AE based on some sort of an open source license and set up a developers environment. that wouldn't be much work for you and the development progress of jPCT-AE would increase really really fast. It's too sad to see such a good preliminary work is going to just become irrelevant to the android community in future. take a look at AndEngine, it's growing massively because of this, and it already kicked Cocos2D, that has been more popular (because of its capability to deploy to iphone and android).
One of the main reasons, why it's not open source is exactly this kind of "oh it's crap, but i can make better by (choose one) (a) renaming some methods, (b) move some classes, (c) refactor (and break) some inner workings to improve (c1) performance or (c2) code beauty or (c3) my gut feeling"-kind of thinking. Just have a look at what happened to Android support for JMonkey...it's open source and popular and all...and the Android version isn't barely working, limited to OpenGL 2.0 devices, slow...and nobody seems to pick up to improve it. It's all a lot of talk but nothing happens. You can't compare 3D to 2D in this regard IMHO. A lot of people can contribute to a 2D engine...for 3D, it's much harder to find somebody who does.
I'm happy with the way the engine is now...and if it goes down the drain because the next big thing comes around the corner, then so be it. I can live with that.