Effective October 1, 2012, QUALCOMM Incorporated completed a corporate reorganization in which the assets of certain of its businesses and groups, as well as the stock of certain of its direct and indirect subsidiaries, were contributed to Qualcomm Technologies, Inc. (QTI), a wholly-owned subsidiary of QUALCOMM Incorporated. Learn more about these changes

Brew MP™ Code Camp – San Francisco, September 2, 2010

The San Francisco session was our last in a series of Brew MP code camps that took place over recent months. It could not have been a better venue at the historic Mark Hopkins Intercontinental in downtown San Francisco as our code camp base once again. We had a pretty good crowd in attendance; we even attracted a couple of developers for a repeat session. It was great to see a few familiar faces of those folks who attended our code camp back in May.

We also had several new attendees. Most attendees for this session were new to Brew MP development. A few others had been developing for a while now. Everyone seemed to show a high level of interest, whether it was learning about Brew MP in general, or learning about how Brew has matured into a true application environment. This made for a more interactive and informative session.
Commercialization and distribution still peaked high levels of interest. Fortunately, our AT&T developer relations representative was on-hand to quickly respond to queries, giving good status updates on their developer portal activities as well as revenue sharing and the developer business models.

Migration seemed to be a hot topic. One gentleman had a few questions about application migration from an earlier version of Brew to Brew MP. We introduced him to our Brew MP migration wizard, stepping through the wizard and walking through a couple of scenarios to start the porting process. He left class with a few remaining items left to sort out, such as addressing some project-specific directory requirements and build dependencies — but I think he was well on his way towards a successful effort.

As we jumped into our hands-on coding exercises, students had the opportunity to experience Brew MP firsthand. General set-up and particular computer environment issues were non-existent. We had students using everything from Windows XP to Windows 7, to Macs running VMs. Students were using our latest Brew MP SDK release, and our tools stood firm and fully functional under the variety of platforms being used. We had a couple of interesting issues with memory availability and the toolsets, but nothing that couldn’t be overcome by some minor tweaking of the PC environment.

We had a couple of students that had concerns about how we’re supporting older versions of the Brew SDK while using our newer versions. We have taken this into account and now support side-by-side installations of our SDK environments – a big selling point for us this time. Many folks are tied back into older versions to support their customers and can’t just let go of previously validated environments. With support now for our earlier versions of Brew (back to 3.1.2) via plugins, we are giving developers the opportunity to fully engage with Brew MP when they’re ready to do so. This topic got significant attention from the attendees.

As typical in our sessions, some students showed interest in getting some additional training on topics like widgets, windowing, and other advanced issues and technologies. We are actively working on adding additional training courses into our portfolio to cover these and other areas. They will be offered either by instructor-led classroom training sessions or by online learning solutions.

Please make sure to continue to follow us and check our Brew MP marketing pages for more information and announcements.

Opinions expressed in the content posted here are the personal opinions of the original authors, and do not necessarily reflect those of Qualcomm Incorporated or its subsidiaries ("Qualcomm"). The content is provided for informational purposes only and is not meant to be an endorsement or representation by Qualcomm or any other party. This site may also provide links or references to non-Qualcomm sites and resources. Qualcomm makes no representations, warranties, or other commitments whatsoever about any non-Qualcomm sites or third-party resources that may be referenced, accessible from, or linked to this site.