updated notes...

Signed-off-by: Alex A. Naanou <alex.nanou@gmail.com>

ui (gen4)/doc/BUILD-NOTES

@@ -26,8 +26,7 @@ Sharp
 
 To build sharp for a specific version of node:
 	cd ./node_modules/sharp/
-	node-gyp --target=v5.7.0 rebuild	# v5.7.0 is the version 
-						# of node used in nw.js
+	nw-gyp rebuild --target=0.17.4 --arch=x64
 
 
 Speedup loading of app

ui (gen4)/doc/NOTES

@@ -6,13 +6,13 @@ Most of the system is loaded via browser context RequireJS loader, in
 node/nw context node-specific stuff is loaded with a second node-enabled
 RequireJS instance or node require.
 
-This is done to:
-	- Minimize the difference between pure browser, nw and node 
-	  versions
-	- Enable devtools introspection on most modules.
-	  NOTE: his is mostly due to the inability to view the node 
-	 	context in nw.js devtools, when this is resolved this
-		point should be revised.
+The ideal solution would be to use one require that sees both the browser
+and node contexts, the problem is exactly in this, the browser requirejs
+does not see either node or node modules while the node require loads code
+that is not visible to devtools unless it is running at that exact moment.
+
+Thus we are forced to use both mode requirejs loaders which may be 
+confusing at times.
 
 
 Different loaders:

ui (gen4)/features/filesystem.js

@@ -2081,7 +2081,6 @@ var FileSystemWriterActions = actions.Actions({
 									.replace(/%I/, I)
 
 									// totals...
-									// XXX revise...
 									.replace(/%t/, len)
 									.replace(/%T/, total_len)