Now I'm developing a portal application with using JDev 126.96.36.199.0 version. In my app, there are lots of components like goImageLinks, goLinks etc. When i want to add some special attributes to these components, i overrided some selectors in "portal-skin.css" file just like "af|goImageLink:hover" "af|goImageLink:active" or "af|goLink"..
But there is a problem here : If a new goImageLink is added to the template or page, it's automatically affected from the selectors of "portal-skin.css" file. I mean the selectors is called default.
How can i find a solution for this problem? I just want to call my selectors whereever i want, not everywhere?
(P.S. : I created new skin files to call in specific points, but it didn't work.)
A portal skin is applied to the portal as a whole, you cannot say "I want to apply this skin to this element, but not to this element".
You can however create your own style classes, and refer to those instead. That way you can selectively style elements. Another downside of styling all elements of a particular type , such as af|goLink, is that it also affects the out-of-the-box pages and taskflows, such as the admin pages and document manager, and may produce undesired side-effects.
Hi Jaap, thanks for reply.
I do understand you. I created my skin files according to this document -> http://docs.oracle.com/cd/E25178_01/webcenter.1111/e10148/jpsdg_skin.htm
To call the selectors from my new skin file, i dragged it to the page source. When i added the selector to the component -just like< styleClass="myskin.css" >- , then the page entirely differ. Style of layouts, images etc. all of them are changing.
What do you think about this, why does it look like ?
I am not a CSS expert, but in your portal-skin.css you can define a style class like:
color: rgb(225, 0, 26);
and then for example add to a PanelGroupLayout you want to style like this the attribute styleClass="H2Style". That should do the trick.
You can easily create a new skin yourself by creating a new CSS file and making a portal resource of it (see 15.2.1).
I don't understand the part about "dragging" the CSS file, but I can see the page does not display correctly.
Probably there is some CSS missing that makes the content stretch on the page. And it display correctly if you switch back to the original skin? Then it should just be a matter of comparing the two files.
To call the styleClass, you have to import the css file in the page source. I mean i added the code to page source :
<link type="text/css" rel="stylesheet"
I hope it is clear now.
And also you are right, if i don't use newkin.css it is correctly working.
Edited by: erdo on 21.Ara.2012 12:16
If you are creating a portal skin, that is not the way to do it.
This way you are just referencing an external CSS file, but you want to treat the CSS as a portal resource.
15.4.4 Creating a Skin in JDeveloper and Making it Available at Runtime
15.5.1 Applying a Skin at Design Time
Sorry for replying late.
there is no problem for declaring in the adf-config.xml, it's done. How i can call my classes/selectors in page source ?
I mean is this code block true?
<af:goImageLink text="Kurumsal E-Posta" styleClass="aaa"
inlineStyle=" width:236px; float:left; font-family:Arial, sans-serif; font-size:12px; font-weight:normal; color: #3f3f3f; padding:11px 13px 10px 12px;text-decoration:none;"/>
p.s. : "aaa" is a class in the new-skin.css
If you have correctly added your new custom skin and are using it as your default skin now you can use a style class from the skin like that, yes.
Please make sure you get rid of the inlineStyle on your component too, that's exactly what you should use a style class for.
Thanks Jaap. I know using "inlineStyle" is not the exact solution, but i haven't got a better idea because of the fact that skin file isn't correctly working. I'll be more careful about it, thanks again.