Obviousness

US Patent 9235428, with a priority date of February 1, 1999, describes a system and method for providing a graphical user interface (GUI) for component-based application programs. An analysis under 35 U.S.C. § 103 for obviousness considers whether the claimed invention, as a whole, would have been obvious to a person having ordinary skill in the art (PHOSITA) at the time of the invention, in light of prior art combinations and motivations for combining them.

The independent claims (Claim 1 for a system and Claim 9 for a method) define the core invention, featuring a renderer, a proxy appearing as a monolithic application to the renderer, and a workflow manager.

Obviousness Analysis of US 9235428

A PHOSITA in 1999 would be familiar with component architectures (such as COM, DCOM, and CORBA, as mentioned in the patent's background [cite: 9235428 col 1, lines 20-24]) and the challenges associated with dynamically updating GUIs for such applications. The PHOSITA would also be aware of web browser technologies, particularly Dynamic HTML (DHTML), which by the late 1990s offered rich layout capabilities and platform independence, making them attractive for GUI development [cite: 9235428 col 3, lines 52-60; col 6, lines 5-10].

The claimed invention, particularly its independent claims, combines several known concepts in a manner that would have been obvious to a PHOSITA.

Combination 1: Renderer + Proxy + Dynamic GUI Determination

1. Renderer for a GUI: The patent describes a renderer as displaying the GUI for an application program. The description explicitly states a DHTML browser is the preferred renderer due to its rich layout features and platform independence [cite: 9235428 col 5, lines 52-54; col 6, lines 5-10]. By the priority date of February 1, 1999, DHTML capabilities were well-established in browsers like Internet Explorer 4.0 (1997) and Netscape Navigator 4.0 (1997). A PHOSITA, seeking to create flexible and platform-independent GUIs for component-based applications, would have been motivated to utilize a DHTML browser as the renderer.
2. Proxy for Component Abstraction (Monolithic Appearance): The patent claims a proxy that provides necessary components to the renderer and appears to the renderer as a single monolithic application program, thereby hiding the details of the underlying component architecture [cite: 9235428 Abstract, Claim 1]. The concept of using proxy objects to abstract underlying complexity and make distributed objects appear local to a client was a well-known technique in object-oriented and distributed computing. For example:
   • US6038395A (International Business Machines Corporation, priority 1994-12-16) teaches "implementing proxy objects in a visual application builder framework," stating that "proxy objects are also used to make distributed objects appear local to the client, thereby simplifying the client's view of a distributed application" [cite: US6038395A Abstract, col 4, lines 10-12].
   • US5511197A (Microsoft Corporation, priority 1992-11-13) describes "network marshalling of interface pointers for remote procedure calls," which is a fundamental mechanism enabling proxies to mediate communication in component architectures [cite: US5511197A Abstract].
   • US6385661B1 (Recursion Software, Inc., priority 1998-10-19) discusses the "dynamic generation of remote proxies" [cite: US6385661B1 Abstract].
     A PHOSITA would be motivated to combine the use of a DHTML renderer with such a known proxy mechanism to interface with complex component architectures, as this would simplify the renderer's implementation and allow for transparent modification of application components [cite: 9235428 col 6, lines 23-34].
3. Proxy Determining GUI Changes (New Layout vs. Updating Present Layout): The patent specifies that the proxy determines whether a given change requires rendering a new layout or updating a present layout in the GUI [cite: 9235428 Claim 1]. Dynamic updating of GUIs in response to application context changes was a recognized practice in the art, even in conventional systems like Microsoft Paint where toolbars could dynamically update [cite: 9235428 col 4, lines 7-10]. US5625783A (Microsoft Corporation, priority 1994-12-13) describes an "automated system and method for dynamic menu construction in a graphical user interface" [cite: US5625783A Abstract]. Given the proxy's established role as the central communication conduit between the application's components and the renderer, it would be a logical and straightforward design choice for a PHOSITA to assign the proxy the responsibility of deciding how to effect GUI changes based on the application's context. This determination (new layout for a significant context switch vs. updating an existing layout for minor changes) is a natural extension of the proxy's function in marshalling UI information to the renderer [cite: 9235428 col 9, lines 16-24].

Combination 2: Adding a Workflow Manager

1. Workflow Manager for Document Viewers and UI Components: The patent introduces a workflow manager defined to communicate document viewers and associated user interface components to the proxy for rendering [cite: 9235428 Claim 1]. The background of the patent acknowledges the difficulty of updating GUIs for component-implemented programs [cite: 9235428 col 3, lines 37-40]. Prior art showed related concepts of managing UI elements and content:
   • US6405192B1 (International Business Machines Corporation, priority 1999-07-30) describes a "navigation assistant" for providing "user configured complementary information for data browsing in a viewer context" [cite: US6405192B1 Abstract]. Although this patent has a priority date after the claimed patent, the concept of managing viewers and contextual information was broadly known.
   • US6222533B1 (I2 Technologies, Inc., priority 1997-08-25) discusses a "universal adapter framework and providing a global user interface and global messaging bus" [cite: US6222533B1 Abstract]. This teaches the idea of a centralized framework for managing UI components.
     A PHOSITA, faced with the known challenges of managing and updating GUIs in component-based applications, would be motivated to introduce a dedicated "workflow manager" to orchestrate the provisioning of document viewers and their associated user interface components to the proxy. This would improve modularity, simplify the addition of new features or components, and streamline the dynamic updating of the GUI, directly addressing the identified problem in the patent's background [cite: 9235428 col 10, lines 43-60]. The workflow manager acts as a logical layer to manage the state and communication related to user interactions and data presentation within the component architecture.

In conclusion, the combination of a DHTML renderer, a proxy providing a monolithic interface for component-based applications (and determining layout changes), and a workflow manager coordinating document viewers and UI components, would have been obvious to a PHOSITA by the priority date of US 9235428. This combination leverages known technologies and design patterns to address identified challenges in GUI development for component architectures.