Development tasks

Aligned with the roadmap, we have identified a list of considerations and development tasks that we need to get started with.

Table of Contents Framework for embedding Chromium / CEF Replacement Tasks Launcher / Stub-Runner Tasks Enable FileSystem sufficient for Adobe Brackets Tasks Demonstrate Intel's interest in Contributing to Chromium/Blink Tasks

Framework for embedding Chromium / CEF Replacement

• Needs to be better than CEF, see Issues with CEF
• With Multiplatform in mind
• Based on Chromium's Content API
• Keep Chromium's multiprocess and sandboxing architecture intact

Tasks

• Learn about Content API (Mikhail, Alexander Sh., Thiago, Dominik)
• Investigate ways to do API extensions (Thiago)
• Investigate Chromium Browser Components (Thiago, Dominik)
• Identify what's wrong with CEF, refine Issues with CEF
• Collect ideas & design an initial API for an embedded Chromium based on Chromium's Content API
• Investigate building Chromium as a library, or in general build an external project against Chromium in a hassle-free way (Raphael?)

Launcher / Stub-Runner

• Depends on Chromium Embedder
• Runs a WebApp based on the above embedding framework
• Should eventually comply with SysApps WG WebApps specification
• Multiplatform in mind (first: Linux & Win)

Tasks

• Prototype simple launcher based on
  1. raw Content API and/or
  2. CEF3

Enable FileSystem sufficient for Adobe Brackets

An initial user story for Cameo would be to run Adobe Brackets.

Tasks

• Find out what kind of FS access Brackets needs
• Implement modifications to our Embedder/Chromium to enable such access

Demonstrate Intel's interest in Contributing to Chromium/Blink

One of our objectives is to demonstrate interest in contributing, and getting involved with Chromium and Blink.

Tasks

• Identify contribution areas, examples:
  • Removing #ifdef's effort
  • Viewport
  • ...
• Contact, get to know Chromium stakeholders & OWNERs
• Submit patches to demonstrate contribution interest