Problem about look and feeling

i want to make my jframe looking and feeling like jdeveloper.what should i do ?

Hi,
if I remember well then JDeveloper uses the JGoodies Plastic Look and Feel. Just go to http://www.jgoodies.com/ and get the look and feel.
Frank

Similar Messages

Problem setting look and feel

It seems like I'm not able to change the windows xp look and feel, I'm using this code to change it but nothing happens, the window comes out with windows LAF:
" public static void main(String[] args)
try {
UIManager.setLookAndFeel("javax.swing.plaf.metal.MetalLookAndFeel");
} catch (Exception e) { System.out.println(e.getMessage()); }
new Ventana();
Maybe... Am I missing some code? or a specific class needs to be downloaded?
I'd apreciate any help

That was not the problem, but thank you...
I finally noticed the problem, what I was trying to do was actually done by writting this:
JComponent.setDefaultLookAndFeelDecorated(true);
Sets the OceanTheme feel on, but I noticed that when you try to use it with a Jdialog and a JFileChooser you get some ugly colors. Orange/Brown with JDialogs and Green with JFileChoosers. Is this a bug or it's ment to do that?
Does somebody know how to fix it?
Thanks for your support

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.

Delay in applying Look and feel on jDialog

I am working with java1.4 / OS as windows Xp.
Recently i came across an interesting problem regarding look and feel.
Actually my syatem llok and feel was windows and i set swing application Look and feel as Metal. Now whenever i am launching any dialog on my awing application , The dialog appears in windows LAF for few nenoseconds and then changes to Metal.
Even if if check the llok and feel just before launcing the dialog i am getting Metal as result
Can any one help me out about what might be going wrong ?

