Overclock.net › Forums › Industry News › Software News › [eng]HP: Open webOS 1.0 arriving in September, Enyo 2.0 framework free to developers today
New Posts  All Forums:Forum Nav:

[eng]HP: Open webOS 1.0 arriving in September, Enyo 2.0 framework free to developers today

post #1 of 3
Thread Starter 
Quote:
When HP announced last month that it would open-source webOS, the outfit seemed mighty pleased (and relieved) to have finally made a definitive decision regarding the fate of its $1.2 billion software experiment. In fact, though, the company's initial announcement was light on detail, other than the fact that webOS will live on with the help of developers both inside and outside HP. Now, the company's ready to talk specifics:

webOS roadmap
Over the first half of the year, HP will make individual elements of webOS source code available – from core applications like Mail and Calendar to its Linux kernel – until the full code base is contributed to the open source community by September.

January:
Enyo 2.0 and Enyo source code
Apache License, Version 2.0

February:
Intended project governance model
QT WebKit extensions
JavaScript core
UI Enyo widgets

March:
Linux standard kernel
Graphics extensions EGL
LevelDB
USB extensions

April:
Ares 2.0
Enyo 2.1
Node services

July:
System manager ("Luna")
System manager bus
Core applications
Enyo 2.2

August:
Build release model
Open webOS Beta

September:
Open webOS 1.0

source

Here's what the official HP statement says
Quote:
Editor’s note: Today’s blog post comes from Sam Greenblatt, the chief technology officer and head of technical strategy for the open webOS project. He guides the project’s strategy around open collaboration and is responsible for technical engineering. His focus is on the practice of developing webOS with the community, and his approach is founded on the belief that the open source development model produces great software and web technology. Sam has many years of open source experience, including being on the board of OSDL (Linux Foundation). His long career in software development includes being a CTO at HP, Chief Innovation Officer at CA Technology, and CTO at Candle Corporation (IBM).

In December, HP announced that webOS would be made available under an open source license, with continued support from HP. We’re proud of webOS and its potential to harness web standards to improve the next generation of applications, web services, and devices.

Today, we’re taking the next step on this journey by releasing Enyo, our JavaScript app framework, under open source licensing, allowing developers to distribute their Enyo-based webOS apps across other platforms. In this post, we’ll also provide a first look at our open source release roadmap.

In any large project, it’s imperative to communicate the plan for achieving the project’s goals. This plan is usually presented in the form of a roadmap, which outlines the steps necessary to achieve project goals and shows the path forward. For an open source project to be a success, that roadmap must be public so all contributors have a sense of where the project is headed.

In subsequent posts, and on the new Enyo website, we will share more details about our roadmap for webOS, including our plans for release phases, governance, tools, documentation, and more. So with that in mind, let’s step into an overview of some of the pieces of the release plan.

Our first contribution is Enyo, our lightweight, cross-platform framework aimed at mobile devices and web browsers.

This initial open source release includes Enyo 1.0, which allows current developers of Enyo apps for webOS devices to distribute their apps to other platforms. While this release is not intended to be expanded any further, there is considerable utility for our current developer base in releasing it.

Today’s release also includes the core of Enyo 2.0, which will be the foundation for Enyo going forward. It expands Enyo’s “write once, run anywhere” capability to even more platforms, from mobile devices to desktop web browsers. It works on many of the most popular web browsers, including Chrome, IE 9, Firefox, and Safari.

While 2.0 does not yet include any UI widgets, the core will support a wide variety of libraries and add-ons. A UI widget set for 2.0 will be released in the near future.

Upcoming releases include our distribution of WebKit, which will support not only HTML5, but also Silverlight and Flash through the use of plug-ins. It will enable the rendering of webpages to HTML Canvas and 3-D textures, and will support a wide range of application interfaces, including multi-touch.

We will also release a new kernel based on the Linux Foundation’s standard kernel. As we continue through the roadmap, you will see enhanced integration with JavaScript through register callbacks and custom multi-process architecture for security, load balancing, and recovery availability.

Look for us to introduce LevelDB to replace our prior database.

Along the way, we will also share our tool sets, and we expect that many of you will want to share yours as well.

In closing, I want to thank the great engineers who have worked with me on creating the open webOS roadmap and let you all know that we look forward to collaborating with the community. As my friend Eric Raymond stated as I embarked on the open source adventure, “It takes a village to create a complete solution.”
post #2 of 3

So does this mean we could be seeing more WebOS phones in the future? There needs to be another competitor in the iOS vs. Android vs. Windows Phone arena.

post #3 of 3
Thread Starter 
Quote:
Originally Posted by Malcolm View Post

So does this mean we could be seeing more WebOS phones in the future? There needs to be another competitor in the iOS vs. Android vs. Windows Phone arena.

I believe that the most likely competitor is mer. Mer is a spinoff of Meego offering an OS "backbone" (that is, there's no GUI, but KDE Contour, stock Meego, Nemo, XBMC, etc can all be used on this framework. The advantage of this is that they don't have to focus on a UI leaving them to focus on making "behind the scenes" work better.

Unlike Meego, Mer will support multiple development types. There is/will be support for Qt, EFL, GTK+, HTML/CSS, etc (though I expect most developers to only use Qt or HTML/CSS).

The biggest things brought to the table by WebOS are Enyo and the WebOS UI. Adding Enyo is likely to become a major priority for Mer developers (as Enyo is the best HTML/CSS/JS environment to date), so adding the WebOS UI on top of Enyo shouldn't be hard.

That said, there may be companies that become interested in what WebOS can offer them, especially when it comes to cutting the umbilical cord tying them to Google.
New Posts  All Forums:Forum Nav:
  Return Home
  Back to Forum: Software News
Overclock.net › Forums › Industry News › Software News › [eng]HP: Open webOS 1.0 arriving in September, Enyo 2.0 framework free to developers today