Dynamic Driver Program Generation via UI Definition Segmentation
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Conventional methods for generating printer driver programs require manufacturers to pre-prepare new versions for image forming apparatuses with changed functions, limiting user flexibility and efficiency, as users cannot modify control programs.
Innovation Solution
A driver program generating apparatus that accesses a definition database to change UI and command definition data, allowing users to generate new driver programs by associating UI and command data based on user input, reducing unnecessary determination processes and improving adaptability to function changes.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If a control program of a new version is prepared in advance by the manufacturer, then the driver program can respond to the image forming apparatus, but the user cannot change the control program and the manufacturer must generate a new version whenever the function changes
Solution Approach 1:
The driver program is segmented into a control program and UI definition data. The UI definition data is stored separately in a database, allowing users to modify only the UI definitions without changing the core control program. This segmentation enables users to adapt the driver to different functions while maintaining the original control logic.
Solution Approach 2:
The system transitions from a static driver program to a dynamic one where UI definition data can be changed according to user needs. The driver program dynamically loads UI definitions from the database based on the image forming apparatus model, allowing real-time adaptation without regenerating the entire driver.
2Reliability
If the manufacturer generates a control program of a new version whenever the function changes, then the driver program corresponds to the added function, but it requires unnecessary determination processes and increases complexity
Solution Approach 1:
Instead of creating entirely new driver programs for each function change, the system copies the existing control program and combines it with different UI definition data from the database. This allows multiple driver versions to be generated from a single control program by simply changing the UI definitions.
Solution Approach 2:
The system changes the parameter of UI definition data rather than regenerating the entire control program. By modifying the UI definition parameters (display commands, setting values) while keeping the control program unchanged, the system achieves function adaptation with minimal complexity.
3Manufacturing precision
If a driver program is generated for each model with different functions, then the driver responds correctly to the image forming apparatus, but the user cannot easily adapt to function changes
Solution Approach 1:
The control program is designed with universality to work with multiple image forming apparatus models. The same control program can serve different models by combining it with appropriate UI definition data from the database, eliminating the need for model-specific control programs.
Data Source
AI summary
A server includes a non-transitory computer readable storage medium and a processor. The computer readable storage medium stores UI definition data, command definition data, and first and second association information. The processor obtains a driver program and generates a correction program. The correction program is generated by changing the UI definition data and the command definition data included in the driver program.