Theme aware management using fusion

• US 6,762,767 B2
• Filed: 04/05/2001
• Issued: 07/13/2004
• Est. Priority Date: 04/06/2000
• Status: Expired due to Fees

• Current Assignee: Microsoft Technology Licensing LLC (Microsoft Corporation)
• Original Assignee: Microsoft Corporation
• Inventors: Guzak, Chris J., Schmidt, Michael A., Hellyar, Paul S., Evans, Christopher A., Amadio, Louis, Hysom, Scott S., Hanggie, Scott R., Fernandez, Roland L., Stoakley, Richard W.
• Primary Examiner(s): Bella, Matthew C.
• Assistant Examiner(s): CUNNINGHAM, GREGORY F
• Application Number:
  US09/827,842
• Publication Number:
  US 20020054046A1
• Time in Patent Office: 1,195 Days
• Field of Search: 345/581, 345/744, 345/746, 345/747, 345/762, 345/763, 345/765, 345/805
• US Class Current: 345/581
• CPC Class Codes: G06F 9/451 Execution arrangements for user interfaces

Abstract

A system and method are described that use theming functions of a theme manager to render graphical components in a themed fashion. The theme manager uses a theme file that has theme properties for graphical components of all types. When an application is started a system is provided that determines whether the application supports theming. If the application supports theming a dynamic link controls library that supports theming is linked to the application. If the application does not support theming, the non-theming controls library is linked. If an application supports themes, application user controls and shell common controls are rendered with themes by using the functions of the theming controls library that interact with functions of the theme manager. Non-client window components are rendered using themes by intercepting render messages to windows and sending the messages to the theme manager. Non-client window components are also measured and rendered using a theme property file when appropriate in response to certain application program interface calls.

Claims

1. A theme management system configured for rendering graphical components on a computer system having a graphical operating system running one or more applications, each application being able to make a request to be linked to a controls module, the theme management system comprising:

a first controls module having one or more first functions responsive to application program interface calls capable of rendering graphical components with themes;

a second controls module having one or more second functions responsive to application program interface calls capable of rendering graphical components without themes; and

a fusion module that responds to the request by determining whether to link the application to one of the first controls module or the second controls module to render graphical components.

2. The theme management system of claim 1 further comprising a theme management module having one or more third functions responsive to rendering calls from the one or more first functions of the first controls module, the third functions capable of rendering graphical components using a theme.

3. The theme management system of claim 2 further comprising:

an intercepting hook module that intercepts a non-client window message sent to a target window, the target window having one or more non-client graphical components in a non-client window area, the non-client window message requesting that the target window perform an action on the one or more non-client graphical components; and

a first routing module that receives the non-client window message from the intercepting hook module and routes the non-client window message to the one or more third functions of the theme manager so that the action will be performed.

4. The theme management system of claim 3 wherein the first controls module further comprises a second routing module that routes an application program interface call to the intercepting hook module so that an action can be performed on the one or more non-client graphical components on the non-client window area in response to the application program interface call.

5. The theme management system of claim 3 wherein the second controls module further comprises a third routing module that routes an application program interface call to the intercepting hook module so that an action can be performed on the one or more non-client graphical components on the non-client window area in response to the application program interface call.

6. The theme management system of claim 3 wherein the non-client window message is a render message that requests that the one or more non-client graphical components on the non-client window area be rendered, the theme management module responding to the render message by rendering the one or more non-client graphical components.

7. The theme management system of claim 3 wherein each of the one or more non-client graphical components is associated with dimensions and the non-client window message is a measurement message that requests that the dimensions of the one or more non-client graphical component on the non-client window area be measured the theme management module responding to the measurement message by measuring the dimensions of the one or more non-client graphical components.

8. The theme management system of claim 1 wherein the first and second functions of the first and second controls modules are capable of rendering user controls and shell common controls.

9. A theme management system configured for rendering graphical components on a computer system having a graphical operating system running one or more applications, each application being able to make a request to be linked to a controls module, the theme management system comprising:

a first controls module having one or more first functions responsive to application program interface calls capable of rendering graphical components with themes;

a second controls module having one or more second functions responsive to application program interface calls capable of rendering graphical components without themes; and

a fusion module that responds to the request by determining whether to link the application to one of the first controls module or the second controls module to render graphical components;

the fusion module comprises;

a first detecting module that detects whether an application has an associated manifest file that indicates which of a set of controls modules should be linked to the application;

a second detecting module that detects whether the manifest indicates that the first controls module should be linked; and

a linking module that links the first controls module to an application if the manifest indicates that the first controls module should be linked.

