Now available: Mojo SDK v1.2

3 BY devrel

Palm® just released webOS™ version 1.2, and with it the latest version of the Mojo™ Software Development Kit.

As always, the number one reason to update your SDK installation is to keep your development environment in sync with the version of webOS that’s running on end-user devices. The emulator ROM and Mojo Framework in the Mojo SDK v1.2 match the software that began rolling out to devices today via over-the-air updates.

Aside from staying up to date, there are plenty of other good reasons to get the latest SDK. Here are some of the highlights:

  • Improved installation and development platform support. The Mojo SDK now supports Mac OS X 10.6 (Snow Leopard), Windows 7 Beta (32- and 64-bit), and Windows Vista 64-bit. We’ve also addressed a number of configuration and installation issues that you’ve reported – thanks for your help in tracking these down.
  • New and improved SDK tools. Debugging your app should be much easier thanks to the new palm-log tool, which can display or tail your app’s log output including JavaScript syntax errors and runtime exceptions. The v1.2 SDK also includes a new webOS Resource Monitor (WORM) tool to help you monitor your app’s memory usage and an updated Palm Inspector with improved reload functionality and reliability.
  • New and enhanced APIs. There are a handful of new APIs in the latest SDK, including perhaps the single most popular request: the new Download Manager API lets apps download and upload files over HTTP.

And, of course, we’ve updated the Mojo SDK documentation so you will know how to take advantage of the enhancements and new functionality.

For a complete list of Mojo SDK v1.2 enhancements, as well as known issues with the new release, go to the Release Notes. And, as ever, please go to the webOSdev Forums to let us know how things are working and what more we can to keep improving your webOS development experience.

Ben Galbraith and Dion Almaer to lead Developer Relations team at Palm

4 BY devrel

Palm has a long history of creating innovative platforms with rich opportunities for developers. Over the years, we’ve sparked the creation of tens of thousands of applications, offering our customers a vast range of options and creating huge opportunities for our developer community.

Now that our exciting Web-based platform, Palm webOS, is ready for developers, the time was right to ramp up our Developer Relations team, to ensure the best possible developer experience. When we sat down to think about the type of person that needed to lead this team, two things were clear: we needed real developers at the helm, and they needed to be developers with a deep understanding of the Web environment.

I’m incredibly excited to announce that we have found two rare individuals to help us lead this charge. As of today, Ben Galbraith and Dion Almaer are joining Palm to run the Developer Relations group. These guys have been in the community forever. They founded Ajaxian.com, a great community built around leading-edge Web development. More recently, they worked together at Mozilla to create some revolutionary forward-looking developer tools, such as Bespin, an innovative Web-based coding environment.

When I first met them, I instantly appreciated the passion that they had for the Web, and their desire to do great things to engage and excite developers. I expect them to think big and work diligently to make Palm webOS a platform you love to be a part of, and also one that helps you grow your business.

Join me in welcoming them to the fold, and also join us as we begin to take the wraps off what we know will be an exciting and compelling developer program.

They have both written on their personal blogs about the start of their journey at Palm. A lot of you already know them so you’ll enjoy reading what Dion and Ben have to say. (You can also connect with them on Twitter: @bgalbs and @dalmaer.)

Best,
Katie Mitic
SVP, Product Marketing

Two videos to watch

0 BY devrel

I thought I’d pass along pointers to a couple of videos you might want to watch.

The first one is to the Engadget Show, where Palm’s CEO, Jon Rubenstein, sits down for a talk about Palm, the Pre  and webOS.

The other video is the second webcast by Palm’s CTO Mitch Allen, this one covering webOS Application basics:

For those getting started programming in webOS, it covers a lot of the ground to get you going and is well worth the time to view.

Sharing Q&A from Application Basics Talk

1 BY devrel

Just a quick note to thank everyone who attended the Application Basics webcast on Tuesday (September 9th), and to thank the O’Reilly team for hosting the webcast. We covered a lot in the hour ranging from how to access and install the SDK, an overview of the SDK tools and building a simple application. The webcast was recorded and has been posted by O’Reilly.

This webcast was based on Chapter 2 of the Palm webOS book, which was released last month and is now available on O’Reilly’s website as well as Amazon, Barnes & Nobles and other sources for technical books. We haven’t scheduled any other webcasts at this time but we are interested in doing more on topics that most interest you. There could be some based on other chapters of the book or just on some specific webOS topics – let us know what you’d like to see.

