Widgetizing Web Applications via Definition Files
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing web-based applications cannot be easily converted into widgets that can run on widget engines like Yahoo!® Widgets or Adobe® AIR™, requiring developers to create applications specifically conforming to these engines, which limits platform independence and increases development complexity.
Innovation Solution
A method and system that automatically converts a web-based application into a widget by generating a definition file and using a widgetizer to expose the application to a widget engine, allowing existing applications to be used as desktop widgets without requiring specific development for each engine, using a platform-independent language like Java™ and configuring the application to produce XML or xBCML output for rendering by the widget engine.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If a web-based application is converted into a widget by generating a definition file and using a widgetizer, then platform independence is improved and development complexity is reduced, but the application must be configured to produce specific output formats (XML or xBCML) for rendering by the widget engine
Solution Approach 1:
The patent introduces a widgetizer as an intermediary component that converts web-based applications into widget format. The widgetizer acts as a mediator between the existing application and the widget engine, generating definition files that bridge the gap between standard web applications and engine-specific requirements, thereby achieving platform independence without requiring developers to learn multiple engine-specific frameworks
Solution Approach 2:
The patent creates a universal widgetizer that can handle multiple widget engines (Yahoo! Widgets, Adobe AIR, etc.) through a single platform-independent language interface. This universal converter allows applications written in standard languages like Java to be adapted to different widget engines without requiring separate development for each engine, thus reducing development complexity while maintaining versatility
2Reliability
If developers create applications specifically conforming to widget engine requirements, then compatibility with the engine is improved, but platform independence deteriorates and development complexity increases
Solution Approach 1:
The patent segments the widget development process into two independent parts: the web-based application (written in platform-independent language like Java) and the widget engine (with its proprietary rendering capabilities). The widgetizer serves as a translation layer that segments the compatibility requirement from the application logic, allowing the application to remain platform-independent while the engine-specific rendering is handled separately by the widgetizer
Solution Approach 2:
The widgetizer serves as an intermediary that translates between platform-independent application code and engine-specific rendering requirements. Instead of developers directly coding for specific engines, the widgetizer mediates this translation, ensuring engine compatibility while preserving platform independence of the original application
3Measurement precision
If developers manually retrieve and extract information from reports, then accuracy of data extraction is improved, but time consumption increases and productivity decreases
Solution Approach 1:
The patent implements self-service by allowing the widget to automatically retrieve and display information from the backend system without requiring manual user intervention. The widget periodically pulls data from the server and updates the display automatically, eliminating the need for users to manually retrieve reports and extract data points, thus significantly improving productivity while maintaining accurate data presentation
Data Source
AI summary
Method and system for widgetizing a web-based application are provided. An example system comprises a widgetizer trigger and a definition module. The widgetizer trigger may be configured to receive at a server computer system, from a web browser application running at a client computer system, a request to widgetize a web-based computer application to permit the computer application to be run as a desktop widget at the client computer system. The definition module may be configured to provide to the client computer application, in response to the request to widgetize, a definition file associated with the computer application, the definition file comprising a reference link to the computer application, the reference link including one or more parameters, the one or more parameters to instruct the computer application to generate output in a format suitable for use by a widget engine provided at the client computer system.