‎2009 Aug 20 11:40 AM
How can I add a TABSTRIP to a Docking Container?
Any pointers to some snippet of code?
I was thinking of creating a screen which has a tabcontrol (say 100) but how do I add this screen to the docking container?
For adding TREE to docking container I have cl_simple_tree_model class which takes docking container as the parent. Is there a similar class for TABCONTROL also?
Regards,
Arpit
‎2009 Aug 20 11:49 AM
You can't place tabstrip in any of the containers (including docking container). Tabstrip is an example of classic control whereas containers are intended to store only GUI controls . Therefore you can place tabstrip only directly on screen layout, or in some subscreen which you dispaly on main screen. Still, however, you must place subscreen area on screen layout, so no way to do it via container.
Regards
Marcin
‎2009 Aug 20 11:49 AM
You can't place tabstrip in any of the containers (including docking container). Tabstrip is an example of classic control whereas containers are intended to store only GUI controls . Therefore you can place tabstrip only directly on screen layout, or in some subscreen which you dispaly on main screen. Still, however, you must place subscreen area on screen layout, so no way to do it via container.
Regards
Marcin
‎2009 Aug 20 12:12 PM
So it means Classic Screen can contain - GUI controls controls and GUI controls can contain - GUI controls only.
There is no way possible that GUI control having Classic Screen. Is there a reason behind this? Why it is so? And any work around from a UI design point of view.
I have a UI with two sections:
- Left view holds a tree and details informations about tree and user details.
- Right section holds screen based of which type of tree node is selected
Now left tree has three type of info and hence I want to categorize them using TABSTRIP. Any other component I can look into for achiving similar UI design?
Regards,
Arpit
‎2009 Aug 20 12:40 PM
So it means Classic Screen can contain - GUI controls controls and GUI controls can contain - GUI controls only.
Yup, GUI controls (only containers) can hold other GUI controls, but classic screen is intended to use them both (directly - classic controls, or inderictly - GUI controls).
There is no way possible that GUI control having Classic Screen. Is there a reason behind this? Why it is so? And any work around from a UI design point of view.
GUI controls (here containers - as these only can hold other GUI controls) can have any classic parts (subscreens, controls) inside it. For some technical reasons this is not possible. Classic controls reside in Application Server (in ABAP program), while GUI controls have their respective instance in SAP GUI (Frontend) called proxy objects . These two have different communication with each other (ABAP object <-> proxy object).
I have a UI with two sections:
- Left view holds a tree and details informations about tree and user details.
- Right section holds screen based of which type of tree node is selected
Now left tree has three type of info and hence I want to categorize them using TABSTRIP. Any other component I can look into for achiving similar UI design?
Instead of using docking container, you can make use of collapsible areas . This is special dialog technique which requires using subscreens. On the left you would place i.e. 3 areas (subscreen) each per one cathegory, in each would be a GUI Tree control. now you can collapse each area and exand depending on requirement (refere transaction BIBS -> link Collapsible Area ). In each such block you could place tree control. For details how to implement it refer
Antoher way would be placing tabstrip directly on screen layout (on the left) and inside each display one subscreen, in that place your custom container, in that place your GUI tree control. You would in fact have the functionality of resizing container (as in docking container) but you would achieve cathegorization.
Regards
Marcin