jsgui3-server 0.0.113 → 0.0.115

package/examples/controls/11) window, mirrored text fields/client.js

@@ -0,0 +1,340 @@
+const jsgui = require('jsgui3-client');
+const {controls, Control, mixins} = jsgui;
+const {dragable} = mixins;
+
+
+const {Checkbox, Date_Picker, Text_Input, Text_Field} = controls;
+
+const Active_HTML_Document = require('../../../controls/Active_HTML_Document');
+
+// Will make Date_Picker use progressive enhancement.
+//   On activation would create a new element? Create a new sibling?
+//     May want code that checks for .el being changed.
+
+
+
+
+
+
+class Demo_UI extends Active_HTML_Document {
+    constructor(spec = {}) {
+        spec.__type_name = spec.__type_name || 'demo_ui';
+        super(spec);
+        const {context} = this;
+
+        // Make sure it requires the correct CSS.
+        //  Though making that 'effortless' on the server may help more.
+
+
+        // Maybe can't do this here???
+
+        // Does not have .body (yet) on the client.
+        //   simple way to get the client to attach the body of the Active_HTML_Document?
+        //     maybe with jsgui-data-controls?
+        //   Though automatically having the .body property available on the client without sending extra HTTP
+        //     plumbing will help.
+
+        // .body will not be available before activation.
+
+
+        // .body should not be a normal function....?
+        //   a getter function would be better.
+
+
+        if (typeof this.body.add_class === 'function') {
+            this.body.add_class('demo-ui');
+        }
+
+        //console.log('this.body', this.body);
+        //console.log('this.body.add_class', this.body.add_class);
+
+
+        const compose = () => {
+            // put 20 of them in place.
+
+            // Then how to arrange them...?
+
+
+
+
+            const window = new controls.Window({
+                context: context,
+                title: 'jsgui3-html Mirrored Text_Input controls',
+                pos: [5, 5]
+            });
+
+            window.size = [480, 160];
+
+            // Have Tab_Page items inside???
+
+            // Setting a 'selectable' property at the composition stage could be very helpful in some cases,
+            //   May want composition-level mixins?
+            //   Maybe those mixins would also have code that runs on activation.
+            //     'compositional mixins' ???
+
+            // Need mixins to be very flexible to avoid the probles React had with them.
+            //   Choose what functionality the mixin provides in some cases.
+            //     Need to keep tight control over the coupling of mixins.
+            //   Each mixin may need to be somewhat complex to avoid hiccups - and to consistently act in the set modes.
+            //     If a mixin is to do something different to before that functionality should be called differently.
+
+            // mixin.enabled_feature_sets = [feature_set_1_name, feature_set_2_name] ....
+
+
+
+            // Will work on more options & perfection for month_view.
+
+            /*
+
+            new Checkbox({
+                context,
+                label: {
+                    text: 'A checkbox'
+                }
+            })
+
+            */
+            
+            // Sensible properties like this will help.
+            
+            // A progressively enhancing control could help a lot.
+            //   Something that when it's in the doc will even replace its own element.
+            //   Lower level code to enable really simple to express progressive enhancement could help, maybe would not be needed.
+
+
+
+
+
+            const ti1 = new Text_Field({
+                context,
+                text: 'A'
+                //label: {
+                //    text: 'A checkbox'
+                //}
+            })
+
+            window.inner.add(ti1);
+
+            const ti2 = new Text_Field({
+                context,
+                text: 'B'
+                //label: {
+                //    text: 'A checkbox'
+                //}
+            })
+
+            window.inner.add(ti2);
+
+            this.body.add(window);
+
+
+
+            
+            this._ctrl_fields = this._ctrl_fields || {};
+            this._ctrl_fields.ti1 = ti1;
+            this._ctrl_fields.ti2 = ti2;
+
+
+        }
+        if (!spec.el) {
+            compose();
+        }
+    }
+    activate() {
+        if (!this.__active) {
+            super.activate();
+            const {context, ti1, ti2} = this;
+
+            console.log('activate Demo_UI');
+            // and events dealing with changes to those tis.
+
+            // ti1, ti2.
+
+            // Some kind of tracking of what the event initiator could help?
+            //   Automatically avoiding feedback somehow???
+            //     If it gets changed to its current value it does not push the change...?
+
+
+            // a non-dom change???
+            //   or basically .view.model.change even????
+
+            // ti1.view.model.on('change') could be much clearer, disambiguating it from a dom change event.
+            //  assign .view.model events ....?
+            //    doing this on a lower level would help.
+
+            // Just creating .view and .view.model objects (getters and setters specified) in jsgui3-html will help
+            // when referring to them.
+
+
+
+
+            // ti1.value.on('change') ????
+            //   where the value is an Evented_Class or even Data_Object????
+            //    and where we can also get the value out of it easily / do so automatically, maybe within other useful functions.
+
+
+            // ti1.model.on('change') ????
+            //  or .view.model to be most specific for the moment...?
+            //   and raise those events within the controls on those .view.model objects.
+
+            // Maybe just try it on Text_Field for the moment.
+
+
+
+            // Need to work on having it update the dom with value changes....
+
+            ti1.view.model.on('change', e => {
+                //console.log('ti1 change e', e);
+
+
+                if (e.property_name === 'value') {
+                    if (e.value !== e.old) {
+                        ti2.value = e.value;
+                    }
+                }
+
+                // setting ti2.view.model.value even????
+                
+
+                
+
+            })
+            ti2.view.model.on('change', e => {
+                //console.log('ti2 change e', e);
+
+                // 
+
+                if (e.value !== e.old) {
+                    ti1.value = e.value;
+                }
+
+                
+            })
+
+            // listen for change events.
+            //   would be nice to know which change events originated from the user interacting with that specific HTML element (or ctrl???)
+
+            // e.from_user === true test.
+
+            // e.user_initiated_on_this ????
+
+
+
+
+            //console.log('activate Demo_UI');
+            // listen for the context events regarding frames, changes, resizing.
+
+            context.on('window-resize', e_resize => {
+                
+                // Could see about having some window contents bound through CSS to the size of the window.
+                //   Though having a framework of adjusting CSS from the JS on-the-fly could work too.
+
+                // May be done with the 'bind' mixin, or will make more specific mixins to do things like bind
+                //   a control to the space within another control, space within a specific part of that control.
+
+                // Or bind to parent size. That should be possible with CSS though.
+                //   May make some controls make more use of CSS by default
+                //   Or having an absolutely positioned box model used extensively could avoid some ambiguity, though
+                //     making use of and supporting generally respected CSS features will help too.
+
+                //console.log('window-resize', e_resize);
+
+                // Make all internal controls go absolute in terms of position
+                //   Remove them from their containers too?
+                //   Ie their containing divs?
+
+                // Would be nice to do this really simple with a fn call or very simple piece of code.
+                // Like get absolute position, set position to be absolute, move to that position.
+                // Maybe something within jsgui3-client helps with this, this is more about what needs to be done on the client.
+                //   Though recognising perf implications, it's (more) OK to include client-side functionality in jsgui3-html.
+
+
+
+
+
+
+            });
+
+        }
+    }
+}
+
+// Include this in bundling.
+//  Want CSS bundling so that styles are read out from the JS document and compiled to a stylesheet.
+
+//controls.Demo_UI = Demo_UI;
+
+// A css file may be an easier way to get started...?
+//  Want to support but not require css in js.
+
+// But need to set up the serving of the CSS both on the server, and on the client.
+//  Ofc setting it up on the server first is important - then can that stage set it up in the doc sent to the client?
+
+// Including the CSS from the JS like before.
+//  Needs to extract the CSS and serve it as a separate CSS file.
+//  Should also have end-to-end regression tests so this does not break again in the future.
+//   The code was kind of clunky and got refactored away.
+//   
+
+// Would need to parse the JS files to extract the CSS.
+//  Maybe could do it an easier way??? Now that it's easy, want a faster way.
+
+
+Demo_UI.css = `
+
+* {
+    margin: 0;
+    padding: 0;
+}
+
+body {
+    overflow-x: hidden;
+    overflow-y: hidden;
+    background-color: #E0E0E0;
+}
+
+.demo-ui {
+    
+    /* 
+
+    display: flex;
+    flex-wrap: wrap;
+    
+    flex-direction: column; 
+    justify-content: center;
+    align-items: center;
+    text-align: center;
+    min-height: 100vh;
+    */
+    
+}
+`;
+
+// But may want to remove them from that flex upon picking up / dropping them.
+//  Maybe best upon drop.
+
+// Maybe want other examples that use absolute positioning to position the items at the start?
+// 
+
+
+
+//controls.Square_Box = Square_Box;
+// could export jsgui with the updated controls....
+//  so that they are in the correct Page Context.?
+
+
+controls.Demo_UI = Demo_UI;
+
+module.exports = jsgui;
+
+/*
+module.exports = {
+    Square_Box: Square_Box,
+    Demo_UI: Demo_UI
+}
+*/
+
+// Then if window...?
+
+// Need to add the Square_Box control to the context or original map of controls...
+

