Chromium Code Reviews
chromiumcodereview-hr@appspot.gserviceaccount.com (chromiumcodereview-hr) | Please choose your nickname with Settings | Help | Chromium Project | Gerrit Changes | Sign out
(22)

Side by Side Diff: docs/mojo_in_chromium.md

Issue 1642023003: [mojo] Clean up doc (Closed) Base URL: https://chromium.googlesource.com/chromium/src.git@master
Patch Set: Created 4 years, 10 months ago
Use n/p to move between diff chunks; N/P to move between comments. Draft comments are only viewable by you.
Jump to:
View unified diff | Download patch
« no previous file with comments | « no previous file | no next file » | no next file with comments »
Toggle Intra-line Diffs ('i') | Expand Comments ('e') | Collapse Comments ('c') | Show Comments Hide Comments ('s')
OLDNEW
1 # Mojo in Chromium 1 # Mojo in Chromium
2 2
3 This document is intended to serve as a Mojo primer for Chromium developers. No 3 This document is intended to serve as a Mojo primer for Chromium developers. No
4 prior knowledge of Mojo is assumed, but you should have a decent grasp of C++ 4 prior knowledge of Mojo is assumed.
5 and be familiar with Chromium's multi-process architecture as well as common
6 concepts used throughout Chromium such as smart pointers, message loops,
7 callback binding, and so on.
8 5
9 [TOC] 6 [TOC]
10 7
11 ## Should I Bother Reading This? 8 ## Should I Bother Reading This?
12 9
13 If you're planning to build a Chromium feature that needs IPC and you aren't 10 If you're planning to build a Chromium feature that needs IPC and you aren't
14 already using Mojo, YES! **Legacy IPC is deprecated.** 11 already using Mojo, YES! **Legacy IPC is deprecated.**
15 12
16 ## Why Mojo? 13 ## Why Mojo?
17 14
(...skipping 314 matching lines...) Expand 10 before | Expand all | Expand 10 after
332 329
333 This is a work in progress. TL;DR: We'll also soon begin using Mojo services 330 This is a work in progress. TL;DR: We'll also soon begin using Mojo services
334 from Blink so that the platform layer can consume browser services 331 from Blink so that the platform layer can consume browser services
335 directly via Mojo. The long-term goal there is to eliminate `content/renderer`. 332 directly via Mojo. The long-term goal there is to eliminate `content/renderer`.
336 333
337 ## Questions, Discussion, etc. 334 ## Questions, Discussion, etc.
338 335
339 A good place to find highly concentrated doses of people who know and care 336 A good place to find highly concentrated doses of people who know and care
340 about Mojo in Chromium would be the [chromium-mojo](https://goo.gl/A4ebWB) 337 about Mojo in Chromium would be the [chromium-mojo](https://goo.gl/A4ebWB)
341 mailing list[.](https://goo.gl/L70ihQ) 338 mailing list[.](https://goo.gl/L70ihQ)
OLDNEW
« no previous file with comments | « no previous file | no next file » | no next file with comments »

Powered by Google App Engine
This is Rietveld 408576698