On Sat, 3 Nov 2018 11:56:09 +0000, Bill wrote:
The other thing I would like to comment on is the use or need to stick
to the specific default directory setup with Android Studio.
Hi Bill,
I apologize for going "dark" as I tried to solve the emulation problems,
where I was successful with emulation.
http://www.bild.me/bild.php?file=7301488androidstudio29.jpg
I now can offer noob Android users 20:20 hindsight of the following:
1. If you're on older AMD CPUs on Windows - don't even think of emulation!
2. If you must emulate, don't use the Google emulators (arm or x86)!
3. The best emulator, for older AMD, is the Microsoft Android Emulator.
With this 20:20 hindsight, I don't recommend bothering with emulation.
Nor do I recommend bothering with text tutorials after the first "hello
world" works using the Google tutorial you and I both used, Bill.
With 20/20 hindsight, I recommend people start with a good video tutorial.
I haven't chosen the best video tutorial yet, but this one is pretty good:
https://youtu.be/dFlPARW5IX8 (Bill Butterfield, an adder app)
Given that it's human nature for each tutorial writer to name their apps in
a way that makes sense to them, my 20/20 hindsight advice to you and any
other noob writing their first Android apps, is to name the first app
"app01" and to name the second app "app02" and to name the third app
"app03", etc.
That way they organize themselves consistently as you jump around from
tutorial to tutorial.
In 20/20 hindsight, I also recommend you choose a consistent *short*
company name, e.g., I'm now using "kiss" as the company name, as all the
apps will have that same company name for consistency.
While I break down my installed programs into categories, I haven't seen
the need (yet) to break down the projects into categories, so all my
projects fit nicely into c:\tmp\android\{app01,app02,app03,etc.}
In stark contrast, my installers are saved in the following hierarchies:
1. JDKs
2. SDKs
3. EMUs
4. IDEs
5. CPUs
6. APKs
7. VIDs
For example,
1. The java jdk/jre is saved to C:\software\editor\android\jdk\oracle\.
2. The Android SDK is saved to C:\software\editor\android\sdk\google\.
3. The MS emulator is saved to C:\software\editor\android\emu\microsoft\.
4. The IDE is saved to c:\software\editor\android\ide\android_studio\.
5. The HAXM software is saved to C:\software\editor\android\cpu\haxm\.
6. The final APKs are copied to C:\software\editor\android\apk\app01\.
7. Downloaded videos are saved to C:\software\editor\android\vid\bradsaw\.
etc.
Of course, none of this did I know _before_ I started, where I'm learning
where things logically fit only with 20:20 hindsight.
I just now deleted the entire setup, and started over because I had
installed so many hacks that I wanted to start with a clean slate.
When you try to wipe out everything, you find stuff in the strangest places
though, Bill, so take note of some of these strange locations...
o %USERPROFILE%\appData\Local\Android
o %USERPROFILE%)\.android\ (I'm not sure why stuff was put here)
o %USERPROFILE%)\.AndroidStudio3.2\ (I'm not sure why stuff is here either)
o %USERPROFILE%)\.gradle\ (I'm not sure why stuff is here either)
o %USERPROFILE%)\.m2\ (I'm not sure why stuff is here either)
o %APPDATA%\JetBrains\ (where did that come from?)
o C:\Program Files\Android\
o %LOCALAPPDATA%\Android\
o %USERPROFILE%\AndroidStudioProjects
etc.
In summary, I think the perfect place for noobs to share how they got their
first few Android apps working using Windows freeware is exactly these
newsgroups.
The hope is that scores of people will follow in our footsteps, benefiting
from our now 20:20 hindsight!
Certainly I _wish_ I knew a week ago what I know now about choices to be
made when a noob decides to code their first few Android apps using Windows
freeware on older desktops.