Demo

中文(较新) | EN

This project is used to demonstrate how to use some basic mechanisms in chromium, including asynchronous multitasking, mojo, multi-process, etc.

Tip: If you are new to chromium, it is recommended to study these demos in order.

Demo list:

demo_exe: The simplest demo to demonstrate gn and create your own exe;
demo_log: Demo log library;
demo_tracing_console: Demonstrate using Trace to output to the console;
demo_tasks: Demonstrate the use of thread pool ThreadPool;
demo_messageloop: Demonstrate using the message loop MessageLoop;
demo_mojo_single_process: Demonstrate the use of the mojo library in a single process;
demo_mojo_multiple_process: Demonstrate the use of the mojo library in multiple processes;
demo_mojo_multiple_process_binding: Demonstrate using the binding layer of the mojo library in multiple processes;
demo_services: Demonstrate the use of servcies and multi-process architecture based on mojo;
demo_ipc: Demonstrate the use of IPC interface based on mojo;
demo_memory: Demonstrate the use of SharedMemory;
demo_tracing_perfetto: Demonstrate the output of Trace as Json format (used to interface with perfetto);
demo_tracing_perfetto_content: Demonstrate how the content module is connected to perfetto;
demo_resources: Demo resources related content, including grit, l10n, pak, etc.;
demo_gl: Demonstrate using //ui/gl for GPU rendering;
demo_viz_gui: Demonstrate using viz to display the GUI interface;
demo_viz_offscreen: Demonstrate using viz for off-screen rendering;
demo_viz_gui_gpu: Demonstrate the use of viz for hardware accelerated rendering;
demo_viz_layer: Demonstrate the use of viz for interactive rendering;
demo_viz_layer_offscreen, demonstrate using VIZ's CopyOutput interface for off-screen rendering;
demo_cc_gui: Demonstrate using cc to display GUI interface;
demo_cc_offscreen: Demonstrate using cc for off-screen rendering;
demo_views: Demonstrate the use of //ui/views to create UI;
demo_apk: Demonstrate the creation of Android applications, the use of base::android::* and JNI;
demo_android_skia: Demonstrate the use of Skia for software rendering and hardware rendering on Android;
demo_skia: Demonstrate the use of Skia for software rendering and hardware rendering on Linux;
demo_x11: Demonstrate using X11 to create transparent windows;
demo_x11_glx: Demonstrate the use of glx in a transparent window;
demo_x11_egl: Demonstrate the use of egl in a transparent window;
demo_shell: Demonstrate the use of content api to create a streamlined browser that supports Linux and Android;

Documents:

Public documents are in the docs directory, and other documents are in the corresponding directory of the code.

Usage one (recommended)

Enter chromium's src directory;
Execute the following command to clone the repository to the src/demo directory;
```
git clone <address of current repository> demo
```

Find the out/Default/args.gn file in your compilation output directory and add the following parameters:

# add extra deps to gn root
root_extra_deps = ["//demo"]

# If you want to compile the demo of android platform, you need to add the following parameters
target_os="android"
target_cpu="arm64" # Other architectures can be selected as needed x86, x64, arm, mipsel

Run ninja -C out/Default demo to generate all demo programs (see BUILD.gn for details);

Usage two (use gclient)

Go to the root directory of the chromium project (the directory above the src) and find the .gclient file;

Open the .gclient file and modify it according to the following settings:

solutions = [
    {"name": "src",
        "url": "https://chromium.googlesource.com/chromium/src.git",
        "deps_file": "DEPS",
        "managed": False,
        "custom_deps": {
            # let gclient pull demo project to'src/demo' dir
            "src/demo": "<address of current repository>",
        },
        "custom_vars": {},
    }
]
...

Find the out/Default/args.gn file in your compilation output directory and add the following parameters:

# add extra deps to gn root
root_extra_deps = ["//demo"]

# If you want to compile the demo of android platform, you need to add the following parameters
target_os="android"
target_cpu="arm64" # Other architectures can be selected as needed x86, x64, arm, mipsel

Execute the gclient sync synchronization code, which will pull the demo repository to src/demo;
Run ninja -C out/Default demo to generate all demo programs (see BUILD.gn for details);

