GB2357168A - Dynamically maintaining the functional module of an application program - Google Patents
Dynamically maintaining the functional module of an application program Download PDFInfo
- Publication number
- GB2357168A GB2357168A GB9929368A GB9929368A GB2357168A GB 2357168 A GB2357168 A GB 2357168A GB 9929368 A GB9929368 A GB 9929368A GB 9929368 A GB9929368 A GB 9929368A GB 2357168 A GB2357168 A GB 2357168A
- Authority
- GB
- United Kingdom
- Prior art keywords
- functional module
- application program
- function
- file
- dynamically maintaining
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Withdrawn
Links
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/40—Transformation of program code
- G06F8/54—Link editing before load time
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/20—Software design
- G06F8/22—Procedural
Abstract
This invention discloses a method for dynamically maintaining the functional module of an application program. When a function of the application program needs to be added. modified or deleted, only the content of a function definition file needs to be modified. including the name, the definition, the corresponding executable file of the functional module, and the names and definitions of its subfunctions. This method makes the application program obtain the functional module needed. The application program thus has certain expandability, and can be easily edited without any other complicated modification and compilation.
Description
2357168 METHOD FOR DYNAIMICALLY MAINTAINING THE FUNCTIONAL MODULE OF AN
APPLICATION PROGRAM The present invention relates to a method for dynamically maintaining the functional module of an application program. which utilizes the computer to edit the original application program and only modifies its function definition file to obtain the function needed.
In current technology, if one wants to change the given functions in a program, such as adding, deleting or modifying the parameters of original functions, the procedure shown in FIG. 1 is often employed. First, the source code 11 of the application program or the C> executable program is read in for corrections by, for example, adding the parameters of a new function or command or deleting and modifying the parameters of a given function or command 10. Then this modified application program needs to be re- compiled to obtain a new executable program 12. This method requires the software programmer to go through complicated editing and compiling processes before finishing the functional expansion or editing of the application program. Therefore, this demands a higher programming and compiling skills on the software developer. When the functions are to be varied very often, those functional parts have to be edited and expanded from time to time. So the cost of developing the software gets higher and the technology for implementing the addition or 0 ZW Z modification of a function is more complicated.
The present invention provides a method for dynamically maintaining the functional module of an application program for implementing the functional expandability of the application program and obtaining an executable file without modifying and compiling the 1) Z> source code of the application program.
Z> Furthermore, the present invention provides a method for editing the functional module of an application program by modifying the function definition file of the original 1 0 - application program (such as a text file, an initialization setting file with an auxiliary filenarne ini, an installation information file with an auxiliary filename inf, a configuration parameter setting file With an auxiliary filenarne efLy. or a program parameter setting file with an auxiliary filename pQp).
The method for dynamically maintaining the functional module of an application program disclosed by this invention uses the computer to proceed the editing for maintaining the original application program. which method comprises the steps of.
obtaining the function definition file of the application program. which is a text file., editing the functional module name of the function with a usual text editor; pointing to the executable file corresponding to the functional module of the above ZP mentioned function and obtamina the executable program needed for this function.
editing and drafting the definitions of the subflinctions according to their functions; and r> storing and closing the function definition file, creating the edited functional module, and creating a linkage between the needed subfunctions and the functional module.
The method for dynamically maintaining the functional module of an application 1 1 program according to the present invention has the following features:
The application program can have certain expandability so that it can provide the functional module needed after modifying or adding a new function.
One only needs to define the above-mentioned new function modification or addition in the function definition file (a text file) of the application program so as to satisfy different needs or provide different effects. The editing method is fairly simple without complicated modification and compilation.
Further scope of applicability of the present invention will become apparent from the detailed description given hereinafter. However, it should be understood that the detailed
0 3 description and specific examples, while indicating preferred embodiments of the invention, are Riven by way of illustration only. 'Since various changes and modifications within the spirit and scope of the invention will become apparent to those skilled in the art from this detailed description.
The present invention will become more fully understood from the detailed description
Riven hereinbelow illustration only, and thus are not limitative of the present invention, and wherein:
FIG. I is a schematic view of editing a functional module in the prior art;
FIG. 2 is a schematic view of the method for dynamically maintaining the functional module of an application program according to the present invention; Z7 FIG. 3) is a flow chart of editing the functional module in the function definition file according to the present invention; FIG. 4 is a detailed flow chart of FIG. 33; FIG. 5 is a structural diagram of the linkage table of the functional module according to the present invention; FIG. 6 is an interface diagram of an embodiment of the invention before adding a new function; and FIG. 7 is an interface diagram of an embodiment of the invention after adding a new function.
Please refer to FIG. 2, which is a schematic view of the method for dynamically maintaining the functional module of an application program according to the present invention. According to the method for dynamically maintaining the functional module of an application program disclosed by the instant invention, the function module is modified 4 bv addinc, statements of the edidng function in the function definition file 20 through relevant messaaes of the functional module, such as the executable file corresponding to the functional module n 22, the editing menu display of the functional module n 22. etc. Then each definition in the function definition fle 20 is analyzed through a public editing and control module 21 so as to link- the functional module n 22 to the application program.
Afterwards, one can perform control and editing processes on the functional module n 22 through the public editing and control module 2 1.
Z Z:1 Please refer to FIG. 3, which is a flow chart of editing the functional module in the function definition File according to the present invention. This diagram shows how one can edit a computer application program. In particular, the editing action can comprises adding a new function. modifying or deleting an original function. This method is applicable to the usual personal computer (PC), a laptop notebook CN13), a handheld personal computer (HPC), and a personal digital assistant (PDA). The method comprises the steps of:
(1).obtaininor the function definition file of the application prograrn (steps 3300-301), wherein the function definition file contains a plurality of function definitions and can be a text file with an auxiliary filenarne txt, an initialization setting file with an auxiliary filenarne ini, an installation information file with an auxiliary filename inf, a configuration 0 parameter setting file with an auxiliary filename cfg, or a program parameter setting file with an auxiliary flename pgp, etc; I (2).editing the functional module name of the function (step 302), which can be directly done with a usual text editor, such as the edit.com under DOS or the notepad.exe under Windows; (3).pointing to the executable file corresponding to the functional module of the above-mentioned function (step 330-33) and obtaining the executable program needed for this function. which can be a program file with an auxiliary flename.exe; (4).editing the definitions of the functional module and assigning the names of the subfunctions included in the functional module (step.3) 04), thaf is, drafting the function definitions according to the needed functions and editing the subfunction names needed if any; (5).editing the definitions of the subfunctions (step 305). that is, drafting the subfunction definitions according to the needed subfunctions in a similar fashion as the previous step; (6).creating the edited functional module 50 and creating the linkage 51 between the subfunctions and the functional module (FIG. 5) (step 306); and (7).storing and closing the function definition file (steps 307-308).
Please refer to FIG. 4, which is a detailed flow chart of FIG. 3. This method utilizes a public editing and control module to analyze the function definition file and adds the functional module into the application program. The analysis procedure is as follows:
(1). obtaining the functional module name from the function definition file (steps 400- 40 1); (2). determining whether the functional module name can be obtained (step 402), and proceeding to the next step if obtainable, otherwise exiting and finishing the CP analysis procedure (step 414); (-3)). reading in the executable file corresponding to the functional module (step 40')); 0 C (4). determining whether the executable file corresponding to the functional module C can be obtained (step 404), and proceeding to the next step if obtainable, otherviise going back to step (1) and analyzing the next functional module; D lt (5). reading in the definition corresponding to the functional module (step 405) such as the graphical interface display; 6 (6). determining whether the definition corresponding to the functional module can be obtained (step 406), and proceeding to the next step if obtainable, otherwise going back to step (1) and analyzing the next functional module.
(7). obtaining the subfunction name according to the subfuriction assioned in the functional module definition (step 407):
(8). determining whether the subfunction name can be obtained (step 408). and proceeding to the next step if obtainable. otherwise going to step (I I) directly:
(9). obtaining the subfunction definition according to the subfunction name (step 409).
(10). determining whether the subfunction definition can be obtained (step 410), and saving the subfunction data (step 411) if obtainable and going to step (7) again to obtain the next subfunction name, otherwise going to step (7) to obtain the next subfanction name; and (11). determining whether there is any subfunction defined in the functional module t after analyzing subfunctions (step 412), and adding the functional module 0 definition and subfunctional module definition into a linkage table (FIG. 5) if there I is, creating the above-mentioned functional module linkage 51 (step 413), and returning to step (1) to analyze the next functional module.
Embodiment The following shows an embodiment of adding a functional module into the original application program. Here lists the program code for reference (the underlined ones consist the new functional module):
[main] (definition of functional module name) item=Board item=Memory item=Video (name of new functional module) 7 [exec] (definition of executable file- of functional module) Board=system.exe Memory=mem.exe Video=intvideo.exe (executable file of new functional module) [Board] (definition of functional module) HelpCtx=The System Board Configuration and Testing, (display message in menu interface of functional module) funid= 100 (function identification of functional module) descript=Sys-B-oard (fanctional module display in menu) item=DMACtrl (definition of subfunction in functional module) item=lntCtrl [DMACtrl] (definition of subfunction in functional module) fiinid=105 (function identification of subfunction in functional module) childs=O (no next level subfunction definition) descript--D-1\4A Controller (subfunction display in menu of functional module) [IntCtrll funid= 106 childs=O descript--I-nterrupt Controller [Memory] HeIpCtx--Memory Configuration and Testing funid=200 descript--M-emory item=BIOSROM )0 item=Parity [BIOSROM] funid=201 childs=O descript=-B-IOS ROM [Parity] funid=202 childs=0 descriptP-arity [Kido] (definition of new functional module) HelpCtx=Videc, Configuration and Testing (display message in menu interface of new functional module) funid=400 (function identification of new functional module) descript--V-ideo (flinctional module display in menu) item=VMemory (definition of subfunction in functional module) item=Attribut lyMemory] (definition of subfunction in functional module) funid=401 (subfunction identification of subfunction in functional module) childs=0 (no next level subfunction definition) descript=Video -M-emory (subfunction display in menu of functional module) LA.ttribut funid=402 childs=0 descriptA-ttribute Referring to FIG. 6 and FIG. 7, which are the interfaces before 60a and after 60b adding a new function, respectively. First, the function required by the functional module is compiled into an executable file (such as the above-mentioned intvideo. exe). The function definition file (such as the above program code) is accordingly modified by adding the definitions of the function and its subfunctions in the new module.
In the embodiment, the original application program has had two functional modules 1 SysBoard 61 and Memory 62. If one wants to add a new functional module such as the Video functional module 633, first the definition of the functional module name ([main]) in the function definition file -should be added with the new functional module name (itern.=Video). Then the definition of the functional module executable file ([exec]) should be added with the setting of the new functional module executable file (Video=intvideo-exe). Subsequently. the definitions of the subfunctions ([ViMemory], [Attribut]) are added into the new functional module definition, such as the program code behind the above [Video]. Finally. the new functional module is moved under the directory of the application program to finish the process of adding a new function to the application program.
The invention being thus described, it will be obvious that the same may be varied in many ways. Such variations are not to be regarded as a departure from the spirit and scope I:D of the invention, and all such modifications as would be obvious to one skilled in the art are intended to be included within the scope of the following claims.
Claims (16)
1. A method for dynamically maintaining the functional module of an application program for adding a functional module to a computer application program. which method comprises the steps of..
obtaining a function definition file of the application program, wherein the function definition file contains a plurality of function definitions; adding the functional module name; CP pointing to an executable file corresponding to the functional module of the function; adding the definition of the functional module and assigning the subfunction C> -P name included in the functional module; adding the definition of the subfanction; creating a linkage table between the function module and the subfunction; and storing and closing the function definition file.
0
2. The method for dynamically maintaining the functional module of an application program of claim 1, wherein the function definition file is a text file.
3 3. The method for dynamically maintaining the functional module of an application program of claim 2, wherein the auxiliary filename of the text file is txt.
4. The method for dynamically maintaining the functional module of an application 1 program of claim 2, wherein the auxiliary filename of the text file is ini.
W
5. The method for dynamically maintaining the functional module of an application program of claim-2-, wherein the auxiliary filename of the text file is cfg.
6. The method for dynamically maintaining the functional module of an application program of claim 2, wherein the auxiliary Filenarrie of the text file is pgp.
7. A method for dynamically maintaining the functional module of an application program substantially as hereinbefore described with reference to and/or substantially as illustrated in anv on of or anv combination of the accompanying drawings.
S. A method for dynamically maintaining the functional module of an application program for editing a computer application program, which method comprises the steps of- obtaining a function definition file of the application program, wherein the M, function definition file contains a plurality of function definitions; editing a functional module name of a function; pointing to an executable file corresponding to the functional module of the I:D function; editing the definition of the functional module and assigning the subfunction name included in the functional module; editing the definition of the subfunction; creating a linkage table between the function module and the subfunction; and storing and closing the function definition file.
9. The method for dynamically maintaining the functional module of an application program of claim 8, wherein the editing means is deletion.
10. The method for dynamically maintaining the functional module of an application I 12 program of claim 8, wherein the editing means is modification.
11. The method for dynamically maintaining the functional module of an application program of claim 8, wherein the function definition file is a text file.
12. The method for dynamically maintaining the functional module of an application program of claim 11, wherein the auxiliary filename of the text file is tXt.
13. The method for dynamicaily maintaining the functional module of an application program of claim 11, wherein the auxiliary filename of the text file is ini.
14. The method for dynamically maintaining the functional module of an application program of claim 11, wherein the auxiliary filename of the text file is cfg.
15. The method for dynamically maintaining the functional module of an application program of claim 11, wherein the auxiliary filename of the text file is pgp.
16. A method for dynamically maintaining the functional module of an application program substantially as hereinbefore described with reference to and/or substantially as illustrated in any on of or any combination of the accompanying drawings.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| GB9929368A GB2357168A (en) | 1999-12-10 | 1999-12-10 | Dynamically maintaining the functional module of an application program |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| GB9929368A GB2357168A (en) | 1999-12-10 | 1999-12-10 | Dynamically maintaining the functional module of an application program |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| GB9929368D0 GB9929368D0 (en) | 2000-02-09 |
| GB2357168A true GB2357168A (en) | 2001-06-13 |
Family
ID=10866168
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| GB9929368A Withdrawn GB2357168A (en) | 1999-12-10 | 1999-12-10 | Dynamically maintaining the functional module of an application program |
Country Status (1)
| Country | Link |
|---|---|
| GB (1) | GB2357168A (en) |
Cited By (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN100388193C (en) * | 2003-08-01 | 2008-05-14 | Kw-软件有限公司 | Online-modification of CIL code program for industrial automation |
| CN100432876C (en) * | 2003-08-28 | 2008-11-12 | 三菱电机株式会社 | Inspecting device and programming tool |
Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| EP0304071A2 (en) * | 1987-08-21 | 1989-02-22 | Wang Laboratories Inc. | Data integration by object management |
| US5226161A (en) * | 1987-08-21 | 1993-07-06 | Wang Laboratories, Inc. | Integration of data between typed data structures by mutual direct invocation between data managers corresponding to data types |
| GB2280289A (en) * | 1993-05-18 | 1995-01-25 | Jr East Japan Information Syst | Method for generating specific program systems and tools to facilitate program system generation |
| EP0722140A1 (en) * | 1994-07-12 | 1996-07-17 | Jr East Japan Information Systems Co., Ltd. | Method of writing program for specific business |
-
1999
- 1999-12-10 GB GB9929368A patent/GB2357168A/en not_active Withdrawn
Patent Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| EP0304071A2 (en) * | 1987-08-21 | 1989-02-22 | Wang Laboratories Inc. | Data integration by object management |
| US5226161A (en) * | 1987-08-21 | 1993-07-06 | Wang Laboratories, Inc. | Integration of data between typed data structures by mutual direct invocation between data managers corresponding to data types |
| GB2280289A (en) * | 1993-05-18 | 1995-01-25 | Jr East Japan Information Syst | Method for generating specific program systems and tools to facilitate program system generation |
| EP0722140A1 (en) * | 1994-07-12 | 1996-07-17 | Jr East Japan Information Systems Co., Ltd. | Method of writing program for specific business |
Non-Patent Citations (2)
| Title |
|---|
| http://www.opussoftware.com/tutorial/TutMakefile.htm 17 October 1998, "The Makefile" * |
| Windows NT (RTM) Help page, "To put a shortcut on the Desktop", 1996 * |
Cited By (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN100388193C (en) * | 2003-08-01 | 2008-05-14 | Kw-软件有限公司 | Online-modification of CIL code program for industrial automation |
| CN100432876C (en) * | 2003-08-28 | 2008-11-12 | 三菱电机株式会社 | Inspecting device and programming tool |
Also Published As
| Publication number | Publication date |
|---|---|
| GB9929368D0 (en) | 2000-02-09 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US6562078B1 (en) | Arrangement and method for inputting non-alphabetic language | |
| US7719535B2 (en) | Method for displaying character strings | |
| US20070245339A1 (en) | Creating documentation screenshots on demand | |
| JP2000003274A (en) | Method for generating text element of editor executable on computer and device therefor and computer-readable storing medium for storing program constituted for generating text element on editor | |
| CN101377738B (en) | Method for implementing page turning of electric document | |
| US20080141241A1 (en) | Method and system for allowing an eclipse feature to create/remove/update program groups and shortcuts, via an eclipse install handler | |
| US7603624B2 (en) | System and method for styling content in a graphical user interface control | |
| US7600199B2 (en) | Task-based interface with underlying extensible framework | |
| KR20080039080A (en) | Terminal having an interfacing function of the heterogeneity language compile library, api calling method and compile function generating method | |
| US6578194B1 (en) | System and method using extended relocation types and operations in relocating operations | |
| US20080082961A1 (en) | Extensibility mechanisms for visual programming | |
| EP1025489B1 (en) | System to associate control with applications using drag and drop interface | |
| GB2357168A (en) | Dynamically maintaining the functional module of an application program | |
| US6321378B1 (en) | Automated code replication during application development | |
| EP0692112B1 (en) | Dynamic browser system | |
| JP3254793B2 (en) | Control method of interactive processing system | |
| JPH0954688A (en) | Gui design supporting method | |
| Parsons et al. | Compiling and Running Java Programs | |
| Bennett et al. | Introducing Objective-C and Xcode | |
| TW452728B (en) | Method for dynamically maintaining function modules of applications | |
| KR100269172B1 (en) | Script file generator for hard disk master manufacturing system | |
| JPH09185499A (en) | Method and device for generating interactive program | |
| Cowell et al. | The Disappearing Memo | |
| Bergmann | Product Reviews | |
| JPH0887416A (en) | Control program generating device |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| WAP | Application withdrawn, taken to be withdrawn or refused ** after publication under section 16(1) |