#treetable | Explore Tumblr posts and blogs

openui5 · 8 years ago

Text

Preview of OpenUI5 1.46 available now - What is new?

OpenUI5 1.46 is now available as a preview download and can also be used and browsed online at https://openui5beta.hana.ondemand.com.

As always: feel free to test and report issues, but please do not use it for productive apps.

The most significant update is the reworked demo apps page we blogged about earlier this year. In addition, there’s one completely new demo app (Browse Orders) and one overhauled demo app (Shop Administrator). See below chapter “Demo Kit and Documentation Changes”. In addition, new features were developed and many controls and features were improved.

New Features

New Themes

The High Contrast White (HCW) and High Contrast Black (HCB) themes (sap_belize_hcw / sap_belize_hcb) are now delivered with all SAP Fiori-related libraries. They offer a better visual experience for people with visual impairments.

Support for Persian Calendar

All our controls now support the Persian calendar. The Persian calendar is also sometimes referred to as "Solar Hijri", "Iranian" or "Farsi" calendar.

The Persian calendar year begins around March 21st of each Gregorian year and ends at around March 20th of the following year. To convert the Persian calendar years into the equivalent Gregorian year, add 621 or 622 years to the Persian calendar year depending on whether the Persian calendar year has begun or not.

New Controls

sap.f.Avatar is an SAP Fiori 2.0 image-like control that has different display options for representing images, initials, and icons. It allows the usage of different content, shapes, and sizes depending on the use case.

There are several predefined sizes, as well as an option to set a custom size.

For more information, see the API Reference and the sample in the Explored app.

sap.f.FlexibleColumnLayout: This control represents the new SAP Fiori 2.0 base layout for an app. It implements the master-detail-detail paradigm by displaying up to three pages in separate columns. The columns are referred to as Begin, Mid, and End, and their width is variable depending on the current layout. There are several possible layouts that can be changed with the control's API, and also by the user with navigation arrows.

For more information, see Building an App with the Flexible Column Layout and Related Classes, the API Reference, and the sample in the Explored app.

sap.f.semantic.SemanticPage: This new SAP Fiori 2.0 control represents an enhanced sap.f.DynamicPage that contains controls with semantic-specific meaning. You can set different actions using the available aggregations, and the sap.f.semantic.SemanticPage will automatically position them in dedicated sections of the title or the footer of the page, facilitating the implementation of the SAP Fiori 2.0 design guidelines.

Figure 1: Different types of actions in the title positioned in a predefined order

Figure 2: Different types of actions in the footer’s right and left areas, positioned in a predefined order

For more information, see the API Reference and the sample in the Explored app.

Improved Features

OpenUI5 OData V4 Model

The new version of the OpenUI5 OData V4 model now supports the following features:

Changing query options on sap.ui.model.odata.v4.ODataListBinding and sap.ui.model.odata.v4.ODataContextBinding

Requesting $count system query option on sap.ui.model.odata.v4.ODataListBinding

Accessing value lists

Forwarding the $search system query option

