12-03-2008 07:52 AM
12-03-2008 08:41 AM
So far, none of our applications failed to run on the Storm "out of the box".
However, each of these applications benefited from some tweaking of the UI using the 4.7 JDE and the Touch API's.
12-03-2008 08:45 AM
12-03-2008 08:50 AM
I had a report of a testing failure on a simulator but this was due to
missing default image or one specific for the new screen size. We had never gotten a
profile with this info, ( apparently 9500 4.7.0)
The user failed to complain subsequent to putting the right images up - since we are testing
I regularly wipe out our logs but apparently it at least loaded some images and the home page ( this
is a browser app). FWIW, it runs to varying degrees ( there are definitely some problems on
some models, but they seem to be specific to browserfield issues) at least on these models,
$ cat xxxx.xxx | sed -n 's/.*BlackBerry//p' | sed -e 's/ .*//' | sort | uniq
Now that you have me going, I did check some older logs after the 9500 profile was cached.
AFAIK, the simulator was able to browse ( the app worked ) but it was only tried for a few quick hits,
$ cat /cygdrive/c/temp/ud_log* | sed -n 's/.*BlackBerry//p' | sed -e 's/ .*//' | sort | uniq -c
Note also that so far this app is only built for a single target, 4.0.2, but we will probably need to
add things in the future that make that impossible ( and the conditional compilation and server logic
will be a big deal).
12-03-2008 09:50 AM
Luckily, we are not using the "real" filter, but I am aware of the issue.
There are some other "usability" details, but I would say that we are about 95% Storm-compliant with just a little bit of tweaking.
Overall, I would rate this transition as no worse than going from Trackwheel to Trackball.
The only "hard-core" development we had to do was duplicating the Toolbar control, which RIM inexplicably left out of the API. Even this was not a huge deal - completed in a couple of days.