Hallo Stefan,
I was slightly surprised by your detailed question. Somehow you already know a lot :). But I have now found the E+H connection, and understand from where this question comes.
A check on our documentation resulted in nix. Due to situations outside our control (a number of little babies in last 12 months:), the raw draft of the information was never finalized for the documentation. This was not considered critical, as until now the skin development was a special case development we did long time ago for a perceived problem at a customer. But it was never used.
Never the less, for a copy of the draft documentation in my dry writing style, I would recommend OSS/CSN note 616900. This is the BSP FAQ note. In the attachments of this note, there is a very large document. Do a search in this FAQ for skin, and you will find all the text that I wrote light-years ago.
What is the design idea? For most problems, it is OK just to modify the stylesheets of the extension library to get a new look-and-feel. However, in the specific case, the customer wanted to also change our rendering. And they were looking at a complete rewrite of the total library. However, this is a lot of work, with a lot of risk. So with the skin manager, you can selectively replace the rendering of some tags only, and still use our library for most of the work.
However, this is to be used carefully. Always overwrite both beginning and end calls if you want to accept rendering responsibility for a specific control.
Finally, my recommendation, at least in the beginning, is to use the form below:
<%@page language="abap" skinManager="CL_BSP_MY_SKIN_MANAGER" %>
If you use the table, it applies for all BSP applications. Using a manager class, you can reference this only in your test pages, and can then work effectively in $TMP namespace for all development.
regards, brian
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.