Author Topic: Developing JPCT-AE program on Android device  (Read 1841 times)

Offline MichaelJPCT

  • long
  • ***
  • Posts: 235
    • View Profile
Developing JPCT-AE program on Android device
« on: September 16, 2016, 02:18:34 pm »

Most people develop Android apps on a PC, then test run in Android Emulator, then do further testing on real Android device. But sometimes you don't need a PC to develop Android apps - you can write code, compile, and test run on an Android device.
I'm introducing the basic usage of AIDE - an Android app which can compile another Android app, with JPCT-AE.
For this to work well, you need these:
1) latest version (2016) of AIDE, free version will do
2) an Android device fast enough, such as quadcore A53/A72 CPU
3) a real keyboard
4) a not-so-small screen, say 10 inch or more
5) jpct-ae.jar

when AIDE is launched, if no project is opened, AIDE lets you choose whether to learn lessons or to code, just choose "for experts".
then if no project is created yet, you choose to create a new Gradle project.
by default AIDE creates project folder inside /mnt/sdcard/AppProjects/.
after project is created, you create a folder named "libs" in /YourProjectFolder/app/, then copy jpct-ae.jar into folder "libs".
then you are ready to write codes.

you can also copy your Gradle or Eclipse project folder from PC to Android device and continue with the old project.

here are some basic operations you need to know when you work with AIDE:
1) to handle files, choose menu VIEW, then FILES, then click on the file to open. on the top of screen there are file tabs that you can click and a menu shows up providing CLOSE FILE options.
2) to build, just click the button looking like a triangle on top right corner of the screen.
3) in menu VIEW, there is LOGCAT, which is important for debugging.
4) in menu PROJECTS, there is REFRESH BUILD, you need to do that sometimes - when you find your app behaves like un-updated.

In this way, you can spend most development time on Android device - writing code. you only need a traditional PC to process images, sound, or build 3d models.