I'd like to bring out an Android app in the near future, so I was wondering
how to support a couple of funcitonalities I have got used whilst
developing for J2ME and iPhone
first the versioning. With J2ME (using NetBeans as IDE) I had the
option to auto-increment the softwwares version every time I compiled
it. I was wondering if something like this is available for Eclipse
and if so how to use it ?
secondly a common code base. Is it possible to have a common code
base for several projects ? For example I might have a game which
actually uses the same code but needs different graphic resources. I'd
hate to have a different project for every game/app and have to
manually edit every project's source every time I want to submit a new
code-change. Any solution for this ?
Thanks in advance for every kind of help/hints/tips !
Another idea:
If you can package the common code into Classes then a library approach would help.
In eclipse under project properties you can add a library to your project.
Hope this helps you on.
Related
For a project, I am changing certain ContentProvider-files in the Application Framework Layer of the Android System. As I am trying different things, I was wondering if it is necessary to build the Android Source for every change I make, or if there is a way to somehow emulate the system without the build?
I am not entirely sure what "building" means, as I cannot find a proper definition including Android as a context. I assume it is some kind of compiling?
Converting the source code into an executable program? In that case I do not think there is another way, is there?
But do I understand building correct in the first place? In that case, I would believe there is no other way than building the system every time and then see how it works out.
So I might have the solution right here, but I was hoping someone could assure me that it is right or maybe tell me why it is not?!
Any help is very much appreciated!
Building in this context means that all Android source files are re-compiled by the java compiler and a massive .jar file is produced. This is the Android.jar file that we see in the library dependencies of an Android application project.
Unfortunately, the short answer is that there is no way out for you except to re-compile the entire blob of the Android framework files each time you make a change. What I can advise you is to plan all your changes beforehand so you don't end up wasting a lot of time.
I am working in a team to create an andorid application.Initially we worked on a particular single system for developing.
Problem is that we want to divide the work among all of the team members so that they can work on a particular section of the development in seperate systems.
But we dont know how to divide a project into different systems.Also we would like to know how to club these works together after completion to form the application.We are using eclpse for developing.
Please help us.We are having a great problem with this.
Please help us.
#user3285824 : You need a Revision Control or Source Control Tool. Please check out Apache Subversion which is the best tool to develop separate modules in eclipse with team members.
Follow the tutorial to install SVN in eclipse.
Use GIT repositories in a common server. There you can get your own copy of the project and you can modify your copy. Then you can update your changes in the server. Please refer to http://git-scm.com/book/en/Git-on-the-Server-Setting-Up-the-Server
I have a project that I have been working on which is a standard android application that does not include any other external libraries at this time. I am now looking at making a game at the end of the app(its a quiz so after the questions I want to make a mini game).
So what I am trying to find out is can I just import the libraries that it uses and connect them to my project rather than creating a LibGDX project and importing that?
What it comes down to is your personal preference. In answer to your question, yes you could just add in the jar files and such into your current project, however you are going to have to edit your manifest and some add in some other stuff besides jars using this Setup. In my personal opinion it would be easier to create a libgdx project using the tutorial found here, but in the end as I said before it all depends on what exactly you want to do.
Before deciding, ask yourself.
Do I want to have everything in one project, or can it be in more than one?
What would be better in the long run for managing my app.
Do I want ease now or later?
Cheers!
I need to build two version of same android app and install both on same device, i can achieve this by keeping two different projects (different package name),but it's pain full to manage both, rather than keeping two projects is there any better way to achieve this.
Sam.
You can use a library, but you'll need to restructure your code quite a bit in order to do it.
Basically, write the code specific for one app in one project, and the code specific for another app in another project then write the code thats the same across both apps in a library and reference it.
Can I ask what your doing this for though? If your doing a "free" version of your app and a "paid" version there are a few other options as well. Like making a dummy app and checking for it's presence in the main app.
We have several apps that will be very similar in layout and code. The only difference is we will be switching out graphical elements, and making changes to a single constants file and strings file. Of course, theres several problems with this -- the first being namespace. Having an app with the same namespace will overwrite any other apps.
What are some suggestions to doing this?
Currently our namesapce is:
com.company.appname
I figured I could do:
com.company.appname.appversion
I've seen post about ant scripts that helps with this, but I'm wondering if theres more fluid solutions now.
I would suggest looking into Android Library Projects to help with this.
I use this approach for a Lite vs. Free edtions of one of my apps. I have a Library project that contains all of the source and most of the resources for the apps and then 2 projects that use the 1st as a library project, one for Lite and one for Full edition.
The two dependent projects each have their own resources and manifest, allowing the namespace to be different and for me to swap in different strings, drawables, etc. depending on the edition.
I tried the Ant approach but it seemed to be much more of a hassle than the Library project approach. Hope that helps.