Palm webOS SDK The Palm webOS Software Development Kit
Download

Palm webOS SDK Ranking & Summary

Palm webOS SDK Tags

sdk software development Palm webOS webOS SDK

Palm webOS SDK Description

The Palm webOS Software Development Kit Palm webOS offers you a complete tutorial on the design principles, architecture, tools, UI and services necessary to develop webOS applications.Palm© webOS is Palm's next generation operating system. Designed around an incredibly fast and beautiful user experience and optimized for the multi-tasking user, webOS integrates the power of a window-based operating system with the simplicity of a browser. Applications are built using standard web technologies and languages, but have access to device-based services and data.Palm webOS is designed to run on a variety of hardware with different screen sizes, resolutions and orientations, with or without keyboards and works best with a touchpanel though doesn't require one. Because the user interface and application model are built around a web browser, the range of suitable hardware platforms is quite wide, requiring only a CPU, some memory, a wireless data connection, a display, and a means for interacting with the UI and entering text.You can think of webOS applications as native applications, but built from the same standard HTML, CSS and JavaScript that you'd use to develop web applications. Palm has extended the standard web development environment through a JavaScript framework that gives standardized UI widgets, and access to selected device hardware and services.The user experience is optimized for launching and managing multiple applications at once. WebOS is designed around multi-tasking, and makes it utterly simple to run background applications, to switch between applications in a single step, and to easily handle interruptions and events without losing context.You will build WebOS applications with common web development tools following typical design and implementation practices for Ajax applications. But your webOS applications are installed and run directly on the device, just as you are used to doing with native applications. What's New in This Release: Highlights: · webOS incorporates WebKit 4, which features enhanced CSS support and numerous other improvements · The webOS implementation of the HTML 5 Media API has been updated, bringing closer conformance to the spec and incremental improvements to audio performance · The Camera API has been extended to let an app initiate video capture, in addition to image capture · The V8 JavaScript engine used in webOS has been updated · Numerous tools fixes and enhancements Current Versions: · All operating systems - Palm webOS SDK v1.4 Build 419 Tools: · Emulator ROM updated to webOS 1.4 · In the emulator, location services are now enabled by default · palm-generate now offers two project templates (new_app and hello_app) and two scene templates (new_scene and hello_scene) · new_app (the default) generates a completely empty app with no boilerplate content in index.html and no boilerplate scenes. This template differs from previous versions, which included boilerplate text in index.html. · hello_app generates a project with a boilerplate scene. This template is new for version 1.4. · new_scene adds an new scene without boilerplate HTML content. This template is unchanged in version 1.4. · hello_app adds a new scene with boilerplate HTML content. The template is new for version 1.4. · palm-generate now uses an HTML doctype for a project's index.html file (formerly used XHTML) · The project and scene generators for the webOS Eclipse plug-in have been updated to incorporate the new templates used in palm-generate · FIXED: palm-emulator fails to launch on 64-bit windows if no args are supplied · FIXED: palm-package fails if directory name has spaces (Windows only) · FIXED: creating package from Eclipse sometimes fails due to file in use (Windows only) Mojo Framework: · Updated Framework to revision 330 · Template rendering performance is significantly improved · Framework has changed more between 1.3.5 and 1.4 than in previous updates · Care has been taken to avoid changing public APIs, but many private APIs and internals have changed · If you use undocumented framework APIs or override framework functionality, your app may exhibit issues in 1.4 APIs: · The webOS implementation of the HTML 5 Media API has changed in version 1.4 · The new implementation is simpler and conforms more closely to the HTML 5 Media spec · Audio playback latency has been significantly reduced (though audio performance improvements are still a work in progress) · Both the original version and the new version of the API are supported in 1.4 · Developers beginning work on new apps should use the updated API, described on the Audio and Video doc pages · Developers with applications already in the App Catalog should transition to the updated API · The Camera API has been extended to let an app initiate video capture, in addition to image capture · The Mojo.StageController.pushScene() method now allows for template substitution in a scene's initial HTML content · Template subsitution syntax is the same as for other Mojo templates · To specify values for substitution, add a templateModel property to the sceneArguments object passed to pushScene() Documentation: · The Audio and Video doc pages have been significantly revised and now reflect the updated Media API Key Fixes & Enhancements: · webOS 1.4 incorporates WebKit 4 · Many incremental improvements over the version previously used in webOS, most notably enhanced CSS support · webOS is now more consistent in behavior and appearance with other WebKit-based browsers · CSS changes and numerous low-level WebKit differences introduce the possibility of app appearance or behavior changing from webOS 1.3.5 to 1.4. — see 1.3.5 to 1.4 Transition Checklist below · The V8 JavaScript engine used in webOS has been updated 1.3.5 to 1.4 Transition Checklist: · See Transitioning to the Updated Media API for a summary of important changes between 1.3.5 and 1.4 and advice on managing your transition. · To limit the impact of app performance issues on on overall device responsiveness, long-running JavaScript routines (10 seconds or longer) will time out in webOS 1.4. · Bugs causing unintended loops or long-running routines may show different symptoms in 1.4 than in previous releases. · If you have a legitimate need for long-running operations, you may need to re-implement them in ways that avoid the 10-second timeout. · Scene transition timing has changed · Any content in your app's index.html file will appear briefly before the first scene is pushed. In most cases, you should simply remove all content from index.html. · For subsequent transitions, you may need to perform template substitution on a scene's initial HTML content (see APIs, above) or use CSS to set some elements to "display: none" to prevent display issues. · The implementation of the Canvas element has changed significantly. It is meant to be compatible with previous versions of webOS, but apps utilizing the Canvas should be tested extensively. · X-fade animation transitions in WebKit 4 are different. If you are using Mojo scene transitions, you should be fine, but apps "rolling thieir own" transitions may show differences. · The Mojo WebView widget is implemented using a browser plug-in. Due to some changes in the way WebKit 4 instantiates plug-ins, WebView widgets styled "display: none" will no longer work in webOS 1.4. Specifically, the methods and properties exposing the widget's core functionality will not be accessible, and attempts to access them will trigger errors. If, for some reason, you need a hidden (aka windowless) WebView widget, Mozilla's Plug-in basics page contains a nice write-up and the appropriate CSS style to hide a plugin. · If your app code includes full paths to files within your application directory, make sure you use the Mojo.appPath property to get your application root directory and compose the path from there. (This is not a change in 1.4, but a best practice made especially important in changes between 1.3.1 and 1.3.5.) · The Mojo Framework webOS 1.4 includes changes to the included PrototypeJS library's JSON encoder in order to prevent it from interfering the ECMAScript 5 JSON.stringify() now found in V8. · PrototypeJS defines a toJSON() method on the prototype on many of JavaScript's built-in objects that returns the encoded form of the object. PrototypeJS uses these methods in a recursive fashion to JSON encode objects. · The problem occurs because ECMAScript 5's JSON.stringify() function will call a toJSON() method, if present, to get an alternative representation to use for encoding. Unfortunately, PrototypeJS's methods aren't compatible with this definition, as they return the target object already encoded as a string. As a result, the presence of PrototypeJS's toJSON() methods causes JSON.stringify() to produce JSON that, when parsed, doesn't match the original object before encoding. · To avoid this problem, webOS 1.4 renames all of PrototypeJS's toJSON() methods to _toJSON(), and modifies PrototypeJS's encoder to use those methods, rather than ones named toJSON(). · In order to keep existing application code that uses the PrototypeJS toJSON() methods directly from failing, new toJSON() methods, compatible with JSON.stringify(), were added. While these methods aren't completely compatible with the original PrototypeJS methods, they will likely work well enough in cases where toJSON() is being used for something like logging. Known Issues: Emulator: · Reset options are not working, applications and data cannot be erased The user is not able to sign in to or sign up for a Palm Profile using the First Use application · More than one emulator is listed from the novacom -l command output if the user resets the emulator · Unable to login to gtalk or AIM in emulator

Palm webOS SDK Related Software