Page and PageContainer confusing layout
At the moment, a Page
instance acts like an invisible layer to the layout. Any nodes inside of a page are completely unaware, with their parents being set to the parent of the Page - not the page itself. This system leads to a few drawbacks:
- The
Page
class is not constructed the same as other classes. Many features are missing or difficult to implement due to this unneeded complexity - Animating the transitions between pages using this method would be extremely difficult and inefficient
- Child nodes are unaware of the pages presence and have a hard time manipulating it
The proposal is to rewrite this system so that the pages act like actual containers with their own canvas. The canvas dimensions will match that of the parent PageContainer
. This allows transitions to be created by positioning the pages out of view and animating them into view using various different effects.
Using this system, the Page
class will only add a few new functions and will likely extend a more suitable class, like ScrollContainer
. This will allow the page to have it's own separate scrollbar and theme declarations.