Two months ago, I set up Eclipse Indigo to build android application. Then i got some problems with my computer so I uninstalled it.
I downloaded Eclipse Indigo again and tried to set up Eclipse but the interface has changed. There are some additional folders and options. I followed newboston tutorials for installation.
So, my question is how can I get back to the old interface like the one in the tutorial? I don't like the new one. Here is how it looks in the new interface. I've also attached a video which has the old interface.
I don't think this is a problem of Eclipse. This is related to Android Development Tools(ADT), which is a plugin for Eclipse.
If you really want to go back to previous version of ADT, please take a look at this Answer to get old versions of ADT.
Related
Can Eclipse in conjunction with ADT still be used for Android Development (and if yes, how do I go about it) or should I just keep using Android Studio?
I tried setting up ADT on my Eclipse, but it wouldn't work (after many, many tries).
Any advice would be appreciated.
yes you can but the best practice for android development is by using Android Studio because linux users has also problem with eclipse. you can take help from below link
https://stuff.mit.edu/afs/sipb/project/android/docs/sdk/installing/installing-adt.html
but as per my suggestion you should use Android Studio because if you are using eclipse then you need to migrate the code also.
I'm a newbie in Android development and I have some difficulties with installing environment. Normally I'm trying to solve this questions by myself, however here I really need your help. This questions may look for you a bit stupid, I'm sorry for this in advance.
First question: is it really matters which eclipse package I will use? I saw it's a number of different packages like Luna, Mars, Neon and so on, and each package has different versions of eclipse, which one I should use?
I installed Eclipse platform(version 3.8.1) on my Ubuntu 15.10, connected ADT plugins, SDK, everything were ok, until I created a new project. It gave me an error "Could not open the editor: The editor class could not be instantiated. This usually indicates a missing no-arg constructor or that the editor's class name was mistyped in plugin.xml." and long list of problems under "Details" button.
and why you want to use eclipse ?
The official IDE now for android is Android Studio its pretty simple and better here's the link to download it and it's easy to download too :
http://developer.android.com/sdk/index.html
So I've been trying to install libgdx for a few days with Eclipse and it kept telling me various things (Android ADT, Java JDK, etc.) needed to be updated, so I did that, but I kept getting the same error.
Then I decided to download an older version (0.9.8) and I used the gdx-setup-ui.jar to set up my projects. But upon opening them in the Eclipse/ADT bundle, the Android and HTML projects had errors in them involving the import statements, which I tried to solve to no avail.
This is the tutorial I've mainly tried to follow.
Does anybody have a solution for me to get it to work? I'm most familiar with Eclipse, having worked with it for Android for a while now, so I'd prefer not to switch IDEs.
Thanks in Advance
Use ADT (Android Developer Tools) instead of Eclipse. (Is the same thing anyways)
http://developer.android.com/tools/index.html
If you got errors after importing your projects on android, right click on the android project, and at android, check the version that is there.
For HTML you need to install the GWT plugin.
Recently libGDX has moved to Gradle, so you might want to look over that
https://github.com/libgdx/libgdx/wiki/Project-Setup-Gradle
Well I want to highlight this and bring it all in this thread, as the rest of threads did not have a concluded answer, so before skipping into them here are the threads I referred to:
Adt doesn't create default hello world but command line does
[solved ]Eclipse behaving differently while creating new project/activity
ADT has been behaving a bit weird since past few days. I keep my SDK always updated so I frequently Run the SDK manager and download all the updates. recently I noticed that if I create a new android app project it is not creating a default MainActivity even if I check that box, it does not create a Activity under src and more to annoy me, I wasnt able to refactor anything, so I realized that I had to update my Eclipse as after reading few posts, but now when I create every new project it creates an annoying appcompat_v7 project with EVERY project, say I create two new projects it creates appcompat_v7_2....this is driving me crazy and the new project library is the appcompat_v7 project. This is becoming annoying and no idea whats going on here !!!! What should I do...please rescue me ! Thanks in advance ....A screenshot to annoy u guys too ... :)
***************Current Alternative, not a solution***********************
As of 12/5/2014 with ADT 23.0.2 I dont see this issue anymore.
I have waited for an acceptable solution on this issue (as of now there is none), but one of the SO members directed me to this post https://code.google.com/p/android/issues/detail?id=66975. What I am doing is described in one of the solutions below, but for people who have come to this post, the alternative is to delete that ugly project(if you have more than one) which has been created and add up this one(appcompat_v7) as a library. So if you create another project and appcomat_v7_2...comes up delete that and point your project to the appcompat_v7, do the same for other projects too. This is not recommended for some reason though, but it worked well for me till now without issues. If anyone hits up with a solution please post it here.
****************Current Alternative, not a solution*****************************
the folder appcompat_v7 doesnt get created if i use
minSdkVersion="14"
Seems like it is a eclipse bug. What you need to do is go to properties in the of the Android Project and in the Android Section. Add the library appcompat_v7 and remove the appcompat_v_7_2 (duplicate). Then you can remove the appcompat_v7_2 as a eclipse project. All errors fixed.
Just a workaround.
The appcompat project is a library to support android's older versions. The support library was introduced by Google recently - I don´t know in which Android version.
But the point is, this project is only created when you create an Android project to cross Android platforms. I mean, when you select an old min API, e.g. API 8 (Froyo), but target recently versions, your project must have the support library.
Anyway, the creation of appcompat_v7 project is some issue that has to be better configured by the eclipse plugin maintainers. However you can elegantly turn over this issue by targeting newer APIs and including in the build path the support library. This is more elegant than the others because it is better to you focus in only one android version when building your application, and when it is done, you have an authentic version of your app that you can use as a mold to support other versions, either older or newers.
I posted this question on the IntelliJ community forums but it seems as if they aren't very active so I'll just post it right here on S/O. I'm new to IntelliJ and I'm switching to use it from Eclipse which was really buggy and not useful to my needs. However, I'm attempting to build an Android project in IntelliJ Idea and it is only creating a .idea folder and the src directory without any inner files in them like it should. I've got the Android-SDK properly installed and I'm using JDK 1.7 and I'm even following the directions to properly start an Android project from the IntelliJ Wiki (found here) but it still leads me to no success. It seems as if I've got the Android Support plugin already installed with my program but then again I'm not really sure. Can I get some help please so I don't have to revert back to Eclipse again? Thanks.
Try to delete Android SDK and install it again, then download at least one Platform. IDEA runs SDK tools to create Android project template, for some reason it's failing on your system.
Check if it works better with JDK 1.6.
See the screencast that I've just recorded.