Description:BACKGROUND
Field of Invention
[001] Embodiments of the present invention generally relate to a system for managing files and particularly to a system for managing file extensions.
Description of Related Art
[002] Traditional methods of managing files face significant hurdles when it comes to handling large volumes and diverse types of file extensions in modern computing environments. These challenges manifest in form of compatibility issues and inefficiencies within existing file management systems. As technology advances, a proliferation of various file formats further complicates the organization, categorization, and retrieval of data. Users often experience frustration due to a lack of a cohesive and streamlined approach to managing files with diverse extensions. This frustration not only impacts user experience but also hampers productivity by creating obstacles in accessing and working with the required information efficiently.
[003] Additionally, within these modern computing environments, a notable challenge arises from the fact that uploaded files, in particular, often lack compatibility or convertibility between different extensions. Unlike many other file types that can be easily converted or manipulated, uploaded files retain their specific extensions and formats, making it difficult to seamlessly integrate or convert them into different formats without potential loss or corruption of critical data or functionalities. This lack of convertibility adds another layer of complexity to the already intricate landscape of file management and exacerbates difficulties in achieving a unified and efficient system for organizing and manipulating files across various extensions.
[004] There is thus a need for an improved and advanced system for managing file extensions that can administer the aforementioned limitations in a more efficient manner.
SUMMARY
[005] Embodiments in accordance with the present invention provide a system for managing file extensions. The system comprising: a user interface to enable a user to upload a file using a user device. The system further comprising: a processor located on an application server, and in communication with the user device. The processor is configured to: detect an extension of the uploaded file; recognize a type of the file based on the detected extension; search for a program string upon recognizing the type of the uploaded file as a programming file; deduce a programming language of the program string of the uploaded file; convert the program string of the uploaded file based on a user selected extension by employing an artificial intelligence algorithm; convert the detected extension of the uploaded file into the user selected extension, and store, or share the converted uploaded file in a storage medium or on the user device.
[006] Embodiments in accordance with the present invention further provide a method for managing file extensions. The method comprising steps of: detecting an extension of an uploaded file; recognizing a type of the file based on the detected extension; searching for a program string upon recognizing the type of the uploaded file as a programming file; deducing a programming language of the program string of the uploaded file; converting the program string of the uploaded file based on a user selected extension by employing an artificial intelligence algorithm; converting the detected extension of the uploaded file into the user selected extension, and storing, or sharing the converted uploaded file in a storage medium or on a user device.
[007] Embodiments of the present invention may provide a number of advantages depending on their particular configuration. First, embodiments of the present application may provide a system for managing file extensions.
[008] Next, embodiments of the present application may provide a system for managing file extensions that is backward and forward-compatible.
[009] Next, embodiments of the present application may provide a system for managing file extensions that is user-friendly.
[0010] Next, embodiments of the present application may provide a system for managing file extensions that are operative on cross-platform operating systems.
[0011] These and other advantages will be apparent from the present application of the embodiments described herein.
[0012] The preceding is a simplified summary to provide an understanding of some embodiments of the present invention. This summary is neither an extensive nor exhaustive overview of the present invention and its various embodiments. The summary presents selected concepts of the embodiments of the present invention in a simplified form as an introduction to the more detailed description presented below. As will be appreciated, other embodiments of the present invention are possible utilizing, alone or in combination, one or more of the features set forth above or described in detail below.
BRIEF DESCRIPTION OF THE DRAWINGS
[0013] The above and still further features and advantages of embodiments of the present invention will become apparent upon consideration of the following detailed description of embodiments thereof, especially when taken in conjunction with the accompanying drawings, and wherein:
[0014] FIG. 1 illustrates a block diagram of a system for managing file extensions, according to an embodiment of the present invention; and
[0015] FIG. 2 depicts a flowchart of a method for managing file extensions, according to an embodiment of the present invention.
[0016] The headings used herein are for organizational purposes only and are not meant to be used to limit the scope of the description or the claims. As used throughout this application, the word "may" is used in a permissive sense (i.e., meaning having the potential to), rather than the mandatory sense (i.e., meaning must). Similarly, the words “include”, “including”, and “includes” mean including but not limited to. To facilitate understanding, like reference numerals have been used, where possible, to designate like elements common to the figures. Optional portions of the figures may be illustrated using dashed or dotted lines, unless the context of usage indicates otherwise.
DETAILED DESCRIPTION
[0017] The following description includes the preferred best mode of one embodiment of the present invention. It will be clear from this description of the invention that the invention is not limited to these illustrated embodiments but that the invention also includes a variety of modifications and embodiments thereto. Therefore, the present description should be seen as illustrative and not limiting. While the invention is susceptible to various modifications and alternative constructions, it should be understood, that there is no intention to limit the invention to the specific form disclosed, but, on the contrary, the invention is to cover all modifications, alternative constructions, and equivalents falling within the scope of the invention as defined in the claims.
[0018] In any embodiment described herein, the open-ended terms "comprising", "comprises”, and the like (which are synonymous with "including", "having” and "characterized by") may be replaced by the respective partially closed phrases "consisting essentially of", “consists essentially of", and the like or the respective closed phrases "consisting of", "consists of”, the like.
[0019] As used herein, the singular forms “a”, “an”, and “the” designate both the singular and the plural, unless expressly stated to designate the singular only.
[0020] FIG. 1 illustrates a block diagram of a system 100 for managing file extensions, according to an embodiment of the present invention.
[0021] According to embodiments of the present invention, the system 100 may comprise a user device 102, a user interface 104, an application server 106, a processor 108, and a storage medium 110.
[0022] In an embodiment of the present invention, the user device 102 may be a device that may enable a user to upload a file into the system 100 using the interface. According to embodiments of the present invention, the user device 102 may be, but not limited to, a computer, a laptop, a tablet, a smartphone, and so forth. Embodiments of the present invention are intended to include or otherwise cover any type of the user device 102, including known, related art, and/or later developed technologies.
[0023] In an embodiment of the present invention, the processor 108 may be located on the application server 106. In an embodiment of the present invention, the application server 106 may be a hardware on which the processor 108 may be installed. According to embodiments of the present invention, the application server 106 may be, but not limited to, a motherboard, a wired board, a mainframe, and so forth. Embodiments of the present invention are intended to include or otherwise cover any type of the application server 106, including known, related art, and/or later developed technologies.
[0024] The processor 108 may be configured to be in communication with the user device 102, in an embodiment of the present invention.
[0025] In an embodiment of the present invention, the processor 108 may be configured to detect an extension of the uploaded file. According to embodiments of the present invention, the extension of the uploaded file may be, but not limited to, .c file extension, a .cpp file extension, a .java file extension, a .apk file extension, a .iOS file extension, a .py file extension, and so forth. Embodiments of the present invention are intended to include or otherwise cover any extension of the uploaded file, including known, related art, and/or later developed technologies.
[0026] In an embodiment of the present invention, the processor 108 may be configured to recognize a type of the uploaded file based on the detected extension. If the type of the file may not be recognized as a programming file, then the processor 108 may return an error. Else, the processor 108 may be configured to search for a program string upon recognizing the type of the file as the uploaded file.
[0027] In an embodiment of the present invention, the processor 108 may be configured to deduce a programming language of the program string of the uploaded file. According to embodiments of the present invention, the programming language may be, but not limited to, a C programming language, a C++ programming language, a C# programming language, a Python programming language, a Java programming language, a Swift programming language, and so forth. Embodiments of the present invention are intended to include or otherwise cover any type of the programming language, including known, related art, and/or later developed technologies.
[0028] In an embodiment of the present invention, the processor 108 may be configured to convert the program string of the uploaded file based on a user selected extension by employing an artificial intelligence algorithm.
[0029] In an embodiment of the present invention, the processor 108 may be configured to convert the detected extension of the uploaded file into the user selected extension.
[0030] In an embodiment of the present invention, the processor 108 may be configured to store or share the converted uploaded file in the storage medium or on the user device 102. The storage medium 110 may be a non-transitory storage medium, in an embodiment of the present invention. According to embodiments of the present invention, the storage medium 110 may be, but not limited to, a Random-Access Memory (RAM), a Static Random-access Memory (SRAM), a Dynamic Random-access Memory (DRAM), a Read Only Memory (ROM), an Erasable Programmable Read-only Memory (EPROM), an Electrically Erasable Programmable Read-only Memory (EEPROM), a NAND Flash, a Secure Digital (SD) memory, a cache memory, a Hard Disk Drive (HDD), a Solid-State Drive (SSD) and so forth. Embodiments of the present invention are intended to include or otherwise cover any type of the storage medium 110, including known, related art, and/or later developed technologies.
[0031] In an embodiment of the present invention, the processor 108 may be configured to execute the converted uploaded file using a compiler and provide an output of the converted uploaded file on the user device 102. According to embodiments of the present invention, the compiler may be, but not limited to, Just-In-Time (JIT) Compiler, a Single-Pass Compiler (SPC), a Multi-Pass Compiler (MPC), an Ahead-of-Time (AOT) Compiler, a Binary Compilation (BC), and so forth. Embodiments of the present invention are intended to include or otherwise cover any type of the compiler, including known, related art, and/or later developed technologies.
[0032] In an embodiment of the present invention, the processor 108 may be configured to compare the content of the uploaded file and the content of the converted uploaded file. The differences in the content of the uploaded file and the content of the converted uploaded file may be displayed to the user on the user device 102, in an embodiment of the present invention.
[0033] In an exemplary embodiment of the present invention, the user may upload the uploaded file of the Python programming language to the system 100. The uploaded file of the Python programming language may have the program string tallying to the Python programming language and the .py file extension. Further, the user may instruct the system 100 to convert the uploaded file of the Python programming language, for example to the Java programming language.
[0034] The system 100 may employ the artificial intelligence algorithm for conversation of the uploaded file of the Python programming language to the uploaded file of the Java programming language, such that an output that may be produced by the uploaded file of the Python programming may remain consistent in the uploaded file of the Java programming. The system 100 may further display changes made in the content of the uploaded file of the Python programming for generation of the uploaded file of the Java programming.
[0035] FIG. 2 depicts a flowchart of a method 200 for managing file extensions using the system 100, according to an embodiment of the present invention.
[0036] At step 202, the system 100 may detect the extension of the uploaded file.
[0037] At step 204, the system 100 may recognize the type of the file based on the detected extension. If the type of the file may be recognized as the programming file, then the method 200 may proceed to a step 206. Else, the method 200 may continue a step 214.
[0038] At step 206, the system 100 may search for the program string in the uploaded file. If the program string is in the uploaded file, then the method may proceed to a step 208. Else, the method 200 may continue a step 214.
[0039] At step 208, the system 100 may deduce the programming language of the program string of the uploaded file.
[0040] At step 210, the system 100 may convert the program string of the uploaded file based on the user selected extension by employing the artificial intelligence algorithm.
[0041] At step 212, the system 100 may convert the detected extension of the file into the user selected extension.
[0042] At step 214, the system 100 may store, or share the converted file in the storage medium 110 or on the user device 102.
[0043] While the invention has been described in connection with what is presently considered to be the most practical and various embodiments, it is to be understood that the invention is not to be limited to the disclosed embodiments, but on the contrary, is intended to cover various modifications and equivalent arrangements included within the scope of the appended claims.
[0044] This written description uses examples to disclose the invention, including the best mode, and also to enable any person skilled in the art to practice the invention, including making and using any devices or systems and performing any incorporated methods. The patentable scope of the invention is defined in the claims and may include other examples that occur to those skilled in the art. Such other examples are intended to be within the scope of the claims if they have structural elements that do not differ from the literal language of the claims, or if they include equivalent structural elements within substantial differences from the literal languages of the claims. , Claims:CLAIMS
I/We Claim:
1. A system (100) for managing file extensions, the system (100) comprising:
a user interface (104) to enable a user to upload a file using a user device (102);
a processor (108) located on an application server (106), and in communication with the user device (102), characterized in that the processor (108) is configured to:
detect an extension of the uploaded file;
recognize a type of the file based on the detected extension;
search for a program string upon recognizing the type of the uploaded file as a programming file;
deduce a programming language of the program string of the uploaded file;
convert the program string of the uploaded file based on a user selected extension by employing an artificial intelligence algorithm;
convert the detected extension of the uploaded file into the user selected extension, and
store, or share the converted uploaded file in a storage medium (110) or on the user device (102).
2. The system (100) as claimed in claim 1, wherein the processor (108) is configured to execute the converted uploaded file using a compiler, and provide an output of the converted uploaded file on the user device (102).
3. The system (100) as claimed in claim 1, wherein the processor (108) is configured to compare the content of the uploaded file and the content of the converted uploaded file.
4. The system (100) as claimed in claim 3, wherein differences in the content of the uploaded file and the content of the converted uploaded file are displayed to the user on the user device (102).
5. The system (100) as claimed in claim 1, wherein the compiler is selected from a Just-In-Time (JIT) Compiler, a Single-Pass Compiler (SPC), a Multi-Pass Compiler (MPC), an Ahead-of-Time (AOT) Compiler, a Binary Compilation (BC), or a combination thereof.
6. The system (100) as claimed in claim 1, wherein the extension of the uploaded file is selected from a .c file extension, a .cpp file extension, a .java file extension, a .apk file extension, a .iOS file extension, a .py file extension, or a combination thereof.
7. The system (100) as claimed in claim 1, wherein the user device (102) is a computer, a laptop, a tablet, a smartphone, or a combination thereof.
8. A method (200) for managing file extensions, the method (200) characterised by steps of:
detecting an extension of an uploaded file;
recognizing a type of the file based on the detected extension;
searching for a program string upon recognizing the type of the uploaded file as a programming file;
deducing a programming language of the program string of the uploaded file;
converting the program string of the uploaded file based on a user selected extension by employing an artificial intelligence algorithm;
converting the detected extension of the uploaded file into the user selected extension, and
storing, or sharing the converted uploaded file in a storage medium (110) or on a user device (102).
9. The method (200) as claimed in claim 8, wherein the user device (102) is a computer, a laptop, a tablet, a smartphone, or a combination thereof.
10. The method (200) as claimed in claim 8, wherein the extension of the uploaded file is selected from a .c file extension, a .cpp file extension, a .java file extension, a .apk file extension, a .iOS file extension, a .py file extension, or a combination thereof.
Date: November 23, 2023
Place: Noida

Dr. Keerti Gupta
Agent for the Applicant
(IN/PA-1529)