Update, Update, Update... Failure... Update

I did another update of all three of my applications on Friday.  The updates to the Launch Bar(s) was pretty minor, but important.  I was looking for a better way to save the intent (how to call the application).  I actually found a good post on stack overflow on how to do this by saving the URI information.  So I put that into both versions and things seem to working well.

I made a big change to the Desk Clock Plus application two (?) weeks ago now.  I was really happy with what I was able to do with integrating my desk clock program and Picasa.  I'm using Picasa in 3 different ways:

1. Use the featured images (top 20) as part of the backgrounds.
2. I'm using my Picasa account to host a bunch of themes.
3. You can display Images from Picasa for your background and / or slide show.

I was very proud of what I was able to do and was planning  a big post explaining all of it and I just never sat down and wrote it (real work and home have been very busy lately).

I kept tinkering with the code and putting in fixes for for the force close reports that were coming in.  I made a change that I'm hoping should fix some of the random force closes when the Desk Clock is not the main application, however, this caused another issue when the application is closed (removed from the dock or the back button is pressed).  I really didn't have time to do anything with it until today, but I do want to thank all 36 people who sent in the Force Close report!  I know I've said it in the past, but I need to stop pushing updates on Friday, it seems that when I do there's some kind of bug that goes out too.

I've been thinking of what's next...  Given all that I've learned in the past nine months or so, I the launch bar could probably be re-written better. For Desk Clock Plus, I'll more than likely, I'll probably do one more enhancement for skinning,  probably draw up a large screen layout and prompt the user launch the location and security screen when a location can't be detected.

Update Bomb

I've been rather busy with all three of my projects lately... I was finally able to get everything done and taken care of and I just got done pushing updates to all of them.  But first a little rant...

I personally am very happy with my version of the Desk Clock.  It works very well for me on my original Droid.  It works well, on the Droid 2 and on the HTC incredible (according to my cousin and sister).  I've also have a co-worker using it on his Droid X.  However there are some people who are still having issues with it force closing on start.  That sucks.  I want my software to work for everyone.  The problem is the phones that they say that it doesn't work for... I don't have access to.  Beyond that, I can't say if this is some specific to the phone or the user or a combo of the two.  Additionally, If you going to bitch about it not working, HELP ME, HELP YOU!.  Fill out the Force Close Report!!!  I'll get a stack trace that should help me figure out what the problem is.  I guarantee that it will take less time than going back to the market and complaining there...

I feel a little better... sorry about that.

Desk Clock Pro: I changed how I get the "default background" and I suspect that was the cause of some of the problems or at least I can guess cause nobody fills out the Force Close Report (sorry about that)... The added bonus is that now the Live Wall papers will show through which is pretty cool.  It turns out that I was doing too much work and in most cases if your doing too much work then your doing it wrong.

I still don't know what the problem is with some people and the music button.  It tries to find the default first and then if it can't it should display a list to choose from.  I'm planning on putting an option in the settings for the user to choose which one they want to use.  I'm hoping that speeds things up a little and reduces some of the problems (or at least helps me find the source of the problem.

Launch Bar Pro:  I've learned a lot since I started programming for the Android OS six months ago.  Some of that has been slowly working it's way into the Launch Bar.  I was able to reduce the amount of work it was doing and therefore made the loading and scrolling features a lot faster.

Launch Bar:  The big thing that I'm excited about is that you can now unlock the Pro version from the basic version buy purchasing it though PayPal for $1 USD.  What's nice is that if you are running both versions, you can unlock the free version and basically be running two different Pro widgets!

I don't think I'm going to get rich off of any of my applications, but any extra scratch helps at the end of the month!

Looking forward, I 'm probably going to change out the weather icons for the Clock in the near future.  I talked about a menu option of the musing and I think I'm going to get picasa support for the slide show / backgrounds.

Until then...

Scolling widget... sort of

The paid version of the Launch Bar was just updated. The new feature is that the widget "scrolls". Well, fake scrolls... I run the Launcher Pro home replacement app and it supports scrolling widgets however, it looks like the scroll can only be vertical. The launch bar is of course horizontal and as far as I know you can't make a horizontal scrolling widget. The reasoning is pretty simple, the left / right swipe motion is reserved by the system to change home screens. So my original idea of using the gallery and a nice smooth horizontally scrolling widget went out the window. Although, this was probably for the best as the design change allowed me to add more than 7 icons and not require a special home replacement (although I highly recommend Launcher Pro).

So, here's how it works. There is now a 'Mode' button that will give you 4 choices:

• Classic - This is the Launch Bar that we've come to know and love. Seven customizable buttons
• Arrows - When this is selected, you see two gray arrows that will allow you to scroll one icon left or right in the list. It's a continuous loop, so when you get to your last icon, the list will start over. I cut the number of icons down to 6 when the phone is in portrait mode. This was for sizing / usability reasons. You can also double tap the arrow to jump seven icons at a time.*
• Scroll Bar - When selected, you will see an orange bar below your icons. You can touch that bar at any point to jump to that part of the list. Sadly, you can't slide your finger over the bar to scroll (you can't have a true slide bar as the left / right slide is reserved for the changing of screens).
• Mixed - When the phone is in portrait mode it will use the Scroll Bar mode. When the phone is landscape it will use Arrow mode. This came about just because of how widgets are sized differently in portrait vs landscape. It gives you the best of both worlds in my opinion.

