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.
Labels:

Comments

Post a Comment

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
Post a Comment
Read more

Best Documentation of a Free Software Package

One oft overlooked artifact in software development is the documentation. An API that is not well documented is no API at all when time is of the essence. That's why I think it is important to discuss some of the tools I have used and their documentation. AutoIt - I love how you simply press F1 within the AutoIt editor and boom, the reference to the particular syntax or function pops up in the help window. This help file is well written, self-contained, and chock full of examples that can be opened up in the editor right from the help, a fantastic symbiotic relationship. After installing AutoIt and giving it a try using their examples, I was able to create client/server scripts, GUI scripts, and window management scripts in no time. Overall, AutoIt is tops in this competition. A+ MySQL - At the bottom of each page of documentation that discusses a particular statement, users are able to post comments containing code snippets for that particular statement. This is great... M...
1 comment
Read more

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 pa...
Post a Comment
Read more