IC_BASE look and feel (Default theme) very urgent !!!

Hi Gurus,
Somehow the theme of my BSP application ic_base has been changed, entire look and feel of the application has been changed. Is the link between ic_base.css file with the ic_base bsp application has been changed?
How can I restore my look and feel of my application?
Very urgent!!!!
regards,
Abhi...

avoid duplicate threads. continue the discussion in your old thread at
BSP portal display problem (Urgent!!!)

Similar Messages

Look And Feel: Metal Themes

Hello,
I have two basic questions I can't find the answer to. I hope someone can help.
From my understanding of Java 1.5 you now have 2 basic themes to them metal look and feel, they are "Ocean" (the default) and "Steel". Is this understanding correct?
My second question is, I can switch between Look & Feels, ie. default to system, how do you switch between themes though? I want to use "Steel" but can't !
Thanks,
Alan

How to Set the Lood and Feel:
http://java.sun.com/docs/books/tutorial/uiswing/misc/p
laf.htmlThat actually doesn't tell you how to do what he's asking.. at least not from what I saw.
Here's how to set the metal theme in 1.5:
import javax.swing.plaf.metal.*;
public static final String STEEL_THEME_CLASS = "javax.swing.plaf.metal.DefaultMetalTheme";
public static final String OCEAN_THEME_CLASS = "javax.swing.plaf.metal.OceanTheme";
public void changeMetalTheme(String themeName) {
   try {
      MetalTheme theme = (MetalTheme)Class.forName(themeName).newInstance();
      MetalLookAndFeel.setCurrentTheme(theme);
   catch (Exception e) { e.printStackTrace(); }
}Note that if you do this after you've created your GUI, you'll have to call SwingUtilities.updateComponentTreeUI() on all top-level windows.

BSP - Look and Feel / Theme

Good Morning All,
disclaimer: I checked the blogs, I checked the discussions, I checked the examples, I checked the doco - and couldn't find the answer to my question.
Question:
I've already seen it, but can't remember where it is, does anyone know the name of the BSP Sample/Example which comes with the WAS which has the EP6 look and feel ?
I saw it a few weeks ago and I can't find it now and I want to study the code from it to make my app have a nicer look and feel.
Note: I read Thomas's blog on - 'A developer's Journal Part VI
and although that example discussed what I am interested in I couldn't see examples in the code of creating the header bar etc, maybe it's just me, but at the moment that's what I would like to achieve and to do it by example.
So to conclude if anyone knows / can remember the name of the BSP example which has an EP6 look and feel please let me know so that I can study it for inspiration.
Thanks very much,
Milan.

Hallo Milan,
I think that you are doing good. It is always the best to follow a small mix of documentation reading and practical work. So let me tell you the minimum to get a first version working. Thereafter to can continue reading!
Problem: we want to implement a simple link tag (in 15 minutes!) that works like this:
<%@page language="abap"%>
<%@extension name="htmlb" prefix="htmlb"%>
<%@extension name="bcm06" prefix="bcm06"%>
<htmlb:content design="design2003">
<htmlb:page>
 <bcm06:simpleLink href="http://www.sap.com">
 SAP Home Page!
 </bcm06:simpleLink>
</htmlb:page>
</htmlb:content>
In SE80 we defined a new BSP library bcm06. We define a new element simpleLink. Typical handler class name will be CL_BCM06_SIMPLELINK (just the convention we use). As body this tag can contain other HTML and also over BSP elements (we want to just render a link around all of body). We don't worry about the rest of the checkboxes. They will become interesting later on.
We activate the library. The workbench will detect that no handler class exists, and will generate all of the stuff we need. Now already the tag is full functional, and can be used on any BSP page. It just will not do anything.
What was generated? The class inheritance diagram is as follow: CL_BCM06_SIMPLELINK --> CLG_BCM06_SIMPLELINK --> CL_BSP_ELEMENT.
The class CL_BSP_ELEMENT is the base class, and it contains a lot of interesting functionality. None of which we worry about now. Never try to change it!
The class CLG_BCM06_SIMPLELINK (note that CLG_!) is generated new each and everytime that you touch the definition of the tag. Effectively all the defined attributes are generated onto this class, so that they are already of the correct type, and that this information is always in sync. This means that all your tag defined attributes are directly attributes on your class. In our case, the defined "href" attribute (type string) is now an attribute on the CLG class.
The last class CL_BCM06_SIMPLELINK will only be generated once if it does not exist. This is the class where you work. In this class there are two methods that are interesting to you at this moment. Later you will learn about the rest.
DO_AT_BEGINNING: This method is called effectively in response to the <lib:tag> sequence. This is the code that executes before the body. This is the place where we would like to render out "<a href=...>" sequence.
DO_AT_END: This method is called effectively at the end of the tag, when the </lib:tag> is seen. The body has now already been processed and sent onto the output stream. So we only need to render "</a>".
Note that these methods are implemented empty. You *MUST* overwrite them, and implement them in your class. See instructions from Thomas. Source code:
METHOD if_bsp_element~do_at_beginning.
DATA: html TYPE string.
CONCATENATE `<a href="` me->href `">` INTO html.
me->print_string( html ).
rc = co_element_continue.
ENDMETHOD.
METHOD if_bsp_element~do_at_end.
me->print_string( `</a>` ).
rc = co_page_continue.
ENDMETHOD.
Notice that you DO NOT need that super call. The base method will always be empty (from definition, will never change). You also have a direct PRINT_STRING method in newer SPs. The return code you must set. (To tell the truth, the constants for RC have been picked so perfectly that if you forget them, it should not hurt in 85% of the cases.)
That is it. Test page. Mine worked!
Of course, we can start looking at more exotic things, like empty tags, at tags that skip their bodies if not required, processing the body, validation, etc.
But this overview was just to give you that first success feeling, and also to give you a better framework for understanding more of the documentation as you continue to read.
Recommended: read <a href="/people/brian.mckellar/blog/2004/06/11/bsp-trouble-shooting-getting-help">Getting Help</a> to see how you can quickly navigate between BSP page and a tag's definition, from where you also quickly get to the implementation class of the tag.
bye, brian
PS: Now if this is not already the first page of your weblog done

JFileChooser not opening when we applied custom Look and Feel & Theme

Dear All,
JFileChooser not opening when we applied custom Look and Feel & Theme.
The following is the source code
import java.awt.Color;
import javax.swing.*;
import javax.swing.plaf.ColorUIResource;
import javax.swing.plaf.metal.MetalLookAndFeel;
import com.jgoodies.looks.plastic.*;
public class CustomTheme {
public static void main(String[] args)throws UnsupportedLookAndFeelException{
UIManager.setLookAndFeel(new MyLookAndFeel());
MyLookAndFeel.setCurrentTheme(new CustomLaF());
JFrame frame = new JFrame("Metal Theme");
JFileChooser jf = new JFileChooser();
System.out.println("UI - > "+jf.getUI());
//jf.updateUI();
frame.getContentPane().add(jf);
frame.pack();
frame.setVisible(true);
static class CustomLaF extends PlasticTheme {
protected ColorUIResource getPrimary1() {
return new ColorUIResource(232,132,11);
public ColorUIResource getPrimary2() {
 return (new ColorUIResource(Color.white));
 public ColorUIResource getPrimary3() {
 return (new ColorUIResource(232,132,11));
public ColorUIResource getPrimaryControl() {
return new ColorUIResource(Color.GREEN);
protected ColorUIResource getSecondary1() {
return new ColorUIResource(Color.CYAN);
protected ColorUIResource getSecondary2() {
 return (new ColorUIResource(Color.gray));
 protected ColorUIResource getSecondary3() {
 return (new ColorUIResource(235,235,235));
 protected ColorUIResource getBlack() {
 return BLACK;
 protected ColorUIResource getWhite() {
 return WHITE;
static class MyLookAndFeel extends Plastic3DLookAndFeel {
 protected void initClassDefaults(UIDefaults table) {
 super.initClassDefaults(table);
 protected void initComponentDefaults(UIDefaults table) {
 super.initComponentDefaults(table);
 Object[] defaults = {
 "MenuItem.foreground",new ColorUIResource(Color.white),
 "MenuItem.background",new ColorUIResource(Color.gray),
 "MenuItem.selectionForeground",new ColorUIResource(Color.gray),
 "MenuItem.selectionBackground",new ColorUIResource(Color.white),
 "Menu.selectionForeground", new ColorUIResource(Color.white),
 "Menu.selectionBackground", new ColorUIResource(Color.gray),
 "MenuBar.background", new ColorUIResource(235,235,235),
 "Menu.background", new ColorUIResource(235,235,235),
 "Desktop.background",new ColorUIResource(235,235,235),
 "Button.select",new ColorUIResource(232,132,11),
 "Button.focus",new ColorUIResource(232,132,11),
 "TableHeader.background", new ColorUIResource(232,132,11),
 "TableHeader.foreground", new ColorUIResource(Color.white),
 "ScrollBar.background", new ColorUIResource(235,235,235),
 "ToolTip.foreground", new ColorUIResource(232,132,11),
 "ToolTip.background", new ColorUIResource(Color.white),
 "OptionPane.questionDialog.border.background", new ColorUIResource(Color.gray),
 "OptionPane.errorDialog.titlePane.foreground", new ColorUIResource(Color.white),
 "OptionPane.questionDialog.titlePane.background", new ColorUIResource(232,132,11),
 "Table.selectionBackground", new ColorUIResource(232,132,11)
 table.putDefaults(defaults);
When i run this program the following error is coming:
Exception in thread "main" java.lang.NullPointerException
at javax.swing.plaf.metal.MetalFileChooserUI$IndentIcon.getIconWidth(Unknown Source)
at javax.swing.SwingUtilities.layoutCompoundLabelImpl(Unknown Source)
at javax.swing.SwingUtilities.layoutCompoundLabel(Unknown Source)
at javax.swing.plaf.basic.BasicLabelUI.layoutCL(Unknown Source)
at javax.swing.plaf.basic.BasicLabelUI.getPreferredSize(Unknown Source)
at javax.swing.JComponent.getPreferredSize(Unknown Source)
at javax.swing.plaf.basic.BasicListUI.updateLayoutState(Unknown Source)
at javax.swing.plaf.basic.BasicListUI.maybeUpdateLayoutState(Unknown Source)
at javax.swing.plaf.basic.BasicListUI$ListSelectionHandler.valueChanged(Unknown Source)
at javax.swing.DefaultListSelectionModel.fireValueChanged(Unknown Source)
at javax.swing.DefaultListSelectionModel.fireValueChanged(Unknown Source)
at javax.swing.DefaultListSelectionModel.fireValueChanged(Unknown Source)
at javax.swing.DefaultListSelectionModel.changeSelection(Unknown Source)
at javax.swing.DefaultListSelectionModel.changeSelection(Unknown Source)
at javax.swing.DefaultListSelectionModel.setSelectionInterval(Unknown Source)
at javax.swing.JList.setSelectedIndex(Unknown Source)
at javax.swing.plaf.basic.BasicComboPopup.setListSelection(Unknown Source)
at javax.swing.plaf.basic.BasicComboPopup.access$000(Unknown Source)
at javax.swing.plaf.basic.BasicComboPopup$ItemHandler.itemStateChanged(Unknown Source)
at javax.swing.JComboBox.fireItemStateChanged(Unknown Source)
at javax.swing.JComboBox.selectedItemChanged(Unknown Source)
at javax.swing.JComboBox.contentsChanged(Unknown Source)
at javax.swing.AbstractListModel.fireContentsChanged(Unknown Source)
at javax.swing.plaf.metal.MetalFileChooserUI$DirectoryComboBoxModel.setSelectedItem(Unknow
at javax.swing.plaf.metal.MetalFileChooserUI$DirectoryComboBoxModel.addItem(Unknown Source
at javax.swing.plaf.metal.MetalFileChooserUI$DirectoryComboBoxModel.access$2300(Unknown So
at javax.swing.plaf.metal.MetalFileChooserUI.doDirectoryChanged(Unknown Source)
at javax.swing.plaf.metal.MetalFileChooserUI.access$2600(Unknown Source)
at javax.swing.plaf.metal.MetalFileChooserUI$12.propertyChange(Unknown Source)
at javax.swing.event.SwingPropertyChangeSupport.firePropertyChange(Unknown Source)
at javax.swing.event.SwingPropertyChangeSupport.firePropertyChange(Unknown Source)
at javax.swing.JComponent.firePropertyChange(Unknown Source)
at javax.swing.JFileChooser.setCurrentDirectory(Unknown Source)
at javax.swing.JFileChooser.<init>(Unknown Source)
at javax.swing.JFileChooser.<init>(Unknown Source)
at CustomTheme.main(CustomTheme.java:20)
I am extending the JGoodies Look And Feel & Theme.
Thanks in advance
Krishna Mohan.

Dear cupofjoe,
Thank you for your response.
I am using the Latest JGoodies Look & Feel which is downloaded from http://www.jgoodies.com.
i am writing our own custom Look & Feel By Overridding Jgoodies Look & Feel.
In that case i am getting that error.
The following is the source code:
import java.awt.Color;
import javax.swing.*;
import javax.swing.plaf.ColorUIResource;
import javax.swing.plaf.metal.MetalLookAndFeel;
import com.jgoodies.looks.plastic.*;
public class CustomTheme {
public static void main(String[] args)throws UnsupportedLookAndFeelException{
UIManager.setLookAndFeel(new MyLookAndFeel());
MyLookAndFeel.setCurrentTheme(new CustomLaF());
JFrame frame = new JFrame("Metal Theme");
JFileChooser jf = new JFileChooser();
//System.out.println("UI - > "+jf.getUI());
//jf.updateUI();
//frame.getContentPane().add(jf);
frame.pack();
frame.setVisible(true);
static class CustomLaF extends PlasticTheme {
protected ColorUIResource getPrimary1() {
return new ColorUIResource(232,132,11);
public ColorUIResource getPrimary2() {
 return (new ColorUIResource(Color.white));
 public ColorUIResource getPrimary3() {
 return (new ColorUIResource(232,132,11));
public ColorUIResource getPrimaryControl() {
return new ColorUIResource(Color.GREEN);
protected ColorUIResource getSecondary1() {
return new ColorUIResource(Color.CYAN);
protected ColorUIResource getSecondary2() {
 return (new ColorUIResource(Color.gray));
 protected ColorUIResource getSecondary3() {
 return (new ColorUIResource(235,235,235));
 protected ColorUIResource getBlack() {
 return BLACK;
 protected ColorUIResource getWhite() {
 return WHITE;
static class MyLookAndFeel extends Plastic3DLookAndFeel {
 protected void initClassDefaults(UIDefaults table) {
 super.initClassDefaults(table);
 protected void initComponentDefaults(UIDefaults table) {
 super.initComponentDefaults(table);
 Object[] defaults = {
 "MenuItem.foreground",new ColorUIResource(Color.white),
 "MenuItem.background",new ColorUIResource(Color.gray),
 "MenuItem.selectionForeground",new ColorUIResource(Color.gray),
 "MenuItem.selectionBackground",new ColorUIResource(Color.white),
 "Menu.selectionForeground", new ColorUIResource(Color.white),
 "Menu.selectionBackground", new ColorUIResource(Color.gray),
 "MenuBar.background", new ColorUIResource(235,235,235),
 "Menu.background", new ColorUIResource(235,235,235),
 "Desktop.background",new ColorUIResource(235,235,235),
 "Button.select",new ColorUIResource(232,132,11),
 "Button.focus",new ColorUIResource(232,132,11),
 "TableHeader.background", new ColorUIResource(232,132,11),
 "TableHeader.foreground", new ColorUIResource(Color.white),
 "ScrollBar.background", new ColorUIResource(235,235,235),
 "ToolTip.foreground", new ColorUIResource(232,132,11),
 "ToolTip.background", new ColorUIResource(Color.white),
 "OptionPane.questionDialog.border.background", new ColorUIResource(Color.gray),
 "OptionPane.errorDialog.titlePane.foreground", new ColorUIResource(Color.white),
 "OptionPane.questionDialog.titlePane.background", new ColorUIResource(232,132,11),
 "Table.selectionBackground", new ColorUIResource(232,132,11)
 table.putDefaults(defaults);
pls suggest me the how to solve this problem.
thanks in advance
Krishna MOhan

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.

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

Changing the look and feel of the logon screen and portal themes.

Dear all,
we got some requirements in the portal where i have implement the following things..
1) when we give the portal url in the browser along with logon screen i have to display the some content related to the organaisation ,,, there i want to do logon screen customization also.
2)once login to the portal i need display the some company related information along with different ESS services .i want to remove the masthead area and in the role area want to display different services.
please guide me to achive this.
the client is not at all happy with present look and feel,
so what we can do t achieve ths?
Thank you in advance.
Swapna

Hi Swapna,
Portalapp.xml is the configuration file of portal application holding comonents and services. Where as authschemes.xml file is used to determin and tell portal which of the user authentication schemes is to be used. It also tells portal about which logon PAR file should be used. It is defined inside following tags.
<frontendtarget>Logon PAR File Name</frontendtarget>.
Take a scenario for example. You have created a custom logon PAR file and made some changes. You cannot see the changes before deploying it. You have to deploy it first. Now, you want that whenever somone logon to portal, your logon PAR should be referred and executed. Authschemes.xml does this work. It maintains a reference to the PAR file that should be used for logon.
Now, still have to create a custom authschemes.xml file and upload it. (Follow this link for the authschemes file location http://help.sap.com/saphelp_nw04/helpdata/en/1a/3afd4e641b8f42ac07bb77fe30375b/content.htm)
Refer this link for details on authschemes.xml file: http://help.sap.com/saphelp_nw04/helpdata/en/d3/1dd4516c518645a59e5cff2628a5c1/content.htm
Let us see in brief what are the steps executed:
1) You request a portal login
2) Portal, after receiving a request, looks for a reference to which Authschemes file to be used. It finds it in Visual Admin
3) Once portal have the name of authschemes file, it parse this file and determin what are the authentication schemes to be used and which logon PAR should be executed.
4) Only after these steps, it renders logon page to you
Once you do all these steps, you can see the result on logon page itself. You do not have to look for deployed PAR file.

Creating an messagebox in forms with look and feel of Windows

I wanted to create an message box in my form with look and feel of windows.For this i used the package ORA.FFI...but i am getting an error....and i am not bale to clear it...the code is as follows
Package Specification: -
PACKAGE messagebox IS
/*Function message_box calls windows MessageBox function. */
FUNCTION message_box(plptext IN VARCHAR2,plpcaption IN VARCHAR2)
RETURN PLS_INTEGER;
END;
Package body : -
PACKAGE BODY messagebox IS
lh_window ORA_FFI.LIBHANDLETYPE;
fh_mb ORA_FFI.FUNCHANDLETYPE;
lh_forms ora_ffi.libHandleType;
/* Function i_mbx acts as the interface to the Messagebox
function in windows
FUNCTION i_mbx(funchandle IN ORA_FFI.FUNCHANDLETYPE,
plptext IN OUT VARCHAR2,
plpcaption IN OUT VARCHAR2)
RETURN PLS_INTEGER;
PRAGMA interface(C,i_mbx,11265);
FUNCTION message_box(plptext IN VARCHAR2,
plpcaption IN VARCHAR2)
RETURN PLS_INTEGER IS
ltext VARCHAR2(500) := plptext;
lcaption VARCHAR2(500) := plpcaption;
BEGIN
RETURN(i_mbx(fh_mb,ltext,lcaption));
END;
BEGIN
lh_window := ORA_FFI.LOAD_LIBRARY('d:\','DclMsgBox.dll');
fh_mb := ORA_FFI.REGISTER_FUNCTION(lh_window,'DclMsgBox',ORA_FFI.C_STD);
ORA_FFI.REGISTER_RETURN(fh_mb,ORA_FFI.C_CHAR_PTR);
ORA_FFI.REGISTER_RETURN(fh_mb,ORA_FFI.C_CHAR_PTR);
--ORA_FFI.REGISTER_RETURN(fh_mb,ORA_FFI.C_INT);
END;
Now when i call this function in When-New-Form-Instance as
declare
p number;
begin
p:=messagebox.message_box('hello','test');
end;
I had created an dll for message box and placed the .dll and .lib files in the d:\ of my system.
I get an error message when i run the app. The error is:
The instruction at "0x005a3b24" referenced memory at "0x00000006".The memory could not be "read".
Can anybody please tell me where have i gone wrong....

Colin Martin wrote:
I agree the leather look is horrible. It's just not a reflection of the cutting edge modern design we have all got to love over the years. If it has to be there at least give us a choice of looks.
There is a word for this (not that one) - skeuomorph. Wikipedia defines this as 'a derivative object that retains ornamental design cues to a structure that was necessary in the original. Skeuomorphs may be deliberately employed to make the new look comfortably old and familiar'.
Common examples are found in audio software with pictures of actual knobs that you turn, as here; and the leather-bound tear-off look of calendar and contacts on the iPad is the same principle: the intention is to make it familiar and friendly to people who might otherwise be frightened off by a modern look because they are not used to modern technology. The whole concept and look of the iOS operating system is being brought into use on Macs for the same reason, to encourage non-tech-savvy people not to be frightened of them.
This is all very well in its way, but in these two particular cases the result is unfortunate, particularly for experienced users, and it really ought to be possible to choose between the looks (as you can with the Mail layouts), even if the skeuomorph is the default.

Modifying Quiz look and feel

This question has likely been asked before, but I did a
search of the forum and couldn't find a specific posting. My
company has just purchased me a copy of Captivate 2, so some of it
is a bit new to me.
My question is....
Can the visual components of a quiz slide (such as the button
style) be modified directly in Captivate 2? I get how to modify the
player controls, but can't seem to find any files where I can do
the same to quiz slide components.
If I can not do this directly in Captivate, would I be able
to do this without breaking anything, by exporting a project to
Flash?
The company I work for would like to customize (think
"branding") the Captivate generated controls and general look and
feel of a finished project. This would be so that different, less
technical developers, could create materials that had the same
style.
Any resources anyone can point me toward would be
appreciated.
Thank you,
TPK

Colin Martin wrote:
I agree the leather look is horrible. It's just not a reflection of the cutting edge modern design we have all got to love over the years. If it has to be there at least give us a choice of looks.
There is a word for this (not that one) - skeuomorph. Wikipedia defines this as 'a derivative object that retains ornamental design cues to a structure that was necessary in the original. Skeuomorphs may be deliberately employed to make the new look comfortably old and familiar'.
Common examples are found in audio software with pictures of actual knobs that you turn, as here; and the leather-bound tear-off look of calendar and contacts on the iPad is the same principle: the intention is to make it familiar and friendly to people who might otherwise be frightened off by a modern look because they are not used to modern technology. The whole concept and look of the iOS operating system is being brought into use on Macs for the same reason, to encourage non-tech-savvy people not to be frightened of them.
This is all very well in its way, but in these two particular cases the result is unfortunate, particularly for experienced users, and it really ought to be possible to choose between the looks (as you can with the Mail layouts), even if the skeuomorph is the default.

Discussion of Weblog: ABAP Look and Feel Service

<a href="/people/brian.mckellar/blog/2005/06/12/bsp-in-depth-abap-look-and-feel-service In-Depth: ABAP Look and Feel Service</a>
The three minutes routine to change any SAP-blue theme to the new theme that is required for you next demo!
If there should be any questions, comments, etc on this weblog, please post it here, so that it is easier to handle the traffic. We are also interested to see if anyone does actually use the tool.

Hiya,
I saw this blog posted a while back and have only now had a chance to use it - very cool work there Brian and Steffan!
The only thing is I'm having what looks like the same problem as Maximilian!
We're on 620 sp45.
Everything installed fine, I tweaked the mime version code for 620 (me->ifur_d2_system~css_version) and the left hand side of the screen, the editor itself, looks and works fine - but the preview screen doesn't work, the BSP is displayed with no theme at all.
I opened the BSP in a new page with default theme and set the theme manually with paramters and this doesn't work either.
i.e.
http://<host>:<port>/sap/bc/bsp/sap/it05/entrypoint.htm?sap-themeRoot=%2fsap%2fpublic%2fbc%2fur%2fdesign2002%2fthemes%2falfs1000202FFE4C43B2D1B7D674EDAA520565656
But if I try with an SAP standard theme everything works fine and the new theme is picked up correctly
i.e.
http://<host>:<port>/sap/bc/bsp/sap/it05/entrypoint.htm?sap-themeRoot=%2fsap%2fpublic%2fbc%2fur%2fdesign2002%2fthemes%2f~sap_standard
I've checked the URL encoding (using program BSP_DECODE_URL) and with the alfs theme this looks fine.
In the source code the stylesheets are referenced using the correct themeRoot i.e.
<link id="urstyle" rel="stylesheet" type="text/css" href="/sap/public/bc/ur/design2002/themes/alfs1000202FFE4C43B2D1B7D674EDAA520565656/ur/ur_ie6.css">
When I set a break point in the ALFS HTTP handler this is not picked up.
BUT the one really puzzling thing about all this is that whilst I've been trying to fix this and work out what is going wrong I've made small changes to the ALFS class, i.e. to change the default BSP application used in the editor, and sometimes after generating the class code, refereshing both browser and system caches, everything worked fine - even the debugging of the HTTP handler - for some generated themes - and then stopped working again!
Now I know how this reads - and I've worked with enough users in my time to know you must be thinking - well she must have changed something! But I really can't work out what it could have been.
I've been round and round trying to reproduce what ever it was to get this working.
I've tried all the following in various combinations:
- restarting ICM
- removing ALFS HTTP handler from ICF service
- starting with a completely new copy of the class
- adding alert statements to the ALFS editor page to track themeRoot values
- changing the code relating to me->ifur_d2_systemcss_version and me->ifur_d2_systemur_version so that there is a version number (tried 'urversion=DAT<date>' and plain 'DAT<date>'), changed the code so there is no version number used at all.
- even (don't laugh!) put the ALFS HTTP handler on node SAP/BS/BSP just to make sure the external debugger was still working (it was). At this point I could see each time it was called, and since each call did not have the alfs string in it, all the internal class processing was correctly skipped.
All of the above in combination with cache refreshing on both server and brower side and logging on/off.... and still feel no closer to resolving this.
From what I understand, the ALFS HTTP handler is called everytime a MIME or theme object is requested from the theme root - as this is the only time that a request would pass via SAP/PUBLIC/BC/UR. And I understand that if the requested object is already cached, there will be no request passing via this node, so the ALFS HTTP handler won't be called - but think that there must be some important point relating to caching that I must have missed ...
So that's my first question... help!
Also, Brian, what you have mentioned before, this patch you have to take a theme, patch it with ALFS then import it into the theme editor - this sounds like exactly what we need to do ... I couldn't see any weblogs relating to this - so could you point me in the right direction??
We have no portal so I'll be trying the standalong theme editor plug in for Eclipse.
Thanks in advance,
Cathy

Notification center look and feel

The new notification center look and feel seems quite unlike the rest of the iPhone.
Most of the iPhone has a light colored, rounded, kind of comfortable look. But the new notification center has a much more dark, angular look. (To me, it looks more like an Android app than an iOS component.)
Any chance it can be rebranded? Or failing that, any chance of a settings option to customise the background image, so I can at least change from the dark "linen" texture to a wallpaper of my choice? (e.g. it might look much nicer (to me!) if I could change it to use the default iPhone water drops background). The slide down button itself (the bit of the notification center graphics which appears on screen, even in full-screen mode, if you make the 'wrong' move) could be much more rounded, as well.
Mike

iOs 5 in general looks and feels awkward to me. It feels cheap and not at all as polished as Apple's products have been in the past. The alarms have new colors for no apparent reason, the text messages have colors for no apparent reason, the notification center has a distracting texture, again, for no reason... Yet none of these colors or textures are configurable or removable. What was the point exactly?
This theme shift is quite discouraging in the grand scheme of things. It doesn't bother me much, but I definitely prefered the way my phone looked when I bought it.

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

JFileChooser & XP look and feel

Hello!
I'm changing an exiting applet to have a local look & feel by simply doing this:
UIManager.setLookAndFeel(UIManager.getSystemLookAndFeelClassName()); When the JFileChooser shows with the "metal" (java default) Look&Feel all is good but when it shows with
XP (or windows) L&F it has added a "panel" on the left side with icons for "My Recent Document" , "Desktop" , "My Documents", "My Computer" and " My Network places".
I really don't want them showing since it looks weird on the HTML page.
Does somebody know if and how I can get rid of that "panel" and still have the rest of the L&F intact?
Regards Calle

Check out skin look and feel. They have all sorts of look and feels including windows XP.
http://www.l2fprod.com

Emty topic window in Nimbus Look and Feel

I have Java applications using OHJ. When we swith to Nimbus Look and Feel our topic Windows is blank. Helps work correctli in other look and feels. If I print topic it's is printed correctly, so information is there but it is not visible.

AndrewThompson64 wrote:
No, I'd say it is a pity that you did not initially use layouts when creating the code in Netbeans. There is no point blaming the tool. Well, some of this code is almost 10 years old (and i didn't write it), and back then nobody used layouts correctly. Even now java layouts are a pain to use compared with other GUI layouts (FLEX, HTML). Our customer just wants a prettier GUI on top of this legacy java app.
We looked at incrementally using JavaFX to slowly change out screens, but it doesn't support integration with a regular java application (why?)
Even with a unsupported workaround i cannot open a modal dialogs from JavaFX. I think they are targeting JavaFX at the wrong market, it is usless as a RIA and will never beat out Flash. They should have targeted it as a Swing replacement. Just my 2 cents.
>
That seems a shoddy 'solution'. Even the current code under the current PLAF might fail on another screen size, resolution, default font size or a number of other factors..This is true, unfortunately the code base is very very large (300k lines).

Swing disabled components look and feel problem.

Hi All,
I have a Swing application. My system is recently upgraded to JRE 1.6 and I'm facing problem with look and feel of swing components when they are disabled. Color of disabled components is very faint and its being difficult to read the text in such disabled components. In JRE 1.4 this problem was not there. Please let me know what I can do to get the look and feel(Color and Font) of disabled components, same as JRE 1.4.
Thanks

Sandip_Jarad wrote:
..I have a Swing application. My system is recently upgraded to JRE 1.6 and I'm facing problem with look and feel of swing components when they are disabled. Which look and feel is the application using? As an aside, did it never occur to you to mention the PLAF?
..Color of disabled components is very faint and its being difficult to read the text in such disabled components. Why is it so gosh-darned important to read the text on a control that is (supposedly) not relevant or not available?
..In JRE 1.4 this problem was not there. Please let me know what I can do to get the look and feel(Color and Font) of disabled components, same as JRE 1.4. Here are some suggestions, some of them are actually serious. I'll leave it as an exercise for you, to figure out which ones.
- Run the app. in 1.4.
- Use a custom PLAF that offers a 'less faint' rendering of disabled components.
- Use Motif PLAF (I haven't checked, but I bet that has not changed since 1.4).
- Put the important text in a tool-tip.

IC_BASE look and feel (Default theme) very urgent !!!

Similar Messages

Maybe you are looking for