Hosting controls in a window via an interface for controlling the window

• US 6,473,100 B1
• Filed: 05/20/1998
• Issued: 10/29/2002
• Est. Priority Date: 05/20/1998
• Status: Expired due to Fees

• Current Assignee: Microsoft Technology Licensing LLC (Microsoft Corporation)
• Original Assignee: Microsoft Corporation
• Inventors: Stefanovic, Nenad, Beaumont, Christian, Springfield, James F.
• Primary Examiner(s): Kincaid, Kristine
• Assistant Examiner(s): Joseph, Thomas J
• Application Number:
  US09/082,234
• Time in Patent Office: 1,623 Days
• Field of Search: 345/346, 345/340, 345/341, 345/342, 345/333-335, 345/813, 345/760, 345/744-747, 345/804-805, 345/781, 345/784, 345/788, 345/789, 345/792, 345/793, 707/513, 709/302, 709/303, 709/339, 709/201, 709/203, 709/328, 709/329
• US Class Current: 715/781
• CPC Class Codes: G06F 9/451 Execution arrangements for user interfaces

Abstract

Hosting user interface controls in a window via an interface for controlling the window is disclosed. One aspect of the invention is a computerized system having an operating system and at least one program. The operating system provides for hosting controls of a predetermined type within windows of a predetermined type via an interface for controlling the windows. The programs utilize the interface to host one or more controls within one or more windows. Thus, with respect to versions of the MICROSOFT WINDOWS operating system, a program may utilize the WIN32 API (i.e., interface) to host ACTIVEX-type controls within windows hosted by the program, also via the WIN32 API.

Claims

1. A computerized method comprising:

a) within an operating system, registering a window class for implementing a control container;

b) receiving a create window command at an application programming interface (API), the command including a control parameter of a type selected from the group of types consisting of a program identifier, a class identifier, a Universal Resource Locator (URL) address, and a HyperText Markup Language (HTML) code;

c) creating an instance of a window by the API;

d) determining at the API the type of control parameter;

e) upon determining that the control parameter is a program identifier, converting the control parameter at the API to a class identifier, and creating by the API an instance of a control having support for the IUnknown interface as referenced by the class identifier for placement into the window;

f) upon determining that the control parameter is a class identifier, creating by the API an instance of a control having support for the IUnknown interface as referenced by the class identifier for placement into the window;

g) upon determining that the control parameter is a URL address, creating a viewer control having support for the IUnknown interface at the API to view the URL address, and creating by the API an instance of the viewer control created for placement into the window; and

h) upon determining that the control parameter is an HTML code, creating a viewer control having support for the IUnknown interface at the API to view the HTML code, and creating by the API an instance of the viewer control created for placement into the window.

2. The computerized method of claim 1, wherein the API comprises a WIN32 API.

3. The computerized method of claim 1, wherein the API is part of a version of the MICROSOFT WINDOWS operating system at least as recent as the MICROSOFT WINDOWS 95 operating system.

4. The computerized method of claim 1, wherein the window created in e), f), g), and h) comprises a window of a version of the MICROSOFT WINDOWS operating system at least as recent as the MICROSOFT WINDOWS 95 operating system.

5. A computerized method comprising:

a) within an operating system, registering a window class for implementing a control container;

b) receiving a create window command at an application programming interface (API), the command including a control parameter of a type selected from the group of types consisting of a program identifier, a class identifier, a Universal Resource Locator (URL) address, and a HyperText Markup Language (HTML) code;

c) creating an instance of a window by the API;

d) determining at the API the type of control parameter;

e) upon determining that the control parameter is a program identifier, converting the control parameter at the API to a class identifier, and creating by the API an instance of an ACTIVEX-type control as referenced by the class identifier for placement into the window;

f) upon determining that the control parameter is a class identifier, creating by the API an instance of an ACTIVEX-type control as referenced by the class identifier for placement into the window;

g) upon determining that the control parameter is a URL address, creating a ACTIVEX-type viewer control at the API to view the URL address, and creating by the API an instance of the ACTIVEX-type viewer control created for placement into the window; and

h) upon determining that the control parameter is an HTML code, creating a ACTIVEX-type viewer control at the API to view the HTML code, and creating by the API an instance of the ACTIVEX-type viewer control created for placement into the window.