Know I’m typing on my brand new ZT-280  I received today.
I can’t say I’m impressed, the tablet is about half the size of the Superpad and is also smaller than the wm8650. The capacitive screen is a bit hectic or oversensitive. It has no haptic feedback, but I can live with that.

It’s exterior is superb compared to the previous mentions, and is bordering on acceptable. I don’t like the reddish metal finish on the sides too much, but it’s not all that bad. I can’t understand the mini USB connectors really. After all micro sockets are taking over, don’t they? Also I don’t get why a separate power input is needed, when it could use the 5v straight from the port. As far as I’m concerned it should have two micro USB and scrap the rest.

The tablet came with the connector cables for both pc to tablet and external device to tablet connection, a power adapter and the usual EU socket adapter. It has a little deep socket for the micro sd card, but it’s reasonable, as I don’t want to change it too frequently anyway.

And so I used the pad for a day or so with the following issues.

The touch is a bit laggy, there are times, when the strength registers a “click ” at a previous position. I seems like a driver issue and I don’t think it would be dealt with anytime soon.

The firmware is definitely based on cyanogen 7 so it promise a relatively long usability period. Unfortunately it doesn’t use clockwork boot loader, and has a legacy package format too. It still begs the question weather it can be used to do incremental upgrades, or only full updates are possible. The supplier released new firmware packs about monthly, and I can only hope they keep it up for the release of the icecream sandwich of cyanogen.

Now again, I’m kind of late on publishing, so here’s an update. A new release is available from the manufacturer ‘s site as of November 4th. I only did a partial update, so a new kernel is running on the pad. This seems to have resolved the touch issues. I’ve also recalibrated the battery, so now it provides a little bit more reliable info. This doesn’t solve the standard charge  issue of the pad. That only affects the charge level display so it only shows the range between 97% (uncharged) to 100% fully charged.  I don’t mind, as I leave office charge overnight anyway.

It does have a five point touch screen which looks nice in Fruit ninja, that I used to test 3d, where I could use 5 blades to slice through tons of fruit in seconds.

I really miss the light sensor. It boggles my mind trying to understand what made the designers think to omit such a cheap, but vital component from this otherwise well built tablet? It also shows that Android heavily relies on its existence. There is only a very limited possibility of customizing it properly, even with the notorious Cyanogen. One cannot set the actual levels to use in the power applet or the status bar, you can only select some predefined level combinations, all of which contain an auto option, despite the missing sensor.

Rooting the device is pretty simple. Connect with the provided cable, remount system with adb, copy su and superuser.apk cynosure the su and done. You can than use all rooted applications. This is required if you want to clean up the crappy preinstalled applications.

Chainfire works out of the box but I’m not a gamer, so I have no idea what’s the point. I did some fooling Around in Fruit Ninja and Angry Birds but I can’t tell the difference.

I wrote this article on the subway, using my ZTE Blade as a Wi-Fi hotspot to publish it.

The task is to write a method that takes a string as a parameter and returns the acronym of the string in uppercase made up of the first letters of the words in the string. The acronym must ignore the words “the”, “of” and “and”.

The usual solutions are either to sequentially step through the string (Yuck!) or split it up or use a StringTokenizer class. The people usually overlook the fact, that the input strings can be padded with whitespace, or contain multiple spaces, and they usually ignore, that the keywords that are to be omitted might be found on the begining of a valid word. Thus my test ” United   States of Andorra” string breaks most of the methods.  The ones who have time to write the answer down, usually forget to return the value from the method, or to change it to uppercase and sometimes even ignore that it should be a method to start with! This is my favourite question, as it can really show how the applicant can handle stressful situations.

I was tired after several interviews one day and tried to come up with the  shortest possible solution. Naturally it contains regular expressions.

My solution looked something like this (OK I just reproduced it for the sake of the article, using nano and javac, so it might have overlooked flaws in it):

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15

public class Acronym { 
 
private static String toAcronym(String str) {
        return str.toUpperCase().
                        replaceAll("(THE|OF|AND)(\\W+|$)","").
                        replaceAll("(\\w)\\w*\\W*","$1");
}
 
public static void main (String args[]) {
                if(args.length>0) {
                        System.out.println(toAcronym(args[0]));
        }
}
 
}

Once upon a time, in a kingdom not far from here, a king summoned two of his advisors for a test. He showed them both a shiny metal box with two slots in the top, a control knob, and a lever. “What do you think this is?”

One advisor, an engineer, answered first. “It is a toaster,” he said. The king asked, “How would you design an embedded computer for it?” The engineer replied, “Using a four-bit microcontroller, I would write a simple program that reads the darkness knob and quantizes its position to one of 16 shades of darkness, from snow white to coal black. The program would use that darkness level as the index to a 16-element table of initial timer values. Then it would turn on the heating elements and start the timer with the initial value selected from the table. At the end of the time delay, it would turn off the heat and pop up the toast. Come back next week, and I’ll show you a working prototype.”

