Adapting External Controls to Portal Themes
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Web portal designers face challenges in adapting external controls to match the look-and-feel of a portal theme without disrupting user experience, as external controls often have a different appearance that needs to be harmonized with the portal's uniform design.
Innovation Solution
A method and apparatus that allow designers to preview and adapt external controls by sending requests to the portal to render components with enhanced CSS files, enabling changes to be made without affecting other users, using a runtime engine and add-in components within the development environment like Visual Studio .NET, ensuring only the designer's environment renders the updated styles before deployment.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If external controls are used in portal components, then the control's functionality and customization capability are improved, but the uniform look-and-feel of the portal is compromised
Solution Approach 1:
The patent applies local quality by allowing external controls to have their own specific styling properties while maintaining the overall portal theme. The external controls can be customized with theme-specific styles (colors, fonts, borders) without requiring changes to the control's core functionality or structure. This enables each control to have localized styling adaptations that match the portal theme while preserving the control's inherent capabilities.
Solution Approach 2:
The patent utilizes parameter changes by modifying the visual parameters (CSS properties) of external controls to match the portal theme. The system changes parameters such as color schemes, font families, border styles, and other visual attributes of external controls dynamically based on the selected theme, without altering the control's functional parameters or code structure.
2Ease of operation
If the designer adapts the control's look-and-feel to each theme, then the harmonic user experience is improved, but the user's workflow is interrupted and other users are affected
Solution Approach 1:
The patent applies preliminary action by pre-defining theme-specific style configurations that can be automatically applied to external controls. Instead of requiring the designer to manually adapt each control to every theme, the system provides pre-configured theme styles that can be selectively applied, allowing the designer to preview and deploy harmonious control appearances across multiple themes without repetitive manual adaptation work.
Solution Approach 2:
The patent utilizes copying by creating and storing theme-specific style templates that can be reused across multiple controls and themes. Once a control's look-and-feel is adapted to match a theme, the styling configuration can be copied and applied to other external controls, significantly reducing the time and effort required to maintain harmonic user experience across the entire portal.
3Manufacturing precision
If the designer previews changes before deployment, then the quality of the adaptation is improved, but additional rendering processes are required
Solution Approach 1:
The patent introduces an intermediary preview rendering mechanism that allows designers to visualize theme adaptations before deploying changes to the live portal. This intermediary system renders control previews in the designer's environment using the selected theme's styles, enabling quality verification without affecting the actual portal deployment. The preview function acts as a mediator between the design phase and deployment phase, ensuring adaptation quality while isolating the complexity of theme rendering from the production system.
Data Source
AI summary
A method and apparatus for adapting the looks of an at least one control developed in an environment to a portal developed in a different environment. The apparatus and method enable the preview of a component comprising the control without deploying the changes to the portal, so other users can continue using the component in an uninterrupted manner until deployment.