See T5351 (Naviframe API in EO land).
One idea to replace naviframe is to provide a few similar widgets which present one "page" at a time. @eunue is working hard on making such widgets.
The problem is that all "pages" need to be created when instantiating this parent container. A solution to that is to have a magical widget, single slot container, that will create its content when it becomes visible, i.e. on "realize".
Here comes the "Realize" Widget.
It interacts with other containers to know when to realize/unrealize its content (i.e. create or destroy it, or potentially placing it in a cache).
It should be associated with a factory and some data (model?) in order to know how to create the internal content that it holds.
Using such a "Realize" widget one could use a simple Box in a Scroller and implement something like a simple genlist. (The idea is NOT to replace genlist with this^^).
Many questions remain:
- How to expose the factory API?
- How to pass data to that factory?
- Should the realize widget be a real widget with a NULL resize_object (or invisible rect), until realized?
- How to handle various actions like in Naviframe, where it's not just page 1, 2, 3 but more like page 1, then 2.A or 2.B depending on which action was taken in page 1.
- Do we even want this?