Component Hierarchy Transfer Between Applications
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Users of software applications often face challenges in obtaining desired functionality due to the unknown functions performed by individual components, requiring a trial and error approach to select and combine components effectively.
Innovation Solution
A method is described that involves associating parent and child components in an executing source application, allowing their outputs and inputs to be connected, enabling the transfer of computer-readable instructions between applications, and presenting document data in a consistent manner across different applications through navigation interfaces.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Productivity
If users manually select and combine components to obtain desired functionality, then functionality can be achieved, but the process requires trial and error and significant time
Solution Approach 1:
The patent applies preliminary action by pre-assembling complete component hierarchies (parent components with their child components) into reusable units. When a user needs functionality, they can directly insert pre-tested component hierarchies rather than manually assembling individual components through trial and error. This preliminary preparation of component structures significantly reduces assembly time and eliminates the need for users to understand internal component relationships.
2Adaptability or versatility
If users transfer individual components between applications, then component reuse is achieved, but users must understand component relationships and connections
Solution Approach 1:
The patent merges parent components and their child components into a single transferable unit called a component hierarchy. This consolidation allows users to transfer complete functional units between applications without needing to understand or manually re-establish the internal relationships between parent and child components. The merged hierarchy maintains all connections internally, simplifying the user operation to a single drag-and-drop action.
Solution Approach 2:
The patent implements copying by creating transferable representations of component hierarchies that can be duplicated and inserted into target applications. When a user drags a parent component to a target application, the system copies the entire component hierarchy including all child components and their connections. This copying mechanism preserves the complete functional structure without requiring users to manually recreate relationships.
3Reliability
If complete component hierarchies are transferred between applications, then functionality is preserved, but the transfer process becomes more complex
Solution Approach 1:
The patent applies self-service by enabling the component hierarchy to carry its own structural information and connection definitions. When a parent component is transferred, it automatically brings with it the definitions of its child components and the relationships between them. The component hierarchy is self-contained and self-describing, eliminating the need for complex external transfer mechanisms to manually map and re-establish connections in the target application.
Data Source
AI summary
Methods, systems, and apparatus, including computer program products, for reusing components from an application are provided. In some implementations, a method includes associating a parent and child component in a source application. The components are used in the presentation of document data during navigation among documents. A navigation interface in an application window of the source application is presented, including presenting document data according to the parent and child components. Input adding the parent component from the source application window to an application window of a target application is received. It is determined that the output of the child component is connected with the input of the parent component, and then computer readable instructions associated with the parent component and the child component are inserted into the target application. A navigation interface is presented in the target application window, including presenting document data according to the parent and child components.