I'm trying to develop a plugin for Android Studio to add a new type of project to the selection of project wizards. Unfortunately it seems like Android Studio blocks every project wizard besides the one for Android projects. So far I already have a solution which works well in IntelliJ but not in AS. I already took a look at this question but as I am trying to create a new wizard instead of reactivating an existing one I hope there might be a solution for that.
For everyone trying to convince me to use IntelliJ IDEA with Android Plugin instead: unfortunately this is not and option as I have to stick to Android Studio.
tl;dr: trying to create a project wizard in Android Studio. Works in Intellij IDEA but not in Android Studio.
Related
I am a novice at android development, and I am following some tutorials to practice.
I notice that in several tutorials there is always a "Include C++ support" option when they are creating a new project. like in this image:
However, when it comes to Android studio 3.3 (which is the latest version, and I just installed it yesterday), I just can't find it. Android studio 3.3 is like this:
I have tried to google something like "android studio 3.3 include C++ support", but failed to get an answer.
So, where is that option? Did they abandon it?
By the way, I am developing on linux (Ubuntu16.04), while most tutorials I found are on windows. Could this be a reason?
Yes, In android studio 3.3 it has been changed and now it comes under New>New Project>Choose your project scroll down and you will find something called Native C++, as show in below image,
Reference Link
I can't create new android projects the way that it is intended to like in the instructions.
This is the first page I get: .
I don't know how I create a android project from here. Also when I open older android project I can't build them...
I'm using Mac btw
Any Idea?
Why don't we have a file similar to the .xcodeproj (for XCode applications) or an .xds (for Sencha Architect Projects) for our Android Studio Project?
I'm pretty sure a good number of you here have experienced the frustration of trying to import a project you see online in order to piece it apart better and learn how it works. I get that we are supposed to Import Android Projects built using Eclipse and Open Android Projects built using Android Studio.
However, why is it that we have to go through File -> Open -> then pick out the directory of the Android Studio app that we want to open? And the thing is, Android Studio doesn't seem to know it's an Android Studio project until it tries to open and build it. In the screenshot I have below, I have the sample Android Studio projects of ARToolKit, but I've only imported two of them.
As you can see, only those I've imported "can be seen as an Android Studio Project" as indicated that they have the Android Studio logo instead of a Folder.
This can be an issue for those just starting to develop in Android Studio on their own and they try and use existing projects (build from Eclipse or Android Studio) and they hit a snag with just trying to import the projects for reference. They might not know that they should import the folder and not the projectname/src subfolder. It adds to the "steep learning curve" that Android Development has if opening/importing projects aren't streamlined to a degree.
To sum up, my question is:
Why don't we have a single file that we can open that would in turn open Android Studio and import and build the project if it isn't built yet?
Android is not iOS. iOS development is only possible in xcode, hence it makes sense they added a shortcut to open it in xcode directly with a .xcodeproj file. Make life easier for iOS developers.
Android development however can be done outside of android studio as well. Eclipse is just one example, there may be other IDE's that support this. This is possible because android has standalone SDKs and tools that third party applications can use. iOS does not.
Imagine you are working on an android project in android studio. Then your boss tells you someone from 3000km away is going to help you. This guy may be using android studio, but maybe he isn't. When there are multiple options that developers can choose from individually, you do not want to pollute version control with files that you are using, but others may not care about. Each their environment.
This is merely a logical conclusion that you can come to by comparing. The "real" reason why this was done can only be answered by the people that created (adapted intellij) android studio.
This has been very frustrating to me too.
I try to give you a "beta" answer, waiting somebody to confirm it to me.
An Android project is just the composition of many parts that in some cases are concurrent to create the apk file.
It's just like what happens for the whole java projects: you have the main/src/java, the main/src/test, the maver or gradle files, the gradle or maven wrapper, the manifest, the configuration etc.
So you won't have a single project, but a series of folders that can contain many "flavours" or "versions" of the product itself.
The only help it is given to us is the Android studio icon that appears if a folder contains an android project in its subfolders.
I don't know if I have really answered to you, I just have given you my impressions and my thought.
I am trying to create an android program but, every time I set it up it does not make a new project **successfully**, the project that is made has a huge number of errors..
All the specifications are given in the screen shots below...
Making the Project
ADT
Maybe you can try opening it on Android Studio, an then making the new project there. Hope it could help you.
you need to import android-support-v7-appcompat library then clean your project
try to start using android studio, as suggest by developers/google Android studio for android Development, Android studio having much more functionality then eclipse and provide faster tools.
Android Studio
I'm trying to follow tutorials on Android but the default project that Android Studio creates has stuff like PlaceholderFragment and fragment XML files.
I'm having trouble following any of these guides because they all expect you to use Eclipse, which creates a different standard project without all this fragment code.
Should I just switch to Eclipse?
I would recommend synchronizing your tutorials and tools. Right now, that probably means switching to Eclipse. Android Studio is still an early-access previews. I don't recommend that newcomers to Android start with Android Studio, in part because of the struggles that you are encountering. Android Studio uses project structures set up for the new Gradle-based build system, which is different from what Eclipse uses. Plus, the wizards may generate different files, as you are seeing.
Now, if you can find a set of tutorials that happen to be based on Android Studio, and you want to go that route, that's your call. But a newcomer to Android trying to translate instructions for Eclipse into instructions for Android Studio is likely to get frustrated. So, if your tutorials are for Eclipse, I would recommend using Eclipse.