Java Components and Look and Feel

Can anyone suggest a free look and feel that does not resemble the standard stuff that comes with the JDK?
Also, Swing seems to be missing some important components like dockable windows, and toolbars. Can anyone suggest some resource that offers interesting swing components?

Can someone suggest a good API for doing this stuff?
I would really like to consider using Java for some
e real world application, but the swing interface
makes applications look at least 15 years old.Really? My applications look like native windows applications (when run under Windows, at least). Try setting the native look and feel. Search the forum if you don't know how.

Similar Messages

Does java has "Transparent" look and feel?????

I want to know whether there is a transparent look and feel developed for java,
if it is there please post an link to download the API
Thank you very much..

As far as I know, NO.
There is a way to do this, using robot to get desktop image and draw it using paint object when you render your component, but, performance is not good.

Windows look and feel instead, in InternalFrameDemo.java

Hi all, I am learning swing and I am trying to modify the
InternalFrameDemo.java source from
http://docs.oracle.com/javase/tutorial/uiswing/examples/components/index.html#InternalFrameDemo
My idea is to add the line
JFrame.setDefaultLookAndFeelDecorated(true); in the constructor, but it doesn't work
and I don't understand why.
Could somebody please help me?
Kindest regards,
Lasse
public InternalFrameDemo() {
super("InternalFrameDemo");
//Make the big window be indented 50 pixels from each edge
//of the screen.
int inset = 50;
Dimension screenSize = Toolkit.getDefaultToolkit().getScreenSize();
setBounds(inset, inset,
screenSize.width - inset*2,
screenSize.height - inset*2);
//FDoesn't work
JFrame.setDefaultLookAndFeelDecorated(true);
//Set up the GUI.
desktop = new JDesktopPane(); //a specialized layered pane
createFrame(); //create first "window"
setContentPane(desktop);
setJMenuBar(createMenuBar());
//Make dragging a little faster but perhaps uglier.
desktop.setDragMode(JDesktopPane.OUTLINE_DRAG_MODE);
}

Uh I think you're mistaken. Whenever in doubt or something doesn't work as expected, check the javadocs. The link to the javadocs can usually be found really easily by typing "java 6 classname". In this case:
http://docs.oracle.com/javase/6/docs/api/javax/swing/JFrame.html
If you want to set the Windows look & feel as your thread title suggests, this was not the method you were looking for as the javadocs will tell you. That method controls if a frame is decorated or not (as the name suggests), which it is by default. Setting it to true will not change anything.
So what then? You type into Google "java swing windows look and feel". Without quotes of course.

Swan Look and Feel

Swan and look and feel is supposed to be available in a future release of Apex. Has anyone already implemented this style? I am on 2.0 and probably will be for a while so the upgrade really won't help. If you have already done this, would I be able to get a copy of the export theme, graphics, and css? Is this all I would need from someone to be able to implement that look and feel?
Thanks,
Tim

Hello,
There is already an enhancement request to create a theme that mirrors the swan look and feel.
http://blogs.oracle.com/schan/2006/05/04#a111
I have a pretty good idea of the guy that will have to build it ;)
Carl

Photoshop Express 3.0 - Information on in app purchases, looks and borders

Thank you for using Photoshop Express. In our latest 3.0 version, we revamped the rendering engine in order to deliver great new effects, improved editing controls and a streamlined user experience. That means some things you were familiar with may not be available in this version.
In-app purchases have been renamedThe “Effects Pack” that you previously purchased has been renamed "Premium Looks Pack". You still have access to this Pack.
The “Camera Pack”, which provided Noise Reduction, is now called "Noise" and can be found in the Corrections slider menu.
Restoring in-app purchases. You do not have to initiate a re-purchase.
If you've previously purchased either of the packs above, they are still available to you by restoring your purchase, which is accessed in Settings.
Other changesPrevious Effects and Borders have been replaced with Looks, Premium Looks, and Borders. Some of the new looks replicate many of the most popular effects. We will be adding new borders, looks and sharpen controls in future releases.
We appreciate your feedback and will take it into consideration for future releases. We value you as a customer, and hope you like the new borders and looks and continue to enjoy using Photoshop Express.

