Change of Layout/Look and Feel in BI 7 Reports.

Hi,
This is Prem from NetWeaver Portals.
Currently we have a couple of BI 7.0 reports integrated into portal.
We have also used Portal Themes to alter the Look and Feel of the BI reports with respect to Heading colors, alternate row colors etc. But the scope of changing the Look and feel of BI reports from the Portal theme is very limited.
Is there a way to modify it further from BI's CSS?
Where is this functionality provided in SAP BI 7.0?
We are also interested in changing the Layout of the reports in BI. i.e. unlike the standard BI format of reports as generated from the Web Application designer, we would like to change the layout as well.
How is this layout change carried out? Web Templates?
Kindly spell out a solution for me as I'm not aware of BI
Thanks and Regards,
Prem

Could yo please explain little detial. how do you changed the look and feel of reports through the portal themes. We are trying to change the colors of the execptions and text box and some more. we have created a custom theme in which we changed the complex formatted table crictal, bad, good colors. when we assigned this theme through personalization to the user, custom theme colors are not seen in the BW report.
Please let us know
thanks and regards
venkata bandi

Similar Messages

How to change the default look and feel

Hi.
Does anyone knows how to change the default Caspian look and feel to, for example, Nimbus ?
Or the skin feature turns look and feel setting, as We know in java, unnecessary in javafx ?
I´m using javafx 1.2.
Cheers

Canspian is not a look&feel, it's a skin.
Look&feel only change the SwingComponent,
regards.

Extending JComboBox behavior and changing look and feel

In order to change JComboBox behavior, usually we will extend the MetalComboBoxUI or WindowsComboBoxUI (for example: for controlling the popup width)
The problem arise when we want to be able to change the pluggable look and feel: all components got the new look and feel except for the comboboxes.
A dirty solution can be extending our ComboBoxUI from the new look and feel library but in the case of jgoodies it is even impossible because PlasticComboBoxUI is final
Any ideas?

In order to change JComboBox behavior, usually we will extend the MetalComboBoxUI or WindowsComboBoxUI (for example: for controlling the popup width).
The problem arise when we want to be able to change the pluggable look and feel: all components got the
new look and feel except for the comboboxes. A dirty solution can be extending our ComboBoxUI from
the new look and feel library but in the case of jgoodies it is even impossible because PlasticComboBoxUI is final
My best suggestion: request the L&F provider to make his combo box homogeneous with the other components.

NetBeans: Dinamically changing Look and Feel Problem

Hi there, Java lovers.
I need some help here!
I love java, and I used to program my graphical user interfaces by hand. In my applications, there is a dropdown for the user to chose the desired look and feel. Then I save the selected option to a file and on the startup I do something like this:
UIManager.setLookAndFeel(savedUserSelectedLookAndFeel);That always worked really fine. The look and feel would change and everything worked really well.
However, programing GUI by hand is really a PITA. So I was seduced by Netbeans. I am using Netbeans 6.0 on Windows XP, and I designed the GUIs really fast now.
The problem is, the system look and feel works really well, but when I change the look and feel of my application to a different one (Java/Motif/etc..) the look and feel changes but the components positions and sizes becomes all messed up. It really becomes impossible to work with a different look and feel because some components are outside of frames.
I believe the cause of this is because Netbeans generates the code automatically using Grids and stuff like that, and by doing so, the change of the look and feel becomes messed up. This is a thing that would not happen with my manually created code.
This is really troubling me. Does someone has the same problem. Is there something I can do? Or do I need to create my GUIs by hand like before?

