IDE Tools for Device-Class UI Adaptation
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current integrated development environments (IDEs) lack support for device-independent development of user interface documents, making it difficult to adapt applications for diverse devices and lack visualization of results in target languages like WML or VoiceXML.
Innovation Solution
The system provides a computer-based IDE with device-class dependent tools such as a complexity indicator, device-class dependent page view, and frames layouting view to support authors in generating device-class specific user interface documents, identifying potential issues early and ensuring compatibility across various device classes.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If generic IDE functionality is used for document authoring, then the IDE can support multiple application types, but it lacks specific support for device-independent development and transformation to target languages
Solution Approach 1:
The IDE is segmented into modular plug-ins, with specific plug-ins handling device-independent document authoring, device class detection, and transformation to target languages. This allows the generic IDE framework to maintain versatility while specific modules provide specialized functionality for device-independent development.
Solution Approach 2:
An intermediary transformation layer is introduced between the device-independent document authoring tools and the target language outputs. This intermediary handles the complex transformation logic, supporting multiple target languages (WML, VoiceXML, etc.) without requiring the IDE core to be aware of specific device constraints.
2Adaptability or versatility
If developers manually adapt user interfaces for different delivery contexts, then customization is possible, but the task becomes increasingly difficult with heterogeneous devices
Solution Approach 1:
The system uses a universal device class model that categorizes heterogeneous devices into standardized classes with common characteristics. This universal model allows the IDE to handle multiple device types through a single framework, reducing the complexity of adapting interfaces for each device individually.
Solution Approach 2:
The system automatically adjusts interface parameters based on the detected device class. Instead of manually adapting each interface, the IDE transforms the device-independent document by changing relevant parameters (layout, resolution, input methods) according to the target device class characteristics.
3Reliability
If device-specific adjustments are made after document completion, then device compatibility can be achieved, but development time and effort increase significantly
Solution Approach 1:
The IDE performs preliminary device class detection and compatibility analysis during the document authoring phase, not after completion. The complexity indicator and device class dependent views provide early feedback about potential compatibility issues, allowing authors to make necessary adjustments before finalizing the document.
Solution Approach 2:
The system provides continuous feedback through complexity indicators and device class dependent views that show how the document will be transformed for different device classes. This feedback mechanism allows authors to identify and correct compatibility issues early in the development process.
4Measurement precision
If comprehensive device class analysis is performed, then compatibility issues can be identified early, but the system complexity increases
Solution Approach 1:
The system performs partial device class analysis by focusing on the most critical compatibility aspects through complexity indicators and device class dependent views. Rather than analyzing every possible device parameter, the system concentrates on the most impactful factors that affect document compatibility.
Data Source
AI summary
Integrated development environment IDE (999), method and computer system for developing user interface documents. An editor (104) is used for editing a user interface document. An adaptation engine (105) generates device class specific representations of the user interface document. Each device class specific representation refers to a respective device class. Device class dependent tools (120) of the IDE (999) are used for generating device class specific information and providing it to the author. Device class specific information can be information about the complexity of the user interface by device class provided by a complexity indicator (121), information about how many pages are generated for which device class provided by a device class dependent view (122) or information about the layout for various device classes provided by a frames layouting view (124).