There was a big change in Photoshop Express 3.0 in the rendering engine. Many items that users accessed often were incorporated in the new release before it went out, but there are other features that had to be implemented differently due to the new rendering engine. Many of these items are on a roadmap for future versions. There are yet others that are more difficult to implement and require more research as to how they would be added. We have a survey out to offer users a way to give input as to which features they are most interested in. (https://www.surveymonkey.com/s/DYGG2RH ) Feel free to give your input here.
New versions will be released shortly that will include the Sharpen tool and some of the features you have been requesting. We are also working on adding several additional looks and many symmetrical borders, similar to those you used in previous versions. These features will be added in the near future. We appreciate your patience.
For those who wish to restore an old version of Photoshop Express:
Please see the FAQ: http://forums.adobe.com/thread/1298203
Pattie
Also, please see this post by the Photoshop Express product manager:
Hi there,
I am sorry many of you are frustrated with the new version. We made the choice to move forward with a new rendering engine which gives us significantly improved editing and capabilities. Unfortunately, that hindered us from being capable of some previous effects and borders. This decision was driven by low usage numbers on the effects we were no longer capable of, which I apologize affected your workflows. We hope you like the premium looks that we developed which are free to you if you restore your purchases (settings menu). We also took the step to create brand new borders, which we will continue to add to as we go along. Again, I apologize that the features you used previously are no longer available. We hope you continue to use the product and give the new features a shot.
Sincerely,
Ian Parks
Product Manager

Problem with java look and feel

Hi! This is my first time posting here. Do apologize me if I am not familiar with the regulations here. Thanks!
Currently, I am developing a project using NetBeans IDE. It is using RMI, and some basic UI. I am facing the following error when I tried applying the java look and feel code. Please see below for the code used and the error message.
try {   UIManager.setLookAndFeel("com.sun.java.swing.plaf.windows.WindowsLookAndFeel");
} catch (Exception e) { }
Exception in thread "AWT-EventQueue-0" java.lang.ClassCastException: javax.swing.plaf.ColorUIResource cannot be cast to java.util.List
at javax.swing.plaf.metal.MetalUtils.drawGradient(MetalUtils.java:196)
at javax.swing.plaf.metal.MetalInternalFrameTitlePane.paintComponent(MetalInternalFrameTitlePane.java:384)
at javax.swing.JComponent.paint(JComponent.java:1027)
at javax.swing.JComponent.paintChildren(JComponent.java:864)
at javax.swing.JComponent.paint(JComponent.java:1036)
at javax.swing.JComponent.paintChildren(JComponent.java:864)
at javax.swing.JComponent.paint(JComponent.java:1036)
at javax.swing.JLayeredPane.paint(JLayeredPane.java:564)
at javax.swing.JComponent.paintChildren(JComponent.java:864)
at javax.swing.JComponent.paint(JComponent.java:1036)
at javax.swing.JComponent.paintChildren(JComponent.java:864)
at javax.swing.JComponent.paint(JComponent.java:1036)
at javax.swing.JLayeredPane.paint(JLayeredPane.java:564)
at javax.swing.JComponent.paintChildren(JComponent.java:864)
at javax.swing.JComponent.paintToOffscreen(JComponent.java:5129)
at javax.swing.BufferStrategyPaintManager.paint(BufferStrategyPaintManager.java:285)
at javax.swing.RepaintManager.paint(RepaintManager.java:1128)
at javax.swing.JComponent.paint(JComponent.java:1013)
at java.awt.GraphicsCallback$PaintCallback.run(GraphicsCallback.java:21)
at sun.awt.SunGraphicsCallback.runOneComponent(SunGraphicsCallback.java:60)
at sun.awt.SunGraphicsCallback.runComponents(SunGraphicsCallback.java:97)
at java.awt.Container.paint(Container.java:1797)
at javax.swing.RepaintManager.paintDirtyRegions(RepaintManager.java:734)
at javax.swing.RepaintManager.paintDirtyRegions(RepaintManager.java:679)
at javax.swing.RepaintManager.seqPaintDirtyRegions(RepaintManager.java:659)
at javax.swing.SystemEventQueueUtilities$ComponentWorkRequest.run(SystemEventQueueUtilities.java:128)
at java.awt.event.InvocationEvent.dispatch(InvocationEvent.java:209)
at java.awt.EventQueue.dispatchEvent(EventQueue.java:597)
at java.awt.EventDispatchThread.pumpOneEventForFilters(EventDispatchThread.java:273)
at java.awt.EventDispatchThread.pumpEventsForFilter(EventDispatchThread.java:183)
at java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java:173)
at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:168)
at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:160)
at java.awt.EventDispatchThread.run(EventDispatchThread.java:121)
Java Result: 1

