File Type Association with Web-Based Applications
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current computing systems lack an intuitive method for users to view local files using Web-based applications when the necessary application is not locally installed, requiring users to manually open a Web browser and upload files.
Innovation Solution
A system that allows users to associate file types with Web-based applications, enabling automatic launching of Web applications by using a launching engine that detects file selections and directs the user to corresponding Web sites for viewing, with options for local or Web-based handling and user-configurable preferences.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If users manually open a Web browser and upload files to view in Web-based applications, then the system can provide remote functionality, but the ease of operation deteriorates due to multiple manual steps
Solution Approach 1:
The system performs preliminary action by pre-configuring file type associations with Web-based applications before the user needs to view a file. When a user double-clicks a file, the association table is consulted and the Web application is automatically launched with the file already uploaded and loaded, eliminating the need for manual browser navigation and upload steps.
Solution Approach 2:
The system enables self-service by allowing the file association mechanism to automatically determine and launch the appropriate Web-based application without user intervention. The launching engine self-determines which Web application should handle the file type and initiates the process automatically, making the system serve itself rather than requiring manual user guidance through multiple steps.
2Ease of operation
If the system automatically determines and launches Web-based applications based on file associations, then the ease of operation improves, but the device complexity increases due to additional association tables and launching engines
Solution Approach 1:
The association table structure is designed with universality by maintaining multiple sets of associations (local applications, Web-based applications, and their corresponding URLs) within a single integrated framework. The launching engine serves multiple functions by handling both local and remote application launches through the same mechanism, reducing overall system complexity despite the expanded functionality.
Solution Approach 2:
The launching engine acts as an intermediary component that mediates between the file association table and the actual application launch process. It consults the association table, determines the appropriate Web application, and initiates the launch sequence, thereby simplifying the interaction between various system components and reducing the apparent complexity of the automatic launching mechanism.
3Adaptability or versatility
If different sets of file associations are maintained for local and Web-based applications, then the adaptability improves, but the device complexity increases due to multiple association tables
Solution Approach 1:
The association table is segmented into different sections or sets that separately store local application associations and Web-based application associations. This segmentation allows the system to maintain distinct association rules for different application types while organizing them in a structured manner that the launching engine can systematically consult during file opening operations.
Solution Approach 2:
The association table structure is designed dynamically, allowing the system to flexibly consult different association sets based on the file type and user configuration. The launching engine can adaptively select which association table entries to consult (local first, Web-based first, or both) based on configurable preferences, providing adaptability without requiring rigid multiple separate tables.
Data Source
AI summary
The present invention discloses a launching engine configured to automatically launch a Web site and load an electronic document responsive to a launching event for the electronic document. The launching engine can be a component of a computer operating system (e.g., MAC OS, OS/2, WINDOWS XP, etc.) or a graphics management component (e.g., KDE, GNOME, etc.) of a computer. A launching event can be initiated by user selection of a document icon, a user selection of an electronic document from a file management application, a launching script for the electronic document triggered by a media insertion action, and the like.