The second advisor, a Java developer, highly skilled in object oriented design, immediately recognized the danger of such short-sighted thinking. He said, “Toasters don’t just turn bread into toast, they are also used to warm frozen waffles. What you see before you is really a breakfast food cooker. As the subjects of your kingdom become more sophisticated, they will demand more capabilities. They will need a breakfast food cooker that can also cook sausage, fry bacon, and make scrambled eggs. A toaster that only makes toast will soon be obsolete. If we don’t look to the future, we will have to completely redesign the toaster in just a few years.”

“With this in mind, we can formulate a more intelligent solution to the problem. First, create a class of breakfast foods. Specialize this class into subclasses: grains, pork, and poultry. The specialization process should be repeated with grains divided into toast, muffins, pancakes, and waffles; pork divided into sausage, links, and bacon; and poultry divided into scrambled eggs, hard-boiled eggs, poached eggs, fried eggs, and various omelet classes.”

“The ham and cheese omelet class is worth special attention because it must inherit characteristics from the pork, dairy, and poultry classes. Thus, we see that the problem cannot be properly solved without multiple inheritance. At run time, the program must create the proper object and send a message to the object that says, “Cook yourself.” The semantics of this message depend, of course, on the kind of object, so they have a different meaning to a piece of toast than to scrambled eggs.”

“Reviewing the process so far, we see that the analysis phase has revealed that the primary requirement is to cook any kind of breakfast food. In the design phase, we have discovered some derived requirements. Specifically, we need an object-oriented language with multiple inheritance. Of course, users don’t want the eggs to get cold while the bacon is frying, so concurrent processing is required, too.”

“We must not forget the user interface. The lever that lowers the food lacks versatility, and the darkness knob is confusing. Users won’t buy the product unless it has a user-friendly, graphical interface. When the breakfast cooker is plugged in, users should see a cowboy boot on the screen. Users click on it, and the message “Booting Application Breakfast v1.2” appears on the screen. (Breakfast v1.2 should be out by the time the product gets to the market.) Users can pull down a menu and click on the foods they want to cook.”

“Having made the wise decision of specifying the software first in the design phase, all that remains is to pick an adequate hardware platform for the implementation phase. An Intel Pentium 1.86GHz with 1.2GB of memory, a 220GB hard disk, and a TFT monitor should be sufficient. Selecting a multitasking, object oriented language that supports multiple inheritance and has a built-in GUI, means writing the program will be a snap. (Imagine the difficulty we would have had if we had foolishly allowed a hardware-first design strategy to lock us into a four-bit microcontroller!).”

The king had the computer scientist thrown in the moat, and they all lived happily ever after.

NB. The story mentions a Java developer and thus provides a valuable insight: Java coders are lazy and provide specs they don’t have to develop when possible. This is why the multiple inheritance was suggested, instead of AOP.
Actually the story is way older than Java, and in those times developers actually knew languages and didn’t try to design everything so it can be solved in their language of choice.

First I suspected it was because I signed the application using SUN JDK 1.6, and it might have some compatibility issues (as if) then I suspected it was the IBM JDK 1.5′s ikeytool I used to create the key (NB. I’m lazy to learn the keytool paramers, so I prefer to use a GUI for creating keys)

It turned out I was presuming the keys use UTF internally, like most Java applications should, so when entering the locality I used “Vác” with accented characters. Neither ikeytool, neither keytool warned me about this. Once creating a new key without the accent the application started working straight away.

Since “Budapest” doesn’t have any special characters, I never noticed this, but I think it deserves to be mentioned, so others won’t run into this problem.

For the original concept see:Availabot

For the cuter Linux version visit Push puppet toy

I can imagine my desk full of these puppets each representing a friend I usually talk to, these puppets would dance up and down all day depending on who’s leaving for lunch.

Also it would be great to have this extended to have an intermediary stage, ie. when the button is half pushed these puppets usually start letting their head down. So when the contact is not offline, but only away they could show how said they are to be away from their computer, and when they are offline they are completely splattered.

Winstone is the name of a rather large Jamaican man a friend of mine met one night, while he was out clubbing in the Roppongi area of Tokyo. He (my friend) was a little liquored up at the time, and when Winstone suggested they head to “this really cool club” he knew, he didn’t think anything was wrong. It wasn’t until Winstone led him down a dark stairwell and dropped his trousers that my friend clued in and ran like hell.

It was too good a story to let die, so I named this project Winstone so that said friend will continue to be reminded of it.

Now who claims java devs should get a life?