-
Notifications
You must be signed in to change notification settings - Fork 0
All three of these open source browser projects have their technical advantages and disadvantages, and their partisans. We had to pick one. The current Tizen runtime uses WebKit2 but contributing to that was made more difficult by Apple's December 2012 policy changes. The success of the first version of the Chromium Embedded Framework (which is similar in intent to our Embedded model) showed that developers using that model like what Google's project has to offer. It would not be surprising if someone decided to start other runtime projects based on the other code bases. We think that would be cool - the more attention paid to developers doing applications, not just web sites in HTML5, the better.
CEF 1.0 has proven to be quite popular, but it is being phased out in favor of the larger CEF3.0. Since we want a consistent implementation in the Cameo project for all three distribution models (managed, embedded, bootstrapped) we had to pick a level in the Chromium architecture that could accomodate all three use cases. By starting with Blink and building up, vs. starting with CEF 3.0 and removing pieces, we think we'll end up with a tighter, more consistent result. But we have no criticism of CEF for the use cases it's aimed at.
No.
- The Cameo Application Runtime isn't aimed at the web at all, it's aimed at applications that happen to be written in HTML5, CSS and JS.
- Applications using a Cameo Application Runtime know about the runtime they are built for. Minor differences between runtime implementations (e.g., a sensor available on one platform but not on another) are easily accommodated by developers.
- We don't intend to fork Blink, the underlying rendering engine for Chromium.
- We are going to rebase regularly to new versions of Blink.
- We will submit changes that make sense for Chromium generally upstream.
Someone can take the code at any point and build a product. We're going to indicate relative stability at each milestone in the roadmap. It's up to the community to offer commercial products. So, don't ask us when/if any particular product will use what we're building. Even if we know we can't say.
With Chrome packaged apps, you get access to the Chrome app store and the capabilities Chrome offers. But the end user has to explicitly download Chrome in order to gain access to Chrome packaged apps. With the Cameo project, you have other choices. If you are building a platform, you can include the Cameo Managed Runtime as a service for your own catalog of applications. A developer can package an application with the Cameo Embedded Runtime so that the app and runtime are never revised without developer permission. Or a developer can deploy a personal Cameo Bootstrapped Runtime whose updates are controlled for a suite of applications. Of course, because Cameo is based on Blink and Chromium, a developer could publish a standard HTML5 app for both solutions.