10. A theme management system configured for rendering graphical components on a computer system having a graphical operating system running one or more applications, the theme management system comprising:

an intercepting hook module that intercepts a render message to a target window having non-client graphical components, the render message requesting that the target window render the target window'"'"'s non-client graphical components;

a theme manager module having one or more first functions capable of rendering any window'"'"'s non-client graphical components using a theme; and

a routing module that routes the render message to the one or more first functions of the theme manager module so that the target window'"'"'s non-client graphical components are rendered using a theme having a set of theme properties;

a first controls module having one or more second functions capable of interacting with the one or more first functions of the theme management module to render user controls or shell common controls having theme properties;

a second controls module having one or more third functions capable of rendering user controls and shell common controls not having theme properties; and

a fusion module responsive to a request from an application to link the application to one of the first controls module or the second controls module.

11. A method of rendering a graphical control on a computer display of a computer having a graphical operating system, a first set of applications implementing theme capability, and a second set of applications not implementing theme capability, the method comprising:

providing a first controls module having one or more first functions capable of rendering graphical controls for applications not implementing theme capability;

providing a second controls module having one or more second functions capable of rendering graphical controls for applications implementing theme capability;

receiving a request from an application, requesting that the application be linked to one of the first controls module and second controls module;

determining whether the application implements theme capability; and

linking the application to the second controls module if the application implements theme capability, so that the application can use the functions of the second controls module to render graphical controls with themes.

12. The method of claim 11 further comprising:

receiving an application program interface call from an application, the application program interface call requesting that a graphical control be rendered;

determining whether the graphical control implements theme capability; and

calling a theme manager that uses a theme file having graphical component property data to render the requested graphical control in a themed fashion if the graphical control implements theme capability.

13. The method of claim 11 wherein the act of determining comprises:

detecting whether a manifest exists for the application; and

searching the manifest for an indicator that indicates that the application is capable of interacting with the second controls module to render graphical controls with themes.

14. The method of claim 12 further comprising:

intercepting a non-client window message sent to a window having one or more non-client graphical components, the non-client window message requesting that the window perform an action on the one or more non-client graphical components;

routing the non-client window message to the theme manager that manages theme properties for non-client graphical components; and

performing the action on the one or more non-client graphical components.

15. The method of claim 14 wherein the non-client window message is a render message and the action is rendering the one or more non-client graphical components.

16. The method of claim 14 wherein the non-client window message is a measurement message, each of the one or more non-client graphical components are associated with dimensions, and the action is measuring the dimensions of the one or more non-client graphical components.

17. The method of claim 12 further comprising:

routing the application program interface call to an intercepting hook module;

routing the application program interface call to the theme manager that renders non-client graphical components in a themed fashion;

determining whether the application program interface call affects one or more non-client graphical components of a window being used by the application; and

rendering the one or more non-client graphical components in the themed fashion if the application program interface call affects the one or more non-client graphical components.

18. A computer program product readable by a computing system and encoding a computer program of instructions for executing a computer process for rendering a graphical control on a computer display of a computer having a graphical operating system, a first set of applications implementing theme capability, and a second set of applications not implementing theme capability, the computer process comprising:

receiving a request from an application, requesting that the application be linked to one of the first controls module and second controls module;

determining whether the application implements theme capability; and

linking the application to the second controls module if the application implements theme capability, so that the application can use the functions of the second controls module to render graphical controls with themes.

19. The computer program product of claim 18 wherein the computer process further comprises:

receiving an application program interface call from an application, the application program interface call requesting that a graphical control be rendered;

determining whether the graphical control implements theme capability; and

calling a theme manager that uses a theme file having graphical component property data to render the requested graphical control in a themed fashion if the graphical control implements theme capability.

20. The computer program product of claim 18 wherein the act of determining comprises:

detecting whether a manifest exists for the application; and

searching the manifest for an indicator that indicates that the application is capable of interacting with the second controls module to render graphical controls with themes.

21. The computer program product of claim 19 wherein the computer process further comprises:

intercepting a non-client window message sent to a window having one or more non-client graphical components, the non-client window message requesting that the window perform an action on the one or more non-client graphical components;

routing the non-client window message to the theme manager that manages theme properties for non-client graphical components; and

performing the action on the one or more non-client graphical components.

22. The computer program product of claim 21 wherein the non-client window message is a render message and the action is rendering the one or more non-client graphical components.

23. The computer program product of claim 21 wherein the non-client window message is a measurement message, each of the one or more non-client graphical components is associated with dimensions, and the action is measuring the dimensions of the one or more non-client graphical components.