Hi Charlie, that is correct. Technically it does not matter how the starting Activity is called as long as it is declared in the AndroidManifest.xml. Calling them is also not problematic since they are in different java packages, i.e. edu.berkeley.boinc.MainActivity vs com.example.projectapp.MainActivity.
But if it causes trouble with Eclipse, let's rename them... Joachim On Mon, Jan 28, 2013 at 11:53 AM, Charlie Fenton <[email protected]>wrote: > Hi Joachim, et al, > > I am new to both Java and Android, so please forgive my ignorance. The > main activity classes are named MainActivity.Java for both the BOINC UI (at > .../boinc/android/BOINC/src/edu/berkeley/boinc/MainActivity.java) and the > example project (at > .../boinc/android/ProjectApp/src/com/example/projectapp/MainActivity.java). > > But when I try to add both projects to Eclipse, it refuses to accept the > second one because it already has a project named MainActivity. > > According to < > http://stackoverflow.com/questions/10779275/must-the-main-activity-name-be-mainactivity> > and < > http://developer.android.com/training/basics/activity-lifecycle/starting.html>, > you can use any name for the main class of an Android app, as long as you > declare it in the Android manifest file AndroidManifest.xml. > > So it seems it would be a better practice to use unique names for the > different projects, such as BOINC_UI and BOINC_EXAMPLE. > > Cheers, > --Charlie > > -- > Charlie Fenton [email protected] > BOINC / SETI@home Macintosh & Windows Programmer > Space Sciences Laboratory > UC Berkeley > > _______________________________________________ boinc_dev mailing list [email protected] http://lists.ssl.berkeley.edu/mailman/listinfo/boinc_dev To unsubscribe, visit the above URL and (near bottom of page) enter your email address.
