Вы находитесь на странице: 1из 3

Uninstalling SAPUI5 Tools

Context
To uninstall all frontend components required for UI5 tools, proceed as follows:
Procedure
1
Launch your Eclipse workbench.
2
Choose
HelpAbout
.
3
Choose
Installation Details
.
4
Select the
SAPUI5
node and choose
Uninstall
.The
Uninstall Details
page displays a list of feature groups that will be uninstalled.
5
To start the uninstall function, choose
Finish
2.1.2 Versioning of SAPUI5
With SAPUI5 1.6 there is a close coupling of SAPUI5 core/runtime and SAPUI5 tool
s: It is required that within a running system both have the same version, that
is, have the same major and minor version. For example, SAPUI5 core/runtime 1.6.
1 works together with SAPUI5 tools 1.6.2, but not with SAPUI tools 1.8. For a fu
ture release it is planned to have a more lose coupling here with regards to the
minor and micro version. Please note that with SAPUI5 1.6 we can only support c
ustomers, which follow this rule in their system landscapes.
10
PUBLIC

2014 SAP SE or an SAP affiliate company. All rights reserved.SAPUI5 Developer G


uide for SAP HANA
SAPUI5 Developer Guide
2.1.3 Upgrading jQuery for SAPUI5
When upgrading to SAPUI5 1.20.0, check whether the changes listed below influenc
e the application:
Upgrade to jQuery version 1.10.2
This upgrade requires changes to SAPUI5 controls and may also influence other co
ntrols or the application. For more information about the jQuery upgrade, see th
e jQuery Upgrade Guide. The following list gives an overview of the changes that
affect SAPUI5.
?
Findings
?
Setting height or width of a JQuery objectWhen setting the height or width of an
object via
jQuery(...).height("1px")
and the object used the CSS-property
box-sizing
, the height of the box instead of the content was changed. As of jQuery 1.8.0,
the function changes the content height regardless of the

box-sizing
property.For more information and recommendations, see the jQuery API documenta
tion on
http:// api.jquery.com
.
?
jQuery( ).data("events")jQuery(...).data("events")
has been removed with jQuery 1.9. An alternative is now available and part of t
he
QUnitUtils
:
jQuery#_sapTest_dataEvents()
.
?
strictEqual
in QUnit testsDo
not
compare
jQuery(...).attr("tabindex")
with
strictEqual
or
===
. As an alternative, use string values or
prop("tabindex")
which returns a parsed value.
?
font-weight: "normal"
jQuery 1.10 converts
font-weight: "normal"
to the value 400. The workaround
jQuery#_sapTest_cssFontWeight()
is provided in
QUnitUtils
that hides the differences between browser and jQuery.
?
Check for jQuery versionTo fix issues for a newer or different jQuery version, y
ou can use
jQuery.sap.Version(jQuery.fn.jquery).toString()
or
jQuery.sap.Version(jQuery.fn.jquery).getMajor()
to check the version. You use this core function to check the major, minor, pat
ch and all appending stuff of the version.
?
Deprecated and removed functions
?
CommonCheck for functions that have been deprecated in jQuery versions 1.7, 1.8,
or 1.9 and may have been removed in jQuery 1.10. See the corresponding jQuery d
ocumentation.
?
.live()
This function has been set as deprecated in jQuery version 1.7 and was removed i
n jQuery version 1.9. For recommendations how to replace the
.live()
function, see the respective jQery documentation.
SAPUI5 Developer Guide for SAP HANA
SAPUI5 Developer Guide
PUBLIC

2014 SAP SE or an SAP affiliate company. All rights reserved.

11
JQuery UI Upgrade to 1.10.4
jQuery UI version 1.10.4 contains incompatiple changes to jQuery UI version 1.8.
23. For more information, see the jQuery UI 1.9 Upgrade Guide and the jQuery UI
1.10 Upgrade Guide.A major incompatiple change is in
jQuery.ui.position
, where the offset property has been removed. SAPUI5 runtime adopted this change
, for example in
Popup
, but applications may need to adopt their logic too.Also, the file names for jQ
uery UI effects have changed. Applications using the jQuery UI effects may also
have to adopt their logic. In IE8 and jQuery version <1.8, the detection whether
the new
jQueryUi
logic is active or not fails. This may be due to interaction issues between jQu
ery UI version 1.10 and jQuery version 1.7. In this case, the new jQuery UI posi
tion logic is used: Applications that still want to use jQuery version 1.7.1 and
jQuery UI version 1.8 or older have to load the jQueryUI core and not only the
position module).

Вам также может понравиться