Years ago, on Eclipse Galileo and Helios, in 2010, I wrote some Android applications. This is me
trying to resurrect that knowledge, but using Android Studio (IntelliJ IDEA).
—can take some time to download (380940715) at work where things are slow. I got to reading
around and dicovered that, if one's already using IDEA, there's no point to getting the whole
—might be better to go look for Android plug-ins, then download the smaller, Android SDK. See
Prerequisites for Android Development
...if you are already using this IDE before beginning to develop Android applications with it.
This section includes how to get stuff set up except that it assumes you've already got Intelli
IDEA and also the Android SDK download (not Android Studio, just the SDK).
I already had IntelliJ IDEA installed and didn't want to download and install the whole Android
Studio shebang. After all, Android Studio is but the community edition of IntelliJ IDEA.
This is treated by JetBrains on at
IntelliJ IDEA 15.0 Help / Prerequisites for Android Development and there is a
link reference to detailed instructions for Adding SDK Packages where you're told,
first off, that by default the Android SDK does not include everything you will need.
In short, this means that you will need to make some choices in this dialog. Important note:
when this linked page says, "Tools directory" or "Android folder," etc., "directory" and
"folder" really mean sections to be expanded with options to click on inside this
Don't dismiss this dialog just yet.
I saw one error, "Stopping ADB server failed (code -1). I happen to know that this is the
Android debugger. It probably tried to stop it; it wasn't running in the first place.
(While the installation proceded, my host became sluggish and I lost my gvim cursor.)
My host is pretty fast (i7 4GHz with SSD), but this took about 5 minutes. Ultimately, there
was no button to dismiss this dialog except the close-window box.
As the dialog offered me no SDK choices, except to navigate (but to where?), I'm stuck and
have to resort to Google. Here's what I ended up doing:
Java SDK: 1.7
Build target: Android 6.0
I clicked OK.
I put a comment on this
This string ends up on the path res/values/strings.xml.
requestWindowFeature( Window.FEATURE_NO_TITLE );
At this point, I note that the formal
Tutorials page has additional, useful stuff to cover:
And, I'm interested in all of them, though I'm acquainted with the events thing.
However, I'm tired of this and I think I'll move on to my friend, Lars Vogel.
I thought I'd try out Lars' new tutorial. I once wrote a
page like this one alongside
his original Android tutorial, but that one's been lost. I don't know how useful those notes will
Lars states that "Android tooling uses Gradle as [its] build system". This does not appear to be
true in the sense that you don't have to if you do not want to. Maybe I'll discover this to be true
anyway. So far, I haven't used Gradle and I certainly do not plan to.
JUnit works, but it can't be used to test Android-specific components for which there are wrappers.
I haven't done this tutorial yet.
I want to make some observations on this.
Additional notes breaking down Android development...
...toward functionality I know I'll need in an application I'm considering.