SimpleWebKit - Revision history

Multix: colorize sttus cells

2012-02-24T09:45:19Z

colorize sttus cells

Multix: status tables

2012-02-24T09:27:38Z

status tables

Multix: Apply framework

2012-02-24T08:52:28Z

Apply framework

Multix: /* SWK Browser */

2010-10-23T14:13:30Z

SWK Browser

Hns: /* Source Code */

2010-02-06T12:50:25Z

Source Code

Hns: /* How it Works */

2010-01-13T12:47:48Z

How it Works

Hns: /* Status */

2010-01-13T12:45:37Z

Status

Hns: /* Status */

2010-01-13T12:45:12Z

Status

Hns: /* How it Works */

2008-01-21T08:11:04Z

How it Works

Hns: /* Status */

2008-01-21T08:03:19Z

Status

@@ Line 93: / Line 93: @@
 |-
 |Forms
+|style="background:orange" |
 |Basic form elements (fieds, buttons) work.
 |-
 |Frames
+|style="background:orange" | Basic
 | Basic frames work.
 |+
@@ Line 105: / Line 105: @@
 |-
 | Lists
+|style="background:orange" |
 | Parsed, displayed, not formatted correctly. Ordered lists do not count.
 |-
 |Tables
+|style="background:red" |
 |Partially supported only on Cocoa. Formatting is rough. GNUstep and myStep lack support.
 |}

@@ Line 41: / Line 41: @@
 == Status ==
 Features of the Subversion (SVN) trunk code:
 * parses (X)HTML into a DOM tree

@@ Line 1: / Line 1: @@
 === SimpleWebKit ===
@@ Line 132: / Line 144: @@
 * @import ed sheets are loaded as needed
 * the CSS is not yet applied to the HTML -> NSAttributedString translation

← Older revision		Revision as of 14:13, 23 October 2010
Line 58:		Line 58:

	We have compiled Simple WebKit and SWK Browser with Cocoa so that it runs natively on a Mac.		We have compiled Simple WebKit and SWK Browser with Cocoa so that it runs natively on a Mac.
		+
		+	SWK Browser has been ported to GNUstep as well and runs using NIB loading without any additional code change.

	Download it here: [http://www.quantum-step.com/download/SWKBrowser.app.zip]		Download it here: [http://www.quantum-step.com/download/SWKBrowser.app.zip]

@@ Line 12: / Line 12: @@
 == Source Code ==
 svn+ssh://user@svn.gna.org/svn/gnustep/libs/simplewebkit/trunk
 http://svn.gna.org/viewcvs/gnustep/libs/simplewebkit/trunk
 == Status ==

@@ Line 114: / Line 114: @@
 * uses Foundation for basic types (string, number, boolean, null)
 * uses WebScriptObject as the base Object representation
-* DOMObjects are a subclass of WebScriptObjects and therefore provide bridging, so that changing a DOMHTML tree element through JavaScript automativally triggers the appropriate WebDocumentView notification
+* DOMObjects are a subclass of WebScriptObjects and therefore provide bridging, so that changing a DOMHTML tree element through JavaScript automatically triggers the appropriate WebDocumentView update notification
 . the CSS engine
-* has to be written
+* CSS style sheets are translated into a DOMCSS tree
-* shall have three components: CSS database, CSS parser, CSS evaluator
+* @import ed sheets are loaded as needed
 == Contact ==

@@ Line 28: / Line 28: @@
 * handles <frame>
 * handles <form>
-* handles <table> (if the NSTextView backend can handle)
+* handles < table > (if the NSTextView backend can handle)
 * has an ECMAScript engine that parses 90% of the syntax and evaluates expressions (missing are Statements and the native Objects including "document", "window", "event" etc.)

@@ Line 21: / Line 21: @@
 Features of the Subversion (SVN) trunk code:
 * parses (X)HTML into a DOM tree
-* renders approx. 90% of the HTML 4.0 tags in a reasonable way (e.g. < font color="#667788">, < center>, < h2>, works)
+* renders approx. 98% of the HTML 4.0 tags in a reasonable way (e.g. < font color="#667788">, < center>, < h2>, works)
 * makes <a> links clickable and processes them
 * loads <img>
 * loads <script> etc. asynchronously i.e. loads them as subresources
-* is prepared to handle <frame>
+* loads CSS etc. asynchronously i.e. loads them as subresources
-* is prepared to handle <form>
+* handles <frame>
 * has an ECMAScript engine that parses 90% of the syntax and evaluates expressions (missing are Statements and the native Objects including "document", "window", "event" etc.)
 Missing:
 * properly compile and run <script>
 * completion of the ECMAScript engine
-* all CSS processing
+* properly parse and apply CSS
 == SWK Browser ==

@@ Line 77: / Line 77: @@
 * it provides an estimated content length (for a progress indicator) and the MIMEType of the incoming data stream
 * as soon as the header comes in a WebDocomentRepresentation is created and incoming segments are notified
-* it also collects the incoming data, so that a WebDocomentRepresentation can handle either segments or the collected data
+* it also collects the incoming data, so that a WebDocumentRepresentation can handle either segments or the collected data
 . the WebDocumentRepresentation(s)
@@ Line 86: / Line 86: @@
 * so, if you want to handle an additional MIME type, write a class that conforms to the WebDocumentRepresentation protocol
-. the DOMHTMLTree
+. NSXMLParser
-* is only for HTML content
+* a private variant is used that adds a stalling mechanism and selection of the file encoding
-* is (re)built each time a new segment of HTML data comes in
+* recognizes the <?xml> tag for XHTML and has a lazy mode for pure HTML
 * any change in the DOMHTMLTree is notified to the WebDocumentView (or one of its subviews) by setNeedsLayout
 . the WebDocumentView(s) an its subviews
 * are responsible for displaying the contents of its WebDataRepresentation
 * either HTML, Images, PDF or whatever (e.g. SVG, XML, ...)
@@ Line 99: / Line 106: @@
 * for HTML, we do a simple trick: the WebDocumentView is an NSTextView and the DOMHTMLTree objects can be traversed to return an attributedString with embedded Tables and NSTextAttachments
 . the JavaScript engine
 * is programmed according to the specificaion of [[http://www.ecma-international.org/publications/standards/Ecma-262.htm] ECMA-262]
 * uses a simple recursive stateless parser (could be optimized in stack useage and speed by a state-table driven approach)
@@ Line 108: / Line 115: @@
 * uses WebScriptObject as the base Object representation
 * DOMObjects are a subclass of WebScriptObjects and therefore provide bridging, so that changing a DOMHTML tree element through JavaScript automativally triggers the appropriate WebDocumentView notification
 == Contact ==