2010
My last few Android development posts have been kind of long (took long to write anyway), so here's a short one...
My last few Android development posts have been kind of long (took long to write anyway), so here's a short one...
So overnight an update to ColdFusion Builder was released. According to the update instructions, if you're running ColdFusion Builder as a plug-in to Eclipse (like I am), you need to start/restart Eclipse clean, which can be done by typing "eclipse -clean" at the command prompt within your Eclipse folder.
The problem I ran into was I couldn't do that on my MacBook Pro. I opend up a Terminal window, navigated to my Eclipse folder, tried the command, and was told "command not found."
I had an eclipse exec file in the directory along with the normal Eclipse.app application bundle file, so I'm not sure why it didn't work. I probably either did something wrong or perhaps there's something funky about my Eclipse install.
But fortunately I found another way to launch Eclipse with the clean option in an old set of Eclipse (3.3) documentation. Here's what I did (after installing the ColdFusion Builder update):
In my last post, I talked briefly about how the R.java file, a resource file located in the "gen" folder of your Android application project that is automatically generated and updated by Eclipse and serves as a resource map. My example code demonstrated how you could reference layout.xml files via the R.java file and how Eclipse would register the id of the UI objects within the R.java file as well.
I also mentioned that the layout XML files for your Android app are located in a "layout" folder within the "res" ("resources") folder. There are other folders under the "res" folder as well, and the content within those folders is also registered with the R file, allowing you to access those resources within your Android code.
In my last post, I promised to show how I would attach my simple example layout to an Activity object and make a change or two.
In my last post, I alluded to the fact that you can lay out your visual elements and controls on your Android application screens (your Activity objects) using XML. In this post, I'm going to give you a peek at what that XML looks like.
Recent Comments