I've sold my soul to the devil!

Well not quite. But some Android fanboys might think I have, or even worse. Cut a long-ish story short, I caught my Advent Vega Android tablet with my foot this morning and cracked the screen. One of the reasons I bought it was so that I would have internet access while on trips away. I have a trip to Canada coming up and so a replacement is needed... and I decided on an iPad. Not an iPad2. The only thing that has appealed to me about the iPad2 is the nice £100 price drop it meant for the original iPad. I rarely buy like for like with gadgets when they expire and I'm not a fanboy. I just try to buy the best product in my price range. I feel the iPad is now that product.

So does it mean I'll be developing apps for IOS? Maybe. Oh and for those interested in how my Vega now looks:

It along with it's official Vega case will be listed here shortly: http://www.amibay.com

Oh Google Maps! Why don't you love me anymore?!

To be honest I know full well why Google Maps has stopped loving me. Whilst trying to find the travelling distance between one fixed postcode and 1500 others (programatically of course!), Google Maps blocked me after the 338th request within a 6 minute period! Thankfully today the block has reset. Obviously I need to add a delay between requests. Google's FAQ says 2,500 requests per day can be made but if you make too many requests in a certain period they block you. How many in what period is not mentioned! Grrrrr!

DHCP Checker v2.3 released

As promised here is an updated version of my DHCP Checker script, complete with more comments and a tad tidier code!

DHCP Checker v2.3

Not Android related

I was starting to forget that my blog wasn't just about Android development! Anyway after a request out of the blue to help a stranger (hi Matt!) use my DHCP Alert script I've decided to spend a bit of time modifying it. For those who don't know the script checks a Windows DHCP server log and when it finds a new lease has been issued it checks to see if the computer exists in Active Directory... and if it doesn't it sends an email to the specified email account.

I plan on making a few changes that Matt has requested like checking renewals and the option of turning off Active Directory checking. The script also badly needs some comments as I found whilst trying to help Matt with implementing the script. More on that to follow soon...

Sorry...

Sorry to anyone who is awaiting my next blog post. Sorry that this one won't be what you were waiting for! I'll be honest, my PlayStation 3 has taken over my spare time... to be more specific Gran Turismo 5! Also I'm in the process of selling and buying houses, which as anyone who has been through that process will know it is quite a time consumer. I would try to commit more time to the blog, but I'm not making any promises... just keep an eye out... see what happens!

You are going to need Java more than it needs you

Android applications are written in Java. You will need to know Java. I knew this before I started but knew very little Java. So whilst learning to develop Android applications I knew really I would be learning Java. I had hoped that the various Android development books would also be a nice introduction to Java along the way... but no.

I have been doing my Java learning in the background, using a book (see left) and a great set of video tutorials. The videos are even more suited to the aspiring Android developer because whilst learning Java you are also learning how to get the best out the Eclipse IDE which most Android development books/tutorials recommend. The only downside of the videos is that they are in SWF format. I spent a little bit of time converting them into something I could watch on my Advent Vega tablet.

The book (Beginning Programming with Java) is about to get a revision so it might be worth while you holding out for it. To be honest the video tutorials are in my opinion a better introduction to Java. Plus they are FREE!

Two months? Really!?

Blimey, has it really been two months since my last blog post? My apologies. A few things have gotten in the way of Android development. A new toy (Advent Vega Android 2.2 based Tablet), Christmas, New Year, Holiday planning, HTC Desire ROM testing... all excuses, I know!

But Santa did bring me:

So I plan on starting that in the next few days so watch out for a quick review of the first few chapters. A quick flick through has shown that early chapters talk more about the bits I didn't understand from the previous book. I hope also to be able to develop apps for both phone and tablet forms, coupled with that my phone now runs Gingerbread (Android 2.3) I am prepared for most areas of Android development that the current platform presents.

Phonegapping

After a problem where I could not scroll the application up and down with the touch screen, I soon saw the quality of the Phonegap CSS in all it's glory on my phone:

