Palm might have delayed the release of webOS 1.2.0 firmware update for the Palm Pre for about two weeks, yet, as soon as the new OS flavor was out, the mobile phone maker also unleashed the Mojo SDK v1.2 for the platform, as well as a new version of its webOS Doctor, the software solution that helps users to restore the functionality of their devices after almost bricking them.

According to the Sunnyvale-based company, the new version of the Mojo Software Development Kit has been made available so that developers can benefit from an environment on par with the OS version available on handsets. Both the emulator ROM and Mojo Framework in the Mojo SDK v1.2 have been updated to match the software update that went over-the-air to the Palm Pres in the wild.

A post on the Palm Developer Network Blog shows that the changes Mojo SDK v1.2 comes along with include:
- 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
- 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.

At the same time, the Mojo SDK documentation has been updated too, so that developers are up to date with the latest changes in the development kit to take advantage of the enhancements and new features. The entire list of changes that were made to the Mojo SDK with the release of the new version can be seen here. Developers will also find there a list of the known issues the v1.2 comes with.

Follow the editor on Twitter @softpediamobile