www.webOShelp.net

Just this week, photos of a Palm Centro apparently running webOS made waves in the headlines. These rumors have since been proven false, however what we saw was more than just a fancy Photoshop job.

The cool webOS theme that the Centro is running is actually TealOS, a new program by TealPoint Software designed to run on current PalmOS handhelds. From the video we saw of TealOS in action, it's actually quite impressive in emulating several UI features of the new platform. Engadget also posted a video that further demonstrates features of the software.

Mitch Allen, vice president and software CTO for Palm, Inc. has scheduled an hour-long webcast for Wednesday, February 25 titled "Developing Applications for webOS: A Preview". 

As the principle architect of Palm's new OS and application development framework, Allen wiill go over the material included in the first chapter of "Palm webOS: Developing Applications in JavaScript Using the Palm Mojo(tm) Framework", by O'Reilly. The webcast is designed to give a preview into application development with the Mojo SDK.

This is a great opportunity to hear an insider's perspective on webOS development and get a glimpse into the development environment and toolset for this breakthrough mobile web platform.

The event takes place on Feb 25, 2009 at 10:00 am PST / 1:00 pm EST.

You can register for the webcast here.

 

Slightly delayed but still incredibly useful, here is part 2 of our summary of Palm webOS: Rough Cuts by O'Reilly. (Go here for part 1.)

Mojo application framework

• Apps are run within UI system manager
• UI system manager built on standard browser technology:
  • renders display
  • assists with events
  • handles Javascript
• webOS APIs delivered as Javascript framework called Mojo
• Supports common application-level functions:
  • UI widgets
  • access to built-in apps and data
  • native services
• Can also leverage HTML5 features such as video/audio tagging and database functions
• Prototype JavaScript framework "not formally" part of Mojo framework, but is included to assist with registering for events and DOM handling
• Framework provides structure based on standard MVC architecture.
  • Better separation of business logic, data, and presentation
• Framework includes:
  • Application structure:
    • controllers
    • views
    • models
    • events
    • storage
    • notification
    • logging
    • asserts
  • UI widgets:
    • single and multi-function widgets
    • integrated media viewers
  • Services
    • access to app data
    • cross-app launching
    • storage, location, cloud services
    • accelerometer data

Engadget has had a chance to sit down with Palm today, and tackled some of the recent news about the Pre and webOS. Basically, Palm was staying silent about carriers for their GSM version of the Pre that was spotted at the show, and keeping the actual device at arm's reach at all times.

They did however, confirm that games are in development for webOS, and although they denied accusations that the "OS can't handle that stuff", they were adamant to focus on the fact that web-style app development will limits options for games overall. 

Palm Infocenter had a chance to interview Christian Sepulveda, VP of Business Development for Pivotal Labs about developing for webOS. Pivotal Labs is a Bay Area software development consultacy who have worked with big names including Best Buy, Twitter, and Salesforce. In the Palm CES presentation, CEO Ed Colligan named them as one of their primary partners.

Pivotal Labs does a lot of software development directly for clients, focusing on core development with clients' developers, transferring ownership of project and process. They have been working with Mojo and webOS for a few months so far, including a developer camp last thanksgiving before the CES announcement.

This is part 1 of the "cliffs notes" version of Chapter 1 of Palm webOS "Rough Cuts" by O'Reilly Media.  We're going to be summarizing each chapter as it's released, in case you don't have time to read the whole (in this case, 26-page) doc.  We will also be leaving out stuff that you probably already know (e.g. "Palm webOS is Palm's next generation operating system.")

Tomorrow we'll be posting the rest of the Chapter 1 summary, which gets into more technical details of the Mojo framework. Update: Posted.

Earlier we reported on an interview series with current PalmOS developers, and the main theme appeared to be that webOS would not support backwards compatiblity with PalmOS applications. This was emphasized in Palm CEO Ed Colligan's recent announcement that Palm OS is being discontinued. Already, this is causing headaches among established developers and users of the soon-to-be legacy OS.

An article tucked away at Brighthand however, gives hope to the masses that their old applications won't completely go to waste once upgrading. StyleTap, who already make an application that allows Palm programs to run on Windows Mobile, is considering making a similar program for webOS. While far from perfect, this would at least give users the option of giving their old software a second wind as they make the transition over to the Pre.

The article goes on to describe how Palm's previous strategy in 2007 of "merging PalmOS with a Linus-based operating system" amounts to a broken promise to those hoping to run their old software on the new OS.

So when should we expect such an emulator? Right now, StyleTap is gauging interest in the marketplace for such a program, and those interested should send comments to .

Source

User Ameet has posted an article on fivemobile on the pros and cons of developing Mobile Applications vs. mobile websites, taking into account the recent spike in smartphone handsets. Many companies tend to do both, such as Facebook, who have both a mobile website and application often complementing each another. A decent read for those planning on developing websites and apps for the Palm Pre. To summarize:

Pros for creating mobile websites include a very low cost (vs. a downloadable application), quick creation, and easy connection to an already established, high traffic website. Cons include the inability to take advantage of device-specific features, high cost, clunky interface, cross-compatibility issues, and a more narrow audience.