I’m here again after a long time because i’m trying to migrate my 3.6 application in 4.2.
In 3.6 i used a tabbar with dhx_web skin and inside it i put a layout with dhx_skyblyue skin that was the same for all the object inside the layout.
All runned correctly. My willings were having a dhx_skyblue application with a different skin (dhx_web) only for the main tabbar.
Using 4.2 i’ve a problem in showing the objects inside my layout because: positions, padding, borders seems to be a mix between dhx_skyblue and dhx_web.
OK this is a project choice. In this context how can i solve the problem to use dhx_skyblue skin changing the apparence only of main tabbar (in the tabs i have other tabbars that follow the normal skin)
Something like in the pitcure: The tabbar is dhx_web. In the lower part i’ve a layout with dhx_skyblue with a grid with same skin.
Second problem. I’ve to use my application with Explorer 8 or Chrome
With dhx_skyblue the column header of a grid are normally shown in Chrome with borders.
With IE8 the borders are not shown ! Where is the problem ?
To explain the problem of border in grid header depending on browser i link this snapshot where you can see compared the two browsers showing a grid example of your documentaion.
What’s the problem ?
For the first problem i understood your way but i’d like to do exactly the opposite. Change the attributes of main tabbar and mantain the nested tabbar standard skyblue, something like you can see in the attachment to my previous post.
After a lot of experiments and surfing on Internet i found this patch.
DIV.isIE.gridbox_dhx_skyblue TABLE.hdr TD {
background-color: transparent;
}
This solution permit to view borders but I believe it does not allow viewing the gradient and anyway is not a full solution on the entire skin.
Will it possible to have the patch ?
[b][u]I've also the other question, following the Andrei's answer thanks.[/u][/b]
Well, actualy technique is the same. You need to apply some class to tabbar’s elements you need to change and add new rules. Use our online skin builder to generate colors.
Also you always can contact our sales department, they can help.
i tried to change the class name, as you explained, for the main tabbar that is included in the layout and then i changed the background-color.
javascript:
main_layout.cells(“b”).cell.className += " main_tabbar"
This code permits to modify the background-color of main tabbar but this is true also for furthter tabbars and this is the same with or without changing the name of nested tabbars. For sure it depends on the CSS hierarchy i suppose.
How can i solve the problem ? I’m not very good with CSS rules.
Another question. Did you find any solution for CSS gradient issue with IE8 (see my previous posts).
Hi Darya and many thanks for the sample that is very useful to learn the css rules of tabbar, but my problem is another.
I modified your example and attached it to this post to make you understand my problem. The first Tabbar is exactly what i want, but i attached another tabbar to layout’s cell “a”.
What i’d like to happen is that this “nested” tabbar (tab 4 and tab 5) were standard skyblue and not inherited the modified css rules. How you can see, instead, the nested tabbar inherit from the main one, even if i specified the skin in the configuration code.
How can i do?
Andrei in a previous post suggested to change the name of tabbar class but this is good to change the nested tabbar but not the main.
To show you the result i send you the reviewed example where i need another small help:
I used iframe as you suggested but how can i avoid the small border inside the iframe (margin - padding or somethin else) ???. I tried everything without success. I’m sure you will solve the problem in two seconds.
The last question concerns my previous post of 15th May about the grid headers border with IE8 and the Sematik’ answer. Did you find a solution.
This will permit me to abandon 3.6 suite and upgrade to 4.2.
The last question concerns my previous post of 15th May about the grid headers border with IE8 and the Sematik’ answer. Did you find a solution.
Unfortunately we’re still working on a solution.
