Type tree for representing Elm's Html

• TextTag is just a plain old bit of text.
• NodeEntry is an actual HTML node, e.g a div
• CustomNode are nodes defined to work with the renderer in some way, e.g webgl/markdown
• MarkdownNode is just a wrapper for CustomNode designed just for markdown

Text tags just contain text

A node contains the tag as a string, the children, the facts (e.g attributes) and descendantsCount

Custom nodes contain facts (e.g attributes) and a json value for the model

A markdown node contains facts (e.g attributes) and the model used by markdown

Facts contain various dictionaries and values for a node

• styles are a mapping of rules
• events may be a json object containing event handlers
• attributes are pulled out into stringAttributes and boolAttributes - things with string values go into stringAttributes, things with bool values go into boolAttributes

Tagger holds the map function when Html.Map is used, the tagger should then be applied to events comming from descendant nodes, it is basically a javascript function.

EventHandler holds the function that is called when an event is triggered, it is basically a javascript object like this:

{ decoder: [Function] }

Type for representing the five kinds of elements according to HTML 5 spec. Used to handle different rendering behavior depending on the type of element.

decode a json object into ElmHtml, you have to pass a function that decodes events from Html Nodes. If you don't want to decode event msgs, you can ignore it:

decodeElmHtml (_ _ -> ()) jsonHtml

if you do want to decode them, you will probably need to write some native code like elm-html-test does to extract the function inside those.

Just empty facts

Identify the kind of element. Helper to convert an tag name into a type for pattern matching.