Add-in UI Component Mapping for Parent Application Compatibility

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Software add-ins face compatibility issues when the user interface of the parent application is modified, leading to the add-in application's functionality being inaccessible to users unless the add-in user interface is updated to match the new layout and design of the parent application.

Innovation Solution

The solution involves adding buttons or controls associated with the add-in application's functionality to the new or modified parent application user interface in a way that is consistent with the parent application's visual and functional properties, while maintaining a prior version of the parent application's user interface in the background to link corresponding components, allowing seamless execution of add-in application functionalities without requiring updates to the add-in application.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If the parent application user interface is modified to update to a new version, then the parent application's functionality and performance are improved, but the add-in application's user interface becomes incompatible and its functionality becomes inaccessible to users

Engineering Contradiction:

Improveparent application interface adaptabilityVSAvoidadd-in application compatibility

Core Design Contradiction:

Adaptability or versatilityVSReliability

Solution Approach 1:

The patent creates a copy of the add-in application's user interface components and maps them to corresponding components in the new parent application interface. This copying mechanism allows the add-in to function with the updated parent application without requiring the add-in itself to be rewritten, resolving the compatibility issue while maintaining the benefits of interface updates

Inventive Principle:

Principle #26Copying

Solution Approach 2:

The patent introduces an intermediary mapping mechanism that translates between the old add-in interface components and the new parent application interface components. This intermediary layer enables communication and functionality transfer between incompatible interfaces, allowing the add-in to adapt to parent application updates without direct modification of the add-in code

Inventive Principle:

Principle #24Intermediary (Mediator)

2Reliability

If the add-in application user interface is updated to match the new parent application interface, then compatibility is maintained, but the add-in application requires additional development work and updates

Engineering Contradiction:

Improveadd-in application compatibilityVSAvoidadd-in application maintenance complexity

Core Design Contradiction:

ReliabilityVSDevice complexity

Solution Approach 1:

Instead of modifying the add-in application code, the patent copies the add-in's user interface components and maps them to the new parent application interface. This approach maintains compatibility without requiring the add-in developer to rewrite or update the add-in application, significantly reducing maintenance complexity

Inventive Principle:

Principle #26Copying

Solution Approach 2:

The patent inverts the traditional approach by not modifying the add-in to match the new interface, but rather creating a mapping from the new interface back to the original add-in components. This inversion eliminates the need for add-in updates while maintaining compatibility

Inventive Principle:

Principle #13The other way round (Inversion)

3Adaptability or versatility

If a mapping mechanism is introduced to link prior user interface components to present user interface components, then add-in functionality remains accessible without updates, but the system complexity increases

Engineering Contradiction:

Improveinterface version flexibilityVSAvoiduser interface system complexity

Core Design Contradiction:

Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent introduces a mapping mechanism as an intermediary that links prior user interface components to present user interface components. This intermediary layer enables the system to support multiple interface versions simultaneously, allowing add-in functionality to remain accessible without requiring updates to the add-in application itself

Inventive Principle:

Principle #24Intermediary (Mediator)

Data Source

PatentUS7886290B2Cross version and cross product user interface

Publication Date: 2011.02.08 MICROSOFT TECHNOLOGY LICENSING LLC

AI summary

When a user interface of a parent software application is modified such that user interface components of an add-in application are not compatible with the parent application user interface, user interface components associated with functionalities of the add-in application are added to the modified parent application user interface. A prior user interface of the parent application to which the add-in application user interface components are added is run in a background of the parent application and is not visible to users. User interface components in the parent application user interface are linked to corresponding add-in application user interface components in the prior user interface. Selection of a user interface component from the present user interface that is associated with an add-in application functionality causes selection of a corresponding user interface component in the background user interface, and the associated add-in functionality is executed.