Phonegap example app running on my HTC Desire

The scrolling issue needed a slight code adjustment:

function init(){

document.addEventListener("touchmove", false);

document.addEventListener("deviceready", deviceInfo, true);

}

The first line of the function did read: document.addEventListener("touchmove", preventBehavior, false);

I will now continue to play with Phonegap but I'm starting to see it's limitations. I can see it not being very responsive and obviously games are out of the question. When I say games I mean anything with any movement, puzzle and strategy etc should be ok. In fact it maybe worth looking at some existing Javascript stuff and maybe porting it to Phonegap.

Is phonegap cheating?

Chapter 3 of the book has gone waaaaayyy over my head. It seems to have gone up a few notches very quickly. There are no comparisons to existing languages to ease you in. So as a result I've put the book down for a bit and decided to look at phonegap. It still uses Eclipse for the IDE but everything else is HTML, Javascript and CSS.

I've built the sample in no time and I am already changing it to get an idea of how it will look. Firstly the sample CSS makes everything look like a native app, very slick. But you would think it would not have the capability of a native app... you would be wrong. You can make the phone vibrate, beep, take readings from the accelerometer, geolocation, bring up the dialler etc... Pretty much everything the average developer would want. Also it is multi platform compatible so with a bit of work it can run on iPhone, Blackberry, Symbian and Palm as well as Android. I'm not too fussed by that but you never know, a killer app multiplied by 5 outlets is more than just one. Next I'm going to see what the sample app looks like on my HTC Desire.

Slow going

Just a quick post to say I'm still working my way through the book. Had a read of chapter 3 which talks about dialogues, intents and activities. I think it will take a couple of read-throughs to get this cemented in my brain. Plus it might be worth while me doing some simple Java tutorials in the meantime as the book has already used some examples with code in, of which I have zero clue about!

Another day another tutorial recommendation

I think I'm going to have to keep a list of tutorials that have been suggested to me somewhere! Thanks to helium from a forum I visit who has suggested:

http://www.smashingmagazine.com/2010/10/25/get-started-developing-for-android-with-eclipse/

Search Amazon.com for android

Android Market reaches 100,000 apps but does that really matter?

As has been reported by plenty of sites already, the Android Market has reached 100,000 apps. But should we care? The Apple App Store is at 300,000 but to be honest most of the apps I see when searching for with various key words are total guff. The same themes over and over again but tweaked slightly. An example is the World Cup themes for every team but each one a different app. 32 apps that could have been just one.

For me it is all about quality over quantity. That is why when I get to the point of releasing my potential apps I will do my best to make sure they are worthwhile releasing.

Weekend of no development(s)

This weekend saw a great F1 race and pretty much no development work. I read chapter two of the book which details information about debugging tools and using other tools to help with testing, such as send text messages to the virtual environment, make calls, browse the net etc. All very handy, saves building the app on my phone and wasting texts and minutes. Save wasting them on the final builds eh?!

Should I abandon Java and use phonegap... or both?!

Thanks to a recommendation via twitter from @Substitute79 (thanks very much!), I have had a quick look at http://www.phonegap.com/

Looks like at first glance that you can still use Eclipse but use HTML/Javascript/CSS etc... to produce applications... interesting... I think I will be spending some time with this along with the Java route. My findings, as ever, will follow!

Chapter 1... Hello World... Unsurprisingly

So into chapter 1 and the inevitable 'Hello World' app is dealt with. Now I've already tackled this in an on-line tutorial in the past so I knew where this was going. However this is where spending money shows it's worth. The book explains more of the finer details, why you are doing things, what each bit does along with some nice gentle exercises like adding more strings and changing the order they appear. The little end-of-chapter quiz is a little pointless for chapter 1 but I expect it will become a handy recall exercise in later chapters.

I still plan on looking at the on-line tutorials for a comparison with the book but also you never know what one misses the other may pick up on. Unfortunately the inevitable diversion in routes into Android development that both tutorials take are bound to differ very soon!