Archana Turaga a �crit : > The cool thing i like about this approach is that since you > have the whole skinning out in the css and only the > definition in the xreg file it is easier to experiment with > colors...The skin.xreg if changed involves restarting the > webserver...with this new approach though now all i have to > do is specify everything in the css and keep changing the > colors and refreshing the browser to see how a new color > looks...i enjoy that aspect of it.
Yes, that makes the skin development much easier, I agree on that :) > I do have some problems though: > > It seems as if only a given portlet can get the skin. What if > i want to apply this skin to the whole portal. For whatever > reason when i go to my portal page i do not see the mynewskin > skin that i specified being applied. I set the skin in JRP > and also the css is set in the JRP. So i think i have > everything covered...Till i go manually to the portlet and > change the skin of the portlet i cannot see the new skin that i > applied. The skinning mechanism in jetspeed is the following : for each portlet, check if it has a skin, if not, check its parent. So if you want to apply a skin to all the skins present in a pane, you FIRST have to remove all overriden skins (means not "default" property) and then take the higher pane (or lower, depends what you want to do) to apply the skin. In your case, that must be because one of your panes (= portlet container) has a skin which is not "default", check this ;) I'd like to add the option "Add the skin to all sub-portlets/panes" in a future release (in fact that would be "Add the skin to current portlet, set sub-portlets as "default"), whenever I get time to work back on jetspeed :( > The other thing i noticed is this: > > I went to the jetspeed portal and clicked on the Global > customize button(this was just to see how the default > jetspeed website worked and if i messed something up in mine) > and tried to change the skin from orange-grey to something > else and that does not change the look of the whole portal > either. Is there a bug or something or am i missing? Same as above, "apply skin" only applies to current element and sub-elements that doesn't ALREADY have a skin, so that's the way it works. My advice : reset all your skins / panes to "default" (you must have one or more that are defined), and if you have to globally change a skin then take the highest pane possible. HTH, Aurelien --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
