Application program interface that can maintain similar look and feel of a displayed image regardless of whether the interface is platform dependent or platform independent

• US 6,957,391 B2
• Filed: 05/31/2001
• Issued: 10/18/2005
• Est. Priority Date: 05/31/2001
• Status: Expired due to Fees

• Current Assignee: International Business Machines Corporation
• Original Assignee: International Business Machines Corporation
• Inventors: Broussard, Scott J.
• Primary Examiner(s): Cabeca, John
• Assistant Examiner(s): Bonshock, Dennis G.
• Application Number:
  US09/870,611
• Publication Number:
  US 20020180783A1
• Time in Patent Office: 1,601 Days
• Field of Search: 715/760, 715/515, 715/902, 715/746, 345/760, 345/746
• US Class Current: 715/746
• CPC Class Codes: G06F 8/38 for implementing user interfaces

Abstract

A system and method are disclosed whereby the look and feel of the OS/2 operating system is added to the Swing application program interface (API), in an enhanced version of the API, referred to herein as AWTSwing. A further disclosure is the creation of a thread-relative setLookAndFeel method, which only accepts calls from a particular thread to adopt a prescribed look and feel. This makes it possible for an application to have a look and feel distinct from that of the platform, or of other concurrently executing applications. This capability is not present in the conventional version of the Swing API, which treats look and feel settings as global.

Claims

1. A display system, comprising:

a display;

a processor;

an application program interface coupled to the display, wherein the interface comprises;

a UIManager containing code which, when executed by the processor, generates either a default image or an image that is user-defined;

a first pointer, which points to the code for generating the default image with an operation system independent look and feel setting;

a second pointer, which points to the code for generating the user-defined image with an operating system dependent look and feel setting; and

a peer component coupled to the UIManager and configured to (i) enable a selection capability of the UIManager, wherein said enablement causes the UIManager to select either the first pointer or the second pointer, or (ii) disable the selection capability of the UIManager, wherein said disablement causes the UIManager to select the first pointer.

2. The display system as recited in claim 1, wherein if the selection capability of the UIManager is enabled and the first pointer is selected, the default image is generated for displaying and object initially created by a first application program to be independent of code within an operating system software.

3. The display system as recited in claim 2, wherein if the selection capability of the UIManager is enabled and the second pointer is selected, the user-defined image is generated for displaying an object initially created by the first application program to be dependent on code within the operating system software.

4. The display system as recited in claim 3, wherein if the selection capability of the UIManager is disabled, the default image is generated for displaying an object, regardless of whether the object was initially created by the first application program to be independent from, or dependent on, code within the operating system software.

5. The display system as recited in claim 4, further comprising:

a second application program;

a software component defined by the application program interface for execution by the first application program and the second application program, wherein the software component is invoked during runtime to display an object created by the first application program, such that the appearance and operation of the displayed object is specific to the first application program and different from that of another instance of the object created by a second application program.

6. The display system as recited in claim 5, wherein the first application program is running under an operating system and the appearance and operation of the displayed object is substantially independent of the operating system.

7. The display system as recited in claim 5, wherein the object is part of a graphical user interface associated with the application program.

8. The display system as recited in claim 5, wherein the first application program is written in the Java programming language.

9. The display system as recited in claim 5, wherein the software component contains an instruction sequence to implement the specific appearance and operation of the displayed object, and wherein said instruction sequence is executed only in response to the first application program.

10. The display system as recited in claim 5, wherein the operating system comprises a computer operating system such as Windows, Unix or OS/2.