dolf <dolfboek@hotmail.com> wrote in
news:aY-dnTw33_dBz8z8nZ2dnUU7-IHNnZ2d@giganews.com:

> This is actually a quasi-rational statement which is a product of the
> deficiency to selection process itself:
>
> If (not node.parent.selected && no child node selected) then *no*
> child nodes are included.
>
> It is rather more appropriate to conform to acceptable standards or
> customs of usage and set the folder selected accordingly …
>
> Since !0 produces a true result and !1 a false result it probably more
> suitable to deploy an binary state for the selected value:
>
> 2**0 = 1 as not selected
> 2**1 = 2 as selected
>
> Where a folder node can have a value 3 conveying that there are
> selected and non selected elements within.
>
Never a more truer explination Dolf.

> That shall be tomorrow‘s logical thinking task.
>
> - dolf
>
> dolf <dolfboek@hotmail.com> wrote:
>> DATE / GRAMMAR CORRECTION
>>
>> Currently our folders or listfolders multiple select option is
>> ubiquitous (ie. it ought to work with any d3.hierarchy()) and our
>> continuing task this week is to display the relevant context.
>>
>> Our example NOETIC / LEXICON data for a TELOS value #231 -
>> JUXTAPOSITION CONTROL is as follows:
>>
>> H3318
>> - 143
>> - 401
>> - 517
>> - 546
>>
>> So as to retain the ubiquitous design consideration we are going to
>> use the node.ancestors() -- array of nodes, starting with the
>> actionClick event node index to items obtained by the node.copy()
>> action, then followed by each parent node up to the root:
>>
>> actionClick: function (ev) {
>>
>> var el = d3.select(ev);
>>
>> var index = el.attr("name");
>> var f = GNOSIS.research.concepts.FOLDERS.folders;
>> var id = f.items[index].id
>> var selected = f.items[index].data._selected;
>>
>> console.log (f.items[index].ancestors()); <-- *EXAMPLE*
>> *ONLY*
>>
>> ...
>>
>> }
>>
>> And downwards by node.descendants() -- array of nodes, starting with
>> the actionClick event node index, then followed by each child node
>> down to the tree extent.
>>
>> Our first step to achieving any viable outcome is to determine what
>> action need to be undertaken that we ought to codify.
>>
>> Thusly the first action is to determine what type of node is related
>> to the actionClick() event.
>>
>> If the array [] has a length of 1 it then conveys the node index as a
>> tree extent.
>>
>> The next notion in order of precedence might be to determine whether
>> there are selected nodes. Such action might best be deduced from a
>> disparity been increased / decreased selection action.
>>
>> If (increased > decreased) then there is a further selection
>> consideration to be made:
>>
>> If (node.parent.selected && no child node selected) then *all*
>> child
>> nodes are included.
>>
>> However If (node.parent.selected && some child node selected)
>> then
>> *some* child nodes are included.
>>
>> So our first coding task is to implement the increase / decrease
>> variables within the folders {} data object within the FOLDERS
>> concept as part of the actionClick() event process and to ensure
>> these variables are re-initialised whenever the hierarchy changes
>>
>> On 25/9/21 15:47, dolf wrote:
>>> Our logical thinking weekend activity will be to code the folders or
>>> listfolders multiple select option and to display the relevant
>>> context.
>>>
>>> We’re going to undertake that task at a leisurely pace… our goal
>>> for such a rudimentary display action will be to cognize the grapple
>>> / lexicon spiral intersections to determine whether such data
>>> normalisation has any merit in representing reality.
>>>
>>> *UPDATE* As we speculated earlier that the d3.hierarchy {} object at
>>> this juncture is an iconoclasm against our existing method...
>>>
>>> That is the copy() function returns the sparse hierarchy elements
>>> only and not any id or selected included variables.
>>>
>>> So we are going to have to give some more thought to how best to
>>> resolve such conundrum which of necessity requires those variable
>>> elements to be exposed.
>>>
>>> IT IS LIKELY THAT WE'LL PLACE the id / selected variables within the
>>> data {} object since the associated data (node.data) can store
>>> whatever additional fields you like.
>>>
>>> *THAT* MISCONCEPTION HAS BEEN RESOLVED and we now have persistence
>>> for selected nodes.
>>>
>>> dolf <dolfboek@hotmail.com> wrote:
>>>> Having completed the instantiateFolders () as d3call we now need to
>>>> do the
>>>> same with a list view: instantiateListFolders() …
>>>>
>>>> So that will be our logical thinking task for today.
>>>>
>>>> dolf <dolfboek@hotmail.com> wrote:
>>>>> To traverse down the directory hierarchy we need to determine
>>>>> whether there are any children nodes:
>>>>>
>>>>> if (GNOSIS.research.concepts.FOLDERS.folders.items[index].children
>>>>> == null)
>>>>> return;
>>>>>
>>>>> GNOSIS.research.concepts.FOLDERS.folders.root =
>>>>> GNOSIS.research.concepts.FOLDERS.folders.items[index];
>>>>> GNOSIS.research.concepts.FOLDERS.folders.items = [];
>>>>> GNOSIS.research.concepts.FOLDERS.refresh = true;
>>>>>
>>>>> COINRULES.automate.grappleConcept ({
>>>>> handle: GNOSIS.grizzle.data.gizmo.id,
>>>>> place: `GIZMO-${GNOSIS.grizzle.data.gizmo.id}-INFO`,
>>>>> template: GNOSIS.research.concepts,
>>>>> notion: "FOLDERS"
>>>>> });
>>>>>
>>>>> And to traverse up the directory hierarchy we need to check the
>>>>> parent boundary:
>>>>>
>>>>> switch (true) {
>>>>> case (GNOSIS.research.concepts.FOLDERS.folders.parent == null) :
>>>>> GNOSIS.research.concepts.FOLDERS.folders.root =
>>>>> GNOSIS.scenario.noeticHierarchy;
>>>>> break;
>>>>> default :
>>>>> GNOSIS.research.concepts.FOLDERS.folders.root =
>>>>> GNOSIS.research.concepts.FOLDERS.folders.root.parent;
>>>>> }
>>>>>
>>>>> GNOSIS.research.concepts.FOLDERS.folders.items = [];
>>>>> GNOSIS.research.concepts.FOLDERS.refresh = true;
>>>>>
>>>>> COINRULES.automate.grappleConcept ({
>>>>> handle: GNOSIS.grizzle.data.gizmo.id,
>>>>> place: `GIZMO-${GNOSIS.grizzle.data.gizmo.id}-INFO`,
>>>>> template: GNOSIS.research.concepts,
>>>>> notion: "FOLDERS"
>>>>> });
>>>>>
>>>>> At this juncture our support for d3.hierarchy is ubiquitous in
>>>>> displaying either a folder or file icon depending upon the
>>>>> children[] array status.
>>>>>
>>>>> Since we've accomplished this before schedule, our weekend logical
>>>>> thinking activity will be to:
>>>>>
>>>>> a) Support a list directory view;
>>>>> b) Implement alternative icons;
>>>>> c) Enable support via the FOLDERS.know() function for alternatives
>>>>> to our default GNOSIS.scenario.noeticHierarchy{} structure
>>>>>
>>>>> But that is sufficient logical thinking for today.
>>>>>
>>>>> On 16/9/21 18:08, dolf wrote:
>>>>>> We've implemented the d3.hierarchy {} object without any .data()
>>>>>> joins, by instead copying the nodes pointer to the items[] array
>>>>>> which then exposes the hierarchy data.
>>>>>>
>>>>>> if (GNOSIS.research.concepts.FOLDERS.refresh)
>>>>>>     el.data(nodes, function (d) {
>>>>>>         if (d.depth == depth) {
>>>>>>             d.selected = false;
>>>>>>             items.push(d);
>>>>>>         }
>>>>>>     });
>>>>>> GNOSIS.research.concepts.FOLDERS.refresh = false;
>>>>>>
>>>>>> And given such feature, we'll deploy this approach.  Our weekend
>>>>>> activity will then be to implement the traversal capability.
>>>>>>
>>>>>> If we then designate the root variable which can be adjusted to
>>>>>> reflect the node traversal:
>>>>>>
>>>>>> folders: {
>>>>>>     initialise: undefined,
>>>>>>     select: false,
>>>>>>     depth: 1,
>>>>>>     root: GNOSIS.scenario.noeticHierarchy,
>>>>>>     items: []
>>>>>> },
>>>>>>
>>>>>> We can then do a node copy which will then return the new root
>>>>>> and the depth can be determined from that reference:
>>>>>>
>>>>>> var nodes = (GNOSIS.research.concepts.FOLDERS.folders.root) ?
>>>>>> GNOSIS.research.concepts.FOLDERS..folders.root.copy() :
>>>>>> undefined;
>>>>>>
>>>>>> ----------
>>>>>>
>>>>>> The reason why we are hesitant to implement the d3.hierarchy {}
>>>>>> object at this juncture is that such approach is an iconoclasm
>>>>>> against our existing method, and which doesn't provide sufficient
>>>>>> gain over a shallow hierarchy...
>>>>>>
>>>>>> We don't need any data binding which would be useful for complex
>>>>>> hierarchy structures...
>>>>>>
>>>>>> Nevertheless, we'll give some thought to an entirely d3 command
>>>>>> driven rather than our d3 template approach and determine which
>>>>>> is more elegant and efficient.
>>>>>>
>>>>>> That will be tomorrow's logical thinking task.
>>>>>>
>>>>>> dolf <dolfboek@hotmail.com> wrote:
>>>>>>> Our first approach to folders support for d3.hierarchy ought to
>>>>>>> be ubiquitous.  Since we are intentioned to navigate the
>>>>>>> children [] array we'll need to provide a '...' returning
>>>>>>> action.
>>>>>>>
>>>>>>> Accomplishing both functional capabilities will be our logical
>>>>>>> thinking task for the next day or two.
>>>>>>
>>>>>> Since we’re going to retain the lexicon {} object structure
>>>>>> within our scenario {} dataset. Our first approach is to create
>>>>>> the d3 directory / hierarchy {} datasets whenever the scenario
>>>>>> file is retrieved.
>>>>>>
>>>>>>     parseNoeticCognitions: function (noetic) {
>>>>>>
>>>>>>         var i = 0;
>>>>>>         var n = GNOSIS.scenario.noeticDirectory =  {
>>>>>>             "name": `Noetic`,
>>>>>>             "children":[],
>>>>>>             "type": NOETIC_ROOT
>>>>>>         }
>>>>>>
>>>>>>         for (var lex in noetic) {
>>>>>>             i = n.children.push ({
>>>>>>                 "name": lex,
>>>>>>                 "children":[],
>>>>>>                 "type": NOETIC_CONCEPT
>>>>>>             });
>>>>>>             for (var telos in noetic[lex]) {
>>>>>>                 if (isNaN(telos))
>>>>>>                     continue;
>>>>>>
>>>>>>                 n.children[i-1].children.push ({
>>>>>>                     "name": telos,
>>>>>>                     "children": null,
>>>>>>                     "type": NOETIC_TELOS
>>>>>>                 });
>>>>>>             }
>>>>>>         }
>>>>>>
>>>>>>         GNOSIS.scenario.noeticHierarchy = d3.hierarchy
>>>>>> (GNOSIS.scenario.noeticDirectory);
>>>>>>        
>>>>>> GNOSIS.research.concepts.FOLDERS.folders.initialise = undefined;
>>>>>>
>>>>>>     },
>>>>>>
>>>>>> Since our design goal is to make the FOLDERS concept entirely as
>>>>>> integral component, we’ve moved external variables into that
>>>>>> object:
>>>>>>
>>>>>> folders: {
>>>>>>         initialise: undefined,
>>>>>>         select: false
>>>>>> },
>>>>>>
>>>>>> The hierarchy can then be passed to the know () function.
>>>>>>
>>>>>>>
>>>>>>> <https://www.grapple369.com/gnosis/research.json>
>>>>>>>
>>>>>>> On 14/9/21 11:37, dolf wrote:
>>>>>>>> Our logical thinking task today will be to implement the select
>>>>>>>> / select all feature and following that interface enhancement
>>>>>>>> we'll implement support for d3.directory / d3.hierarchy...
>>>>>>>>
>>>>>>>> We've completed the select action which required a
>>>>>>>> consideration of persistence...
>>>>>>>>
>>>>>>>> Our next consideration is the select all action and we'll leave
>>>>>>>> the implementation of support for d3.directory / d3.hierarchy
>>>>>>>> as tomorrow's activity ...
>>>>>>>>
>>>>>>>> On 13/9/21 16:08, dolf wrote:
>>>>>>>>> we've put together a simple folders based view of the NOETIC
>>>>>>>>> LEXICON COGNITIONS as concept being an integral component and
>>>>>>>>> in doing so we resolved a stubborn error with the dialog
>>>>>>>>> resizing which occurred when the dialog height was set to
>>>>>>>>> document.body.scrollHeight at load.  That value is 0 until
>>>>>>>>> the document is rendered and so the proper value is
>>>>>>>>> screen.availHeight ...
>>>>>>>>>
>>>>>>>>> We still need to enhance our click / touch actions which are
>>>>>>>>> added to the <td> element within the simple code as follows:
>>>>>>>>>
>>>>>>
>>>>>> this.concepts["FOLDERS"] = {
>>>>>>     name: "folders",
>>>>>>     folders: {
>>>>>>         initialise: undefined,
>>>>>>         select: false,
>>>>>>         depth: 1,
>>>>>>         root: GNOSIS.scenario.noeticHierarchy,
>>>>>>         items: []
>>>>>>     },
>>>>>>
>>>>>>     initialise: function (id) {
>>>>>>
>>>>>>         this[0].id = `${this.name}-${id}`;
>>>>>>
>>>>>>         if
>>>>>> (d3.select(`#GIZMO-${GNOSIS.grizzle.data.gizmo.id}-INFO`).style
("d
>>>>>> isplay") == "none")
>>>>>>             return;
>>>>>>
>>>>>>     },
>>>>>>     0: {type: "div", class: "contentContainer", align:
>>>>>> "left", style: {"display": "inline-block"},
>>>>>>         0: {type: "br"},
>>>>>>         1: {type: "span", class: "innerElement", style:
>>>>>> {"margin": "2px", "padding": "1px", "width": "48px", "height":
>>>>>> "20px"}, align: "center", field: "@BUTTON.foldersToolbar-2"},
>>>>>>         2: {type: "span", class: "innerElement", style:
>>>>>> {"margin": "2px", "padding": "1px", "width": "48px", "height":
>>>>>> "20px"}, align: "center", field: "@BUTTON.foldersToolbar-0"},
>>>>>>         3: {type: "span", class: "innerElement", style:
>>>>>> {"margin": "2px", "padding": "1px", "width": "48px", "height":
>>>>>> "20px"}, align: "center", field: "@BUTTON.foldersToolbar-1"}
>>>>>>     },
>>>>>>     know: function (obj) {
>>>>>>
>>>>>>         var possible = ['handle', 'diegesis', 'refresh'];
>>>>>>
>>>>>>         COINRULES.library.getPossibilities ({form: this,
>>>>>> possible: possible, data: obj});
>>>>>>
>>>>>>         if (GNOSIS.scenario.noeticHierarchy) {
>>>>>>             this[1] = {type: "table", class: "form",
>>>>>> align: "center", style: {width: "100%"}, border: 0,
>>>>>>                 0: {type: "tbody", d3call:
>>>>>> "@CODE.instantiateFolders",                 }
>>>>>>             }
>>>>>>            
>>>>>> GNOSIS.research.concepts.FOLDERS.folders.root =
>>>>>> GNOSIS.scenario.noeticHierarchy;         } else {
>>>>>>             delete this[1];
>>>>>>         }
>>>>>>
>>>>>>         this["@BUTTON"]["foldersToolbar-0"] = {
>>>>>>             type: "button2",
>>>>>>             name: "0",
>>>>>>             style: {"width": "68px", "height": "20px",
>>>>>> "background-color": (this.folders.select) ?
>>>>>> _vColors[14]["background-color"] :
>>>>>> _vColors[12]["background-color"], "color": _vColors[12].color},
>>>>>>             value: "SELECT",
>>>>>>             onclick: function (event) {
>>>>>>
>>>>>>                
>>>>>> GNOSIS.research.concepts.FOLDERS.folders.select =
>>>>>> !GNOSIS.research.concepts.FOLDERS.folders.select;
>>>>>>                 d3.select (this).style
>>>>>> ("background-color",
>>>>>> (GNOSIS.research.concepts.FOLDERS.folders.select) ?
>>>>>> _vColors[14]["background-color"] :
>>>>>> _vColors[12]["background-color"]);
>>>>>>
>>>>>>             }
>>>>>>         }
>>>>>>
>>>>>>         switch (true) {
>>>>>>         case (typeof
>>>>>> (GNOSIS.research.concepts.FOLDERS.folders.initialise) ==
>>>>>> "undefined") :            
>>>>>> GNOSIS.research.concepts.FOLDERS.folders.initialise = true;
>>>>>>             this.refresh = true;
>>>>>>         }
>>>>>>         return (GNOSIS.research.concepts);
>>>>>>
>>>>>>     },
>>>>>>     "@CODE" : {
>>>>>>         instantiateFolders: function (el) {
>>>>>>
>>>>>>             var nodes =
>>>>>> (GNOSIS.research.concepts.FOLDERS.folders.root) ?
>>>>>> GNOSIS.research.concepts.FOLDERS.folders.root.copy() : undefined;
>>>>>>             var folders =
>>>>>> GNOSIS.research.concepts.FOLDERS.folders;            
>>>>>> var depth = folders.depth;             var items =
>>>>>> folders.items;
>>>>>>
>>>>>>             if (typeof (nodes) == "undefined")
>>>>>>                 return;
>>>>>>
>>>>>>             if
>>>>>> (GNOSIS.research.concepts.FOLDERS.refresh)
>>>>>>                 el.data(nodes, function (d) {
>>>>>>                     if (d.depth == depth) {
>>>>>>                         d.selected =
>>>>>> false;                        
>>>>>> items.push(d);                     }
>>>>>>                 });
>>>>>>             GNOSIS.research.concepts.FOLDERS.refresh =
>>>>>> false;
>>>>>>
>>>>>>             var node = el.data(items);
>>>>>>
>>>>>>             var row = 0;
>>>>>>             var width = 60;
>>>>>>             var cols = Math.floor
>>>>>> (GNOSIS.grizzle.data.gizmo.width / width);
>>>>>>             var rows = Math.floor (items.length /
>>>>>> cols);
>>>>>>
>>>>>>             if (rows * cols < items.length)
>>>>>>                 rows++;
>>>>>>
>>>>>>             var tr = null;
>>>>>>             var td = null;
>>>>>>
>>>>>>             for (var row = 0; row < rows;
>>>>>> row++)     {                 tr =
>>>>>> node.append('tr');
>>>>>>
>>>>>>                 for (var col = 0; col < cols;
>>>>>> col++) {                     td =
>>>>>> tr.append('td')                        
>>>>>> .attr("class", "pointer")
>>>>>>                         .attr("align",
>>>>>> "center")                        
>>>>>> .attr("width", `${width}px`)
>>>>>>                        
>>>>>> .style("padding-left", "5px")
>>>>>>                        
>>>>>> .style("padding-right", "5px")
>>>>>>                        
>>>>>> .style("background-color", function () {
>>>>>>
>>>>>>                             if
>>>>>> (row*cols + col < items.length)
>>>>>>                                
>>>>>> return ((items[row*cols + col].selected) ?
>>>>>> _vColors[14]["background-color"] :
>>>>>> _vColors[11]["background-color"]);
>>>>>>
>>>>>>                             return
>>>>>> (_vColors[11]["background-color"]);
>>>>>>
>>>>>>                         })
>>>>>>                         .attr("id",
>>>>>> function ()
>>>>>> {                             if
>>>>>> (row*cols + col < items.length) <-- *CORRECTIONS*
>>>>>>                                
>>>>>> return items[row*cols + col].data.name;
>>>>>>
>>>>>>                             return
>>>>>> 'blank';                         })
>>>>>>                         .attr("name",
>>>>>> row*cols + col)                        
>>>>>> .on("click", function (event) {
>>>>>>                             var el =
>>>>>> d3.select(this)
>>>>>>                             var index
>>>>>> = el.attr("name");
>>>>>>
>>>>>>                             if
>>>>>> (Number(index) <
>>>>>> GNOSIS.research.concepts.FOLDERS.folders.items.length) {
>>>>>>                                 if
>>>>>> (GNOSIS.research.concepts.FOLDERS.folders.select)
>>>>>>
>>>>>> GNOSIS.research.concepts.FOLDERS.folders.items[index].selected =
>>>>>> !GNOSIS.research.concepts.FOLDERS.folders.items[index].selected;
>>>>>>
>>>>>>                                
>>>>>> el.style ("background-color",
>>>>>> (GNOSIS.research.concepts.FOLDERS.folders.items[index].selected)
>>>>>> ? _vColors[14]["background-color"] :
>>>>>> _vColors[11]["background-color"]);
>>>>>>                             }
>>>>>>
>>>>>>                         })
>>>>>>                         .html(function ()
>>>>>> {                             if
>>>>>> (row*cols + col < items.length) {
>>>>>>                                
>>>>>> return (`<span align="center" style="font-size: 48px;">
>>>>>>                                 <i
>>>>>> class="far fa-folder"></i>
>>>>>>
>>>>>> </span><br>${items[row*cols+col].data.name}`);
>>>>>>                             } else {
>>>>>>                                
>>>>>> return ("&nbsp;");
>>>>>>                             }
>>>>>>                         });
>>>>>>
>>>>>>                     if (row*cols + col ==
>>>>>> items.length) {                        
>>>>>> td.attr("colspan", cols - col)
>>>>>>                            
>>>>>> .style("width", `100%`)
>>>>>>                         col = cols;
>>>>>>                     }
>>>>>>                 }
>>>>>>             }
>>>>>>         }
>>>>>>     },
>>>>>>     "@BUTTON": {
>>>>>>         "foldersToolbar-0": undefined,
>>>>>>         "foldersToolbar-1": {
>>>>>>             type: "button2",
>>>>>>             name: "0",
>>>>>>             style: {"width": "42px", "height": "20px",
>>>>>> "background-color": _vColors[12]["background-color"], "color":
>>>>>> _vColors[12].color},
>>>>>>             value: "ALL",
>>>>>>             onclick: function (event) {
>>>>>>
>>>>>>                 var f =
>>>>>> GNOSIS.research.concepts.FOLDERS.folders.items;
>>>>>>
>>>>>>                
>>>>>> GNOSIS.research.concepts.FOLDERS.folders.select =
>>>>>> !GNOSIS.research.concepts.FOLDERS.folders.select;
>>>>>>
>>>>>>                 for (var i = 0; i < f.length; i++)
>>>>>>                     f[i].selected =
>>>>>> GNOSIS.research.concepts.FOLDERS.folders.select;
>>>>>>
>>>>>>                 COINRULES.automate.grappleConcept
>>>>>> ({                     handle:
>>>>>> GNOSIS.grizzle.data.gizmo.id,
>>>>>>                     place:
>>>>>> `GIZMO-${GNOSIS.grizzle.data.gizmo.id}-INFO`,
>>>>>>                     template:
>>>>>> GNOSIS.research.concepts,                    
>>>>>> notion: "FOLDERS"                 });
>>>>>>
>>>>>> d3.select(`#BUTTON-${GNOSIS.grizzle.data.gizmo.id}-
foldersToolbar-
>>>>>> 0`).style ("background-color",
>>>>>> (GNOSIS.research.concepts.FOLDERS.folders.select) ?
>>>>>> _vColors[14]["background-color"] :
>>>>>> _vColors[12]["background-color"]);
>>>>>>
>>>>>>             }
>>>>>>         },
>>>>>>         "foldersToolbar-2": {
>>>>>>             type: "button2",
>>>>>>             name: "0",
>>>>>>             style: {"width": "42px", "height": "20px",
>>>>>> "background-color": _vColors[12]["background-color"], "color":
>>>>>> _vColors[12].color},
>>>>>>             value: "...",
>>>>>>             onclick: function (event) {
>>>>>>
>>>>>>                 alert ("Move up level...");
>>>>>>
>>>>>>             }
>>>>>>         }
>>>>>>     }
>>>>>> }
>>>>>>
>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> On 12/9/21 13:09, dolf wrote:
>>>>>>>>>> Correction that ought to be #419 and not #491
>>>>>>>>>>
>>>>>>>>>> dolf <dolfboek@hotmail.com> wrote:
>>>>>>>>>>> Before we begin that folder view, we'll need to resolve the
>>>>>>>>>>> existing
>>>>>>>>>>> *DATA* *PROBLEM* display problem...
>>>>>>>>>>>
>>>>>>>>>>> We've resolved that *DATA* *PROBLEM* display problem and the
>>>>>>>>>>> file has a
>>>>>>>>>>> resonance for 10 SEPTEMBER
>>>>>>>>>>>
>>>>>>>>>>> On 11/9/21 09:54, dolf wrote:
>>>>>>>>>>>> We’ve added the SCENARIO and NOETIC LEXICON COGNITIONS to
>>>>>>>>>>>> the case study
>>>>>>>>>>>> directory and our intention is to evolve the representation
>>>>>>>>>>>> of this:
>>>>>>>>>>>>
>>>>>>>>>>>> <https://www.grapple369.com/Case%20Studies/Noetic%
20Lexicon%
>>>>>>>>>>>> 20231%20-%20Juxtaposition%20Control.pdf>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> <https://www.grapple369.com/Case%20Studies/NOETIC-IDEA-
231.j
>>>>>>>>>>>> son>
>>>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> We are not suggesting that in every instance a #231 -
>>>>>>>>>> juxtaposition control
>>>>>>>>>> is adverse such as in the instance of usurping @1 - self with
>>>>>>>>>> an intention
>>>>>>>>>> to subjugate or #419 - slaughter by claims to piety as
>>>>>>>>>> Pythagorean binomial
>>>>>>>>>> onomantic derived mysticism belief systems, but rather that
>>>>>>>>>> it can function
>>>>>>>>>> as a natural mechanism of juxtaposition when in this instance
>>>>>>>>>> one is giving
>>>>>>>>>> a reply to a question ...
>>>>>>>>>>
>>>>>>>>>> The #237 - USE OF FORCE which is a male DEME as ONTIC extent
>>>>>>>>>> can from the
>>>>>>>>>> grounding of #231 - juxtaposition control, be improperly
>>>>>>>>>> deployed as #6 -
>>>>>>>>>> formula of progression {Form of nature {#3 - Nature Surmounts
>>>>>>>>>> Nature}}.
>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>      #233 - GLOBUS CRUCIGER / NOUMENON RESONANCE FOR 10
>>>>>>>>>>> SEPTEMBER 2021
>>>>>>>>>>> as [#1, #80, #5, #20, #100, #10, #9, #8] /
>>>>>>>>>>>      #349 as [#1, #80, #70, #20, #100, #10, #50, #8,
>>>>>>>>>>> #10] / #233 as [#1, #80, #5, #20, #100, #10, #9, #8] /
>>>>>>>>>>> #283 as [#1, #80, #5, #20, #100, #10, #9, #8, #50] /
>>>>>>>>>>> #345 as [#1, #80, #70, #20, #100, #10, #9, #5, #50] /
>>>>>>>>>>> #349 as [#1, #80, #70, #20, #100, #10, #50, #8, #10] /
>>>>>>>>>>> #359 as [#1, #80, #70, #20, #100, #10, #9, #8, #50, #1, #10]
>>>>>>>>>>> / #433 as [#1, #80, #5, #20, #100, #10, #9, #8, #200] /
>>>>>>>>>>> #452 as [#1, #80, #70, #20, #100, #10, #50, #70, #40, #1,
>>>>>>>>>>> #10] / #484 as [#1, #80, #5, #20, #100, #10, #9, #8, #200,
>>>>>>>>>>> #1, #50] / #505 as [#1, #80, #70, #20, #100, #10, #9, #5,
>>>>>>>>>>> #10, #200] / #506 as [#1, #80, #70, #20, #100, #10, #9, #5,
>>>>>>>>>>> #10, #200, #1] / #556 as [#1, #80, #70, #20, #100, #10, #50,
>>>>>>>>>>> #5, #200, #9, #1, #10] /
>>>>>>>>>>> #603 as [#1, #80, #70, #20, #100, #10, #9, #8, #300, #5] /
>>>>>>>>>>> #637 as [#1, #80, #5, #20, #100, #10, #50, #1, #300, #70] /
>>>>>>>>>>> #647 as [#1, #80, #70, #20, #100, #10, #50, #5, #300, #1,
>>>>>>>>>>> #10] / #814 as [#1, #80, #70, #20, #100, #10, #9, #8, #200,
>>>>>>>>>>> #5, #300, #1, #10] /
>>>>>>>>>>> #850 as [#1, #80, #70, #20, #100, #10, #9, #5, #50, #300,
>>>>>>>>>>> #5, #200] /
>>>>>>>>>>> #929 as [#1, #80, #70, #20, #100, #10, #9, #8, #200, #70,
>>>>>>>>>>> #50, #300, #1,
>>>>>>>>>>> #10] = apokrínomai (G611): {UMBRA: #452 % #41 = #1}} 1) to
>>>>>>>>>>> give an answer to a question proposed, to answer; 2) to
>>>>>>>>>>> begin to speak, but
>>>>>>>>>>> always where something has preceded (either said or done) to
>>>>>>>>>>> which the
>>>>>>>>>>> remarks refer;>
>>>>>>>>>>>> T'AI HSÜAN CHING {POLAR OPPOSITIONS / INTERPLAY OF
>>>>>>>>>>>> OPPOSITES} [4 BCE]:
>>>>>>>>>>>>
>>>>>>>>>>>> UMBRA: #452 % #41 = #1 - To Guide with Names, Reason's
>>>>>>>>>>>> Realisation;
>>>>>>>>>>>> I-Ching: H58 - Joy, Open, Lake; Tetra: 24 - Joy;
>>>>>>>>>>>>
>>>>>>>>>>>> THOTH MEASURE: #1 - Oh thou of long strides, who makest
>>>>>>>>>>>> thine appearance in
>>>>>>>>>>>> Annu; I am not a doer of wrong.
>>>>>>>>>>>> #VIRTUE: If it is Center (no. #1), then yang begins.
>>>>>>>>>>>> #TOOLS: With Center (no. #1), it begins.
>>>>>>>>>>>> #POSITION: If it is Response (no. #41), then yin is born.
>>>>>>>>>>>> #TIME: With Full Circle (no. #2), it wheels back.
>>>>>>>>>>>> #CANON: #45
>>>>>>>>>>>> ONTIC_OBLIGANS_45@{
>>>>>>>>>>>> @1: Sup: 1 - CENTRE: CHUNG (#1); Ego: 1 - CENTRE: CHUNG
>>>>>>>>>>>> (#1), @2: Sup: 2 - FULL CIRCLE: CHOU (#3); Ego: 1 - CENTRE:
>>>>>>>>>>>> CHUNG (#2), @3: Sup: 43 - ENCOUNTERS: YU (#46); Ego: 41 -
>>>>>>>>>>>> RESPONSE: YING (#43),
>>>>>>>>>>>> @4: Sup: 45 - GREATNESS: TA (#91); Ego: 2 - FULL CIRCLE:
>>>>>>>>>>>> CHOU (#45 - I
>>>>>>>>>>>> AM NOT A DOER OF WRONG {%1}),
>>>>>>>>>>>> Male: #91; Feme: #45
>>>>>>>>>>>> } // #45
>>>>>>>>>>>>
>>>>>>>>>>>> Our intention is to deploy this Category of Understanding
>>>>>>>>>>>> #231 - Juxtaposition Control for our display of NOETIC
>>>>>>>>>>>> LEXICON COGNITIONS.
>>>>>>>>>>>>
>>>>>>>>>>>> First thing we realise is that the resultant 15 entries
>>>>>>>>>>>> generates some 38
>>>>>>>>>>>> pages which is too much information. So our first approach
>>>>>>>>>>>> is to provide a
>>>>>>>>>>>> folder 📁 and list view of the information so that we
>>>>>>>>>>>> might then make an
>>>>>>>>>>>> interpretation of our data.
>>>>>>>>>>>>
>>>>>>>>>>>> dolf <dolfboek@hotmail.com> wrote:
>>>>>>>>>>>>> Our next activity with the display of NOETIC LEXICON
>>>>>>>>>>>>> COGNITIONS is the
>>>>>>>>>>>>> focus on the Category of Understanding of #231 -
>>>>>>>>>>>>> JUXTAPOSITION CONTROL
>>>>>>>>>>>>> which is inherent to Pythagorean binomial onomantic
>>>>>>>>>>>>> derived mysticism belief
>>>>>>>>>>>>> systems and for which we have the following meta logic
>>>>>>>>>>>>> associated with the
>>>>>>>>>>>>> autonomous delimiter:
>>>>>>>>>>>>>
>>>>>>>>>>>>> #THREE:    #125    as #44 - STOVE (TSAO)
>>>>>>>>>>>>> #FOUR:    #200    as #38 - FULLNESS (SHENG)
>>>>>>>>>>>>> #FIVE:    #325    as #1 - CENTRE (CHUNG)
>>>>>>>>>>>>>
>>>>>>>>>>>>> And we note several lexicon concepts of the 15 Hebrew /
>>>>>>>>>>>>> Greek lexicon
>>>>>>>>>>>>> entries:
>>>>>>>>>>>>>
>>>>>>>>>>>>> #127 - GLOBUS CRUCIGER / NOUMENON RESONANCE FOR 10
>>>>>>>>>>>>> SEPTEMBER 2021 as
>>>>>>>>>>>>> [#6, #10, #90, #1, #500] /
>>>>>>>>>>>>> #154 as [#6, #1, #6, #90, #10, #1, #600] /
>>>>>>>>>>>>> #198 as [#30, #5, #6, #90, #10, #1, #50, #6] /
>>>>>>>>>>>>> #491 - PATER FAMILIAS PRINCIPLE as [#90, #1, #400] /
>>>>>>>>>>>>> [#400, #90, #1] =
>>>>>>>>>>>>> yâtsâʼ (H3318): {UMBRA: #101 % #41 = #19} 1) to go out,
>>>>>>>>>>>>> come out, exit, go
>>>>>>>>>>>>> forth; 1a) (Qal); 1a1) to go or come out or forth, depart;
>>>>>>>>>>>>> 1a2) to go forth
>>>>>>>>>>>>> (to a place); 1a3) to go forward, proceed to (to or toward
>>>>>>>>>>>>> something); 1a4)
>>>>>>>>>>>>> to come or go forth (with purpose or for result); 1a5) to
>>>>>>>>>>>>> come out of; 1b)
>>>>>>>>>>>>> (Hiphil); 1b1) to cause to go or come out, bring out, lead
>>>>>>>>>>>>> out; 1b2) to
>>>>>>>>>>>>> bring out of; 1b3) to lead out; 1b4) to deliver; 1c)
>>>>>>>>>>>>> (Hophal) to be brought
>>>>>>>>>>>>> out or forth;
>>>>>>>>>>>>>
>>>>>>>>>>>>> #681 as [#5, #60, #400, #10, #200, #6] = çâthar (H5641):
>>>>>>>>>>>>> {UMBRA: #660 % #41
>>>>>>>>>>>>> = #4} 1) to hide, conceal; 1a) (Niphal); 1a1) to hide
>>>>>>>>>>>>> oneself; 1a2) to be
>>>>>>>>>>>>> hidden, be concealed; 1b) (Piel) to hide carefully; 1c)
>>>>>>>>>>>>> (Pual) to be hidden
>>>>>>>>>>>>> carefully, be concealed; 1d) (Hiphil) to conceal, hide;
>>>>>>>>>>>>> 1e) (Hithpael) to
>>>>>>>>>>>>> hide oneself carefully;
>>>>>>>>>>>>>
>>>>>>>>>>>>> #213 - GLOBUS CRUCIGER / NOUMENON RESONANCE FOR 10
>>>>>>>>>>>>> SEPTEMBER 2021 as
>>>>>>>>>>>>> [#6, #1, #200, #1, #5] /
>>>>>>>>>>>>> #213 as [#6, #200, #1, #6] /
>>>>>>>>>>>>> #218 as [#6, #200, #1, #5, #6] /
>>>>>>>>>>>>> #242 as [#1, #200, #1, #600] /
>>>>>>>>>>>>> #242 as [#30, #200, #1, #6, #5] /
>>>>>>>>>>>>> #257 as [#50, #200, #1, #6] /
>>>>>>>>>>>>> #257 as [#6, #10, #200, #1, #600] /
>>>>>>>>>>>>> #262 as [#6, #50, #200, #1, #5] /
>>>>>>>>>>>>> #262 as [#5, #200, #1, #50, #6] /
>>>>>>>>>>>>> #277 as [#6, #10, #200, #1, #50, #10] /
>>>>>>>>>>>>> #277 as [#10, #200, #1, #6, #50, #10] /
>>>>>>>>>>>>> #271 as [#10, #200, #1, #50, #10] = râʼâh (H7200):
>>>>>>>>>>>>> {UMBRA: #206 % #41 = #1}
>>>>>>>>>>>>> 1) to see, look at, inspect, perceive, consider; 1a)
>>>>>>>>>>>>> (Qal); 1a1) to see;
>>>>>>>>>>>>> 1a2) to see, perceive; 1a3) to see, have vision; 1a4) to
>>>>>>>>>>>>> look at, see,
>>>>>>>>>>>>> regard, look after, see after, learn about, observe,
>>>>>>>>>>>>> watch, look upon, look
>>>>>>>>>>>>> out, find out; 1a5) to see, observe, consider, look at,
>>>>>>>>>>>>> give attention to,
>>>>>>>>>>>>> discern, distinguish; 1a6) to look at, gaze at; 1b)
>>>>>>>>>>>>> (Niphal); 1b1) to
>>>>>>>>>>>>> appear, present oneself; 1b2) to be seen; 1b3) to be
>>>>>>>>>>>>> visible; 1c) (Pual) to
>>>>>>>>>>>>> be seen; 1d) (Hiphil); 1d1) to cause to see, show; 1d2) to
>>>>>>>>>>>>> cause to look
>>>>>>>>>>>>> intently at, behold, cause to gaze at; 1e) (Hophal); 1e1)
>>>>>>>>>>>>> to be caused to
>>>>>>>>>>>>> see, be shown; 1e2) to be exhibited to; 1f) (Hithpael) to
>>>>>>>>>>>>> look at each
>>>>>>>>>>>>> other, face;
>>>>>>>>>>>>>
>>>>>>>>>>>>> Thusly we ask the question whether the inhibitors of
>>>>>>>>>>>>> female autonomy under
>>>>>>>>>>>>> Islamic belief are framed by such principles?
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>
>>
>>
>
>
>