Visual Component Layout Input via Tag-Based Markup
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Traditional application development processes limit the ability of artists/designers to directly affect the appearance of visual components, as they rely on programmers to handle both logic and visual asset placement, resulting in a lack of artistic expression and a frustrating iterative process.
Innovation Solution
A system that allows artists to describe the positional relationships of visual assets using a tag-based language, enabling non-programmers to directly modify the layout, and allowing developers to write script for layout definition, allowing both groups to contribute to the design.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Ease of operation
If developers use code to define both logic and visual asset placement, then the application functionality is complete, but artists/designers cannot directly modify the appearance and layout
Solution Approach 1:
The patent segments the visual asset placement definition from the logic code by introducing a separate markup language (XML) format. Visual assets are defined in markup files while logic remains in code files, allowing artists to edit visual components without affecting logic and developers to maintain functional integrity. This resolution allows artists to directly modify appearance while keeping the system architecture clean and maintainable.
Solution Approach 2:
The patent introduces a markup language (XML) as an intermediary between the visual design requirements and the underlying code implementation. This intermediary format serves as a bridge that artists can use to define visual asset placement without needing to understand programming logic, while developers can still access and manipulate these definitions through the structured markup format.
2Productivity
If artists mock up appearance and programmers implement it, then artistic vision can be expressed, but the process becomes frustrating and iterative
Solution Approach 1:
By segmenting visual asset definitions into a separate markup language format, the patent enables artists to directly create and modify visual components without requiring programmer intervention for each change. This eliminates the iterative back-and-forth between artists and developers, significantly reducing revision time and accelerating the visual component development process.
Solution Approach 2:
The patent empowers artists to self-service the visual asset placement task by providing them with a dedicated markup language interface. Artists can independently define, modify, and adjust visual components using the markup format without needing to request changes from developers, thereby eliminating wait time and iterative revisions while maintaining design quality.
3Adaptability or versatility
If developers handle all visual asset placement through code, then logical consistency is maintained, but artistic expression is limited
Solution Approach 1:
The patent segments the visual definition system from the logic system, allowing artists to express creative vision through markup language while developers maintain logical consistency through code. This segmentation enables both artistic expression and logical consistency to coexist by giving each group appropriate tools for their specific needs without compromising the other.
Solution Approach 2:
The patent creates a universal markup language format that serves multiple functions: it enables artistic expression for visual asset placement, maintains logical consistency through structured formatting, and provides a bridge between artistic design and technical implementation. This multi-functional markup system resolves the contradiction by being adaptable to both artistic and logical requirements.
Data Source
AI summary
A system, method, and computer program product for creating a visual component in an application include a first functional unit operable to receive first input specifying logic functions of the visual component, a second functional unit operable to receive second input defining one or more visual assets to be included in a layout of the visual component, and a third functional unit operable to receive third input in alternate forms, said third input specifying one or more layouts of the visual component. The alternate forms may include tag input and script input.