Also a thanks to the readers who have taken time to email or submit comments and corrections to the book. We rushed to get the book into print and available as close to the SDK release as we could, but in doing so we missed a number of problems in the sample code and in the book copy. Those are all being corrected in a second printing of the book which O’Reilly is working on now and once available, there will be a simple change summary provided on the webOS book’s page on O’Reilly’s site.

I had a lot of great questions in the Q&A period, so I wanted to share them with other developers who may have similar queries:

Application Basics – Webcast Q&A

Q: How do I get access to the shipping applications, on the emulator?

Most of the Palm applications included on end-user devices are accessible from the emulator as well, and may be run from the webOS Launcher, just like on a real device. Because the emulator doesn’t currently support all device functionality, some apps (particularly the media apps) are not fully functional in the emulator. You can access application code by connecting to the emulator via Novaterm or SSH and browsing to /usr/palm/applications.

Note that carrier-specific applications (e.g. Sprint Navigation) are not available in the emulator. Nor is the App Catalog, so third-party apps cannot be installed from the catalog. Of course, you can use the SDK’s command-line tools to install any app for which you have source code or a package file (.ipkg), including your own applications and the SDK sample apps.

Q: Besides the emulator, what tools are there to test a webOS app?

The Mojo SDK includes a variety of tools that complement the emulator, including a terminal-based JavaScript debugger, a DOM inspector, and tools for viewing application log output. The SDK’s command-line tools can be used to install apps on physical devices as well, for real-world testing. Third-party tools are emerging as well – for example, Pivotal Labs has developed a library called Pockets for doing test-driven development for webOS. Pockets includes a version of the Jasmine test framework and is available from their gitHub repository.

Q: Are there plans to release additional tools for creating apps without using the command line?

Yes, we believe that it’s very important to have high level tools and are actively working on solutions. We don’t currently have any specifics to announce, but it’s a high priority for the SDK team. For now, besides Palm’s own Eclipse plug-in, a number of third-party tools integrations exist — check the webOSdev forums for more information.

Q: When will the 1.2 SDK be available?

The 1.2 SDK will be released as soon as webOS 1.2 itself is released.

Q: Can we use jQuery or other libraries?

Yes, you can use other JavaScript libraries and frameworks like jQuery. In some cases, however, there may be some constraints, or issues affecting interoperability with the Mojo framework and Prototype (on which the Mojo framework depends). This topic has been discussed in the webOSdev forums for some frameworks, including jQuery.

Q: When will the SDK support 64-bit Windows?

The latest SDK release (1.1.0.19) supports 64-bit Windows. However, note that this release contains an installer bug that affects upgrades. If you’re a new user, the 1.1.0.19 SDK will install correctly on 64-bit Windows. If you’re upgrading from an older version of the SDK, you’ll need to uninstall the old version before installing 1.1.0.19. This bug will be fixed in the next SDK release.

Do you have more questions? Join us on the developer  forum and ask away!

(posting this for Mitch — chuq)

Announcing the next webOS device: Palm Pixi

4 BY devrel

A big day for Palm® webOS™ developers: Palm announced the next webOS device, the Palm Pixi™ phone, which will be shipped to Sprint customers later this year.

What this means for you, the developer, is greater visibility for your apps. A growing Palm webOS family of devices will help make your apps available to more potential customers, and the good news is that a single version of your app will run on both Palm Pre™ and Palm Pixi. If you use the Palm Mojo™ SDK and Framework and follow the UI guidelines and the rest of the SDK documentation, you’ll find it’s easy to make your app work well across the growing Palm webOS family.

In most ways, developing for Pixi is the same as developing for Pre, so the Palm Mojo SDK provides everything you need to develop apps that work well on both devices. One important difference is that the new device’s display resolution is 320×400 pixels (the Pre resolution is 320×480), which was necessary to create a small and pocketable candy-bar form factor that’s the thinnest Palm device ever.

The display resolution difference, however, will mostly affect apps that are designed to fill the entire screen instead of scrolling to reach additional content and elements. If your app works this way, you will have to approach its layout with flexibility in mind if it is to work well on both Pre and Pixi.

To see how your app will perform on Pixi, you can run it in the Palm Emulator shipped with the Mojo SDK. Keep watching webOSdev. We’ll soon have more specific guidance for designing your apps to work on both Pre and Pixi and for running the Palm Emulator at Pixi resolution.

For more information about Palm Pixi, read the Palm press release as well as the post to the Palm Blog.

Topics  Palm Devices