tinganho / composer Goto Github PK

We currently treat one page lifecycle as:

1. Hide contents of the current page(except for those content that should be rendered on the next page).
2. Load the contents for the next page(exclude loading of content that are already on the current page).
3. Remove contents of the current page.
4. Paste content of the next page.
5. Show content of the next page.

Though there is some side effects with this approach(All below examples results in a new URL on the address bar):

1. What if one want to transition from one page to an another, while in the middle of the transition both page is shown side-by-side?
2. What if we want to show a modal with content on it. Beneath it lives the current page. But we want to update the URL to reflect the new page.
3. What if we want to show endless modal above modal views? All views

The buitl file right now defaults composer.js. It should instead be router.js

We save all the rendering and never dispose them, right now. It was just a temporary solution to deal with efficiently getting the instances of child components. But as of right now, we need to pay the debt.

Each render is stored in an array:

instantiatedComponents[renderId][componentId]

First approach was to manually dispose them. But that turned out to be too error proned can we make this more automatic?