MobileESP: Updated for BlackBerry Curve Touch 9380

Hi, folks —

A quick update to the code libraries today.

ALL LIBRARIES: PHP, JavaScript, Java, ASP.NET (both), Python

Added support for the BlackBerry Curve Touch 9380. It’s a new monoblock all-touchscreen device from BlackBerry and is a little smaller than a Storm. Because the screen is (reasonably) large and it lacks a keyboard, we decided to add support to it to the DetectBlackBerryTouch() method. (Special thanks to Robert P. for bringing the recent launch of this device to our attention.)

PHP Bug Fix

Fixed a bug in the DetectKindle() method. The call to DetectAndroid() needed the class identifier (“this”). (Special thanks to the several people who wrote in about this one.)

Python Bug Fix

In adding support for the Curve Touch to the DetectBlackBerryTouch() method, we noticed a copy & paste error in the code. All of the existing lines of code were looking for the Storm device only. Oops! So we added in support for all necessary devices: Storm, Torch, Bold Touch and Curve Touch.

All libraries have been updated in the Google Code project and are available for download now.

– Anthony

Owner of the MobileESP project. For the latest source code downloads, visit: http://code.google.com/p/mobileesp/

Posted in Code Updates, MobileESP APIs
2 comments on “MobileESP: Updated for BlackBerry Curve Touch 9380
  1. Andy says:

    Hi Anthony,

    I’ve just started using your plugin and it seems super easy to use. I have 1 question. Is it possible to alter the code so that when the user wants to see the full site after visiting the mobile site they can? ie so that it doesn’t automatically redirect back to the mobile site.

    Many thanks and keep up the good work,

    Andy

  2. Anthony Hand says:

    Thanks for the note, Andy. MobileESP is optimized for one thing only: to detect whether the guest is using a mobile device. All other business logic, such as redirecting a user to a mobile-optimized version of your site (or not), is up to the web site publisher to determine and implement in a way that makes sense with your goals, your CMS’ capabilities, and so on.