DroidDraw turns out to be a dud… imagine that. Actually it was ‘okay’, at least it gives you a starting point. But to fine tune the UI, you still need to hand code the XML file. Sigh. Reminds me of the DOS days, before Windows dev and GUI IDE’s.
Too many layout schemes to choose from, hard to write an app if you don’t know exactly what will work. Went with the relative layout to start, sounded flexible. Thinking eventually I’d have to code two views for each of the screens, vertical and horizontal views – but, why bother? It’s tough enough to fit all the widgets onto a vertical screen, it would be impossible to fit them all horizontally. The device naturally fits in your hand in the vertical position anyway, so I changed to table layout before getting into deep in the mud.
Wow, turns DroidDraw is perfect for setting widgets on a table layout. Good thing I abandoned the ‘relative layout’ early on. But, after spending 30 minutes drawing widgets, try to compile, it keeps telling me ‘Error in an XML file: aborting build’. Of course it doesn’t give any inkling of what the error is. Sigh – 30 minutes of staring at the screen I realized that DroidDraw had put a bunch of listeners into the XML of each widget. It was probably my fault, but it asked for a listener name, I assumed it would name it correctly.
Discovered ListView means something totally different in Android. A traditional drop down list is called a spinner in Android. Spinner? WTF? To confuse the newbies I guess.
Android has something the iPhone/iTouch hasn’t had since version 1.1, automatic numeric keypad popup when you touch a number field. iPhone OS 1.1 had it, then Apple dropped the ball on subsequent versions. Corporate dicks, long live open source.
Here it is, 3 days of work, a pretty picture. Anyone familiar with other version of the software will instantly recognize the interface. Of course there is no code behind. Rapping up early with some sense of accomplishment, too nice of a day to waste indoors. Tomorrow is another day.
