forked from crosswalk-project/crosswalk
-
Notifications
You must be signed in to change notification settings - Fork 0
Development tasks
drott edited this page Apr 18, 2013
·
33 revisions
Aligned with the roadmap, we have identified a list of considerations and development tasks that we need to get started with.
- 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
- 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?)
- 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)
- Prototype simple launcher based on
- raw Content API and/or
- CEF3
An initial user story for Cameo would be to run Adobe Brackets.
- Find out what kind of FS access Brackets needs
- Find out other requirements for Brackets and how to realize them with our embedding framework
- Implement modifications to our Embedder/Chromium to enable such access
One of our objectives is to demonstrate interest in contributing, and getting involved with Chromium and Blink.
- Identify contribution areas, examples:
- Removing #ifdef's effort
- Viewport
- ...
- Contact, get to know Chromium stakeholders & OWNERs
- Submit patches to demonstrate contribution interest