==== Wording ====

==== Wording ====

In the following sections, i'm going to use AE for jPCT-AE and jPCT for desktop jPCT.

In the following sections, i'm going to use AE for [http://www.jpct.net/jpct-ae jPCT-AE] and jPCT for desktop [http://www.jpct.net jPCT].

AE provides the 3D engine only. It doesn't provide any Activity example or framework for Android. You'll find some example code on [http://www.jpct.net/jpct-ae/ the AE-homepage]. So porting from jPCT to AE means to port from your native OpenGL window or AWT/Swing component with its key and mouse polling and/or listeners to an Android Activity...and vice versa.

AE provides the 3D engine only. It doesn't provide any Activity example or framework for Android. You'll find some example code on [http://www.jpct.net/jpct-ae/ the AE-homepage]. So porting from jPCT to AE means to port from your native OpenGL window or AWT/Swing component with its key and mouse polling and/or listeners to an Android Activity...and vice versa.

To ease porting, I suggest to use the Lights class for managing lights in jPCT, not the methods in World. That way, you can simply port those sections by changing the import only (because the Lights class has moved from util into the main package). It's cleaner that way anyway...

To ease porting, I suggest to use the Light class for managing lights in jPCT, not the methods in World. That way, you can simply port those sections by changing the import only (because the Light class has moved from util into the main package). It's cleaner that way anyway...

==== Performance and memory issues, serialized objects ====

==== Performance and memory issues, serialized objects ====

On the desktop, memory and performance are to spare...at least to a degree. On Android, this isn't the case. Remember that you have to work with a max memory of 16mb...and coming close to that border isn't really fun, so you should plan to use some mb less. CPU power is limited too and many phones don't even have a FPU, meaning that all the floating point calculations are done in software emulation mode.

On the desktop, memory and performance are to spare...at least to a degree. On Android, this isn't the case. Remember that you have to work with a max memory of 16mb on older devices...and coming close to that border isn't really fun, so you should plan to use some mb less. CPU power is limited too and some older phones don't even have a FPU, meaning that all the floating point calculations are done in software emulation mode.