Yes, I got that. See next response.
It would present a paradox if it pertained to the same data, but it’s not the same data. I started with an overall strategy and reported success with the concept of splitting the tree content into two parts. The bulk of the data sits in the node content which naturally inludes in principle also the associations which renders it a recursive hierarchy. Using some cleverness on the server, I extract those association data (abstracted to a association by which each node has 0 or more child nodes in a specified order) into an entirely different dataset akin to another schema. This structural “schema” represents what the UI needs to know about how nodes (known solely by their IDs) are related to each other.
In the LiveView domain I handle the nodes and the structure data separately. After all the filtering and cutting out rectangular view sections, the structure data is small enough to be retained in memory as assigns and since it’s a single record it doesn’t even make sense to conider streaming that as it would always change anyway but without a previous one to compare to. The nodes, i.e. the big data it refers to and which gets rendered to HTML under its ID is a different matter. I don’t need LV to track the changes there because I already track those changes in my application, meaning I know about changes before getting to the presentation stage. When a changed or changing node is displayed or subscribred to, it will be updated as a whole, but here the whole “excludes” its children. Changes to the children will also go through, but under their own steam.
In the end, it comes down to this: As the user navigates through and interacts with the content via this tree view there is smart pagination logic behind it which has all the information it needs to build the correct view window structure from the database and can identify with “surgical accuracy” which of the nodes has to be updated, added because they were excluded from the previous ‘page’ or deleted because they are no longer needed. That’s the part that aligns with the Streams idiom whereas the minimalistic structure reflecting the structural essense of what is on screen is not designed for streaming but rather for direct assigns which renders and drives the container.
The job’s not done yet, so I would only be able to validate my understanding and assumptions about how LV’s JS side conspires with the DOM and how the container I use actually handle the style changes driving the tree layout holds true or breaks down once I have that running with extensive tracing at every level. It’s tense times, but I’m cautiously optimistic that the inevitable surprises will be technical issues since those always have solutions. It’s the so-called “soft-issues” like unforeseen impedence mismatches and divergent agendas that tends to trip us up.