I've never noticed this before. (I guiess my eyes aren't good enought to spot something for a few nanoseconds)
If you need further help then you need to create a [url http://homepage1.nifty.com/algafield/sscce.html]Short, Self Contained, Compilable and Executable, Example Program (SSCCE) that demonstrates the incorrect behaviour, because I can't guess exactly what you are doing based on the information provided.
Don't forget to use the [url http://forum.java.sun.com/help.jspa?sec=formatting]Code Formatting Tags so the posted code retains its original formatting.

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

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

Problems installing the new 'Look And Feel' done by Francios Degrelle

I have download the new verison of the new 'Look And Feel' from
http://sheikyerbouti.developpez.com/forms-pjc-bean/LAF/sources/v133/LAF_133.zip
1- I defined a new section in formsweb.cfg named summit in the middle tier (AS 10g Rel2):
[Summit]
baseHTML=base.htm
baseHTMLjinitiator=basejpi.htm
baseHTMLjpi=basejpi.htm
baseHTMLie=baseie.htm
HTMLdelimiter=%
workingDirectory=e:\app\summit
envFile=default.env
IE=JInitiator
escapeparams=true
form=customers_laf
debug=no
otherparams=buffer_records=%buffer% debug_messages=%debug_messages% array=%array% obr=%obr% query_only=%query_only% quiet=%quiet% render=%render% record=%record% tracegroup=%tracegroup% log=%log% term=%term% useSDI=yes
buffer=no
debug_messages=no
array=no
obr=no
query_only=no
quiet=yes
render=no
pageTitle=Summit
serverURL=/forms/lservlet
codebase=/forms/java
imageBase=DocumentBase
width=100%
height=100%
separateFrame=false
splashScreen=no
lookAndFeel=oracle
colorScheme=blue
logo=no
restrictedURLparams=HTMLbodyAttrs,HTMLbeforeForm,pageTitle,HTMLafterForm,log,allow_debug,allowNewConnections
serverApp=default
archive_jini=frmall_jinit.jar
archive=frmall.jar,laf.jar
WebUtilArchive=
jpi_download_page=http://java.sun.com/products/archive/j2se/1.4.2_09/index.html
jpi_classid=clsid:8AD9C840-044E-11D1-B3E9-00805F499D93
jpi_codebase=http://java.sun.com/products/plugin/autodl/jinstall-1_4-windows-i586.cab#Version=1,4,0,0
2- then I put a copy of the file 'forms.css' in the middle tier in the folder :
apache\apache\htdocs
so as to be on the path and then modified PM$CSS_FILENAME in all forms to be 'forms.css' instead of 'c:\forms.css' and recompiled.
3-I put a copy of the file 'laf.jar' in the folder : 'd\Ora_AS\forms\java' in the middle tier and added this path to the classpath environment variable.
4- I restarted the middle tier and wrote this URL:
http://test/forms/frmservlet/config=summit
the customers form opened but with no background images,I added the following to the URL '&form=test_laf_color_scheme.fmx',the form opened with the default color scheme to 'purple',I changed it from a drop down list to orange and all buttons background color degraded to orange.
My questions:
1-where are the background images ?
2- I cannot compile the 'laf.pll' file to 'laf.plx',when I compile I get this error:
FRm-91507 -internal error
P.S. I read this thread :
FRM-91507 when compiling a library with Forms 6i
and I didn't understand it,where do I change the Forms_Path? in the forms Home release 1 or Forms home release 2?!!!
3-Is the 'forms.css' file properly located? if not? where do I put it?
Sorry for the long scenario but I'm really confused?
Thanks
Mohammad

Hello,
I'm curently out of everything so I cannot answer this one. All I can tell is that images are read from the client machine or jar file. If you want read images from the application server, you need the http:// syntax.
Francois

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

Attn : Geoflee A Genreral Comment About the New Look and Feel

Hi,
I feel that the discussion forums look and feel has improved and it allows us to chosse only theForums that we need to see and thus eliminates unneccasr sctrolling.
It would be better if OTN Reverts back to the old look and feel as regards showing the Questions and replies posted on that thread.
That way would be easier to see all the details in one strech instead of clicking on the replies...
I hope this would be considered.
Fellow Forum readers pls air u'r comments on this....
Regards,
Ganesh R

UIManager.put("ToolTip.background", Color.YELLOW);You can use these other properties for the tool tips:
ToolTip.backgroundInactive
ToolTip.border
ToolTip.borderInactive
ToolTip.font
ToolTip.foreground
ToolTip.foregroundInactive
Regards.

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

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

Error While running Oracle Look and feel Template Form - (LAF_TEMPLATE)

Forms Version 10.1.2.3
JRE version 1.6.0_30
Operating System Windows XP
I am trying to setup oracle look and feel project on my local machine.
For that i upgraded forms to 10.1.2.3 then i also applied path no *9593176* (But not yet performed steps related to jacob and webutil).
Problem : When i run Oracle look and feel template form it comes up with following error.*
Forms Applet version is : 10.1.2.3
Exception in thread "thread applet-oracle.forms.engine.Main-1" java.lang.NoSuchMethodError: oracle.forms.handler.IHandler.getApplet()Ljava/applet/Applet;
     at oracle.forms.fd.DrawLAF.init(DrawLAF.java:285)
     at oracle.forms.handler.UICommon.instantiate(Unknown Source)
     at oracle.forms.handler.UICommon.onCreate(Unknown Source)
     at oracle.forms.handler.JavaContainer.onCreate(Unknown Source)
     at oracle.forms.engine.Runform.onCreateHandler(Unknown Source)
     at oracle.forms.engine.Runform.processMessage(Unknown Source)
     at oracle.forms.engine.Runform.processSet(Unknown Source)
     at oracle.forms.engine.Runform.onMessageReal(Unknown Source)
     at oracle.forms.engine.Runform.onMessage(Unknown Source)
     at oracle.forms.engine.Runform.sendInitialMessage(Unknown Source)
     at oracle.forms.engine.Runform.startRunform(Unknown Source)
     at oracle.forms.engine.Main.createRunform(Unknown Source)
     at oracle.forms.engine.Main.start(Unknown Source)
     at sun.plugin2.applet.Plugin2Manager$AppletExecutionRunnable.run(Unknown Source)
     at java.lang.Thread.run(Unknown Source)

Hello,
I have spent a lot of time to indicate wherever I could that you don't have to ask questions about the LAF on this forum. You have two other different locations, a dedicated email and a dedicated forum.
At the first sight, it seems that you have not used the laf_10123.jar in your archive tag.
Thank you,
Francois

Make one bitmap have same "look and feel" as another

Hello community.
First time I am coming across this problem for a client.
He wants an old photograph (b/w, scanned) to be the "blueprint" for another one, which he just made with his digicam. The latter is of course quite different in lighting etc., but that's not what I am really worried about as I have the raw file so I can play around.
But is there a reasonably quick way to have that new digicam image have the same "look and feel" of that old, scanned image? I cannot post the image I am talking about (copyright issue), but if I had to make a new digicam image have the same "look and feel" of, say, such a picutre - what would I have to do?
Hints to simple techniques will do, because the pay for this job is close to lousy... :-(
Thanks all.
- creedless -
equipped with a MacBook Pro and Photoshop CS4 Extended

Download a "grunge" or "old photo" pic from stock xchange and put it on top of the photo in overlay or soft light mode. You can adjust the grunge layer with levels to make it a more neutral layer for blending. Use the dodge and burn tools to draw smudges on the photo, particularly lightening or darkening the edges of the photo. You can also use the blur brush to soften the image, except for around the face.
See tutorials:
http://www.adobe.com/designcenter/photoshop/articles/phs8kbfilmgrain.html
http://photoshoptutorials.ws/photoshop-tutorials/photo-effects/natural-film-grain.html
http://www.photoshoptalent.com/photoshop-tutorials/old-looking-photos.php
http://www.photoshopessentials.com/photo-effects/old-photo/

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

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 ..

Problem about look and feeling

Similar Messages

Maybe you are looking for