Context Recognition Engine Bypasses Software Integration Overhead
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
The integration of child software applications with parent applications leads to increased loading and unloading times, productivity losses, and potential technical issues due to the need for multiple integrations, resulting in a cumbersome computing environment.
Innovation Solution
A context recognition and activation engine that allows users to access child application functionalities without direct integration with parent applications, enabling the selection and launch of child applications from a separate interface, thereby bypassing the need for multiple integrations and navigation steps.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If child applications are integrated with parent applications using traditional integration methods (COM objects, ODMA, DLL integration), then the functionality of child applications becomes available within the parent application, but the loading time of the parent application increases and productivity decreases
Solution Approach 1:
The patent segments the integration mechanism by introducing a separate integration manager component that independently manages child application integrations. This allows the parent application to load without waiting for child applications, while still providing access to child functionality through the integration manager's interface.
Solution Approach 2:
The integration manager acts as an intermediary between the parent application and child applications. It provides a unified interface for accessing child functionality without requiring direct integration between parent and child, thereby decoupling the loading processes and reducing parent application load time.
2Adaptability or versatility
If multiple child applications are integrated within a parent application, then the capability of the parent application expands, but the interface of the parent application becomes crowded with additional buttons and menu options
Solution Approach 1:
The integration manager provides a universal interface that can access multiple different child applications through a single consistent mechanism. Instead of adding separate buttons and menu options for each child application, the system uses a unified interface that presents child functionality in an organized, non-crowded manner.
3Adaptability or versatility
If child applications are integrated with the parent application, then the functionality is available from within the parent application, but the parent application opens up to potential errors, bugs, and technical issues caused by multiple child applications seeking integration
Solution Approach 1:
The integration manager serves as a centralized intermediary that mediates all interactions between the parent application and child applications. This centralization allows for better control and management of integration relationships, potentially reducing conflicts and technical issues that arise from multiple direct integration points.
Solution Approach 2:
By segmenting the integration management function into a separate integration manager component, the system isolates potential errors and conflicts related to child application integrations from the core parent application logic, thereby improving overall system reliability.
Data Source
AI summary
Systems and methods are disclosed for launching a child application to perform functions on a document created by a parent application without the need for integration of the child application within the parent application. In one implementation, a system detects a child application available for activation by a processor of a computer and determines what functions the child application can perform. The system then determines that the function can operate on an open file, and once the system receives a selection of the function, the system launches the child application and performs the function on the open file. In another implementation, the system determines that the function may operate on a plurality of open files, creates an interface that allows selection of one of the plurality of open files, and launches the child application and performs the function on a selected file.