Transparent Interface Element for Drag-and-Drop Between Host and Embedded Browser

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current software applications that embed other applications do not support drag-and-drop operations between the host and embedded interfaces, limiting the functionality of embedded applications like web browsers within Office applications.

Innovation Solution

A transparent interface element is generated to detect and intercept object manipulation events from the framework application, allowing the embedded application to receive information about repositioned objects and process them appropriately, enabling seamless drag-and-drop operations between the host and embedded interfaces.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If a web browser application interface is hosted within an Office application using a COM add-in, then the web browser functionality is integrated into the Office interface, but drag-and-drop operations between the Office interface and the web browser interface are not supported

Engineering Contradiction:
Improveintegration capabilityVSAvoiddrag-and-drop functionality
Core Design Contradiction:
Adaptability or versatilityVSEase of operation

Solution Approach 1:

The patent introduces a transparent interface element as an intermediary component positioned between the Office application and the embedded web browser. This transparent element intercepts drag-and-drop events from the Office interface and translates them into appropriate actions for the web browser, enabling communication between the two applications without requiring changes to either the Office application or the web browser's native architecture.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Adaptability or versatility

If the embedded application is allowed to exercise full control over its window, then the embedded application maintains its independence and functionality, but object manipulation controls from the framework application cannot be used within the embedded window

Engineering Contradiction:
Improveapplication independenceVSAvoidobject manipulation control
Core Design Contradiction:
Adaptability or versatilityVSEase of operation

Solution Approach 1:

The transparent interface element serves as a mediator that allows the embedded application to maintain full control over its window while still responding to object manipulation controls from the framework application. The transparent element captures events from the framework application and translates them into actions that the embedded application can process, preserving both independence and interoperability.

Inventive Principle:
Principle #24Intermediary (Mediator)

3Adaptability or versatility

If the framework application allocates a smaller window inside the framework for the embedded application, then the embedded application can display its user interface within the framework, but interactions between the two user interfaces are limited

Engineering Contradiction:
Improveembedding capabilityVSAvoidinterface interaction
Core Design Contradiction:
Adaptability or versatilityVSEase of operation

Solution Approach 1:

The transparent interface element enables enhanced interactions between the framework application and the embedded application by acting as a bridge. It allows the framework application to detect and respond to user actions within the embedded window, and vice versa, thereby expanding the interaction capabilities beyond what is normally possible when one application is embedded within another.

Inventive Principle:
Principle #24Intermediary (Mediator)

Data Source

PatentUS10366136B2Method for interacting with a web browser embedded in another software application
Publication Date: 2019.07.30 WOLTERS KLUWER ELM SOLUTIONS INC
  • US10366136B2 patent drawing
  • US10366136B2 patent drawing
  • US10366136B2 patent drawing

AI summary

Systems and methods are provided for manipulating objects in a framework software application that embeds another software application that does not natively support object manipulation controls of the framework software application. To overcome this difficulty, a user interface of the embedded software application is provided in an embedded window disposed within a framework window. Moreover, the user interface of the framework software application is provided in the framework window. Next, a transparent interface element, configured to detect events generated by the object manipulation controls of the framework software application, is generated, and is positioned over the embedded window. When the transparent interface element detects an object repositioning event related to repositioning an object visible from the framework window to the embedded window via the user interface of the framework software application, information related to the repositioned object is provided to the embedded software application.