TODO

Improve the documentation of the process initialization part (docs/startup.md);
Improve the documentation of the UI part (docs/ui.md);
Improve the documentation of the content module (docs/content.md);
Improve the documentation of demo_shell (demo_shell/README.md);
Add demo to demonstrate how to create aar component;
Add demo to demonstrate how to use aura to create UI interface;
Add demo to demonstrate how to use PlatformWindow to create UI interface;
Add demo to demonstrate how to implement off-screen rendering of web pages;
Add a demo to demonstrate how to inject new JS objects into Blink;
Add a demo to demonstrate the principle of navigator.mediaDevices.getUserMedia();
Add a demo to demonstrate the principle of tab capture api;

Changelog

2020.8.10

Add demo_gl, the demo uses the //ui/gl module to call GL for rendering;

2020.7.31

demo_viz_layer_offscreen supports off-screen rendering using the SkiaOutputDeviceOffscreen interface;

2020.7.28

Add demo_viz_layer_offscreen to demonstrate using VIZ's CopyOutput interface for off-screen rendering;

2020.7.24

Add demo_viz_layer, demonstrate the use of VIZ for handwriting writing, and support the use of command lines to switch between software and hardware rendering;

2020.7.18

Add demo_viz_gui_gpu to demonstrate the use of VIZ for hardware accelerated rendering and VIZ Client nesting;

2020.7.15

Add demo_x11_glx and demo_x11_egl;

2020.7.11

Add demo_x11 to demonstrate the use of X11 to create transparent windows;
Update demo_skia, use software rendering by default, support transparent windows, GL rendering supports GL_RGB565 pixel format;

2020.6.28

Add demo_skia to demonstrate the software/hardware rendering using Skia in Linux;

2020.6.4

Update demo_android_skia, add multi-thread rendering and frame rate synchronization;

2020.5.31

Add demo_android_skia to demonstrate the use of Skia in Android for software/hardware rendering;

2020.5.21

Add demo_tracing_perfetto_content to demonstrate how the content module saves trace to a file, which can be used for chrome://tracing;
Add demo_tracing documentation demo_tracing;

2020.5.18

Move demo_tracing to demo_tracing folder and rename it to demo_tracing_console, add Flush function;
Add demo_tracing_perfetto to demonstrate the integration and use of trace and perfetto;

2020.4.29

Add demo_cc_gui to demonstrate using cc to display GUI interface;

2020.4.17

Added TRACE.txt of demo_cc to help understand the runtime behavior of cc;

2020.4.10

Add demo_cc_offscreen, demonstrate the use of cc for off-screen rendering;

2020.4.6

Add demo_viz_offscreen, demonstrate using viz for off-screen rendering;
Modify demo_viz to demo_viz_gui, the function is unchanged;

2020.3.31

Add demo_viz, demonstrate using viz module;
Add documentation for viz: viz

2020.3.21

Add demo_views, demonstrate using //ui/views to develop UI;

2020.3.12

demo_apk supports JNI to call instance method of C++ class;
Add document: [browser startup process brief description] (./docs/startup.md)

2020.3.7

demo_apk supports JNI;
Add document: demo_apk

2020.3.4

Add demo_tracing to demonstrate the use of trace;
Add demo_apk to demonstrate how to use gn to create Android applications;
Add demo_shell to demonstrate how to use the Content API to create a streamlined browser;

Earlier

Add the following demo and related documents:

demo_exe: the simplest demo, demonstrate gn and create your own exe;
demo_log: demonstrate the use of log library;
demo_tracing: demonstrate the use of Trace;
demo_tasks: demonstrate the use of thread pool ThreadPool;
demo_messageloop: demonstrate the use of message loop MessageLoop;
demo_mojo_single_process: demonstrate the use of mojo library in a single process;
demo_mojo_multiple_process: demonstrate the use of the mojo library in multiple processes;
demo_mojo_multiple_process_binding: demonstrate the use of the binding layer of the mojo library in multiple processes;
demo_services: demonstrate the use of mojo-based servcies and multi-process architecture;
demo_ipc: demonstrate the use of mojo-based IPC interface;
demo_memory: demonstrate the use of SharedMemory;

love514425/chromium_demo