I'm sure that there will be other minor changes here and there as oddities are noticed, but I think that's the majority of the major enhancements for now. Although, if a reasonable enhancement request comes in I'll be more than happy to put it in.

Finally....

It's been a while since I was able to update both of the applications (a month or more for Pro and 3+ weeks for basic). I was busy trying to re-organize the code so that it would be easier to update both applications. In some cases I would have to make the same change in four places for some of the common code... bad bad programmer! I consolidated a bunch of stuff and probably need to consolidate some more with the new direct dial feature. Plus the birth of my second child put a damper on things... ;-)

New for the custom button on the basic version and all of the buttons on the pro, when you long press the item in the configuration screen you will be prompted for a "Button Type", either Application or Direct Dial. The application will operate as normal. The direct dial will list all of the phone numbers in your contacts and the picture associated to that number. Long pressing one of the phone numbers will set that button, allowing you to call your favorite person(s) with just one touch.

Next up, scrollable widget!

Update

Been a while since I've published anything... I've been busy cleaning and consolidating code for both the basic and pro versions. This should hopefully make both of them easier to manage. Coming from a .NET world, the Eclipse IDE has a bit of oddities that takes a bit of getting used to. Plus switching from VB to Java and back to VB is alot like going from English to German and back.

I only updated the basic version and this was really intended for people who have upgraded to 2.2 already. The long press on the first button (Phone by default) will give you the choice of the Phone or a picture gallery application. The long press on the fourth button (Browser by default) will give you your choice of browser(s), Google Talk, AIM, Twitter or Facebook. If you don't any of these applications installed then you obviously can't choose them...

Froyo...

Being a Moto Droid owner, I was happy to see the news that Froyo was finally available. I planned on doing the manual update at lunch today. However, I was greeted by a message on my phone after returning from a meeting saying that I had an update to install. In my small circle of Droid owners here at work, I am the only one to receive the OTA update. This also includes my wife who is the primary account holder. My guess is that since I'm a android developer I go to the front of the line?

One of the things that I noticed was that the camera icon on my Launch Bar went away and was replaced by a second Google Maps Icon. I'm sure that they changed the class name or something stupid like what they did with the HTC Sense and Blur. However after running the configuration screen I was greeted with a force close... I still haven't heard the end of it. I found that not all of the code that went into the last update / fix for the Base version made it into the Pro version. So, a little code merge and testing later and all seems to be working again. I really need to learn more about the Eclipse IDE. I shouldn't need to maintain two sets of code that are the same in both applications.

First thoughts on Froyo...

• Updated Multimedia dock is nice
• The gallery and camera apps seem to have some nice enhancements
• The speed increase is very noticeable.
• No wireless tethering? I'm pissed at that and more pissed at the BS reason of "The Droid doesn't have the necessary hardware."
  
• Although, there is a USB tether which just means I need put a micro USB cable in the laptop bag for emergencies. (Although rumor has it you can only get to Verizon's web site...)

So far that's it for now...

HTC and Blur update

After I pushed out the update last week, I noted alot of non-positive reviews about the base version of Launch Bar and how it's really not working for HTC Devices. I then got a text from a co-worker from his brand new Droid X. My app didn't work on his phone at all. Although, it did give me an excuse to play with his phone a bit...

After running a debug app that does the same bit of logic as the Launch Bar, I discovered what the problem was. In the case of the phone dialer, I was looking for a package(application) called com.android.phone. It looks like the motoblur UI tweaks the phone dialer slightly and the name is com.motorola.blur.phone. All of the other "stock" applications all had the same kinds of package name changes. I'm making the assumption that the HTC Sense UI did the same thing for all their apps and hence why it wasn't working for that either.

There's about 3 different rants that I could go on:

1. about how the stock application names shouldn't change and Motorola and HTC should change them (akin to Dell changing the Windows to Dell's Windows)
   
2. the awesomeness that the phone OS is open source and they COULD go and make those changes (akin to Dell changing Windows Vista so that it works)
   
3. the stupid programmer that made the assumption first that he could find the application by label name (which lead to the localization problem) and then the "fix" of trying to find a specific package which doesn't exist on non vanilla installs of Android.

