larryliuqing的专栏-xxx

chrome源代码目录结构简介（版本4.1.249.1059）为了对庞大的源码项目进行分析，先对源码目录树作一个简单的介绍，粗略的了解一下各个模块的功能分布情况，chrome源代码src目录下的结构如下图： 　　app：该目录下的代码主要是和各个操作系统平台相关的应用上层代码的提炼。不同操作系统可能对应不同的c++实现文件。比如裁剪板操作、操作系统数据交换接口、资源管理等。代码

目录1 Overview2 Supported models2.1 Process-per-site-instance2.2 Process-per-site2.3 Process-per-tab2.4 Single process3 Sandboxes and plug-ins4 Caveats5 Implementation notes6 Academic Papers

Overview and backgroundWindows provides very primitive tools for building user interfaces. The system provides a few basic controls and native window containers, but building a custom user interface

Original One-Page Design Doc (still good for a high level overview, with contact information. Many technical details are now obsolete)Aura Graphics ArchitectureAura OverviewAura Cl

Sandbox目录1 Design principles2 Sandbox windows architecture2.1 The broker process2.2 The target process3 Sandbox restrictions

Native ControlsBackgroundDespite the fact that views provides facilities for custom layout, rendering and event processing, in many situations we have found it desirable to use the c

Profile ArchitectureThis page details an ongoing design refactoring, started in January 2012.Chromium has lots of features that hook into a Profile, a bundle of data about the cu

Multi-process Resource Loading目录1 Background2 Overview3 WebKit4 Renderer5 Browser6 CookiesBackgroundAll network communication is handled by the main brows

This document describes how web pages are displayed in Chromium from the bottom up. Be sure you have read themulti-process architecture design document. You will especially want to understand the bl

This document describes Chromium's high-level architecture. ProblemIt's nearly impossible to build a rendering engine that never crashes or hangs. It's also nearly impossible to build a rendering

views provides support for creating dialog boxes and other kinds of windows through its Widget object. The developer creates a WidgetDelegate (or sub-interface) implementation that provides the Wind

Plugin ArchitectureBackgroundBefore reading this document, you should be familiar with Chromium's multi-process architecture. OverviewPlugins are a major source of browser in

转一篇官网上的文章 用于备忘https://sites.google.com/a/chromium.org/dev/developers/how-tos/build-instructions-windowsBuild Instructions (Windows) This page has detailed information on building C

StartupChrome is (mostly) shipped as a single executable that knows how to run as all the interesting sorts of processes we use.Here's an overview of how that works.First there

【二】Chrome的进程间通信1. Chrome进程通信的基本模式进程间通信，叫做IPC（Inter-Process Communication），在Chrome不多的文档中，有一篇就是介绍这个的，在这里。Chrome最主要有三类进程，一类是Browser主进程，我们一直尊称它老人家为老大；还有一类是各个Render进程，前面也提过了；另外还有一类一直没说过，是Plugin进程，每

【五】 Chrome的插件模型1. NPAPI为了紧密的与各个开源浏览器团结起来，共同抗击IE的垄断，Chrome的插件，也遵循了NPAPI(Netscape Plugin Application Programming Interface)标准，支持这个标准的浏览器需要实现一组规定的API供插件调用，这组API形如NPN_XXX，比如NPN_GetURL，插件可以利用这些API进行二次开

Design DocumentsStart here:Multi-process Architecture: Describes the high-level architecture of ChromiumNote: Most of the rest of the design documents assume familiarity with

Inter-process Communication (IPC)目录1 Overview1.1 IPC in the browser1.2 IPC in the renderer2 Messages2.1 Types of messages2.2 Declaring messages2.2.1 Pic

The Security Architecture of the Chromium Browser Stanford Web Security-->Most current web browsers employ a monolithic architecture that combines "the user" and "the web" into a single protecti

【三】 Chrome的进程模型1. 基本的进程结构Chrome是一个多进程的架构，不过所有的进程都会由老大，Browser进程来管理，走的是集中化管理的路子。在Browser进程中，有xxxProcessHost，每一个host，都对应着一个Process，比如RenderProcessHost对应着RenderProcess，PluginProcessHost对应着PluginProce

【四】Chrome的UI绘制1. Chrome的窗口控件Chrome提供了自己的一个UI控件库，相关文档可以参见这里。用Chrome自己的话来说，我觉得市面上的七荤八素的图形控件库都不好用，于是自己倒腾倒腾实现了一套。。。广告虽如此说，不过，Chrome的图形控件结构，我还未发现有啥非常非常特别的地方。Chrome的窗口、按钮、菜单之类的控件，都直接或间接派生自View，这个是控件基类

【序】 开源是口好东西，它让这个充斥着大量工业垃圾代码和教材玩具代码的行业，多了一些艺术气息和美的潜质。它使得每个人，无论你来自米国纽约还是中国铁岭，都有机会站在巨人的肩膀上，如果不能，至少也可以抱一把大腿。。。现在我就是来抱大腿的，这条粗腿隶属于Chrome（开源项目名称其实是Chromium，本来Chrome这个名字就够晦涩了，没想到它的本名还更上一层楼...），Google那充满

苹果的.plist读写，感觉也类似沙箱技术。百度谷歌一下 , 说chrome是浏览器安全标准 , 运用了“沙盒”这个东东，收集了一些资料，归纳如下：沙箱其实就是一个硬盘过滤文件驱动，具体来说，就是你把要写的东西写到了硬盘上，但实际上并没有写到硬盘，而是到了一个转存处，读取内容需要判断是沙箱开启之前就存在的内容还是开沙箱之后写入的内容，要分别从不同的地方读取内容，重启之后把转存的地方

Chromium is a large and complex cross-platform product. We try to share as much code as possible between platforms, while implementing the UI and OS integration in the most appropriate way for each. W

目录1 Overview2 Existing threads3 Keeping the browser responsive4 Getting stuff to other threads4.1 base::Callback4.2 PostTask4.3 base::Bind() and class methods.4.4 How arguments are handled b

怎样打开Chrome的开发者工具？你可以直接在页面上点击右键，然后选择审查元素：Chrome浏览器开发人员工具介绍" style="margin:0px; padding:0px; border:0px; list-style:none">或者在Chrome的工具中找到：Chrome浏览器开发人员工具介绍" style="margin:0px; padding:0px; b