package/examples/controls/11) window, mirrored text fields/server.js

@@ -0,0 +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');
+            }
+        });
+    })
+
+    
+
+}

package/package.json

@@ -12,10 +12,10 @@
     "esbuild": "^0.19.5",
     "fnl": "^0.0.30",
     "fnlfs": "^0.0.29",
-    "jsgui3-client": "^0.0.99",
-    "jsgui3-html": "^0.0.137",
-    "jsgui3-webpage": "^0.0.6",
-    "jsgui3-website": "^0.0.6",
+    "jsgui3-client": "^0.0.101",
+    "jsgui3-html": "^0.0.139",
+    "jsgui3-webpage": "^0.0.7",
+    "jsgui3-website": "^0.0.7",
     "lang-tools": "^0.0.22",
     "multiparty": "^4.2.3",
     "ncp": "^2.0.0",
@@ -25,14 +25,11 @@
     "url-parse": "^1.5.10"
   },
   "commentDeps": {
-    "jsgui3-html": "0.0.102",
     "babel-plugin-minify-dead-code-elimination": "^0.5.0",
     "babel-plugin-remove-comments": "^2.0.0",
     "babel-plugin-transform-class": "^0.3.0",
     "babel-plugin-transform-es2015-classes": "^6.24.1",
-    "babel-plugin-transform-es2015-object-super": "^6.24.1",
-    "iltorb": "^2.4.3",
-    "lang-mini": "^0.0.25"
+    "babel-plugin-transform-es2015-object-super": "^6.24.1"
   },
   "engines": {
     "node": ">=15.0.0"
@@ -43,5 +40,5 @@
     "type": "git",
     "url": "https://github.com/metabench/jsgui3-server.git"
   },
-  "version": "0.0.113"
+  "version": "0.0.115"
 }

package/resources/website-javascript-resource.js

@@ -155,7 +155,7 @@ const call_multi = jsgui.call_multi,
 //var zlib = require('zlib');
 const util = require('util');
 
-const browserify = require('browserify');
+//const browserify = require('browserify');
 const babel = require('@babel/core');
 
 // Extends AutoStart_Resource?
@@ -233,6 +233,9 @@ class Site_JavaScript extends Resource {
 
 	'build_client'(callback) {
 
+		console.trace();
+		throw 'Deprecated';
+
 		// Configurable building mechanisms....
 		//  Want to provide jsgui events / logs on the build process.
 
@@ -269,6 +272,9 @@ class Site_JavaScript extends Resource {
 		var app_path = appDir + '/js/app.js';
 		var app_bundle_path = appDir + '/js/app-bundle.js';
 		var wstream = fs.createWriteStream(app_bundle_path);
+
+
+
 		var b = browserify();
 		//b.require(app_path, {
 		//	entry: true,