Posts tagged with "Java Development"
Sunday, January 6, 2013 9:44:34 AM
First: yes it is possible to use Java 7 to develop Android. However there are two problems.
First Java 6 used a rather strange directory layout. Strange for the average UNIX™ user. Not so strange for unencumbered user as the names used are more readable and understandable.
Since a lot of tools got used to the Java 6 names we need two compatibility links:
sudo ln -s jre/lib Classes
sudo ln -s rt.jar classes.jar
Java 7 also comes with an new jar signer which by default uses a new algorithm. Android devices can't use that algorithm so you have to force the signer to use the old algorithm:
You don't use Maven? Your loose, it is the best way to develop Android. And it is just not my opinion: ViewpageIndicator, AndroidAnnotations, Robotium — All the top Android developers use Maven.
Sunday, May 13, 2012 2:23:37 PM
Wow Issue 3692 for is just about one of the most horrid bugs I have seen in desktop computing. See comment 26 for a breakdown on how it happened.
But then I would not consider it a programming bug. It is more a design bug: The very idea of scanning the entire SD card for pictures to add them to a central database and display them in the gallery is wrong.
Don't get me wrong: I properly done and carefully thought out this feature could be helpfully for the less technically minded users. But this takes time. A and a lot of thinking. As it is it is a bloody bodge job.
- Not all pictures are meant to be displayed by the gallery app. (For example cover art for eBooks and music albums or browser caches)
- It does not scale well. Modern sd cards can now exceed 64GB. Can you even imagine how long it takes to scan one of those once they are full?
- On some devices sd-cards can be removed quite easily.
- On some devices there is more then one sd-cards slot.
- It is difficult to keep the database is sync with the content. For example: Even after adding «.nomedia» to your eBook collection folder the cover art stays in the gallery. A reboot might be needed. And sometimes event that does not help.
- You can get all sorts of horrid bugs. For example when the database sync physically deletes the files from the exclude list.
Just in case you wonder: No I did not loose any files due to this bug (at least I never noticed). But other did. Especially comment 72 is disturbing.
Tuesday, February 28, 2012 8:12:02 PM
Call it the Krischik
law:Any successful lightweight solution will grow over time until it becomes just as heavy weight as the solution it was designed to replace or compete with — only lacking the original solutions elegance.
Ok, the last part only applies when the original solution had some elegance.
Examples would be
SPING — now does everything EJB does.
C — The ISO standard has just as many pages as the one from Ada.
LDAP — was it ever less complex then DAP?
Tuesday, August 10, 2010 9:44:23 AM
I just found out that log messages from java.util.logging are passed on to android.util.Log. Now that is pretty helpful for multi-platform development. By default only messages up and including INFO are copied across but you can adjust that.
Just in case you don't know how: 1st you need to change the Andoid log level using setprop on the device:
adb -e shell setprop log.tag.Main DEBUG
Then you also need to change the java logging level inside you program:
Last not least you need to remember that Android only allows 23 characters as logger name. Longer names will be shortened. Usually by removing the package name.
For me this is also one more reason not to use Log4J.
Friday, June 4, 2010 8:55:16 AM
How java.rmi.RemoteException cripples the whole Jave RMI system.