Last Updated: June 2nd, 2012
You've probably already read headlines in the last hour or two proclaiming that Google has "lost" its copyright case against Oracle, and in the strictest sense of the word, it has. Google lost on a number of counts, including the most important one, question one in the jury instructions. It also lost on a count involving nine lines of code that have long-since been removed from Android.
The first question, though, asked the jurors whether Google's use of 37 Java API packages, taken as a group, constituted an infringement of Oracle's copyrighted works.
Last Updated: March 31st, 2012
It's no secret that we work with a number of publishers to give away a steady stream of books to aid aspiring developers - after all, if we help developers, the entire Android ecosystem as a whole is enriched. But for some people, simply reading a book isn't the ideal way to learn. It's for these people that informIT has released Android App Development Fundamentals LiveLessons - a series of downloadable videos that are designed to teach Java developers how to build apps for Android.
Last Updated: April 16th, 2010
This post and all its comments were migrated from Artem's personal blog beerpla.net
when Android Police launched. If you would like to visit the original post there, please click here
In this article I will describe the problem I've had with Eclipse's handling of XML file formatting as well as the best way to fix it.
I use Eclipse to do my Android development for a few reasons:
- it's the only IDE fully supported by the Android dev team
- it has a visual Layout/Resources builder that transforms XML files into corresponding visual representations
- it's free and open source
- I've been using Eclipse for many years and am very familiar with it
In order to use the visual features in Eclipse when developing for Android, you need to install the ADT plugin
provided by Google
However, one thing about Eclipse Android development has bothered me for a while - and that is XML formatting by the visual tools.