Modification-Free UI Cutting via Control Tree Segmentation

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Pre-existing applications, designed for full-screen use, lack mashup capabilities, making it difficult to customize or combine their components with other applications, as they occupy the entire user interface and do not support data flow between components.

Innovation Solution

A modification-free user interface cutting technique that allows selecting and removing specific portions of a full-screen application's UI, rendering only the desired components and enabling the insertion of mashup components or external applications, without modifying the underlying application, using a UI control tree and personalization settings to store and manage the changes.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If a full-screen application occupies the entire user interface, then the application can display all its components and functionality, but the application cannot be used in mashup scenarios where components need to be combined with other applications

Engineering Contradiction:
Improvemashup capabilityVSAvoidapplication modification complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The user interface is segmented into a control tree structure where nodes represent selectable portions of the UI. This allows the full-screen application to be divided into manageable sections that can be individually selected, cut, and reused in mashup scenarios without modifying the application's core functionality.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

Specific portions of the user interface can be extracted from the full-screen application by selecting them in the control tree and cutting them out. These extracted portions can then be inserted into other applications or workspaces, enabling mashup capabilities while leaving the original application unchanged.

Inventive Principle:
Principle #2Taking out (Extraction)

2Area of stationary object

If a full-screen application is used, then all application components are visible and accessible, but no visual space remains to include multiple mashup components

Engineering Contradiction:
Improveavailable visual spaceVSAvoidUI customization ease
Core Design Contradiction:
Area of stationary objectVSEase of operation

Solution Approach 1:

The UI is segmented into a hierarchical control tree structure, allowing users to select specific portions for cutting. This segmentation creates visual space by removing selected portions from the full-screen layout, enabling mashup components to be added in the emptied areas.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The system performs preliminary actions by pre-defining the control tree structure and pre-positioning UI portions that can be selectively cut. This preparation enables easy customization and mashup component integration without requiring complex manual manipulation during operation.

Inventive Principle:
Principle #10Preliminary action

3Adaptability or versatility

If existing applications are modified to support mashup capabilities, then mashup functionality is achieved, but the underlying business logic and application integrity are compromised

Engineering Contradiction:
Improvemashup functionalityVSAvoidapplication integrity
Core Design Contradiction:
Adaptability or versatilityVSReliability

Solution Approach 1:

Only the user interface portions are extracted and modified, while the underlying application logic remains intact. The control tree structure enables selective extraction of UI elements for mashup scenarios without affecting the core business logic, maintaining application integrity.

Inventive Principle:
Principle #2Taking out (Extraction)

Solution Approach 2:

The control tree acts as an intermediary layer between the full-screen application and mashup scenarios. It provides a mediation mechanism that allows UI portions to be selectively cut and reused without directly modifying the application's core functionality, preserving reliability while enabling versatility.

Inventive Principle:
Principle #24Intermediary (Mediator)

4Manufacturing precision

If the user interface control tree is used to manage UI portions, then precise control over which components to render is achieved, but the system complexity increases

Engineering Contradiction:
ImproveUI component selection precisionVSAvoidcontrol tree management complexity
Core Design Contradiction:
Manufacturing precisionVSDevice complexity

Solution Approach 1:

The control tree structure serves multiple functions: it defines the UI hierarchy, enables selective rendering, supports cutting and copying operations, and facilitates mashup component integration. This multi-functionality achieves precise control without proportionally increasing system complexity.

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

Solution Approach 2:

The control tree uses a nested structure where parent nodes contain child nodes, creating a hierarchical organization of UI portions. This nesting enables precise selection and rendering control by navigating through nested levels, while the structured organization actually simplifies management compared to flat alternative approaches.

Inventive Principle:
Principle #7Nested doll (Nesting)

Data Source

PatentUS8938684B2Modification free cutting of business application user interfaces
Publication Date: 2015.01.20 SAP SE
  • US8938684B2 patent drawing
  • US8938684B2 patent drawing
  • US8938684B2 patent drawing

AI summary

The present disclosure involves systems, software, and computer implemented methods for modification free UI cutting of components in an application. One process includes operations for identifying a selection of a particular portion of the user interface of the application for cutting. The position of the identified portion of the user interface of the application in a user interface control tree is determined and defined as a root node of the user interface control tree. The identification information of the root node is stored in personalization settings of the application, and user interface elements associated with the root node are rendered.