[webkit-dev] [chromium-dev] Learning Webkit: High Level Webkit overview?

[tali garsiel]

On Wed, Oct 14, 2009 at 7:21 PM, Darin Adler <darin at apple.com> wrote:

> On Oct 14, 2009, at 3:33 AM, tali garsiel wrote:
>
>  I'm also trying to figure out Webkit flow. I modified the Mozilla diagram
>> to my understanding of Webkit flow. Is it correct?
>>
>
> The diagram seems basically OK, although I don’t entirely understand what
> the boxes are.
>

The boxes in a flow chart are supposed to be processing steps.

 From Wikipedia:
Processing steps:Represented as rectangles. Examples: "Add 1 to X"; "replace
identified part"; "save changes" or similar.
May be the name should be  "CSS parsing" instead of "CSS Parser" .


> The diagram leaves out the CSS object model, which is what the CSS parser
> actually produces. And you can edit it using the DOM API.
>
> The CSS style selector produces render style from the CSS object model
> objects, and the render style is closely related to the render tree and
> could even be considered part of it.
>

Yes.I see now.
The CSS parser products are "CSSStyleSheets" objects which contain CSS rule
lists - right?.

If I understand correctly the render style gets created in the process of
creating the render tree.
The flow is:
Node::attach()
Node::createRendererIfNeeded()
CSSStyleSelector::styleForElement(...)

I also see that the HTML Parser initiates the parsing of the CSS style
sheets - this is not apparent from my diagram - is this correct?.

>
> I’m not sure I understand what it means to have a box labeled “layout”
> pointing to the render tree. It is true that layout is a procedure performed
> on the render tree.
>

"Layout" box means a layout processing on the input.

>
>    -- Darin
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.webkit.org/pipermail/webkit-dev/attachments/20091014/24617034/attachment.html>