You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+6-6Lines changed: 6 additions & 6 deletions
Original file line number
Diff line number
Diff line change
@@ -1,6 +1,6 @@
1
1
Introduction
2
2
============
3
-
This is a NodeJS module for WebKit. With this module, your Javascript code in HTML can call NodeJS functions directly. The following demo lists the current directory in the page:
3
+
This is a NodeJS module for WebKit. With this module, your Javascript code in the DOM context can call NodeJS functions directly. The following demo lists the current directory on the page:
4
4
5
5
<html><head>
6
6
<title>testfs</title>
@@ -22,7 +22,7 @@ This is a NodeJS module for WebKit. With this module, your Javascript code in HT
22
22
</body>
23
23
</html>
24
24
25
-
From NodeJS code, you can manipulate DOM or run Javascript in DOM context as well:
25
+
From NodeJS code, you can manipulate the DOM or run Javascript in the DOM context as well:
26
26
27
27
var nwebkit;
28
28
nwebkit = require('nwebkit');
@@ -36,7 +36,7 @@ From NodeJS code, you can manipulate DOM or run Javascript in DOM context as wel
36
36
Dependencies
37
37
============
38
38
39
-
A patched version of CEF(Chromium Embedded Framework) is need to make this possible. Prebuilt binaries are available for Linux (Debian and Ubuntu), Windows and OSX.
39
+
A patched version of CEF(Chromium Embedded Framework) is needed to make this possible. Prebuilt binaries are available for Linux (Debian and Ubuntu), Windows and OSX.
40
40
41
41
The source of Chromium is at https://github.com/rogerwang/chromium
42
42
@@ -55,12 +55,12 @@ How it works
55
55
56
56
* Chromium's (render process) main loop is merged with libev's main loop in NodeJS, so they can run in the same process.
57
57
58
-
* WebKit is patched so the V8 context is merged (actually bridged) with the context from NodeJS. This makes NodeJS functions accessiable in web page.
58
+
* WebKit is patched so that the V8 context is merged (actually bridged) with the context from NodeJS. This makes NodeJS functions accessible in a web page.
59
59
60
60
Community
61
61
=========
62
62
63
-
Welcome to join the discussion in our mailing list:
63
+
You are welcome to join the discussion on our mailing list:
64
64
65
65
node-webkit@googlegroups.com
66
66
@@ -71,7 +71,7 @@ subscribe via node-webkit+subscribe@googlegroups.com
71
71
Our vision
72
72
==========
73
73
74
-
We believe that the async I/O framework in NodeJS and the Javascript programming language is a perfect combination for client (mobile) side applications. By bringing WebKit to NodeJS, a new way is avaliable to write applications with web technology. We'll contintue our development and support for this runtime. More platform and applications will be enabled.
74
+
We believe that the async I/O framework in NodeJS and the Javascript programming language is a perfect combination for client (mobile) side applications. By bringing WebKit to NodeJS, a new way is available to write applications with web technology. We'll continue our development and support for this runtime. More platform and applications will be enabled.
0 commit comments