Same "Look and Feel"

Hi I am new to J2EE Programming.. so could you guys help me out with this silly question??
One of the main advantages of Swing is "Same Look and Feel" accross platforms. Now I am coding HTML pages and using servlets to handle the requests. But i dont get this same look and feel . The button on a same webpage looks very differnt in Xp and 2000.
Can u tell me, how can i go about getting this "same Look and Feel"?

Thanks for replying. But isint there any way in which I can dictate the display? For eg. In this very Site the 'Reply' buttons that are available on the Forums page have a same look and feel accross all platforms.
How to go about achieving that?
Message was edited by:
arijit_datta

Similar Messages

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/

Uniform Look and Feel

Can anybody please give me hint on how to build pages like that of sites http://www.tomatoland.com and http://www.kids123.com , ie same look and feel in all the pages.One thing that i have tried is creating Unstructured UI templates and using it in portal pages.Then the problem is that i am not able to use HTML files inside content area as portlets so that i can include it in the portal pages.Please give a hint or link for any tutorial for this.
Regards
Ziyad

ORACLE have told us the sites you refer to have been built with heavy ORACLE involvement. They use images and custom code to make the sites look nice and show off the product.
They are not sites any sensible site manager would build because they will be difficult to maintain.

Is a JSP Tag Library providing Oracle Financial look and feel available

We are going to use Oracle Financial as part of our future application.
That is why other parts of it (which we plan to develop using JDeveloper)
have to have the same Look and Feel.
Is a JSP Tag Library that provides Oracle Financial Look and Feel available?

Oracle Applications use BC4J, UIX, and JDeveloper.
The UIX framework implements the Oracle "Browser Look And Feel" (BLAF) that our Oracle Applications self-service applications use.
The UIX JSP tag library lets JSP developers do the same.

Regarding look and feel

Hi Experts,
We are building our front end interface for Integrated planning solution using webtemplate ..can somebody give me some General suggestion to improve look and feel (ofcourse without hitting performance). Our BI reports are on Xcelsius(It does not allow input query), so obviously there is a comparison between these two tools..
Thanks in advance

We actually took a copy of the SAP standard reporting template to use as it already has a good suite of options. However, there are certain aspects that are not as relevent for planning (navigation pane since data is already presented at desired level of detail) and other things that are only necessary for a planning query (buttons for planning functions, save, etc.)
We inserted a few XPATH commands into the standard template that determine if the query is in change mode or not. With that, we can logically drop the navigation pane or insert extra buttons. In our case, for planning queries, we create a web template with the same name as the planning query and that template contains nothing more than the buttons that are relevant for that query.
This way, all queries in our system retain the same look and feel across all applications, and effectively we don't do any web template creation which saves development time.

Problem With ButtonUI in an Auxiliary Look and Feel

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

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

Look and Feel Issues from NWDS 7.0.9 on Windows 7

