- Paging - Datasource objects can be paged by newly introduced APIs.
- api_datasource.setPage(in_datasourceName_tx varchar2,in_page_nr number,in_rowsPerpage_nr number)
- api_datasource.nextPage(in_datasourceName_tx varchar2)
- api_datasource.previousPage(in_datasourceName_tx varchar2)
- api_datasource.getCurrentPage(in_datasourceName_tx varchar2)
- api_datasource.getRowsPerPage(in_datasourceName_tx varchar2)
- api_datasource.executeQuery(in_datasourceName_tx varchar2,in_page_nr number,in_rowsPerpage_nr number)
Mainly datasources page instence rows, which means brim interfaces dont get queried unless u page datasource using api_datasource.executeQuery
If developer leaves "rowsperpage" attribute blank, framework will use current value, if developer sends null, framework will stop paging and bring all rows.
Pages cannot be less than 1, even if developer uses 0 or negative values, currentPage will be 1.
If datasource is not paged, currentPage will be 1.
Rowsperpage attribute is editable through IDE.
- Scrollbar abilities enhanced for mainframe and dialog - Mainframe/Dialog has new scrollbar abilities.
- api_dialog/api_frame.setViewportPosition(in_name_tx varchar2, in_viewportPosition_t api_graphics.t_point)
- api_dialog/api_frame.setVerticalScrollbarVisible(in_name_tx varchar2, in_visible_yn varchar2)
- api_dialog/api_frame.setVerticalScrollbarEnable(in_name_tx varchar2, in_enable_yn varchar2)
- api_dialog/api_frame.setHorizontalScrollbarVisible(in_name_tx varchar2, in_visible_yn varchar2)
- api_dialog/api_frame.setHorizontalScrollbarEnable(in_name_tx varchar2, in_enable_yn varchar2)
- api_dialog/api_frame.getViewportPosition(in_name_tx varchar2)
- api_dialog/api_frame.getVerticalScrollbarVisible(in_name_tx varchar2)
- api_dialog/api_frame.getHorizontalScrollbarVisible(in_name_tx varchar2)
- api_dialog/api_frame.getVerticalScrollbarEnable(in_name_tx varchar2)
- api_dialog/api_frame.getHorizontalScrollbarEnable(in_name_tx varchar2)
With these APIs we can change position, visibility and enable/disable state of scrollbars. We also can define new attributes in IDE for dialog and mainframe.
New Attributes:verticalScrollbarVisible, horizontalScrollbarVisible, verticalScrollbarEnable, horizontalScrollbarEnable
All of these default values equal to 'Y'
- RGB syntax is supported for colors
Predefined colors are still available, however, if developer likes to use a different color, he/she can use commonly used RGB syntax for defining color.
Syntax in xml editor is simple, RGB definitions start with a "#" then continues with rgb notation.
Examples
#FF0000 : Red
#FFFF00 : Yellow
#0000FF : Blue
For more details of RGB, http://en.wikipedia.org/wiki/RGB
- Parameters of api_error.log was modified. Any more this procedure just have one parameter that is in_message_tx
- Grids doesn't show its scrollbar if it is not needed. When number of rows exceeds grid's height, scrollbar becomes visible.
- Tree and grid now have new font attributes, they can set font style,font size,font family for every record.
- Swing renderer's Look&Feel has parametrized. Parameters name is "application.lnfClass" . Default value is "org.jvnet.substance.skin.SubstanceBusinessBlackSteelLookAndFeel", which will open mostly used l&f.If you like to use OS's default L&F, "systemDefault" should be sent to l&f parameter.
- Multiple keyevents on a ui item (component,panel,dialog,mainframe) are supported.
- Font(Style, Size, Family, Color) Columns are added to Grid and Tree components. These attributes now can be set by using binded datasource.
- Api_application.isDirty is added.
- Api_panel.isCell, Api_dailog.isCell, Api_frame.isCell are added.
- Getting/setting value of record that is not current row funtionality is added.(api_datasource.getColumnValueTX/NR/DT/CL/BL)
- Selection color attribute is added for tree's selected node.
Java Renderer
- Look and Feel setting is parameterized.
- Disabled components cannot take focus.
Javascript (Web) Renderer
- Disabled components cannot take focus
- Mainframe has keyEvents
- actionRun now supports all URLs