Runtime Widget Transfer Across Browser Containers

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current Web technologies restrict the transfer of widgets across different containers at runtime, limiting user interaction and convenience, as users cannot move rendered widgets from one Web browser instance to another without re-adding and re-configuring them.

Innovation Solution

A method and system that detects and responds to user indications to transfer widgets across different widget containers using cross-container data delivery mechanisms, such as HTML5, allowing widgets to be moved and hosted by different containers while maintaining data and state consistency.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Ease of operation

If widgets are transferred across different containers at runtime, then user convenience and flexibility are improved, but system complexity increases due to cross-container data delivery requirements

Engineering Contradiction:
Improveuser convenienceVSAvoidsystem complexity
Core Design Contradiction:
Ease of operationVSDevice complexity

Solution Approach 1:

The patent introduces a data delivery mechanism (HTML5) as an intermediary to enable communication and data transfer between different widget containers. This mediator handles the complexity of cross-container data delivery, allowing widgets to be transferred seamlessly while isolating the complexity from the user interface layer.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The system separates widget management into independent container units, each capable of hosting and managing widgets autonomously. This segmentation allows widgets to be transferred between containers without requiring system-wide changes, reducing overall system complexity while enabling flexible runtime transfers.

Inventive Principle:
Principle #1Segmentation

2Adaptability or versatility

If drag-and-drop operations are enabled across containers, then user interaction flexibility is improved, but data consistency challenges increase

Engineering Contradiction:
Improveuser interaction flexibilityVSAvoiddata consistency
Core Design Contradiction:
Adaptability or versatilityVSReliability

Solution Approach 1:

The patent implements feedback mechanisms through the data delivery system that monitor and ensure data consistency during widget transfers. The system provides feedback loops that verify data integrity between source and destination containers, maintaining reliability while enabling flexible drag-and-drop operations across containers.

Inventive Principle:
Principle #23Feedback

3Adaptability or versatility

If widgets are transferred between different browser instances, then reusability is improved, but transfer capability requirements worsen due to cross-instance communication needs

Engineering Contradiction:
Improvewidget reusabilityVSAvoidtransfer capability
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent implements a universal data delivery mechanism (HTML5) that enables widgets to be transferred across different container types and browser instances. This universal approach allows the same widget to be reused in multiple contexts without requiring instance-specific transfer implementations, improving reusability while standardizing transfer capabilities.

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

Data Source

PatentUS10050845B2Enabling transfer of widgets across containers at runtime
Publication Date: 2018.08.14 INTERNATIONAL BUSINESS MACHINE CORPORATION
  • US10050845B2 patent drawing
  • US10050845B2 patent drawing
  • US10050845B2 patent drawing

AI summary

A method and system for enabling transfer of widgets across containers at runtime. According to embodiments of the present invention, a user is allowed to transfer a widget across containers at runtime, for example, moving a widget that has been deployed and operated in one widget container to another, even though the destination widget container originally does not support the widget. Specifically, the widget being transferred can keep consistency in terms of data and state before and after the transfer. Furthermore, the user can implement the cross-container transfer of widgets at runtime by, for example, convenient interaction means like a drag-and-drop operation. In this way, the user can operate and interact with Web applications in a more convenient and flexible way.