Central Class GUI Report Generation Eliminates Redundant Coding

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing report generation methods using control objects in GUIs require redundant implementation of control and container classes, leading to increased overhead and complexity, making the process time-consuming and not user-friendly.

Innovation Solution

A central class, such as a control factory class, is introduced to generate graphical user interfaces by utilizing a container table and a control table, eliminating the need for explicit implementation of control and container classes, allowing programmers to focus on describing the GUI structure without redundant coding.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Ease of manufacture

If control and container classes are implemented in each report, then the report can generate GUIs with control objects, but the coding becomes redundant and time-consuming

Engineering Contradiction:
ImproveReport generation easeVSAvoidReport generation time
Core Design Contradiction:
Ease of manufactureVSLoss of time

Solution Approach 1:

The central class serves as a universal factory that can generate multiple types of control objects and container structures through a single interface. Instead of requiring separate control and container class implementations for each report, the central class provides a multi-functional framework that handles all GUI generation needs through standardized methods, thereby reducing redundant coding and time consumption.

Inventive Principle:
Principle #6Universality (Multi-functionality)

Solution Approach 2:

The patent uses table-based descriptions (container table and control table) as templates or copies that define the structure and behavior of GUI elements. These tables serve as blueprints that the central class uses to instantiate the actual control objects, allowing the same structural definition to be reused across different reports without requiring manual re-implementation of control and container classes.

Inventive Principle:
Principle #26Copying

2Ease of manufacture

If control and container classes are implemented in each report, then the report can generate GUIs with control objects, but the coding becomes redundant

Engineering Contradiction:
ImproveReport generation easeVSAvoidClass implementation complexity
Core Design Contradiction:
Ease of manufactureVSDevice complexity

Solution Approach 1:

The patent extracts the complex control and container class implementations from individual report programs and consolidates them into a single central class. This extraction removes the redundancy by placing the common functionality in one location, while individual reports only need to provide simple table-based descriptions rather than full class implementations, thereby reducing overall coding complexity.

Inventive Principle:
Principle #2Taking out (Extraction)

Solution Approach 2:

The central class acts as a universal framework that handles all control object and container generation needs through a single standardized interface. This universality eliminates the need for separate control and container class implementations in each report, reducing coding complexity while maintaining full functionality.

Inventive Principle:
Principle #6Universality (Multi-functionality)

3Ease of manufacture

If control and container classes are implemented in each report, then the report can generate GUIs with control objects, but additional overhead is introduced

Engineering Contradiction:
ImproveReport generation easeVSAvoidSystem overhead
Core Design Contradiction:
Ease of manufactureVSLoss of energy

Solution Approach 1:

The central class provides a universal framework that generates control objects and containers through a single standardized interface, eliminating the need for multiple separate class implementations. This universality reduces system overhead by avoiding redundant class definitions and initialization code that would otherwise be present in each report program.

Inventive Principle:
Principle #6Universality (Multi-functionality)

Solution Approach 2:

The patent uses table-based descriptions as lightweight copies that define GUI structure without requiring full class implementations. These table copies are processed by the central class to instantiate the actual control objects, reducing the computational overhead associated with loading and initializing multiple control and container classes in each report.

Inventive Principle:
Principle #26Copying

Data Source

PatentUS7873615B2Control object based report generation using a central class
Publication Date: 2011.01.18 SAP SE
  • US7873615B2 patent drawing
  • US7873615B2 patent drawing
  • US7873615B2 patent drawing

AI summary

A system and technique for generating reports dealing with control objects utilizing a central class, such as a control factory class, without redundant use of container and control classes. The central class creates the entire graphical user interface needed in a particular report during the report's initialization. By calling the central class, the programmer does not have to initialize the class and use a special object within the program and simply may provide the central class with two tables: a container table and a control table. The programmer need not provide the actual control and container classes to the central class through the tables. The programmer need only provide the description of the construction of the graphical user interface through the tables.