jsgui3-server 0.0.121 → 0.0.123

package/resources/jsbuilder/JS_AST/JS_AST_Node_8-Features.js

@@ -1,65 +1,65 @@
-//const babel_node_tools = require('../babel/babel_node_tools');
-
-//const { each } = require('lang-tools');
-const JS_AST_Node_Query = require('./JS_AST_Node_7-Query');
-
-
-
-
-
-
-
-
-
-class JS_AST_Node_Features extends JS_AST_Node_Query {
-    constructor(spec = {}) {
-        super(spec);
-        // Getting the assigned values also seems important.
-        // Possibly will be made into some kind of autoquery? Or may be better to do queries lazily, and store the results.
-        
-        // Declared Object features inside a node.
-
-        // If a node 'features' declared objects, then the syntax in which they are declared is not so important.
-        //  This is an abstraction level above that.
-
-        // Want to keep it faitrly generic at this stage
-        //  Will do more with root node interpretation for the moment I expect.
-        //  First priority is to get everything linking together properly in an output file.
-        //  
-        const arr_features_declared_object = [];
-        const features = [];
-        const map_arr_features_by_feature_name = {
-            
-        }
-        Object.defineProperty(this, 'features', {
-            get() { 
-                //if (!features) {
-                //    features = [];
-                //}
-                return features;
-            },
-            //set(newValue) { bValue = newValue; },
-            enumerable: true,
-            configurable: false
-        });
-
-        // get literal names
-        //  or is it value
-
-        // // Assignment Feature?
-
-
-        // Document features make the most sense to work on from the API point of view.
-        //  Or root node features really.
-
-        // Will try loading up and querying an interpreted root node.
-        //  Or jsgui root node interpreted?
-        // Even with that Object.assign trick, we can make it aware, keep that in the general purpose code.
-
-
-        // The imports and exports features are important for linking together the documents.
-        
-    }
-}
-
+//const babel_node_tools = require('../babel/babel_node_tools');
+
+//const { each } = require('lang-tools');
+const JS_AST_Node_Query = require('./JS_AST_Node_7-Query');
+
+
+
+
+
+
+
+
+
+class JS_AST_Node_Features extends JS_AST_Node_Query {
+    constructor(spec = {}) {
+        super(spec);
+        // Getting the assigned values also seems important.
+        // Possibly will be made into some kind of autoquery? Or may be better to do queries lazily, and store the results.
+        
+        // Declared Object features inside a node.
+
+        // If a node 'features' declared objects, then the syntax in which they are declared is not so important.
+        //  This is an abstraction level above that.
+
+        // Want to keep it faitrly generic at this stage
+        //  Will do more with root node interpretation for the moment I expect.
+        //  First priority is to get everything linking together properly in an output file.
+        //  
+        const arr_features_declared_object = [];
+        const features = [];
+        const map_arr_features_by_feature_name = {
+            
+        }
+        Object.defineProperty(this, 'features', {
+            get() { 
+                //if (!features) {
+                //    features = [];
+                //}
+                return features;
+            },
+            //set(newValue) { bValue = newValue; },
+            enumerable: true,
+            configurable: false
+        });
+
+        // get literal names
+        //  or is it value
+
+        // // Assignment Feature?
+
+
+        // Document features make the most sense to work on from the API point of view.
+        //  Or root node features really.
+
+        // Will try loading up and querying an interpreted root node.
+        //  Or jsgui root node interpreted?
+        // Even with that Object.assign trick, we can make it aware, keep that in the general purpose code.
+
+
+        // The imports and exports features are important for linking together the documents.
+        
+    }
+}
+
 module.exports = JS_AST_Node_Features;

package/resources/jsbuilder/JS_AST/JS_AST_Node_9-Planning.js

@@ -1,32 +1,32 @@
-const JS_AST_Node_Index = require('./JS_AST_Node_8-Features');
-
-class JS_AST_Node_Planning extends JS_AST_Node_Index {
-    constructor(spec = {}) {
-        super(spec);
-
-        // sets the childnodes here.
-        //  will also make available the relevant bable properties.
-
-        // Use the lower level tools to kind of understand the node.
-        //  Provide property getters that will do this.
-
-        // Seeing what pattern / recognised object / pattern it is.
-
-        // plan_variable_name_remapping
-
-        // Will be fastest to carry out multiple changes at once in one iteration.
-        //  May use quite standard babel transform syntax once I have the changes arranged in a nice object that makes them clear.
-
-        // Set up more ctrl-alt-\ then a letter remappings.
-        //  Can use that to quickly type a varierty of snippets.
-
-        
-        
-
-    }
-    plan_variable_name_remapping() {
-        this.each_inner_declaration_declarator_identifier()
-    }
-}
-
+const JS_AST_Node_Index = require('./JS_AST_Node_8-Features');
+
+class JS_AST_Node_Planning extends JS_AST_Node_Index {
+    constructor(spec = {}) {
+        super(spec);
+
+        // sets the childnodes here.
+        //  will also make available the relevant bable properties.
+
+        // Use the lower level tools to kind of understand the node.
+        //  Provide property getters that will do this.
+
+        // Seeing what pattern / recognised object / pattern it is.
+
+        // plan_variable_name_remapping
+
+        // Will be fastest to carry out multiple changes at once in one iteration.
+        //  May use quite standard babel transform syntax once I have the changes arranged in a nice object that makes them clear.
+
+        // Set up more ctrl-alt-\ then a letter remappings.
+        //  Can use that to quickly type a varierty of snippets.
+
+        
+        
+
+    }
+    plan_variable_name_remapping() {
+        this.each_inner_declaration_declarator_identifier()
+    }
+}
+
 module.exports = JS_AST_Node_Planning;

package/resources/jsbuilder/JS_AST/JS_AST_Node_Arrangement.js

@@ -1,15 +1,15 @@
-// A way / structure in which JS_AST_Node objects are arranged.
-
-//  Specifying conditions on the item and on the parents.
-
-// A feature could use different optional arrangements.
-
-// Getting more out of syntax matching with trees and signatures would be of use.
-
-// Arrangement of nodes
-
-// Maybe do this work on it later on.
-//  It gets into some further objects and algorithms involving trees.
-
-
-
+// A way / structure in which JS_AST_Node objects are arranged.
+
+//  Specifying conditions on the item and on the parents.
+
+// A feature could use different optional arrangements.
+
+// Getting more out of syntax matching with trees and signatures would be of use.
+
+// Arrangement of nodes
+
+// Maybe do this work on it later on.
+//  It gets into some further objects and algorithms involving trees.
+
+
+