With the micro-channel public number, applets, games and more popular, HTML5 front-end development of demand is gradually increased. Although they work not directly involved in the development of HTML5, but often dealing with the front end, so for some of these concepts are going to sort out.
Whether front-end developer, or front-end user, most contact is the "browser", including the Chrome (android platform) end of the phone; Safari (IOS platform); FireFox, IE (Windows platform) and so on, the browser can be understood as a presentation of the final results to the application user.
As users learn more content to meet the basic needs of daily use, so HTML5 code written by developers to show how the browser user in front of it? As a developer we generally put together the following process:
1. First of HTML5 developers to write code that is stored in a server path. For example such as Baidu, its HTML5 relevant documents will be stored in a path Baidu's cloud server, then Baidu company will build a map on a cloud server, allowing access of https://www.baidu.com network requests, pointing Baidu Home files stored in the cloud server, so that when the user enters Baidu's domain name in the browser, is the ultimate display Baidu's home page.
2. The above process may require only a very short time, but can be split into the following steps
1) the user to enter the URL Baidu, Baidu browser request resources from the cloud server
2) Baidu cloud server receives a request to return Html5 content written by developers
3) After receipt of these HTML5 browser data to the browser engine called "HTML parser" module
4) HTML parser is based on data such as CSS or JS to determine the next step is to CSS or JS parser engine
5) After the above-described lookup, HTML5 code will be presented in a more aesthetically pleasing browser
3. The above process, the more critical step 3) and 4), the implementation of these two steps is actually the browser "rendering engine"; it is the core of "rendering engine" is also the author understood browser.
Different manufacturers developed different rendering engine; e.g. the WebKit (used in Safari, Chrome and Android browser); Tridend (IE), Gecko (FireFox);
Webkit which is an open source project launched by Apple, currently occupy a monopoly position, based on webkit development as well as Web OS (as far as I know some foreign TV such as Samsung, Sony's operating system is based on Web OS), Chrome OS
4. Webkit internal structure from the bottom up in sequence are:
1) Operating System: run the most basic software on the computer bare metal, and any other software must be to work with the support of the operating system, webkit is running on the operating system.
2) third-party libraries: including graphics library, online libraries, video libraries, data repositories, etc.
3) Intermediate layer: This layer consists of three parts
a) WebCore: This section is part of the shared use of each browser, including Html parser, CSS parser, DOM parser
b) WebKit engine: The default engine is JavaScript Core; is replaced with a V8 engine in Google family of products
c) Webkit Ports: each non-shared part of the browser, because the platform differences, such as different third-party libraries and demand reasons, resulting in a key part of different browser performance and functional differences
4) WebKit Embedded Interface: The interface is mainly for the browser to call, closely related to the transplant, different transplant have different interface specifications.
In summary, we open a website on your phone or computer, hardware depends on the mobile phone (PC) and cloud servers and network equipment; software depends on the browser, the core of the software is "rendering engine", will be played written by developers HTML5 language, it converted into a web page presented to the user.