Branching from OData V4 model into metadata using the hash (#) character (see sap.ui.model.odata.v4.Context#getObject()) in template:with

Caution: Incompatibility Due to Bug Fix. The following bug has been reported: If you call the sap.ui.model.odata.v4.Context#getObject() or the sap.ui.model.odata.v4.Context.requestObject() methods without a parameter, the expected and documented behavior is that the same result is returned as if the parameter sPath="" had been specified. Due to the bug, however, the return value wraps the expected output that can then only be accessed via .value[0], for example oContext.getObject().value[0].

If you have used this workaround, your application will break starting with OpenUI5 version 1.44.6.

Solution: If your application needs to run with both the fixed and unfixed versions of OpenUI5, specify the sPath="" parameter, for sPath parameter. In both cases, you must not use the workaround with .value[0]any longer.

Restriction

Due to the limited feature scope of this version of the OpenUI5 OData V4 model, check that all required features are in place before developing applications. Check the detailed documentation of the features, as certain parts of a feature may be missing. While we aim to be compatible with existing controls, some controls might not work due to small incompatibilities compared to sap.ui.model.odata.(v2.)ODataModel, or due to missing features in the model (such as tree binding). This also applies to controls such as TreeTable and AnalyticalTable, which are not supported together with the OpenUI5 OData V4 model. The interface for applications has been changed for easier and more efficient use of the model. For a summary of these changes, see Changes Compared to OData V2 Model.

For more information, see OData V4 Model, the API Reference, and the sample in the Explored app in the Demo Kit.

OData V2 Model

For OData V2 models, the V2 annotation sap:aggregation-role=”dimension” is now converted into V4 annotation "com.sap.vocabularies.Analytics.v1.Dimension" : { "Bool" : "true" }.

V2 annotation sap:aggregation-role="measure" is now converted into V4 annotation "com.sap.vocabularies.Analytics.v1.Measure" : { "Bool" : "true" }. For more information, see Meta Model for OData V2 and the API Reference.

One Page Acceptance Tests (OPA5)

The new LabelFor matcher checks if a given control is associated with the sap.m.Label control by their labelFor property. You can use it when searching by the text property or by the i18n key of the sap.m.Labelcontrol. For more information, see Cookbook for OPA5, the API Reference, and the sample in the Explored app.

Improved Controls

sap.m.ComboBox:

The value state error message is now visible above all list items in the dropdown list of the sap.m.ComboBox. This improves the usability on mobile devices (tablets and phones).

When the ComboBox displays two columns (for example, key and value), you can search and filter for matching strings in both columns. This is enabled with the filterSecondaryValues property. For more information, see the API Reference and the sample in the Explored app.

sap.m.DatePicker: We have introduced a new navigate event. While navigating in the calendar popup of the sap.m.DatePicker, you can now receive an event containing the first and the last dates that are currently visible. You can use this information for lazy loading of special dates. For more information, see the API Reference.

sap.m.GenericTile: The new Actions scope property was added to provide an editing option for the GenericTile control when included on a Web page, for example, on the SAP Fiori launchpad. It is aligned explicitly with the interaction design of the SAP Fiori launchpad’s Edit mode. Both the sap.m.GenericTile and sap.m.SlideTile controls have been extended with this feature. You use the new scope property to switch the visual representation of the GenericTile or SlideTile on a Web page from the Display scope to the Actions scope. For more information, see the API Reference and the sample in the Explored app.

sap.m.Input and all inheriting controls now allow filtering and searching in two or more columns. Matching is done only on the initial character and the matching sequence is displayed in bold in the suggestion list.

For more information, see the sample in the Explored app.

sap.m.MessageBox can now hold and display formatted text (sap.m.FormattedText) and JSON content. This allows you to display message boxes with complex content. For more information, see the sample in theExplored app.

sap.m.MultiComboBox: The delay for text validation in the sap.m.MultiComboBox has been changed in order to react correctly to special inputs in non-Latin languages (for example, Chinese).

sap.m.MultiInput has been refactored to improve performance and accessibility. The tokenChange() event is deprecated and replaced with the new tokenUpdate(). For more information, see the API Reference.

sap.m.NotificationListItem and sap.m.NotificationListGroup: We have implemented several new features:

When the maximum number of notifications is reached, a message is shown on the bottom of the NotificationListGroup notifying the user about additional notifications that are hidden.

o Action buttons have been moved from the footer of the NotificationListItem to the header to improve usability.

For more information, see the samples Notification List Item and Notification List Group with Max Number of Notifications Reached in the Explored app.

sap.m.PlanningCalendar: We have introduced a new rowHeaderClick event. You can now receive an event when a row header of the sap.m.PlanningCalendar is clicked. For more information, see the API Reference.

sap.m.QuickView and sap.m.QuickViewCard have a new parameter called navOrigin that improves the navigation when you use data binding. The new parameter is set in the navigate and afterNavigateevents and holds a link to the originating card. For more information, see the API Reference.

sap.m.Slider and sap.m.RangeSlider can display labels for tick marks. The labels are defined and represented as a sap.m.ResponsiveScale, which is logically decoupled from the slider. For more information, see the API Reference and the sample in the Explored app.

sap.m.Table: Screen reader support for sap.m.Table has been improved. For more information, see the API Reference.

sap.m.UploadCollection: To add an item to the upload list, you can also use drag & drop on your desktop or tablet. This feature is available in both the Instant Upload and Upload Pending scenarios. For more information, see the API Reference and the sample in the Explored app.

sap.ui.layout.form.Form: The samples in the Explored app have been improved.

sap.ui.table.*:

Keyboard navigation has been enhanced for Edit mode.

You can now define row-specific actions, such as navigation. The actions remain available on the right even when you scroll horizontally.

For more information, see the API Reference and the sample in the Explored app.

Demo Kit and Documentation Changes

You can now switch the Explored app to the new High Contrast White theme from the Settings menu.

We reworked the landing page for the Demo Apps in the Demo Kit. It now features and highlights demo apps in multiple categories, and tests and related documentation chapters are now linked. Check it out at Demo Apps.

New and Reworked Demo Apps:

Browse Orders: A new master-detail app with features for browsing orders

Shop Administrator : The tool page demo app has been completely renovated and now showcases a shop administration scenario with controls from the sap.tnt, sap.ui.layout, and sap.suite.ui library.

We are sure there is something exciting for you in this!

Your OpenUI5 Team!

#openui5 #sapui5 #beta release #new features #odata v4 #new controls #opa5

0 notes