Multi-Page Demo Editing with Aggregated Objects Across Shallow Copies

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing web-based systems face challenges in providing demonstrations without relying on real-time execution, which can be disrupted by bugs or sensitive information, and require customized presentations that do not affect actual users, while efficiently updating the same object across multiple documents.

Innovation Solution

A multi-page demo is created using shallow copies of web-based system pages, allowing for the definition of aggregated objects that can be edited across linked shallow copies, using acquisition methods like XPath and CSS Selectors to apply uniform updates.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Ease of operation

If real-time execution of web-based system is used for demonstration, then interactivity and functionality are improved, but reliability deteriorates due to bugs and sensitive information

Engineering Contradiction:
ImproveinteractivityVSAvoiddemonstration stability
Core Design Contradiction:
Ease of operationVSReliability

Solution Approach 1:

The patent creates static copies of web pages (shallow copies) that replicate the visual appearance and structure of the web-based system without executing its code. These copies include HTML, CSS, and JavaScript files that render the same user interface elements, allowing demonstrations to run independently of the actual web-based system's execution environment, thereby eliminating bugs and sensitive information issues while maintaining visual interactivity.

Inventive Principle:
Principle #26Copying

Solution Approach 2:

The patent extracts only the necessary visual and structural elements from the web-based system pages, separating the demonstration content from the execution logic. By taking out the runnable code and backend connections and retaining only the static page structures, the system enables demonstrations that do not depend on the reliability of the original web-based system's execution.

Inventive Principle:
Principle #2Taking out (Extraction)

2Adaptability or versatility

If customized demos are created for different users, then adaptability is improved, but device complexity increases due to multiple document edits

Engineering Contradiction:
Improvecustomization capabilityVSAvoidediting complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent merges multiple document edits into a single unified structure by introducing aggregated objects that can be edited once and automatically updated across all pages where they appear. Instead of manually editing each page separately, the system combines common elements (like navigation bars, footers, or repeated UI components) into single editable units that propagate changes throughout the entire demo set, significantly reducing editing complexity while maintaining high adaptability.

Inventive Principle:
Principle #5Merging (Combining)

Solution Approach 2:

The patent creates aggregated objects that serve multiple functions simultaneously - a single aggregated object can represent the same element across different pages and contexts. These universal objects can be edited once and will reflect changes across all instances, allowing one edit operation to serve multiple customization needs across the entire demo system.

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

3Stability of the object's composition

If updates are applied to the same object across multiple documents, then consistency is improved, but productivity decreases due to repeated manual updates

Engineering Contradiction:
Improveobject consistencyVSAvoidediting efficiency
Core Design Contradiction:
Stability of the object's compositionVSProductivity

Solution Approach 1:

The patent combines multiple occurrences of the same object across different pages into a single aggregated object representation. When an editor modifies the aggregated object, the system automatically propagates the update to all pages where the object appears, eliminating the need for repeated manual updates and ensuring consistency across the entire multi-page demo while significantly improving editing efficiency.

Inventive Principle:
Principle #5Merging (Combining)

Data Source

PatentUS20260072652A1Editing of a Multi-Page Demo
Publication Date: 2026.03.12 WALNUT LTD
  • US20260072652A1 patent drawing
  • US20260072652A1 patent drawing
  • US20260072652A1 patent drawing

AI summary

A method, system, apparatus and product for editing a multi-page demo. The multi-page demo includes at least two shallow copies of pages of a web-based system. A multi-page demo editor may create, in response to an operator instruction, an aggregated object that may appear in two or more shallow copies. The aggregated object may be associated with objects in two shallow copies, and customization instructions by the operator provided once with respect to the aggregated object may be applied two or more times on associated objects in the two or more shallow copies. In some cases, the multi-page demo may be updated so as to apply the customization of the aggregated object on a first object in a first shallow copy and on a second object in a second shallow copy.