Thanks for everyone's help!
Below is the executable code generated using NetBeans which is enough to generate the error message. Sometimes you can get the error message just by running the program. Sometimes the error will occur when you go into the Menu and click on Item.
* NewJFrame.java
* Created on January 8, 2008, 1:11 PM
package client;
import javax.swing.UIManager;
* @author Yang
public class NewJFrame extends javax.swing.JFrame {
    /** Creates new form NewJFrame */
    public NewJFrame() {
        initComponents();
    /** This method is called from within the constructor to
     * initialize the form.
     * WARNING: Do NOT modify this code. The content of this method is
     * always regenerated by the Form Editor.
    // <editor-fold defaultstate="collapsed" desc=" Generated Code ">
    private void initComponents() {
        jDesktopPane1 = new javax.swing.JDesktopPane();
        jInternalFrame1 = new javax.swing.JInternalFrame();
        jMenuBar1 = new javax.swing.JMenuBar();
        jMenu1 = new javax.swing.JMenu();
        jMenuItem1 = new javax.swing.JMenuItem();
        setDefaultCloseOperation(javax.swing.WindowConstants.EXIT_ON_CLOSE);
        javax.swing.GroupLayout jInternalFrame1Layout = new javax.swing.GroupLayout(jInternalFrame1.getContentPane());
        jInternalFrame1.getContentPane().setLayout(jInternalFrame1Layout);
        jInternalFrame1Layout.setHorizontalGroup(
            jInternalFrame1Layout.createParallelGroup(javax.swing.GroupLayout.Alignment.LEADING)
            .addGap(0, 190, Short.MAX_VALUE)
        jInternalFrame1Layout.setVerticalGroup(
            jInternalFrame1Layout.createParallelGroup(javax.swing.GroupLayout.Alignment.LEADING)
            .addGap(0, 95, Short.MAX_VALUE)
        jInternalFrame1.setBounds(80, 40, 200, 130);
        jDesktopPane1.add(jInternalFrame1, javax.swing.JLayeredPane.DEFAULT_LAYER);
        jMenu1.setText("Menu");
        jMenuItem1.setText("Item");
        jMenuItem1.addActionListener(new java.awt.event.ActionListener() {
            public void actionPerformed(java.awt.event.ActionEvent evt) {
                jMenuItem1ActionPerformed(evt);
        jMenu1.add(jMenuItem1);
        jMenuBar1.add(jMenu1);
        setJMenuBar(jMenuBar1);
        javax.swing.GroupLayout layout = new javax.swing.GroupLayout(getContentPane());
        getContentPane().setLayout(layout);
        layout.setHorizontalGroup(
            layout.createParallelGroup(javax.swing.GroupLayout.Alignment.LEADING)
            .addGroup(layout.createSequentialGroup()
                .addComponent(jDesktopPane1, javax.swing.GroupLayout.DEFAULT_SIZE, 484, Short.MAX_VALUE)
                .addGap(20, 20, 20))
        layout.setVerticalGroup(
            layout.createParallelGroup(javax.swing.GroupLayout.Alignment.LEADING)
            .addComponent(jDesktopPane1, javax.swing.GroupLayout.DEFAULT_SIZE, 279, Short.MAX_VALUE)
        pack();
    }// </editor-fold>
    private void jMenuItem1ActionPerformed(java.awt.event.ActionEvent evt) {
// TODO add your handling code here:
        jInternalFrame1.setVisible(true);
     * @param args the command line arguments
    public static void main(String args[]) {
        java.awt.EventQueue.invokeLater(new Runnable() {
            public void run() {
                new NewJFrame().setVisible(true);
        try {
            UIManager.setLookAndFeel(UIManager.getSystemLookAndFeelClassName());
        } catch (Exception e) {
            e.printStackTrace();
    // Variables declaration - do not modify
    private javax.swing.JDesktopPane jDesktopPane1;
    private javax.swing.JInternalFrame jInternalFrame1;
    private javax.swing.JMenu jMenu1;
    private javax.swing.JMenuBar jMenuBar1;
    private javax.swing.JMenuItem jMenuItem1;
    // End of variables declaration
}Edited by: Boxie on Jan 7, 2008 11:23 PM

How can I include a portal component look and feel in a java servlet

Does any body know how can i include a portal component look and feel (tables, buttons, etc) in a java servlet?

Hi José,
I don't think that is possible. But you can import the css files that ep uses for its look and feel and try to give your web pages similar look and feel. The tables and other controls used in EP are totally different and are done through complex JavaScript coding instead of simple HTML tags. If you want exact lok and feel then i thin you must go for a Webdynpro based application rather then a J2EE application with JSPs.
Regards,
Guru.
PS: Give points for helpful replies.

Setting the Brushed Metal look and feel for macs using Java.

Hello,
I am relatively new to Java and I am new to Mac-specific java stuff. Anyways, when I try to set the look and feel of my classes to the "apple.awt.brushMetalLook" look and feel, I am unable to. It works if I have System.setProperty("apple.awt.brushMetalLook", "true"); written before I create any swing component. This would be fine, except that means that it is impossible to extend any swing component, such as JFrame or JApplet. Is there a way around this?
Thanks!

This might answer your question:
http://lists.apple.com/archives/Java-dev/2003/Apr/msg00829.html

[SOLVED] Java GTK look and feel

I opened a thread recently about replacing the ugly swing buttons in Java applications. After successfully modifying my ~/.bashrc, all was well. However, these new changes were only present when run from a terminal. I assumed it was because my desktop was still running a bash session that hadn't loaded the new options yet, so I restarted.
Symptom: Java apps launched from the GUI still have old swing buttons, but have the GTK look and feel when launched from a terminal.
My .bashrc additions:
# Java stuff
export _JAVA_OPTIONS="-Dawt.useSystemAAFontSettings=on -Dswing.aatext=true -Dswing.defaultlaf=com.sun.java.swing.plaf.gtk.GTKLookAndFeel -Dswing.crossplatformlaf=com.sun.java.swing.plaf.gtk.GTKLookAndFeel"
I use SLiM for a graphical login experience. Could this be affecting it? I'm not sure what happens differently behind the scenes when using a login manager other than that CTRL+ALT+F7 brings me to my GUI when I use one (because all 6 TTYs are still TTYs).
Last edited by 2mac (2014-01-02 20:51:35)

I had a similar issue where .xinitrc wasn't working to set an environment variable. I put mine in ~/.config/openbox/environment and it worked. If you run openbox try that. If using a different window manager maybe try /etc/environment I am unsure of how slim functions though maybe there are config files for it. I think slim is on it's way out though (already lacks some compatibility with systemd; they may fix it though upstream I have no idea). But yeah try the environment file way and see if that does it (assuming you have tested your command from the shell and it works how you want).

Java is designed to have a look and feel equivalent to????

Java is a programming language designed to have a look and feel equivalent to:
a. VB
b. C++
c. Cobol
d. NotesScript
Cheers!

If you mean look and feel from a language perspective, Java was heavily influenced by C++.
Since this is a multiple choice question quoted verbatim from either a textbook or your homework, I assume that you aren't really interested in any more information than that.

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.

Making custom non-standard components aware of custom look and feels.

Hello all.
Maybe the subject of this post could also be the opposite: "Making custom look and feels aware of non-standard custom components". I'm not sure.
If I code a new custom component (extending JComponent, or extending the UI delegate of a standard component) and pretend it to be laf aware then I must create the corresponding UI delegate for each laf, like it happens to be with standard swing components. But I'm not sure it is feasible to create the UI delegates for all unknown existing custom lafs.
On the other side, if I create a custom laf then I will also create a custom UI delegate for each standard component, but I can not create UI delegate for all unknown existing custom components.
The point here is that standard components and standard lafs are universally known, while custom components (or custom ui delegates) and custom lafs are not.
So the question is: How does a swing developer deal with the case of a new custom component that will be used in an unknown custom laf?
For instance:
1. Custom text UI delegate for dealing with styled documents in JTextField. See {thread:id=2284487}.
2. JTabbedPane with custom UI delegate that paints no tab if the component only contains one tab.
In both cases I need a UI delegate for each known laf, but what happens if the application is using a laf that certainly will not be aware of this custom functionally?
Thank you!

If I code a new custom component (extending JComponent, or extending the UI delegate of a standard component) and pretend it to be laf aware then I must create the corresponding UI delegate for each laf, like it happens to be with standard swing components. But I'm not sure it is feasible to create the UI delegates for all unknown existing custom lafs.You are right, this is never going to work. I suggest if you want to make your custom component look & feel aware, you design the way it displays around the l & f of other components that are part of j2se and have l&f implementations.
http://download.oracle.com/javase/7/docs/api/javax/swing/plaf/ComponentUI.html
There are instructions here:
http://download.oracle.com/javase/7/docs/api/javax/swing/LookAndFeel.html
>
On the other side, if I create a custom laf then I will also create a custom UI delegate for each standard component, but I can not create UI delegate for all unknown existing custom components.
The point here is that standard components and standard lafs are universally known, while custom components (or custom ui delegates) and custom lafs are not.
So the question is: How does a swing developer deal with the case of a new custom component that will be used in an unknown custom laf?
For instance:
1. Custom text UI delegate for dealing with styled documents in JTextField. See {thread:id=2284487}.
2. JTabbedPane with custom UI delegate that paints no tab if the component only contains one tab.
In both cases I need a UI delegate for each known laf, but what happens if the application is using a laf that certainly will not be aware of this custom functionally?
Thank you!

JTree Button, Line and Java look and feel ?

Hi all,
I have 3 small problem with my JTree ..
1) The 'expand' button size ...
I set a different Icon for each node in a getTreeCellRendererComponent method (from a class that extends DefaultTreeCellRenderer )...
The icon are 32x32 pixels.. .and the RowHeight and the Font have been changed too. .
How to change the size of the expand button (+/-) near the text node ? Because on my JTree, the expand/collapse buttons are really small compare to the icon & row height.
2) No line appear between the node ...
I try to set the line style property with -> putClientProperty("JTree.lineStyle", "Angled"); in the JTree constructor OR in the DefaultTreeCellRenderer constructor .. but it doesn't work :/
3) How to set a Java look and feel for my JTree (actually, I have a Windows look and feel ..)
I know .. I have grouped 3 question in the same topic ...
If anyone can help me on one of these subjects. .. Thanks !
Regards,
Didier

So, the Problem 1) is solved ..
About the Problem 2)
I put the code UIManager.setLookAndFeel(new javax.swing.plaf.metal.MetalLookAndFeel()) in the main method, like
//Main method
public static void main(String[] args) {
    try {
      UIManager.setLookAndFeel(new javax.swing.plaf.metal.MetalLookAndFeel());
    catch(Exception e) {
      e.printStackTrace();
    new MainApplication();
}But it only set a Java L&F on the spliter, and on the toolbar contained in my application... Any idea why the title bar is not changed too ?
(The title bar stay with a Window$ XP L&F ...)
About the problem 3)
When I set the L&F->UIManager.setLookAndFeel(UIManager.getSystemLookAndFeelClassName()); then the lines appear .. ??!! .. if I set again the previous value UIManager.setLookAndFeel(UIManager.getSystemLookAndFeelClassName()); .. then the lines desappear ..

Tweak Javas Look and Feel

Hello everybody,
just wondering if you can help me here, I want to tweak the Look and Feel of some of the objects within a program such a menu backgrounds etc. I think that I am the right lines with this but it does not appear to do anything
I have a class which is called DefaultDEFTheme in this I am declaring the following lines:
public ColorUIResource getRedBackground()/*Could this be problem because getRedBackground does not exist?*/
return new ColorUIResource(255, 0, 0);
Then I have a class that is called DEFLookandFeel and I want to set the colors in the UIDefaults table, so for instance this is the code if I wanted to change the menu background
protected void initSystemColorDefaults(UIDefaults table)
Object[] systemColors = {
"desktop", getDesktopColor(), /* Color of the desktop background */
"activeCaption", getWindowTitleBackground(), /* Color for captions (title bars) when they are active. */
"activeCaptionText", getWindowTitleForeground(), /* Text color for text in captions (title bars). */
"activeCaptionBorder", getPrimaryControlShadow(), /* Border color for caption (title bar) window borders. */
"inactiveCaption", getWindowTitleInactiveBackground(), /* Color for captions (title bars) when not active. */
"inactiveCaptionText", getWindowTitleInactiveForeground(), /* Text color for text in inactive captions (title bars). */
"inactiveCaptionBorder", getControlShadow(), /* Border color for inactive caption (title bar) window borders. */
"window", getWindowBackground(), /* Default color for the interior of windows */
"windowBorder", getControl(), /* ??? */
"windowText", getUserTextColor(), /* ??? */
"menu", getMenuBackground(), /* Background color for menus, I am right in presuming this does not change? */
"menuText", getMenuForeground(), /* Text color for menus */
"text", getWindowBackground(), /* Text background color */
"textText", getUserTextColor(), /* Text foreground color */
"textHighlight", getTextHighlightColor(), /* Text background color when selected */
"textHighlightText", getHighlightedTextColor(), /* Text color when selected */
"textInactiveText", getInactiveSystemTextColor(), /* Text color when disabled */
"control", getControl(), /* Default color for controls (buttons, sliders, etc) */
"controlText", getControlTextColor(), /* Default color for text in controls */
"controlHighlight", getControlHighlight(), /* Specular highlight (opposite of the shadow) */
"controlLtHighlight", getControlHighlight(), /* Highlight color for controls */
"controlShadow", getControlShadow(), /* Shadow color for controls */
"controlDkShadow", getControlDarkShadow(), /* Dark shadow color for controls */
"scrollbar", getControl(), /* Scrollbar background (usually the "track") */
"info", getPrimaryControl(), /* ToolTip Background */
"infoText", getPrimaryControlInfo() /* ToolTip Text */
for (int i = 0; i < systemColors.length; i += 2)
table.put( (String) systemColors, systemColors[i + 1]);
UIManager.put("Button.select", getButtonSelectColor());
// Set the color for selected button */
UIManager.put("Button.background", getButtonBackground());
/* Set the color for selected button */
UIManager.put("Menu.background", getRedBackground());
/* Set the color for the menu to red background*/
Then further on I set this:
public static ColorUIResource getRedBackground(){ return getCurrentTheme().getRedBackground(); }
But i have left in the getMenuBackground above it, I have also tried to take it out but nothing happens.
I also have a class called DEFTheme and in this I declare the following
public ColorUIResource getRedBackground()
return new ColorUIResource(255, 0, 0 );
Yet after changing all of this nothing ever happens. Am I going about this the completley wrong way ie should I change the colors in the DEFTheme and thats it?
Please please help, this is becoming a real problem and I cannot find any relevant resources!!
Thanks so much in advance,
Z.

Yes, its a crosspost, but this is the correct forum since this a Swing related question. Your crosspost comment belongs in the other forum.
Check out this article:
http://www.javareference.com/jrexamples/viewexample.jsp?id=66

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);

Java Components and Look and Feel

Similar Messages

Maybe you are looking for