Prototype Controller Input Event Routing for GUI Testing
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Conventional GUI prototyping methods often fail to accurately communicate designer intentions to developers, leading to discrepancies between the intended design and the final prototype, and require significant rework, especially when updating specific parts of an existing application, necessitating a method to test prototypes linked with applications without developer assistance.
Innovation Solution
A method that activates a prototype controller on a user terminal to receive and send input events with top priority, allowing the prototype to be displayed as a layer above the application, enabling user manipulation and sensor input feedback without rebuilding the application, and allowing for seamless integration and testing of updated GUI elements with existing applications.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Ease of operation
If a prototype is displayed as a layer above the application with top priority input event reception, then user manipulation and sensor input feedback are enabled without rebuilding the application, but input events may be intercepted before reaching the underlying application
Solution Approach 1:
The patent introduces a prototype controller as an intermediary component that manages input event routing between the prototype layer and the underlying application. The controller receives input events, determines whether they are intended for the prototype or the application, and routes them accordingly. This mediator approach enables the prototype to be tested with full input event access while preventing unwanted interception, as the controller intelligently directs events to the appropriate target based on the current interaction state.
2Productivity
If the prototype controller receives input events with top priority, then seamless prototype testing is achieved, but the underlying application may not receive intended input events
Solution Approach 1:
The patent implements dynamic input event routing where the prototype controller adjusts its priority level and event reception behavior based on the current operational state. When the prototype is active and needs testing, the controller receives input events with top priority. When the prototype is inactive or when certain conditions are met, the controller allows events to pass through to the underlying application. This dynamic adjustment ensures both high prototype testing efficiency and reliable application input reception as needed.
3Adaptability or versatility
If a prototype is stacked as a layer higher than the application, then transparent stacking and seamless integration are achieved, but the application structure becomes more complex
Solution Approach 1:
The patent segments the user interface into distinct functional layers: the application layer and the prototype layer, with the prototype controller managing the prototype layer. This segmentation allows the prototype to be stacked as a separate layer higher than the application, enabling transparent stacking and seamless integration. The prototype controller handles the complexity of layered structure management, while the application maintains its original structure, thus achieving adaptability without permanently increasing application complexity.
Data Source
AI summary
Provided is a method of testing a prototype linked with an application without rebuilding the application. The method is performed by a user terminal in which the application is installed and comprises activating the application built to comprise a prototype controller, loading the prototype and setting the prototype to be displayed on a prototype area, which is at least part of a prototype controller area allocated to the prototype controller, in a screen of the application by using the prototype controller, receiving at least some of input events generated for the application with top priority by using the prototype controller and sending the received input events to the application as they are or sending the received input events to the loaded prototype by using the prototype controller.


