Message from JavaScript discussions

November 2016

— Http://


Each render procedure is actually a promise, with a resolve() call after the important parts of the DOM have been loaded by it

— This way, other views that are dependent on higher-up views can wait until those are loaded

— I chenck

— The parts that are not working OK are the componentUpdate part, it's because the child views dont know if they need to re-render

Message permanent page

— I do have a force argument that makes that render happen, I just don't know how to tell those child views: "Hey! Something deleted your DOM elements! Re render now!"

Message permanent page

— A Virtual DOM would fix this... I am seeing that... haha

— Hhahaha

— The diff is a problem

— Right, since a view wont render if the data is the same as what it has... this is good if it's elements are in the DOM, but if they aren't, you get blank spots the next time you try to render it

Message permanent page

— I am thinking the easiest solution would be... a controllerview that is trying to render can find all the other controllerviews that are on the same level in the heirarchy as itself, then call a resetState interface on all of those, deleting state for the child views

Message permanent page

— If extend de Element object and include the update data info