jsgui3-server 0.0.121 → 0.0.122

package/examples/controls/9b) window, shared data.model mirrored date pickers/server.js

@@ -1,118 +1,118 @@
-const jsgui = require('./client');
-
-const {Demo_UI} = jsgui.controls;
-const Server = require('../../../server');
-
-
-// what would be the (best?) way to include the whole thing in one JS file?
-//  Maybe don't try that right now.
-//  maybe standardise on the dir, then client.js and server.js inside.
-
-
-
-// Want to exclude this from the client bundle.
-//  Some kind of marking to say that it's server-side only?
-
-// Need to include JSGUI3 js within the client document.
-//   Seems like an earlier code simplification removed this functionality?
-//   Just specifying a Ctrl for the server - and giving it the 'disk_path_client_js'.
-//     May as well fix that....
-
-
-// The server code may be tiny, it seems best not to abstract it away totally though.
-// At least not for the moment.
-
-
-
-
-
-if (require.main === module) {
-
-    // By default should include the JS and the CSS.
-    // By reference, serving them from their respective paths.
-
-
-    // This API is not working right now.
-
-    // A very simple syntax for running a single control would be great.
-
-    // Need to in the default (server) configuration build and serve the client-side app.
-    // Want to be able to make interactive apps quickly with minimal server side code that needs to be written as boilerplate to
-    // get the app running.
-
-    // Though maybe defining a webpage, that serves the client js, and renders the control on the server, and activates it on the client,
-    // would be the right approach.
-
-    // Want to make the code really explicit, in a simple way.
-
-
-    // eg { '/': Demo_UI }
-    // eg { '*': Demo_UI }
-    //  as at least it explicitly assigns it to the '/' route
-
-
-    // But worth keeping the '/' Ctrl property?
-    //  Could change it to explicitly setting the route(s).
-
-    // Do want it to build the client js on start.
-
-    // Could extract the CSS from the file itself, or maybe better reading it from the classes and objects that are loaded / referenced.
-    // All kinds of complex server program structures exist already, so could use Publishers if needed for some things.
-    //  But need to keep the surface-level API really simple.
-
-    // Maybe define a Webpage and maybe use / define an HTML_Webpage_Publisher for example too.
-    // The clearest code would be really explicit about what it does, but in terms of almost English idioms
-    //  and on the surface-level not spelling out in great detail what it's doing, but referencing objects and
-    //  instructions with clear purposes, though details could be obscure at the top level. Eg it's the publisher's responsibility
-    //  to include the CSS and JS that's needed to get it to run. A publisher is referenced and used, and it does its thing.
-
-    // The Server could automatically involk the use of a Publisher.
-    //  May be better to either require or recommend more explicit code, have them in the examples,
-    //  but also to document some shortcuts, defaults, and abbreviations (though they may omit some essential info, so not recommended for beginners)
-
-    // Could have a tabbed view for examples for 'explicit' and 'short' notations when there are multiple.
-
-    // jsgui3-html-suite may be of use, for some more extended controls that are built on top of jsgui3-html, but not specifically
-    // client or server.
-
-
-
-
-
-
-    const server = new Server({
-        Ctrl: Demo_UI,
-        //debug: true,
-        // Giving it the Ctrl and disk path client js should enable to server to get the JS-bundled CSS from the file(s).
-        //  Putting the JS files through proper parsing and into a syntax tree would be best.
-
-        //'js_mode': 'debug',
-        'src_path_client_js': require.resolve('./client.js'),
-        //debug: true // should not minify the js, should include the symbols.
-        //js_client: require.resolve('./square_box.js')
-    });
-    // A callback or event for when the bundling has been completed
-    //  a 'ready' event.
-
-    // then start the server....
-    // be able to choose the port / ports?
-    console.log('waiting for server ready event');
-    server.one('ready', () => {
-        console.log('server ready');
-
-        // server start will change to observable?
-
-        server.start(8080, function (err, cb_start) {
-            if (err) {
-                throw err;
-            } else {
-                // Should have build it by now...
-    
-                console.log('server started');
-            }
-        });
-    })
-
-    
-
+const jsgui = require('./client');
+
+const {Demo_UI} = jsgui.controls;
+const Server = require('../../../server');
+
+
+// what would be the (best?) way to include the whole thing in one JS file?
+//  Maybe don't try that right now.
+//  maybe standardise on the dir, then client.js and server.js inside.
+
+
+
+// Want to exclude this from the client bundle.
+//  Some kind of marking to say that it's server-side only?
+
+// Need to include JSGUI3 js within the client document.
+//   Seems like an earlier code simplification removed this functionality?
+//   Just specifying a Ctrl for the server - and giving it the 'disk_path_client_js'.
+//     May as well fix that....
+
+
+// The server code may be tiny, it seems best not to abstract it away totally though.
+// At least not for the moment.
+
+
+
+
+
+if (require.main === module) {
+
+    // By default should include the JS and the CSS.
+    // By reference, serving them from their respective paths.
+
+
+    // This API is not working right now.
+
+    // A very simple syntax for running a single control would be great.
+
+    // Need to in the default (server) configuration build and serve the client-side app.
+    // Want to be able to make interactive apps quickly with minimal server side code that needs to be written as boilerplate to
+    // get the app running.
+
+    // Though maybe defining a webpage, that serves the client js, and renders the control on the server, and activates it on the client,
+    // would be the right approach.
+
+    // Want to make the code really explicit, in a simple way.
+
+
+    // eg { '/': Demo_UI }
+    // eg { '*': Demo_UI }
+    //  as at least it explicitly assigns it to the '/' route
+
+
+    // But worth keeping the '/' Ctrl property?
+    //  Could change it to explicitly setting the route(s).
+
+    // Do want it to build the client js on start.
+
+    // Could extract the CSS from the file itself, or maybe better reading it from the classes and objects that are loaded / referenced.
+    // All kinds of complex server program structures exist already, so could use Publishers if needed for some things.
+    //  But need to keep the surface-level API really simple.
+
+    // Maybe define a Webpage and maybe use / define an HTML_Webpage_Publisher for example too.
+    // The clearest code would be really explicit about what it does, but in terms of almost English idioms
+    //  and on the surface-level not spelling out in great detail what it's doing, but referencing objects and
+    //  instructions with clear purposes, though details could be obscure at the top level. Eg it's the publisher's responsibility
+    //  to include the CSS and JS that's needed to get it to run. A publisher is referenced and used, and it does its thing.
+
+    // The Server could automatically involk the use of a Publisher.
+    //  May be better to either require or recommend more explicit code, have them in the examples,
+    //  but also to document some shortcuts, defaults, and abbreviations (though they may omit some essential info, so not recommended for beginners)
+
+    // Could have a tabbed view for examples for 'explicit' and 'short' notations when there are multiple.
+
+    // jsgui3-html-suite may be of use, for some more extended controls that are built on top of jsgui3-html, but not specifically
+    // client or server.
+
+
+
+
+
+
+    const server = new Server({
+        Ctrl: Demo_UI,
+        //debug: true,
+        // Giving it the Ctrl and disk path client js should enable to server to get the JS-bundled CSS from the file(s).
+        //  Putting the JS files through proper parsing and into a syntax tree would be best.
+
+        //'js_mode': 'debug',
+        'src_path_client_js': require.resolve('./client.js'),
+        //debug: true // should not minify the js, should include the symbols.
+        //js_client: require.resolve('./square_box.js')
+    });
+    // A callback or event for when the bundling has been completed
+    //  a 'ready' event.
+
+    // then start the server....
+    // be able to choose the port / ports?
+    console.log('waiting for server ready event');
+    server.one('ready', () => {
+        console.log('server ready');
+
+        // server start will change to observable?
+
+        server.start(8080, function (err, cb_start) {
+            if (err) {
+                throw err;
+            } else {
+                // Should have build it by now...
+    
+                console.log('server started');
+            }
+        });
+    })
+
+    
+
 }

package/examples/controls/__old/_html-server-color-palette.js

@@ -1,115 +1,115 @@
-/**
- * Created by James on 02/10/2016.
- */
-
-// This one will need to activate on the client.
-//  Really want the whole thing to be in one file.
-//  Possible to have a standard activation?
-//
-// Or we need to have a client-side control?
-//
-// Some of the wiring could be done automatically.
-//
-
-var jsgui = require('jsgui3-html');
-
-
-var Start_Stop_Toggle_Button = jsgui.Start_Stop_Toggle_Button;
-var Color_Palette = jsgui.Color_Palette;
-
-var Server = require('../../../server');
-var port = 8000;
-var Server_Page_Context = require('../../../page-context');
-
-var server = new Server({
-	'routes': {
-		'*': {
-			'name': 'HTML Server'
-		}
-	}
-	
-});
-
-var resource_pool = server.resource_pool;
-
-// Rendering single page controls makes a lot of sense.
-//  It means the activation code can be contained better there.
-
-//console.log('resource_pool', resource_pool);
-//console.log('resource_pool.resources', resource_pool.resources);
-
-// The start stop toggle button would need to be registered on the client side.
-//  May be worth it to have the standard controls registered to start with.
-//  Or to have the app know which controls are used, so it can register them.
-
-// Get the website resource
-
-
-
-// Caching items / resources by type?
-
-// Need to give the resources a name.
-
-
-//var website = resource_pool.get_resource('Server Router');
-
-//console.log('\n\n');
-
-//console.log('resource_names', resource_pool.get_resource_names());
-//throw 'stop';
-var server_router = resource_pool.get_resource('Server Router');
-
-
-
-//console.log('server_router', server_router);
-
-if (!server_router) {
-	throw 'no server_router';
-}
-
-var routing_tree = server_router.routing_tree;
-
-routing_tree.set('/', function (req, res) {
-	//console.log('root path / request');
-	var server_page_context = new Server_Page_Context({
-		'req': req,
-		'res': res,
-		'resource_pool': resource_pool
-	});
-	// Page_Bounds_Specifier
-	var hd = new jsgui.Client_HTML_Document({
-		'context': server_page_context
-	});
-	hd.include_client_css();
-	hd.include_js('/js/app-bundle-active.js');
-	var body = hd.body;
-	body.size = [800, 600];
-	var ctrl = new Color_Palette({
-		'context': server_page_context,
-		'size': [312, 312]
-	});
-	//var ctrl2 = new jsgui.Control({});
-	ctrl.resizable = true;
-	body.add(ctrl);
-	ctrl.active();
-	hd.all_html_render(function (err, deferred_html) {
-		if (err) {
-			throw err;
-		} else {
-			//console.log('deferred_html', deferred_html);
-			var mime_type = 'text/html';
-			//console.log('mime_type ' + mime_type);
-			res.writeHead(200, { 'Content-Type': mime_type });
-			res.end('<!DOCTYPE html>' + deferred_html, 'utf-8');
-		}
-	});
-});
-
-//console.log('pre server start');
-server.start(port, function (err, cb_start) {
-	if (err) {
-		throw err;
-	} else {
-		console.log('master server started');
-	}
+/**
+ * Created by James on 02/10/2016.
+ */
+
+// This one will need to activate on the client.
+//  Really want the whole thing to be in one file.
+//  Possible to have a standard activation?
+//
+// Or we need to have a client-side control?
+//
+// Some of the wiring could be done automatically.
+//
+
+var jsgui = require('jsgui3-html');
+
+
+var Start_Stop_Toggle_Button = jsgui.Start_Stop_Toggle_Button;
+var Color_Palette = jsgui.Color_Palette;
+
+var Server = require('../../../server');
+var port = 8000;
+var Server_Page_Context = require('../../../page-context');
+
+var server = new Server({
+	'routes': {
+		'*': {
+			'name': 'HTML Server'
+		}
+	}
+	
+});
+
+var resource_pool = server.resource_pool;
+
+// Rendering single page controls makes a lot of sense.
+//  It means the activation code can be contained better there.
+
+//console.log('resource_pool', resource_pool);
+//console.log('resource_pool.resources', resource_pool.resources);
+
+// The start stop toggle button would need to be registered on the client side.
+//  May be worth it to have the standard controls registered to start with.
+//  Or to have the app know which controls are used, so it can register them.
+
+// Get the website resource
+
+
+
+// Caching items / resources by type?
+
+// Need to give the resources a name.
+
+
+//var website = resource_pool.get_resource('Server Router');
+
+//console.log('\n\n');
+
+//console.log('resource_names', resource_pool.get_resource_names());
+//throw 'stop';
+var server_router = resource_pool.get_resource('Server Router');
+
+
+
+//console.log('server_router', server_router);
+
+if (!server_router) {
+	throw 'no server_router';
+}
+
+var routing_tree = server_router.routing_tree;
+
+routing_tree.set('/', function (req, res) {
+	//console.log('root path / request');
+	var server_page_context = new Server_Page_Context({
+		'req': req,
+		'res': res,
+		'resource_pool': resource_pool
+	});
+	// Page_Bounds_Specifier
+	var hd = new jsgui.Client_HTML_Document({
+		'context': server_page_context
+	});
+	hd.include_client_css();
+	hd.include_js('/js/app-bundle-active.js');
+	var body = hd.body;
+	body.size = [800, 600];
+	var ctrl = new Color_Palette({
+		'context': server_page_context,
+		'size': [312, 312]
+	});
+	//var ctrl2 = new jsgui.Control({});
+	ctrl.resizable = true;
+	body.add(ctrl);
+	ctrl.active();
+	hd.all_html_render(function (err, deferred_html) {
+		if (err) {
+			throw err;
+		} else {
+			//console.log('deferred_html', deferred_html);
+			var mime_type = 'text/html';
+			//console.log('mime_type ' + mime_type);
+			res.writeHead(200, { 'Content-Type': mime_type });
+			res.end('<!DOCTYPE html>' + deferred_html, 'utf-8');
+		}
+	});
+});
+
+//console.log('pre server start');
+server.start(port, function (err, cb_start) {
+	if (err) {
+		throw err;
+	} else {
+		console.log('master server started');
+	}
 });