...
This document provides an overview of the changes made for Reference Framework 2.0.
- Updates to security roles
- Page events
- Page Navigation
- shortcutFocus
- Dialog management
- XAL caching
- Page container renamed
Requirements
Reference Framework 2.0 runs against Nexaweb Platform 4.5.33 or higher.
Updates to security roles
Security roles have always been a part of the reference framework. In 2.0, where roles can be used has been expanded on the page, command bar and menu, as well as components within the page.
...
- roleEnabled - specifies the role(s) required to make a component enabled
- roleVisibile - specifies the role(s) required to make a component visible
- roleReadOnly - specifies the role(s) required to make a component read only
Page Events
Page events have been added to the reference framework. These events allow control over the lifecycle of the page, as well as navigation to and from a page.
...
onPageClosed
The onPageClose event is fired once when a page is closed. This provides a means for cleaning up any code associated with the page.
Page Navigation
Navigation methods have been added to the PageManager interface. Page navigation methods have been added to allow navigation to the next or previous page as well as back to the homepage. Tab navigation methods have been added to allow navigation to the next or previous open page while in tab mode.
...
prevTab() – Sets the page in the previous tab to be the active page. If the active page is the last tab, this method performs no operation. This method only works when the pageStyle is configured to tabs.
shortcut Focus
The shortcutFocus property defines a key chord that will set focus to a component. If the component being focused is contained within a tab that is not visible, then the tab will be selected. Configuring shortcutFocus on a tab, simply selects the tab.
Dialog Management
A new class has been added to the reference framework for managing modal and modeless dialogs. Pages can now be opened as modeless (pop-ups), or modal dialogs regardless of the page style being used.
The DialogManager class is registered as a system container, so it can be referenced within onCommand definitions. For example, onCommand=”DialogManager.showModalDialog( ‘myDialogPage’ )”.
XAL Caching
Caching of XAL files used by the pages has been added to the reference framework. A new section has been added to the nexaweb-reference-framework.xml to allow for the configuration of the cache.
...
Currently only the size of the cache can be configured. If the cache reaches maximum capacity, the least recently opened (or focused) page will be removed from the cache.
Page Container renamed
The container that holds the page definitions from the nexaweb-reference-framework.xml file has been renamed to pageDef. While this should be a relatively transparent change, if the page container was referenced then these references will have to be changed.
...