Ahem Motorola HQ-Android guys, the blog has moved to:

 http://mobilebytes.wordpress.com

 You will find coverage of the AndCooper Android Dev tool there.

To my OEM readers such as RIM, SonyEricsson, Nokia, Motorola, and etc. As I progress towards the last seps in the AndCooper Android Build Tool 0.1 release I have moved my blogging to a new platform and site.  The new site is:

http://mobilebytes.wordpress.com

on the wordpress blog/CMS platform. since I am able to post sample code easier with wordpress and etc I would like  to see my OEM blog readers at my new site of Android Code and Development blogging. Hopefully, I will see yoru readership there.  Hopefully, at some point PLanetAndorid changes their blogroll links and feed crawing to include and craw my new Android development Blog.

Some new Android Programming Wiki Articles at Mobilebytes. Link in right side menu under Profiles, FredGrott's Knols. I have moved my blogging over to Mobielbytes, so please change your bookmark to:

 http://mobilebytes.wordpress.com

I at my Mobilebytes Post updated the link to the Android Google IO 2009 slides, once they have them up today that is where you can find links to each individual presentation and slide group.

Once gain, I have moved my blogging to Mobilebytes, change your bookmarks to:

 http://mobilebytes.wordpress.com

I started covering the AndCooper Build Tool coding internals at MobileBytes blog. In the first part I cover how I detect the SDK version and adjust the SDK tools location and add-on apis. If you have not adjusted your feed reader, everything now is blogged at MobileBytes and the feed is:

http://mobilebytes.wordpress.com/feed/

AndCooper 0.1 release and release notes posted late Today at MobileBytes blog.

Late today, you wil find coverage of the first release of AndCooper 0.1, the Android Applications Ant based Build Tool, at the MobileBytes blog. Details of where to download, supported features in 0.1 and plans for 0.2 will be disclosed.

As we await the uploading of the Google 2009 IO Android Presentations to Youtube I expect to upload some Android Code Examples and Analysis discussions to my MobileBytes blog to show the challenges of Androdi code optimization for application development.

I have moved all my blogging to MobileBytes blog, but will remind everyone to change their links and bookmarks for another week or two.

For those still using Roller(Jrolller). Rick Ross and the Dzone crew is hard at work hardening the wordpress blogging solution for blogging use on the dzone networks.  I am sure registrations to wordpress powered blogging from Dzone will occur shortly.

 i started a new more focused Mobile blog where Android is covered, called MobileBytes. The RSS feed is:

http://mobilebytes.wordpress.com/feed/

The Roller blog system really has not kept up with changes and improvements in blogging. Hopefully, my switch to the wordpress blogging platform will enocurage a lot more in-depth coverage of mobile technology and Android. Yes, there is already soem Android posts this morning.

One of the challenges of developing the AndCooper build tool of Android application development is the IDE and ANT interactions. For example, lets asy you have a typical build system based on ANT. How many of those ant taskdef  libraries do you have to put in your IDE ant path setting?

If you guess all of them you would be somewhat wrong and would have a build that at would not work as expected. In the AndCooper case its 12 including the ant taskdef libraries from the Android SDK. The whole idea is once AndCooper is installed you can point your IDE java builder setting to use the AndCooper set of build scripts as the java builder for that project so as you develop code the IDE will use AndCooper to build the project in increments and generate soem code analysis data reports to assist in the development process.

Thus, its vital that I get which ant taskdef libraries to put on the IDE ant path correct so the user of AndCooper can jump right into developing code with AndCooper. The lucky part is that each IDE seems to accept that you must load the same subset of taskdef libraries on the IDE ant classpath.