Skip to main content

Android Platform Setup - somewhat circuitous, but still easy

It's been a while since I have had to seriously use Java in a development application, but now that I plan to develop apps on my Atrix, I'm going to have to get back into it.

I just installed my Android environment on my Windows 7 laptop. The instructions from the Android website were somewhat difficult to follow given the number of utilities required and the order in which they ought to be installed. To save time from having to piece together to components in the right order from the Android site, here's what I did:

1. Downloaded and installed JDK (Java SE) 6 update 24 64-bit.

2. Downloaded and installed the Android SDK (installer_r10-windows.exe) from the Android website.

3. Under the Android SDK Manager, selected SDK Platform Android 2.2 (since this is what my Atrix has) and downloaded/installed.

4. Downloaded and extracted Eclipse Classic v3.6.2 (eclipse-SDK-3.6.2-win32-x86_64.zip).

5. Started Eclipse Classic, went to Help -> Install new software, and just followed the directions from the Android website on obtaining the ADT plugin from the Android repositories.

6. In Eclipse Classic, went to Window -> Preferences, and under the Android tab, set the path to the Android SDK.

Now, I'm off to hello world to get something running, or crashing, on my phone.

Comments

Popular posts from this blog

Software Design Principles - SOLID

The SOLID software design principles weren't called SOLID while I was in grad school, but the concepts were there in my Object Oriented Design course. They're worth mentioning here, primarily because I think once you start coding and become dangerous, it's one of the best ways to stay organized once you incorporate it into your daily coding routines, and it even changes your way of thinking for the better: https://en.wikipedia.org/wiki/SOLID

The TL;DR guide to git

While in the past I've held a pretty high opinion to using mercurial for version control, the majority of version control these days seems to done in git.  Here were the commands I found most useful to get productive with git right away. # Clone a repository from an origin, i.e. my github MaskingUtils repository git clone git@github.com:caelumvox/masking-utils.git # Add a file after it's been updated to stage it for commit, or add a new file git add filename # Commit the file to local repo git commit # Push the file to the origin so the rest of the team can see it git push # List all locally tracked branches git branch git branch --list # Get a list of all branches from the remote git branch -r # Create branch locally git branch develop # Push the branch to the origin repository to make sure it is tracked there git push --set-upstream origin develop # Pulls latest from all local branches tracked from origin; won't pull non-tracked branches git pull --all # Fetch the branch

AWS Development On A Budget

I was interested in hosting a small portfolio of applications in AWS, but I wanted to keep costs down.  I was willing to maybe host about $30-$40 a month of servers just to showcase some of the applications I was putting together.  Here's what I came up with. The basic capabilities here were: serve up about 6-10 applications that would require some level of web application hosting, database, file storage for larger items, and possibly queuing or email schedule jobs to run periodically to either scrape websites for new data or access APIs regularly These were the services in mind, all out of US-East-1 (Virginia): EC2 instances are pretty cheap.  You can run a t3a.nano for about $3.38 a month, or a t3a.micro for about double that for $6.77.  The more things can run on one of these instances, the better. Lambdas also don't really add up to much if they are scheduled jobs that do not consume large amounts of memory or computing.   The cost of a Lambda run as part of an API gateway