Oyashiro-sama (少し日本語を知っているし、そんな「様」っていう使い方はちょっと変そうですね　(^_-) 「冗談」っていう顔文字です。）
Sorry for the delay in reply, but one problem for you is that this is not a NetBeans users forum, thus you will not necessarily receive speedy replies here to your NetBeans questions. The best place to send NetBeans questions is:
[email protected]
[email protected] (for NetBeans API issues)
As for your question, you seem to already know quite a bit about NetBeans UI Look and Feel programming, but have you seen these:
WORKING WITH SWING LOOK AND FEEL:
http://java.sun.com/developer/JDCTechTips/2004/tt0309.html#1
Java GUI Swing Programming Using NetBeans 5 (should apply to NetBeans 6):
http://wiki.netbeans.org/JavaGUISwingProgrammingUsingNetBeans5
Regards,
-Brad Mayer

Function to change Boarder Look and feel of Jframe - Not working

Hi all,
In the given SSCE, the functionpublic void changeButtonColor(Component[] comps) to change the border look and feel of JFrame is not working.Please help.
import java.awt.BorderLayout;
import java.awt.Color;
import java.awt.Component;
import java.awt.Container;
import java.awt.Dimension;
import java.awt.FlowLayout;
import java.awt.Insets;
import java.util.Vector;
import javax.swing.AbstractButton;
import javax.swing.BorderFactory;
import javax.swing.JButton;
import javax.swing.JFrame;
import javax.swing.JLabel;
import javax.swing.JPanel;
import javax.swing.JScrollPane;
import javax.swing.JViewport;
import javax.swing.SwingConstants;
import javax.swing.UIManager;
public class ScrollableWrapTest {
    public static void main(String[] args) {
        try {
            final JPanel mainPanel = new JPanel(new WrapScollableLayout(FlowLayout.LEFT, 10, 10));
            mainPanel.setBackground(Color.WHITE);
            JScrollPane pane = new JScrollPane(mainPanel);
            pane.setPreferredSize(new Dimension(320, 200));
            Vector v = new Vector();
            v.add("first");
            JButton button = null;
            for(int i =0;i<v.size();i++){
                    JPanel panel = new JPanel(new BorderLayout());
                    panel.setBackground(Color.WHITE);
                    int num = mainPanel.getComponentCount()+1;
                    button = new JButton("button" + num);
                    button.setPreferredSize(new Dimension(90, 25));
                    JLabel label = new JLabel((String)v.elementAt(i));
                    label.setHorizontalAlignment(SwingConstants.CENTER);
                    panel.add(button, BorderLayout.NORTH);
                    panel.add(label, BorderLayout.SOUTH);
                    mainPanel.add(panel);
                    mainPanel.revalidate();
            ScrollableWrapTest st = new ScrollableWrapTest();
            st.buildGUI(pane);
        } catch (Exception e) {e.printStackTrace();}
    public void buildGUI(JScrollPane scrollPane)
         JFrame frame = new JFrame("Scrollable Wrap Test");
         JFrame.setDefaultLookAndFeelDecorated(true);
        UIManager.put("activeCaption", new javax.swing.plaf.ColorUIResource(Color.LIGHT_GRAY));
        changeButtonColor(frame.getComponents());
        frame.setDefaultCloseOperation(JFrame.EXIT_ON_CLOSE);
        frame.add(scrollPane, BorderLayout.CENTER);
        frame.setLocationRelativeTo(null);
        frame.pack();
        frame.setVisible(true);
    public void changeButtonColor(Component[] comps)
      for(int x = 0, y = comps.length; x < y; x++)
        if(comps[x] instanceof AbstractButton)
          ((AbstractButton)comps[x]).setBackground(Color.LIGHT_GRAY);
          ((AbstractButton)comps[x]).setBorder(BorderFactory.createLineBorder(Color.LIGHT_GRAY));
        else if (comps[x] instanceof Container)
          changeButtonColor(((Container)comps[x]).getComponents());
    private static class WrapScollableLayout extends FlowLayout {
        public WrapScollableLayout(int align, int hgap, int vgap) {
            super(align, hgap, vgap);
        public Dimension preferredLayoutSize(Container target) {
            synchronized (target.getTreeLock()) {
                Dimension dim = super.preferredLayoutSize(target);
                layoutContainer(target);
                int nmembers = target.getComponentCount();
                for (int i = 0 ; i < nmembers ; i++) {
                    Component m = target.getComponent(i);
                    if (m.isVisible()) {
                        Dimension d = m.getPreferredSize();
                        dim.height = Math.max(dim.height, d.height + m.getY());
                if (target.getParent() instanceof JViewport)
                    dim.width = ((JViewport) target.getParent()).getExtentSize().width;
                Insets insets = target.getInsets();
                dim.height += insets.top + insets.bottom + getVgap();
                return dim;
}Please help.
Rony

You are calling changeButtonColor(frame.getComponents()) before you add the JScrollPane to the content pane.
But why not just move this to the button creation loop?
button = new JButton("button" + num);
button.setBackground(Color.LIGHT_GRAY);
button.setBorder(BorderFactory.createLineBorder(Color.LIGHT_GRAY));

SAP Portal Custom Themes to change ESS/MSS UI Look and feel , possible ?

Hi,
I have a requirement where the look and feel of the UI controls of the ESS/MSS applications have to be different - Jazzy
I know XSS homepage framework is for the customisation of Areas, Sub Areas. What I am more interested is only the look and feel UI of ESS/MSS applications.
If I change the standard theme of portal using Theme Editor and create a new custom theme with different back ground colors, fonts, sizes for all the UI controls,.Will the customised Theme apply on the standard ESS / MSS screens ? Also my doubt is we are using EHP3 and I am not sure how many are Webdynpro java based or webdynpro Abap based.
Will the theme apply to both WDA and WDJ application UI controls?
Any inputs in this regard will be of great help. thanks in advance.
Regards,
Sreeram

Hello,
Check :
[Overview on changing the Portal look and feel.|https://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/d077fa17-7fbf-2a10-d983-fb12decf63c7]
FYI :- Search for wiki on : Stylesheet for WDA without integrating in SAP Portal
Cheers,
Remi

Problem With ButtonUI in an Auxiliary Look and Feel

This is my first post to one of these forums, so I hope everything works correctly.
I have been trying to get an axiliary look and feel installed to do some minor tweaking to the default UI. In particular, I need it to work with Windows and/or Metal as the default UI. For the most part I let the installed default look and feel handle things with my code making some colors lighter, darker, etc. I also play with focus issues by adding FocusListeners to some components. I expect my code to work reasonably well no matter what the default look and feel is. It works well with Motif, Metal, and Windows, the only default look and feels I've tested with. What I'm going to post is a stripped down version of what I have been working on. This example makes gross changes to the JButton background and foreground colors in order to illustrate what I've encountered.
I have three source code files. The first, Problem.java, creates a JFrame and adds five buttons to it. One button installs MyAuxLookAndFeel as an auxiliary look and feel using MyAuxButtonUI for the look and feel of JButtons. The next button removes that look and feel. The next button does nothing except print a line to System.out. The next button installs MyAuxLookAndFeel as an auxiliary look and feel using MyModButtonUI for the look and feel of JButtons. The last button removes that look and feel.
The problem is, when I install the first auxiliary look and feel, buttons are no longer tabable. Also, they cannot be invoked by pressing the space button when they're in focus. When I remove the first auxiliary look and feel everything reverts to behaving normally. When I add the "Mod" version, button tabability is fine. The only difference is I've added the following code:
if ( c.isFocusable() ) {
   c.setFocusable(true);
}That strikes me as an odd piece of code to profoundly change the program behavior. Anyway, after adding and removing the "Mod" look and feel, the tababilty is forever fixed. That is, if I subsequently re-install the first look and feel, tababilty works just fine.
The problem with using the space bar to select a focused button is more problematic. My class is not supposed to mess with the default look and feel which may or may not use the space bar to press the button with focus. When the commented code in MyModButtonUI is uncommented, things behave correctly. Even the statement
button.getInputMap().remove( spaceKeyStroke );doesn't mess things up after the auxiliary look and feel is removed. So far I've tested this with JRE 1.4.2_06 under Windows 2000, JRE 1.4.2_10 under Windows XP, and JRE 1.5.0_06 under Windows XP and the behavior is the same.
All of this leads me to two questions.
1. Is my approach fundamentally flawed? I've extended TextUI and ScrollBarUI with no problems. This is the only problem I've encountered with ButtonUI. My real workaround for the space bar issue is better than the one I've supplied in the example, but it certainly is not guaranteed to work for any arbitrary default look and feel.
2. Assuming I have no fundamental problems with my approach, it's possible I've found a real bug. I searched the bug database and couldn't find anything like this. Of course, this is the first time I've tried seasrching the database for a bug so my I'm doing it badly. Has this already been reported as a bug? Is there any reason I shouldn't report it?
What follows is the source code for my example. It's in three files because the two ButtonUI classes must be public in order to work. Thanks for insight you can provide.
Bill
File Problem.java:
import javax.swing.*;
import java.awt.*;
import java.awt.event.*;
public class Problem extends JFrame {
   public boolean isAuxInstalled = false;
   public boolean isModInstalled = false;
   public LookAndFeel lookAndFeel = new MyAuxLookAndFeel();
   private static int ctr = 0;
   public static void main( String[] args ) {
      new Problem();
   public Problem() {
      this.setDefaultCloseOperation(JFrame.EXIT_ON_CLOSE);
      setSize(250, 150);
      setTitle("Button Test");
      JButton install = new JButton("Install");
      JButton remove = new JButton("Remove");
      JButton doNothing = new JButton("Do Nothing");
      JButton installMod = new JButton("Install Mod");
      JButton removeMod = new JButton("Remove Mod");
      this.getContentPane().setLayout(new FlowLayout());
      this.getContentPane().add(install);
      this.getContentPane().add(remove);
      this.getContentPane().add(doNothing);
      this.getContentPane().add(installMod);
      this.getContentPane().add(removeMod);
      install.addActionListener(new ActionListener() {
         public void actionPerformed(ActionEvent e) {
            if ( !isAuxInstalled ) {
               isAuxInstalled = true;
               UIManager.addAuxiliaryLookAndFeel( lookAndFeel );
               SwingUtilities.updateComponentTreeUI( Problem.this );
      remove.addActionListener(new ActionListener() {
         public void actionPerformed(ActionEvent e) {
            if ( isAuxInstalled ) {
               isAuxInstalled = false;
               UIManager.removeAuxiliaryLookAndFeel( lookAndFeel );
               SwingUtilities.updateComponentTreeUI( Problem.this );
      doNothing.addActionListener(new ActionListener() {
         public void actionPerformed(ActionEvent e) {
            System.out.println( "Do nothing " + (++ctr) );
      installMod.addActionListener(new ActionListener() {
         public void actionPerformed(ActionEvent e) {
            if ( !isModInstalled ) {
               isModInstalled = true;
               UIManager.addAuxiliaryLookAndFeel( lookAndFeel );
               SwingUtilities.updateComponentTreeUI( Problem.this );
      removeMod.addActionListener(new ActionListener() {
         public void actionPerformed(ActionEvent e) {
            if ( isModInstalled ) {
               isModInstalled = false;
               UIManager.removeAuxiliaryLookAndFeel( lookAndFeel );
               SwingUtilities.updateComponentTreeUI( Problem.this );
      setVisible(true);
   class MyAuxLookAndFeel extends LookAndFeel {
      public String getName() {
         return "Button Test";
      public String getID() {
         return "Not well known";
      public String getDescription() {
         return "Button Test Look and Feel";
      public boolean isSupportedLookAndFeel() {
         return true;
      public boolean isNativeLookAndFeel() {
         return false;
      public UIDefaults getDefaults() {
         UIDefaults table = new MyDefaults();
         Object[] uiDefaults = {
            "ButtonUI", (isModInstalled ? "MyModButtonUI" : "MyAuxButtonUI"),
         table.putDefaults(uiDefaults);
         return table;
   class MyDefaults extends UIDefaults {
      protected void getUIError(String msg) {
//         System.err.println("(Not) An annoying error message!");
}File MyAuxButtonUI.java:
import javax.swing.*;
import java.awt.*;
import javax.swing.plaf.*;
import javax.swing.plaf.multi.*;
import javax.accessibility.*;
public class MyAuxButtonUI extends ButtonUI {
   private Color background;
   private Color foreground;
   private ButtonUI ui = null;
   public static ComponentUI createUI( JComponent c ) {
      return new MyAuxButtonUI();
   public void installUI(JComponent c) {
      MultiButtonUI multiButtonUI = (MultiButtonUI) UIManager.getUI(c);
      this.ui = (ButtonUI) (multiButtonUI.getUIs()[0]);
      super.installUI( c );
      background = c.getBackground();
      foreground = c.getForeground();
      c.setBackground(Color.GREEN);
      c.setForeground(Color.RED);
   public void uninstallUI(JComponent c) {
      super.uninstallUI( c );
      c.setBackground(background);
      c.setForeground(foreground);
      this.ui = null;
   public void paint(Graphics g, JComponent c) {
      this.ui.paint( g, c );
   public void update(Graphics g, JComponent c) {
      this.ui.update( g, c );
   public Dimension getPreferredSize(JComponent c) {
      if ( this.ui == null ) {
         return super.getPreferredSize( c );
      return this.ui.getPreferredSize( c );
   public Dimension getMinimumSize(JComponent c) {
      if ( this.ui == null ) {
         return super.getMinimumSize( c );
      return this.ui.getMinimumSize( c );
   public Dimension getMaximumSize(JComponent c) {
      if ( this.ui == null ) {
         return super.getMaximumSize( c );
      return this.ui.getMaximumSize( c );
   public boolean contains(JComponent c, int x, int y) {
      if ( this.ui == null ) {
         return super.contains( c, x, y );
      return this.ui.contains( c, x, y );
   public int getAccessibleChildrenCount(JComponent c) {
      if ( this.ui == null ) {
         return super.getAccessibleChildrenCount( c );
      return this.ui.getAccessibleChildrenCount( c );
   public Accessible getAccessibleChild(JComponent c, int ii) {
      if ( this.ui == null ) {
         return super.getAccessibleChild( c, ii );
      return this.ui.getAccessibleChild( c, ii );
}File MyModButtonUI.java:
import javax.swing.*;
import java.awt.*;
import java.awt.event.*;
import javax.swing.plaf.*;
public class MyModButtonUI extends MyAuxButtonUI
   static KeyStroke spaceKeyStroke = KeyStroke.getKeyStroke(KeyEvent.VK_SPACE, 0 );
   public static ComponentUI createUI( JComponent c ) {
      return new MyModButtonUI();
   public void installUI(JComponent c) {
      super.installUI(c);
      c.setBackground(Color.CYAN);
      if ( c.isFocusable() ) {
         c.setFocusable(true);
//      final JButton button = (JButton) c;
//      button.getInputMap().put( spaceKeyStroke, "buttonexample.pressed" );
//      button.getActionMap().put( "buttonexample.pressed", new AbstractAction() {
//         public void actionPerformed(ActionEvent e) {
//            button.doClick();
//   public void uninstallUI(JComponent c) {
//      super.uninstallUI(c);
//      JButton button = (JButton) c;
//      button.getInputMap().remove( spaceKeyStroke );
//      button.getActionMap().remove( "buttonexample.pressed" );
}

here is the code used to change the current look and feel :
try {
               UIManager.setLookAndFeel("com.sun.java.swing.plaf.motif.MotifLookAndFeel");
         catch (InstantiationException e)
              System.out.println("Error occured "+ e.toString());
         catch (ClassNotFoundException e)
              System.out.println("Error occured "+ e.toString());
         catch (UnsupportedLookAndFeelException e)
              System.out.println("Error occured "+ e.toString());
         catch (IllegalAccessException e)
              System.out.println("Error occured in .. " + e.toString());
         Dimension dim = Toolkit.getDefaultToolkit().getScreenSize();
         Fenetre fen = new Fenetre();
         fen.setSize(dim.width, dim.height);
         fen.setResizable(false);
             fen.setLocation(0, 0);
              fen.setVisible(true);

Look and feeling err

i use these to change the frame look and feeling:
try {
UIManager.setLookAndFeel(new oracle.bali.ewt.olaf.OracleLookAndFeel());
} catch (Exception e) {
e.printStackTrace();
but jdev show err like this:
Exception in thread "main" java.lang.NoClassDefFoundError: oracle/bali/share/util/IntegerUtils
     at oracle.bali.ewt.olaf.OracleLookAndFeel.initComponentDefaults(Unknown Source)
     at javax.swing.plaf.basic.BasicLookAndFeel.getDefaults(BasicLookAndFeel.java:97)
     at javax.swing.UIManager.setLookAndFeel(UIManager.java:441)
     at fytest.main.main(main.java:30)

Hi,
it means that at runtime you are obviously missing some classes. So you need to identify the JAR file containing the look and feel classes and put them into the library path.
Frank

Can we change the look and feel of the screen layout

Dear All,
I am new to ABAP WebDynpro, and would like to know the following with respect to ABAP WebDynpro :
1. To what extent can we change the look and feel of the screen layout ?
2. Is it possible to change the background color of the layout?
3. Is it possible to change the color of, Buttons etc ?
Any information / document/ link to explain this would be very helpful ..
Thanks in advance,
Aditi

Hi,
Psl check out these links.
check out these webdynpro standard components in SE80 tcode -
WDR_TEST_UI_ELEMENTS
check out this link on webdynpro for ABAP-
http://help.sap.com/saphelp_nw70/helpdata/EN/03/0048413e466e24e10000000a155106/frameset.htm-WD for ABAP
http://help.sap.com/saphelp_nw70/helpdata/EN/46/9319f88f8115ebe10000000a114a6b/frameset.htm -UI elements
http://help.sap.com/saphelp_nw70/helpdata/EN/46/9319f88f8115ebe10000000a114a6b/frameset.htm-Button Properties
http://help.sap.com/saphelp_nw70/helpdata/EN/46/9319f88f8115ebe10000000a114a6b/frameset.htm- For different Layouts
Regards
Lekha

How can we remove the space after changing look and feel to generic

Hi
I want to remove the space which left blank after changing look and feel to generic in formsweb.cfg file.
Can anybody help me to remove this blank space.

Hi,
can you be more specific on teh space you mean?
Frank

How Can You Change the Look and Feel of Charts in OBIEE 11g

How Can You Change the Look and Feel of Charts in OBIEE 11g?
Edited by: user11973122 on Jul 18, 2012 12:13 AM

Check these files
OFM_HOME\Oracle_BI1\bifoundation\web\msgdb\s_blafp\viewui\chart\dvt-graph-skin.xml
OFM_HOME\Oracle_BI1\bifoundation\web\msgdb\views\dvtchart\obips.dvtchart.xml
OFM_HOME\Oracle_BI1\bifoundation\web\display\chartfontmapping.xml
Pls mark correct or helpful if helps

How to change the look and feel for Heading of quick launch menu in project server 2010

Hi
can someone tell me how to change the look and feel of Header names in quick launch.
I want the header to be displayed in Bold with Underline to it.
could this be possible for just header in quick launch in project server 2010.

Hi Rohan
It does not work this way. You have to use a content editor webpart.
See references below that might help you starting with this customisation:
Http://go4answers.webhost4life.com/Example/sharepoint-2010-quick-launch-look-feel-78379.aspx
Http://m.sharepointpromag.com/sharepoint/four-ways-add-or-remove-quick-launch-menu-control
Hope this helps.
Guillaume Rouyre - MBA, MCP, MCTS

UIX: change image in corporateBranding dependent on choosen Look And Feel

Is it possible to change a image used in the corporateBranding dependent on choosen Look And Feel?

If your corporate branding is an image, you can to bind the "source" attribute and return the appropriate image depending on the laf. You can get the laf off the renderingContext. The data binding chapter is here:
http://helponline.oracle.com/jdeveloper/help/state/content/vtTopicId./navSetId.jdeveloper/vtTopicFile.jdeveloper%7Cuixhelp%7Cuixdevguide%7Cdatabinding%7Ehtml/navId.4/

Change XP Look and Feel Rollover Highlight Color

Is it possible to change the orange rollover highlight color that is used in the Windows XP Look and Feel? If so, how? I want to change it in once place and see the results on every component in my application.

By the way, I'm using 1.5

Change in look and feel

Hi
After the Server has restarted the look and feel of the portal has been changed.
could any one tell me what could be the problem for this change?
regards
ambicasony

Ok,
is it a bad looking look and feel, i mean do you think this look and feel contains error or is kind of bugged ?
what i am trying to know, is if this new look and feel cames from a portal desktop change or if it is really a bug.
Message was edited by:
Fabien REVOL

Change of Layout/Look and Feel in BI 7 Reports.

Similar Messages

Maybe you are looking for