|Download • Git|
|Forums • Blog • Twitter • G+|
Pages are elements allowing the user to browse through the content of the application.
A page allows the user to browse to a specific point of an application. Pages have a hierarchical organisation: Each page can contains other pages. On the top of the hierarchy is an Outline that create the first root pages.
In outline based applications, pages are represented as node of a tree on the left. It is possible to drill down the page to access the child pages (unless the page is configured as leaf). On the right the content of the page is displayed. Instead of the page content, it is possible to display a detail form in this area.
It is possible to reference them with a Bookmark.
There are two types of pages, depending on the type of content you want to represent, you will probably consider one of the two types:
A table page is suitable if you want to represent many elements as rows of a Table (displayed on the right). The table is loaded on event LoadTableData. It is possible to create a child for each row with the event CreateChildPage.
A node page is suitable to represent a single element. The content is a list of child pages created on event CreateChildPages. The child pages are represented on the left in the tree representation of the page hierarchy. The Table on the right contains also the list of child pages.
Defined with getConfiguredXxxxxx() methods.
Defined with execXxxxxx() methods.
With PageActivated and PageDeactivated you are notified when the page is selected and de-selected in the outline tree. This can be usefull to handle the lifecycle of a detail form.