In my defense for number 3, up until my co-worker got his Droid X. Everyone I knew with an Android based phone as the standard Moto Droid and the only development environment that I had to test against was emulator provided by Google. I did try to build the source code from HTC, but I got to a certain point and then stopped (I'll get back to it at some point). It (OK just me) is very frustrating trying to develop for a moving target and to me it seems very difficult to jump though the fiery hoops to build the HTC source and I'm not even sure that's going to work in the emulator.

The update to the base version makes the GUI for both version the same. However, base version when you long press it will present you with a pick list of applications that qualify for that button (Phone, SMS, Contacts, Browser, Maps, Camera). The custom button will show you all the applications installed on the phone. This is actually pretty cool in my opinion as you are no longer stuck using the stock items (I know alot of people use HandSent and Dolphin as their main SMS and Browsers).

However, it seems that on the Droid X the contacts button isn't working... Oh well, just another programming opportunity.

Houston we have a problem...

I knew that I should have waited until over the weekend to push the update. I'm hoping that 99% of the Pro users didn't have the same problem as a user who emailed me on Saturday. After the update the widget disappeared. After thinking about it and a quick email exchange, I realized that the data conversion process was only happening on the configuration side of things and not on the widget side. What happened in his case (on a HTC Incredible) was that it couldn't find the default applications and returned a bunch of blanks. I believe that he then uninstalled the widget and tried to reinstall from the Market.

However, with the new configuration screen, it couldn't find the default apps that I specify. I believe that caused the force quit error. This would explain why the couple of new users canceled their order shortly after purchase.

So here's what it does now:
When the configuration screen loads and it can't find the application I'm looking for (Thank you very much non-vanilla androids... I'm looking at you HTC) it will just get the first application it can find. I'm assuming that everyone is going to change it regardless, but if your configuration window is all Alarm Clocks then you know why.

If you don't go into the configuration screen or the application can't be found you'll get a button with this guy:


Basically, it's saying that I can't find the app for this button. I'm hoping people who see this will just go back to the configuration screen and save their configuration again.

On a side note, this has given me some insight on why the Basic widget has been having issues with the HTC phones. I know what I want to do to fix it, I just need to learn HOW to do it.

The need for speed

During the little bit of time I had for widget development, I saw what I was doing wrong and was able to whip up the updates for both versions of the widget.

So, what's new? The application loads a lot faster. The exception is the first time you load it as there's some internal data conversions that need to be done. The way you choose your buttons has changed and for the pro version it is now a long press on the list the application list. I will update the basic version's configuration screen to mimic what the pro version is doing. I also updated the icon re-sizing on the phone orientation change. The icon re-size is now instantaneous.

What was the big change? No more internal looping looking for stuff and setting icon size via the layouts and not doing it via code. I realized that I was working too hard to do a lot of the stuff I was doing, so I found a much better way.

Coming Attractions

Just a quick update...

I've been working on a semi radical change to the Launch Bar for a couple weeks now. I have the basic version completed and am working on a similar update for the Pro version. However, I'm hitting a little bit of a learning curve when it comes to some more advanced GUI elements. I'm hoping to be able to publish the updates early next week.

This update will include:

• A new GUI for the configuration screens
  
• Removed the icon size slider (for now)
  
• A major speed increase when launching the configuration screen
• A major speed increase when changing the orientation of the device

Also, I've seen a couple of comments regarding the basic Launch Bar not working or missing icons (specifically messaging) on certain phones. Typically these have been HTC devices with the Hero, Desire and EVO being the ones I know being problematic. I have good idea of what the problem is, but with out a phone to test on I can't verify it or write a fix. I've been trying to build the HTC source code so I can use it in the emulator, but haven't had time to really work on that. If you are running the basic version and have seen the missing button issue please send me an email. I have a debug program that I'll send you that should help me out. I can be reached at rmueser (at) gmail (dot) com

Hello World!

I've decided to put a blog together to keep a log of changes / enhancements for my Launch Bar widgets that I've been working on for the past month or so. Hopefully, I'll also be able to get some information and feed back people who have downloaded the free version or bought the pro version.

Here's what's happened so far:

• v1.0 -- Initially released June 13 / 14
• v1.1 -- Increased the size of the buttons. For some reason the icon size was different on two different Motorola Droids
• v1.2 -- Added Icon size slider to the configuration window
• v1.3 -- Cleaned up the GUI and other misc cosmetic enhancements
• v1.4 -- Re-sized the Icons when the phone is in landscape mode. Small note about this, there could be a 5 to 10 second lag this is due to how I'm checking the orientation of the phone. I'm sure there is a better way to do this I just haven't looked into it yet.
• v1.5 -- Internal change of how how I'm was doing things. I realized after someone posted a comment in German that the free app didn't work. I believe this was due to how I was looking up the applications.
  

Just some quick stats according to Google:

• Launch Bar: 536 downloads
• Launch Bar Pro: 66 downloads

It's a bit over whelming to me that so many people have downloaded my apps with out any kind of publicity (although I'm pretty sure it showed up as a "just in" application after the 1.4 update).

For everyone that's downloaded and tried out my application, Thank You!

What's next? Probably going to look into adding a direct dial contact(s) to selection lists.