T
Thierry Ciot
Guest
Here is an outline of some of the V4.0.4 changes: Admin Controls for designing/adapting some UI components to specific device Top Level Menus Top level menus (a.k.a tabs) can be configured per device now i.e a tab can be made visible specific to a device (Desktop, Tablet , Mobile). In the tab edit page, a new category called "Show in" is added where user can select any of the devices on which that particular tab can should be visible in. Once selected the user selection can be also be seen in the tab view page. Sections Similarly, the same configuration UI is available for sections. User can now select which devices a section should be visible on (See the section properties in page designer). Buttons Again, similar to Tabs and Sections, custom buttons can be configured to be used on all devices or specific devices (It can be viewed and modified in button view and buttons edit pages respectively). Usability and Performance Improvements We are now supporting more Ajax Requests instead of full page reload. This improve the performance on client side (faster load and less data transferred) and on server side (better scalability). The list of actions where we now do Ajax Requests instead of full page reload: Top level menus navigation Viewing a record (from grid to object view) Navigating back to Grid from viewing a record (From Object View, toolbar back to list button) Viewing Next and Previous Record (From Object View, toolbar next and previous records buttons) Editing a record (From Object View, toolbar Edit button) - Note: Save is a full page reload Transition - Client-side options As this is a new navigation pattern for end-users, we have client-side options to enable/disable Page Navigation using Ajax. This is helpful considering custom end-user scripts may be written against a specific behavior like document.ready event to customize a page after it is rendered. Such end-user customization could now be affected & with client-side options to enable/disable this feature, users will have time to absorb this change & make required corrections. To disable Page Navigation using Ajax, set this property as false: rb.newui.options.applicationPage.ajaxNavigation = false. To selectively disable particular navigation flows: Navigating between object records: rb.newui.options.objectViewPage.recordNavigationAjax = false Top level Menu (tabs) navigation: rb.newui.options.tabMenuLink.ajaxNavigation = false Masked fields and KendoMaskTextBox widget User can define an input mask for TextInput & PhoneInput fields which will dictate & enforce a pattern of characters. Eg. An input mask defined as (###)##-####, will only allows numerals grouped as (999)88-00000. Earlier in 4.0, users where free to enter any value & we use to apply mask only on field blur event that is when field loses focus. However, we have now bettered this approach & are now incorporating kendo masked textbox widget. This widget from kendo library restricts users to enter only those values as permitted by the mask. Additional info on Kendo Masked Textbox Widget, also see: http://demos.telerik.com/kendo-ui/maskedtextbox/index Filter Improvements We have enabled the Filter option in Related List of Object View. Controlling Advanced Filtering Capability We have added 2 flags to control showing/hiding advanced filter features individually. rb.newui.options.filters.showBooleanOperators: to show/hide boolean AND/OR operator dropdown rb.newui.options.filters.showAdvancedFilterTypes: to show/hide advanced search type dropdown When both properties are false the entire row is hidden to save vertical space. Here is an example script customer will need to add to custom sidebar: Updated Libraries Font Awesome V4.4.0 V4.5.0 Kendo UI Professional 2015.3.916 Not changed Bootstrap v3.3.5 Not changed JQuery V1.9.1 Not changed Library name From Version To Version
Continue reading...
Continue reading...