Questions regarding Personas Flavor conversion to Slipstream

[former_member238607]

Hi,

We are running Personas 3.0 SP7. I have some existing flavors that I would like to convert to Slipstream flavors, but I have some issues I'm running into. The flavors that I'm working on are designed for use on desktops or laptops, not on mobile devices.

1. The FioriStatusBar at the bottom of the screen does not completely fill the area - there is a white border that surrounds it on all four sides. This does not provide a polished look to the screen. The only way I've found to hide it is to make the FioriStatusBar background color white also, which does not blend in well with the Fiori look. Is there a way to remove this border? If not, can this be a future enhancement request?
2. In standard flavors, I use session.info.clientWidth to position objects on the screen. When I attempt to use that in Slipstream, objects that should be centered are pushed to the right-side of the screen, and objects that I'm trying to position on the right of the screen are actually located so far right you have to scroll over to see them. The value returned by session.info.clientWidth seems to be the same in both rendering engines. It's almost like Slipstream uses a different pixel size (or some other unit of measure). I've noticed similar issues with objects created in the traditional rendering engine appearing much larger in Slipstream.

I'd appreciate help on any or all of these issues. Thanks!

[tamas_hoznek · Accepted solution]

Hi Jeff,

let me copy the explanation from another colleague, which was sent as a response to a similar customer incident. Slipstream Engine uses the Belize theme vs. the default Blue Crystal via the personas service.

"The different scale for objects doesn't depend on SAP GUI for HTML or Slipstream Engine, but on the used theme. I would like to give you some background information on the units and metrics that we deal with in SAP Screen Personas.

Both, SAP GUI for HTML and Slipstream Engine render SAP Dynpro screens, that have been defined in the ABAP backend using proprietary units. The values in these units need to be converted in CSS values, in our case px, in order to render those screens in an HTML browser. The conversion factor depends on the used theme.

Let me explain this for one example, the user name field in SU01.
The user name field (SUID_ST_BNAME-BNAME) has a length of 12 defined in the dynpro screen. The formula to convert this into pixel is
px value = (dynpro length + 1) * 8 * theme width factor

The theme width factors are as follows:
sap_bluecrystal 1
sap_belize 1.25

That means, the pixels sizes differ in sap_bluecrystal and sap_belize:
sap_bluecrystal: (12 + 1) * 8 * 1 = 104
sap_belize: (12 + 1) * 8 * 1.25 = 130

I hope this helps to understand the different scaling."

[former_member238607]

Hi Tamas,

Thanks for the explanation.

From what I can tell, this must only apply to width? I have objects that are square in Blue Crystal, but become rectangles (wider width) in Belize. If the height is impacted, it must be much less than the width.

Thanks again!

Jeff

[tamas_hoznek]

As far as I'm aware, there should also be a factor for height, although it's possible this is different than the width factor, and the result can be less obvious to see.