Skip to Content
0

Add old sapui5/openui5 library into Design Studio SDK

Jan 18, 2017 at 05:50 PM

48

avatar image

Hi,

i am currently facing a problem with Design Studio 1.6 SP4 (openui5 1.38). After the update i ran into problems with our sapui5 treetable component. Rendering as well as CSS issues.

Right now, due to the time issues, i am trying to include the old ui5 Version (1.30) into my sdk Extension.

I added the sap-ui-core-js file of the old library via the requirejs tag in the contribution.xml. Libraries are located in my development Project. But it seems that is not sufficient. The Extension tries to load the Default libraries from design Studio. Am i missing something? Is the something else i have to adjust?

Best regards

Saood

10 |10000 characters needed characters left characters exceeded
* Please Login or Register to Answer, Follow or Comment.

2 Answers

Mustafa Bensan Jan 19, 2017 at 06:52 AM
0

Hi Saood,

I have faced the same issue frequently during upgrades of Design Studio for SDK components that use the built-in UI5 library. More often than not, CSS or other rendering tweaks are required. Although you have indicated you have time constraints, my recommendation is that you stick with the built-in UI5 library and implement appropriate fixes for the rendering and CSS issues instead of trying to override with the old version of the UI5 library.

When you use Handler Type "ui5" for an SDK extension, as would be the situation in your case, Design Studio will load the built-in UI5 library by default. If you then try to load an older version of the same UI5 library, I suspect that you are likely to get other conflicts to resolve, which may be more trouble than it's worth.

Regards,

Mustafa.

Share
10 |10000 characters needed characters left characters exceeded
Saood Alvi Jan 19, 2017 at 04:32 PM
0

Hi Mustafa,

thanks for your reply!

I agree with you. We should always try to fix the bugs we run into. And thats' what I'm trying to do (as you know still working on it (; ). The idea was to make sure something like this does not happen again with the next update. As developers, we cannot always control planned updates of the DS environment. Especially, after a project finishes and the product is live. It is an attempt to assure an always running product. I understand, that this is not best practice. It's simply another approach.

So you don't have any idea how to encapsulate an old library?

Best regards

Saood

p.s.: I am, by the way, still trying to fix the original bugs > new question might be coming :)

Share
10 |10000 characters needed characters left characters exceeded