Dear Experts,
I have successfully installed a new NWDS 7.0.9 on my 18' inch laptop:
Windows 7 (64Bit)
JDK 1.4.18 (32Bit)
The NWDS starts without any problems however, i am begining to experience some erratic behavior from the projects i have created.
For instance, when i attempt to Edit the Application Properties for a WDJ project, the neccessary fields (and tabs) are not displayed hence i am unable to edit properties like the 'ExpirationTime' or create new one for that matter.
In some cases,i am unable to embed a View into a Window because the neccessary fields to aid my selection of the view i want to embed are not visible for interaction.
The same challenge occurs with EAR project; i am unable to edit 'application-j2ee-engine.xml' fields because they are not visible.
After some troubleshooting,i discovered that the screen resolution may be affecting the 'Look and Feel' of the NWDS itself,
If i reduced the resolution from 1024*768 to a value much more lower, some of these controls are displayed but with the desktop completely messed up.
Does anybody have a solution to my problem because this challenge is affecting my productivity?
Could my issue be as a result of my laptop screen size (i am using an 18'inch laptop)?
Best regards,
Bakau Onafuwa
Oceanic Bank Int'l PLC

Hi Vishal,
first go to the download section in SMP.
Roughly follow this path (translated from german ;-):
SAP Software Distribution Center -> Download -> Further Download-Infos -> SAP Support Package Stacks -> SP Stack Download
From list select SP Stack SAP NetWeaver 2004s
A new window will pop up:
1. Select your stack
2. Usage Selection: Application Server Java
3. Next Step
4. Under SAP Kernel xx bit select your DB and OS
5. Next Step
6. You get a list of all components of you selected items.
Here you'll find NWDS with a filename like JIDE09P_1-10003480.SAR
You know the rest, right?
Regards,
ok

Themed look and feel broken in sub-site

We have several site collections in a farm using SP2013 + SP1 under a common web application that use a custom theme for the look and feel. After upgrading to SP2013 December 2014 CU, one of the site collections' custom theme is broken. Furthermore,
the same site collection cannot use most of the OOTB themes. I have only successfully gotten the theme "Office" to work correctly. (I have not tested all the OOTB theme choices)
Immediately after the CU was applied the CSS and JS on this site collection was not working. After changing the theme to "Office" I was able to test out other troubleshooting options. If I select another theme choice, the "try it out"
page returns with an error "A cobalt error was thrown." This is not a helpful error for me and I could not find much on the internet regarding it. Another error I have received was "file not found", or yet another error "The
URL
'_catalogs/theme/Themed/4F147962/likefull.11x11x32-F47391E9.themedpng' is
invalid. It may refer to a nonexistent file or folder, or refer to a valid file
or folder that is not in the current Web." I have not been able to fix the issue.
I have found that under 'Site Settings' -> 'Web Designer Galleries' -> 'Themes' -> 'Themed' is a library of folders. My thought is that these folders are created dynamically when a new theme is applied. I have several folders, but all are empty
except one. I am now trying to determine why these folders are empty.
Any ideas?

Hi,
Please try to update the latest CU for SharePoint 2013(April 2015 CU for SharePoint 2013), then check whether the issue still exists or not.
http://blogs.technet.com/b/stefan_gossner/archive/2015/04/14/april-2015-cu-for-sharepoint-2013-has-been-released.aspx
In my test environment, the 'Themed' all folders are not empty.
Best Regards
TechNet Community Support
Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact
[email protected]

Windows XP Look and Feel

Hi,
When I use Windows XP style Look & Feel on Windows XP Title Bar and Scroll Bar disappears or the color is set to transparent.
I set Look and Feel using:
UIManager.setLookAndFeel(UIManager.getSystemLookAndFeelClassName());
Even I run SwingSet2 on Windows XP and set the Look & Feel to Windows XP Style the result is the same.
Is there any recommendation about this?
Thanks...

I forgot to say that I am using Java SDK v1.4.2_4

Look and Feel

Salutations,
I am writing a simple swing program that when the user clicks a button corresponding to a look and feel name ie "Metal" etc. the Look and Feel is Changed, it works great except for one problem, it will not change to the "Metal" look and feel, I believe this to be the default look and feel, but when changed to another, it will not change back. Any suggestions?
thanks,
J

Here's the code from the SwingSet2 Demo:
// Possible Look & Feels
    private static final String mac      = "com.sun.java.swing.plaf.mac.MacLookAndFeel";
    private static final String metal    = "javax.swing.plaf.metal.MetalLookAndFeel";
    private static final String motif    = "com.sun.java.swing.plaf.motif.MotifLookAndFeel";
    private static final String windows = "com.sun.java.swing.plaf.windows.WindowsLookAndFeel";
        try {
            UIManager.setLookAndFeel(currentLookAndFeel);
            SwingUtilities.updateComponentTreeUI(this);
            // where currentLookAndFeel is one of those Strings
        } catch (Exception ex) {
         System.out.println("Failed loading L&F: " + currentLookAndFeel);
         System.out.println(ex);
// And as an (unexpected) bonus, it's the same as the code I once used:
static String windowsClassName = "com.sun.java.swing.plaf.windows.WindowsLookAndFeel";
        try
            javax.swing.UIManager.setLookAndFeel(windowsClassName);
            javax.swing.SwingUtilities.updateComponentTreeUI(this);
        catch(Exception e)

Wireframes to portal look and feel

hi,
i am working on a webcenter portal application.
as usual, we have got wireframes (html prototypes) from customer which has html, js and css files.
now i have to produce same kind of look and feel on webcenter portal.
please suggest what shall i do?
is this recommended way?
i copy content of css file which i got as part of wireframes into portal-skin.css file, now i use html components (div, ul, li, p etc) in page template and other jspx pages (reference could be the html files which i got in wireframes).
please suggest.

Hi.
You can select two ways:
- Continue with your HTML + CSS and create templates based directly on wireframes. Faster and easier solution for non-adf people.
- Translate your wireframes to a ADF Templates and use ADF Skinning to achieve the styles. Slower and hard if you don't have much experience with it.
About the solution of maintain HTML + CSS:
- Maintain your structure of CSS, images and JS in separated folders of skin folder (In Web Content or in project PortalWebAssets).
- In Skin files (like portal-skin.css) change ADF Skinning of components only. Is the best way to maintain the hierarchy of adf skins.
About the solution full ADF:
- Read this document about full ADF Skin and Templates: http://www.oracle.com/technetwork/middleware/webcenter/portal/learnmore/pagetemplates-1438595.pdf
More info:
- In adf-config.xml you can provide rewrite rules to search your static-files when you are using Web Server (OHS) to server static-files.
I hope this help you.
Regards.

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.

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

XE look and feel in Oracle 10g Enterprise Edition

Hi!
I have both Enterprise Edition 10gR2 and XE installed on Linux. I want to use Enterprise Edition as my main database. But I want XE "look and feel" for 10gR2
What do I have to do to accomplish this?
regards
Paal

nothing, you can have both running at the same time.
all depends what you mean by 'look and feel' really

Webutil Open File Dialog look and feel

Webutil all revisions?, Windows NT 4.0/XP.
The open/save file dialog boxes in webutil are always the same style (Oracle/Motif?) when either the LookandFeel is set to Generic/Windows or Oracle/Motif.
Is there anyway to change it to always look like Windows Look and Feel?

Hello,
One possible way would be to write your own Java Bean component that call the standard openfile dialog, then set the LAF yourself:
UIManager.setLookAndFeel(UIManager.getSystemLookAndFeelClassName());
...but, I know, this represents some extra work.
Francois

Same "Look and Feel"

Similar Messages

Maybe you are looking for