Since an application may have several different preconfigured panes and pages (that is, subclasses of
SC.Pane), we need a means to organize them all. This is the purpose of the
SC.Page object. But don't let the name confuse you.
SC.Page is not a type of
SC.View and has nothing to do with rendering the visual page. It is simply a storage object used to hold preconfigured but un-instantiated panes and views.
SC.Page container gives your application an anchor point for looking up a particular view tree and retrieving it for use. This is convenient, but the real work of the page container is that it will only instantiate objects when they are accessed the first time, allowing you to avoid creating all your panes ...