Quote from: EgonOlsen on March 13, 2011, 05:51:28 PM
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.

good software design does not mean to throw a bunch of interfaces inside the source nor does it mean to write anything that is monolithic in ANY way. short and quick: if the software someone writes using jPCT-AE is maintanable too hardly it is not going to be used in some major projects. it's that simple.

Quote from: EgonOlsen on March 13, 2011, 05:51:28 PM
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 ...

no, i said its good work :-) see here:

Quote from: xsynergy on March 13, 2011, 05:26:21 PM
... it's really good work you did up to now ...

Just try to not take it personal, its software and nobody can write software perfectly, and i just have thrown up an idea on improving it. nothing more.

Quote from: EgonOlsen on March 04, 2011, 10:21:27 PM
I'm not sure if it's a smart idea to enter a community by calling the source code of the examples terrible. It took me some time to make up my mind if i should take this post offensive or not...i decided to try not to.

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. 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).

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).