EP1490791A2 - Universal script editor - Google Patents

Universal script editor

Info

Publication number
EP1490791A2
EP1490791A2 EP03716980A EP03716980A EP1490791A2 EP 1490791 A2 EP1490791 A2 EP 1490791A2 EP 03716980 A EP03716980 A EP 03716980A EP 03716980 A EP03716980 A EP 03716980A EP 1490791 A2 EP1490791 A2 EP 1490791A2
Authority
EP
European Patent Office
Prior art keywords
editor
script
module
menu
scripts
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.)
Ceased
Application number
EP03716980A
Other languages
German (de)
French (fr)
Inventor
Randy W. Hostettler
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Honeywell International Inc
Original Assignee
Honeywell International Inc
Priority date (The priority date 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 date listed.)
Filing date
Publication date
Application filed by Honeywell International Inc filed Critical Honeywell International Inc
Publication of EP1490791A2 publication Critical patent/EP1490791A2/en
Ceased legal-status Critical Current

Links

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F8/00—Arrangements for software engineering
    • G06F8/30—Creation or generation of source code
    • G06F8/33—Intelligent editors

Definitions

  • the present invention is generally directed to a script editor and, more specifically, to a universal script editor for creating scripts with arbitrary syntax.
  • script interpreter/script compiler engine which takes a set of textual script command/data structures and interprets/compiles the commands/data structures and provides appropriate processing of the commands/data.
  • a personal computer (PC) with a 1553 card may have a script interpreter engine that takes a file of commands and converts the commands into 1553 I/O messages, data comparisons and pass/fail checks, thereby, controlling and monitoring a system under test.
  • Tool command language (TCL) is one such script interpreter engine that has been used for controlling and monitoring a system under test.
  • the present invention is generally directed to a universal script editor for creating scripts with arbitrary syntax.
  • the universal script editor includes a read module for reading in one or more configuration files and an editor module that is in communication with the read module.
  • a configuration file includes a definition of a menu structure with associated menu items and at least one of a location/name of a file containing a script command structure and a self-contained script command structure.
  • the read module sets up one or more menu systems, which support editing functions for building scripts for a current project, based upon the configuration file associated with each file type being edited.
  • the editor module supports a plurality of editor capabilities, which are utilized to build current project scripts.
  • the universal script editor also includes a miscellaneous support module that provides additional editor capabilities, which may include keyword highlighting, automatic indentation and outline viewing.
  • the editing functions may include cutting, pasting, font selection, page numbering and column numbering.
  • FIG. 1 is a block diagram of an exemplary system for executing a universal script editor for creating scripts with arbitrary syntax, according to an embodiment of the present invention
  • Fig. 2 is a screen dump of an exemplary menu that has been customized through the use of a configuration file, according to an embodiment of the present invention
  • Fig. 3 is a screen dump of another exemplary menu that has been customized through the use of a configuration file, according to another embodiment of the present invention.
  • Fig. 4 is a flow diagram of an exemplary routine for providing menus, based upon one or more configuration files read into a universal script editor, to create scripts with arbitrary syntax, according to an embodiment of the present invention.
  • the present invention is directed to a software application that takes the form of a customizable universal script editor.
  • the script editor utilizes a configuration file to configure a set of menus that are specific to a project— with a menu structure, command names, command source files and other options defined by a user. More than one menu system can be defined, with each menu system associated with the type of the file being edited. These menus can then be used to rapidly build-up scripts for a current project using a general purpose editing window provided by the script editor.
  • the configuration file may identify user created individual or multi-command script text files of an appropriate syntax for each command/function that a user supplied script interpreter engine requires. In this manner, the configuration file identifies menu/command names and structures and may include locations and names of files and/or text containing commands for a user's system.
  • a project specific configuration file can provide the information to the script editor in a variety of ways. For example, the configuration file may provide the location/names of the files containing the project specific and/or generic script command structures. Alternatively, or in addition, the command text can be contained within the configuration file.
  • the configuration file also defines a menu structure for the project, i.e., the number of menus, names and position of the menus, as well as the menu items for each menu structure, i.e., the number of menu items, the name of the menu items and the position of command names associated with the menu items.
  • the configuration file may also contain keyword definitions that are used for highlighting, automatic indentation and outlining and may provide parameter names on pull-down menus for various parameters contained within a project specific and/or generic script command.
  • the script editor may utilize an include command to allow one script to pull in one or more other scripts and/or a pop-up window showing an outline of the commands in a current or new window.
  • a primary advantage of the script editor is that it can be easily reconfigured via configuration file(s) defining menu command structures to support rapid script generation for a wide range of applications with arbitrary syntax.
  • the universal script editor according to the present invention, is applicable to almost any program/product that requires generation of text-based scripts and, more specifically, is applicable to the testing of any program/product that requires generation of text-based scripts.
  • a user creates individual or multi-command script text files of an appropriate syntax for each command/function that a user supplied script interpreter engine can translate.
  • a configuration file defines the characteristics of the script language and may include location/names of the files containing the project specific and/or generic script command structures. Alternatively, or in addition, the command text can be contained directly within the configuration file.
  • a configuration file also includes a menu structure for the project and menu items for each menu structure.
  • a configuration file may include keyword definitions that are used for highlighting, automatic indentation and outlining and may include parameter names and provide pull-down menus for the various parameters contained within a project specific and/or generic script commands.
  • a script editor application program constructed according to the present invention can be easily reconfigured based on read menu command structures to support rapid script generation for a wide range of applications with arbitrary syntax.
  • the universal script editor includes a read module to read in one or more configuration files and an editor module to support typical editor capabilities, e.g., cut, paste, font select, page number, column number, etc., plus connection to the menu structure to pull-in user defined templates, based on menu selections.
  • the universal script editor may also include a support module to support miscellaneous other editor functions customized by the configuration file, such as, keyword highlighting, automatic indentation and outline viewing.
  • Fig. 1 depicts an exemplary computer system 100 that can be utilized to implement the present invention.
  • a processor 102 is coupled to a memory subsystem 104, which may include an application appropriate amount of volatile and non- volatile memory.
  • the processor 102 is also coupled to an input device 110, a display 108 and a mass storage device 106, which may store an operating system, a script interpreter engine, a universal script editor and one or more configuration files.
  • the mass storage device 106 may take any number of forms, such as a compact disc read- write memory (CD-RW) or a hard disk drive.
  • CD-RW compact disc read- write memory
  • an exemplary configuration file includes various menus and menu items, which may have a corresponding test program language file (e.g., a file with extension '.tpl') associated therewith: [0021] $TemplateDir " ⁇ TPLf ⁇ les3 ⁇ "
  • ELStart As is shown above, the .tpl file is directed to a routine in the system-under-test that logs events.
  • Start delay time 0 ;unsigned (0-120, 0.5 sec lsb)
  • Fig. 2 depicts an exemplary screen dump of a menu 200 created from a configuration file similar to the above-referenced configuration file.
  • the 1553 primary/secondary selectable commands allow a user to efficiently set up a test script and thereby initiate the performance of a number of tasks.
  • Fig. 3 depicts another exemplary screen dump 300 illustrating submenu items associated with a telemetry field item of a menu structure associated with a configuration file similar to the configuration file set forth above.
  • the telemetry field items allows the user to efficiently examine the results of an executed test script and thereby perform analysis of the test.
  • the electrical functional status associated with a particular Primary Telemetry data word provides an indication of a sensor failure, an unexpected interrupt failure, a foreground failure, a gimbal system failure, a spin system failure, a switching bank relay failure, a timer failure, a 1553 failure, a power supply voltage failure, a checksum failure, an A/D converter failure, a processor failure, among other failures.
  • a custom menu can be created that facilitates efficient and timely creation of scripts associated with an arbitrary syntax and the analysis of data provided through the execution of the scripts.
  • processor 102 initiates execution of the routine 400, at which point control transfers to step 406.
  • the processor 102 reads in a project-specific default configuration file and builds editor menus and submenus based upon the default configuration file. Control then transfers to decision step 408.
  • the processor 102 determines whether the user has requested to open an existing file. If not, control transfers to step 413. Otherwise, control transfers to step 412, where an associated configuration file is read and the processor 102 builds editor menus and submenus based upon the configuration file associated with the file selected for opening. Control then transfers to step 413.
  • the configuration file may include information such as location/name of a file containing a command script structure and/or the configuration file may include a command script structure. Further, the configuration file includes a menu structure and menu items for the menu structure and may include keyword definitions and parameters names.
  • the processor 102 causes the menus to be displayed to the user on the display 108, for example, a liquid crystal diode (LCD) display. Then, the processor 102 determines whether a user has provided input through input device 110, which may be, for example, a mouse, in decision step 414. If so, control transfers from step 414 to step 416, where the processor 102 performs an input appropriate task. Otherwise, control loops on step 414.
  • LCD liquid crystal diode
  • step 416 control transfers to decision step 418, where the processor
  • the universal script editor includes a read module for reading in one or more configuration files and setting up menu and data structures required to support editing functions for building scripts for a current project.
  • the read module is in communication with an editor module that supports a plurality of editor capabilities, which are utilized to build the script for the current project.

Landscapes

  • Engineering & Computer Science (AREA)
  • Software Systems (AREA)
  • General Engineering & Computer Science (AREA)
  • Theoretical Computer Science (AREA)
  • Physics & Mathematics (AREA)
  • General Physics & Mathematics (AREA)
  • Stored Programmes (AREA)
  • Computer And Data Communications (AREA)

Abstract

A universal script editor for creating scripts with arbitrary syntax includes a read module and an editor module. For a given script type, the read module reads in a configuration file that includes a menu structure with associated menu items and at least one of a location/name of a file containing a script command structure or a self-contained script command structure. The read module sets up one or more menus, which support editing functions for building scripts for a current project, based upon the configuration file. The editor module, which is communication with the read module, supports a plurality of editor capabilities which are utilized to build current projects scripts.

Description

UNIVERSAL SCRIPT EDITOR BACKGROUND [0001] The present invention is generally directed to a script editor and, more specifically, to a universal script editor for creating scripts with arbitrary syntax. [0002] Today, many software and/or hardware development activities use some kind of script interpreter/script compiler engine, which takes a set of textual script command/data structures and interprets/compiles the commands/data structures and provides appropriate processing of the commands/data. For example, a personal computer (PC) with a 1553 card may have a script interpreter engine that takes a file of commands and converts the commands into 1553 I/O messages, data comparisons and pass/fail checks, thereby, controlling and monitoring a system under test. Tool command language (TCL) is one such script interpreter engine that has been used for controlling and monitoring a system under test.
[0003] While standard editors are often used to support the generation of executable scripts, such standard editors are generally inefficient as they have no knowledge of the specifics of the system under test. Alternatively, custom editor applications have been written that support a project-defined command syntax. However, creating/maintaining custom editors can become costly and time-consuming as command syntax is often unique and quite different from one project to the next project.
[0004] Thus, what is needed is a universal script editor that can be used for creating scripts with arbitrary syntax.
SUMMARY [0005] The present invention is generally directed to a universal script editor for creating scripts with arbitrary syntax. The universal script editor includes a read module for reading in one or more configuration files and an editor module that is in communication with the read module. A configuration file includes a definition of a menu structure with associated menu items and at least one of a location/name of a file containing a script command structure and a self-contained script command structure. The read module sets up one or more menu systems, which support editing functions for building scripts for a current project, based upon the configuration file associated with each file type being edited. The editor module supports a plurality of editor capabilities, which are utilized to build current project scripts.
[0006] According to another embodiment of the present invention, the universal script editor also includes a miscellaneous support module that provides additional editor capabilities, which may include keyword highlighting, automatic indentation and outline viewing.
[0007] According to another embodiment of the present invention, the editing functions may include cutting, pasting, font selection, page numbering and column numbering.
[0008] These and other features, advantages and objects of the present invention will be further understood and appreciated by those skilled in the art by reference to the following specification, claims and appended drawings.
BRIEF DESCRIPTION OF THE DRAWINGS [0009] Fig. 1 is a block diagram of an exemplary system for executing a universal script editor for creating scripts with arbitrary syntax, according to an embodiment of the present invention;
[0010] Fig. 2 is a screen dump of an exemplary menu that has been customized through the use of a configuration file, according to an embodiment of the present invention; [0011] Fig. 3 is a screen dump of another exemplary menu that has been customized through the use of a configuration file, according to another embodiment of the present invention; and
[0012] Fig. 4 is a flow diagram of an exemplary routine for providing menus, based upon one or more configuration files read into a universal script editor, to create scripts with arbitrary syntax, according to an embodiment of the present invention.
DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS [0013] The present invention is directed to a software application that takes the form of a customizable universal script editor. According to the present invention, the script editor utilizes a configuration file to configure a set of menus that are specific to a project— with a menu structure, command names, command source files and other options defined by a user. More than one menu system can be defined, with each menu system associated with the type of the file being edited. These menus can then be used to rapidly build-up scripts for a current project using a general purpose editing window provided by the script editor.
Changing from one project to another project, or one file type to another, with a different syntax, command structure and/or menu structures is simply a matter of creating a different configuration file and any supporting script templates, and reading the configuration file into the script editor.
[0014] The configuration file may identify user created individual or multi-command script text files of an appropriate syntax for each command/function that a user supplied script interpreter engine requires. In this manner, the configuration file identifies menu/command names and structures and may include locations and names of files and/or text containing commands for a user's system. A project specific configuration file can provide the information to the script editor in a variety of ways. For example, the configuration file may provide the location/names of the files containing the project specific and/or generic script command structures. Alternatively, or in addition, the command text can be contained within the configuration file.
[0015] The configuration file also defines a menu structure for the project, i.e., the number of menus, names and position of the menus, as well as the menu items for each menu structure, i.e., the number of menu items, the name of the menu items and the position of command names associated with the menu items. The configuration file may also contain keyword definitions that are used for highlighting, automatic indentation and outlining and may provide parameter names on pull-down menus for various parameters contained within a project specific and/or generic script command.
[0016] The script editor may utilize an include command to allow one script to pull in one or more other scripts and/or a pop-up window showing an outline of the commands in a current or new window. However, it should be appreciated that a primary advantage of the script editor is that it can be easily reconfigured via configuration file(s) defining menu command structures to support rapid script generation for a wide range of applications with arbitrary syntax. Thus, it should be understood that the universal script editor, according to the present invention, is applicable to almost any program/product that requires generation of text-based scripts and, more specifically, is applicable to the testing of any program/product that requires generation of text-based scripts.
[0017] According to the present invention, a user creates individual or multi-command script text files of an appropriate syntax for each command/function that a user supplied script interpreter engine can translate. As mentioned above, a configuration file defines the characteristics of the script language and may include location/names of the files containing the project specific and/or generic script command structures. Alternatively, or in addition, the command text can be contained directly within the configuration file. As mentioned above, a configuration file also includes a menu structure for the project and menu items for each menu structure. Further, a configuration file may include keyword definitions that are used for highlighting, automatic indentation and outlining and may include parameter names and provide pull-down menus for the various parameters contained within a project specific and/or generic script commands. Thus, a script editor application program constructed according to the present invention can be easily reconfigured based on read menu command structures to support rapid script generation for a wide range of applications with arbitrary syntax.
[0018] In its basic form, the universal script editor includes a read module to read in one or more configuration files and an editor module to support typical editor capabilities, e.g., cut, paste, font select, page number, column number, etc., plus connection to the menu structure to pull-in user defined templates, based on menu selections. The universal script editor may also include a support module to support miscellaneous other editor functions customized by the configuration file, such as, keyword highlighting, automatic indentation and outline viewing.
[0019] Fig. 1 depicts an exemplary computer system 100 that can be utilized to implement the present invention. As shown in Fig. 1, a processor 102 is coupled to a memory subsystem 104, which may include an application appropriate amount of volatile and non- volatile memory. The processor 102 is also coupled to an input device 110, a display 108 and a mass storage device 106, which may store an operating system, a script interpreter engine, a universal script editor and one or more configuration files. The mass storage device 106 may take any number of forms, such as a compact disc read- write memory (CD-RW) or a hard disk drive.
[0020] As is set forth below, an exemplary configuration file includes various menus and menu items, which may have a corresponding test program language file (e.g., a file with extension '.tpl') associated therewith: [0021] $TemplateDir "ΛTPLfιles3\"
[0022] $Menu "1553 Pri/Sec Cmds"
[0023] $Item "Set Chnl" "SetChnl.tpl" [0024] $Item "Create Msg" "CreateMsg.tpl"
[0025] $Menu "1553 Eng Cmds"
[0026] $Item "Engineering Status" "EngTelm.tpl"
[0027] $Item "Eng Mem Write" "EngMemWrite.tpl"
[0028] $Item "-"
[0029] $ParamMenu "Telem Fields"
[0030] $ParamGrp "PriTlm:0-2"
[0031] $Param "Gimbal Rate" "$PriTelm(GIMBAL_RATE)"
[0032] $Param "Gimbal Angle" "$PriTelm(GIMBAL ANGLE)''
[0033] $Param "Wheelspeed" "$PriTelm(WHEEL_SPEED)"
[0034] $ParamGrp "PriTlm3:Oρer Status"
[0035] $Param "Operating Mode" "$PriTelm(OPER_MODE)"
[0036] $Param "SES Spin Enabled" "$PriTelm(SES)r
[0037] $Keywords "Abort" "SetChnl" "For+" "for+" "lf+"
[0038] $Keywords "-else+" "-endif ' "-loop" " {+" "-} "
[0039] $CommentStr "#"
[0040] The contents of an exemplary project specific .tpl file are set forth below:
[0041] SCRIPT FILE 'A' [0042] set ELStart(CELEO) 0 ;# l=Clear event log event occurred flag [0043] set ELStart(RM) 0 ;# 0=stop on event l=start on event
[0044] ;# the next three parameters are used only when RM
[0045] set ELStart(RFST) 0 ;# 0=from event l=from start
[0046] set ELStart(MEC) 0 ;# 0-7 multiple event counter
[0047] set ELStart(START_DELAY_TIME) 0 ;# 0-120 (resolution 0.5 seconds)
[0048] ;# if RM=0 then REC_T E = length of time to record after trigger occurs
[0049] set ELStart(REC_TIME) 0 ;# 0- 120 (resolution 0.5 seconds)
[0050] ELStart [0051] As is shown above, the .tpl file is directed to a routine in the system-under-test that logs events.
[0052] The contents of another exemplary project specific .tpl file, with completely different syntax, which logs events, is shown below:
[0053] SCRIPT FILE 'B'
[0054] [Event log start]
[0055] Clear event log event occurred flag= 0 ;boolean
[0056] Record mode = 0 ;boolean (0=Stop on Event, l=Start on Event)
[0057] Record from start time = 0 ;boolean
[0058] Multiple event counter = 0 ;unsigned (0-7)
[0059] Start delay time = 0 ;unsigned (0-120, 0.5 sec lsb)
[0060] Record time = 0 ;unsigned (0-120, 0.5 sec lsb)
[0061] Fig. 2 depicts an exemplary screen dump of a menu 200 created from a configuration file similar to the above-referenced configuration file. As is shown in Fig. 2, the 1553 primary/secondary selectable commands allow a user to efficiently set up a test script and thereby initiate the performance of a number of tasks.
[0062] Fig. 3 depicts another exemplary screen dump 300 illustrating submenu items associated with a telemetry field item of a menu structure associated with a configuration file similar to the configuration file set forth above. As is shown in Fig. 3, the telemetry field items allows the user to efficiently examine the results of an executed test script and thereby perform analysis of the test. As is illustrated, the electrical functional status associated with a particular Primary Telemetry data word provides an indication of a sensor failure, an unexpected interrupt failure, a foreground failure, a gimbal system failure, a spin system failure, a switching bank relay failure, a timer failure, a 1553 failure, a power supply voltage failure, a checksum failure, an A/D converter failure, a processor failure, among other failures. Thus, it should be appreciated that depending upon the configuration file, a custom menu can be created that facilitates efficient and timely creation of scripts associated with an arbitrary syntax and the analysis of data provided through the execution of the scripts. [0063] Turning to Fig. 4, an exemplary script editor routine 400 is illustrated. In step
402, processor 102 initiates execution of the routine 400, at which point control transfers to step 406. In step 406, the processor 102 reads in a project-specific default configuration file and builds editor menus and submenus based upon the default configuration file. Control then transfers to decision step 408. In step 408, the processor 102 determines whether the user has requested to open an existing file. If not, control transfers to step 413. Otherwise, control transfers to step 412, where an associated configuration file is read and the processor 102 builds editor menus and submenus based upon the configuration file associated with the file selected for opening. Control then transfers to step 413.
[0064] As previously discussed, the configuration file may include information such as location/name of a file containing a command script structure and/or the configuration file may include a command script structure. Further, the configuration file includes a menu structure and menu items for the menu structure and may include keyword definitions and parameters names. In step 413, the processor 102 causes the menus to be displayed to the user on the display 108, for example, a liquid crystal diode (LCD) display. Then, the processor 102 determines whether a user has provided input through input device 110, which may be, for example, a mouse, in decision step 414. If so, control transfers from step 414 to step 416, where the processor 102 performs an input appropriate task. Otherwise, control loops on step 414.
[0065] Following step 416, control transfers to decision step 418, where the processor
102 determines whether a user selected to quit the script building process. If so, control transfer to step 420 where the process terminates. Otherwise, control transfers to decision step 408 where another file can be opened, resulting in an appropriate configuration file being read to customize the script editor.
[0066] Accordingly, a universal script editor for creating scripts with arbitrary syntax has been described herein. As discussed, the universal script editor includes a read module for reading in one or more configuration files and setting up menu and data structures required to support editing functions for building scripts for a current project. The read module is in communication with an editor module that supports a plurality of editor capabilities, which are utilized to build the script for the current project. [0067] The above description is considered that of the preferred embodiments only.
Modification of the invention will occur to those skilled in the art and to those who make or use the invention. Therefore, it is understood that the embodiments shown in the drawings and described above are merely for illustrative purposes and not intended to limit the scope of the invention, which is defined by the following claims as inteφreted according to the principles of patent law, including the Doctrine of Equivalents.

Claims

1. A universal script editor for creating scripts with arbitrary syntax, comprising: a read module for reading in one or more configuration files each of which includes a menu structure with associated menu items and at least one of a location/name of a file containing a script command structure and a self-contained script command structure, wherein the read module sets up a menu which supports editing functions for building scripts for a current project based upon the configuration files; and an editor module in communication with the read module, the editor module supporting a plurality of editor capabilities which are utilized to build current project scripts.
2. The script editor of claim 1, further including: a miscellaneous support module providing additional editor capabilities including keyword highlighting, automatic indentation and outline viewing.
3. The script editor of claim 1, wherein the editor capabilities include cutting, pasting, font selection, page numbering and column numbering functions.
4. The script editor of claim 1, wherein the editor module is in communication with the menu structure and retrieves templates responsive to a menu selection of the user.
5. The script editor of claim 1, wherein the script editor automatically associates configuration files and the associated menu structure with a type of file being edited.
6. A system for creating scripts using a universal script editor, the system comprising, a processor; a display coupled to the processor; an input device coupled to the processor; and a memory subsystem coupled to the processor, the memory subsystem storing code which includes: a read module, the read module when executed by the processor reading in one or more configuration files each of which include a menu structure with associated menu items and at least one of a location/name of a file containing a script command structure and a self-contained script command structure, wherein the read module sets up a menu which supports editing functions for buildmg scripts for a current project based upon the configuration file; and an editor module in communication with the read module, the editor module when executed by the processor supporting a plurality of editor capabilities which are utilized to build current project scripts.
7. The system of claim 6, wherein the code further includes: a miscellaneous support module for providing additional editor capabilities including keyword highlighting, automatic indentation and outline viewing.
8. The system of claim 6, wherein the editor capabilities include cutting, pasting, font selection, page numbering and column numbering functions.
9. The system of claim 6, wherein the editor module is in communication with the menu structure and retrieves templates responsive to a menu selection of the user.
10. The system of claim 6, wherein the script editor automatically associates configuration files and the associated menu structure with a type of file being edited.
11. A universal script editor for creating scripts with arbitrary syntax, comprising: a read module for reading in one or more configuration files each of which include a menu structure with associated menu items and at least one of a location/name of a file containing a script command structure and a self-contained script command structure, wherein the read module sets up a menu which supports editing functions for buildmg scripts for a current project based upon the configuration file; an editor module in communication with the read module, the editor module supporting a plurality of editor capabilities which are utilized to build current project scripts; and a miscellaneous support module providing additional editor capabilities including • keyword highlighting, automatic indentation and outline viewing.
12. The script editor of claim 11, wherein the editor capabilities include cutting, pasting, font selection, page numbering and column numbering functions.
13. The script editor of claim 11, wherein the editor module is in communication with the menu structure and retrieves templates responsive to a menu selection of the user.
14. The script editor of claim 11, wherein the script editor automatically associates configuration files and the associated menu structure with a type of file being edited.
EP03716980A 2002-04-04 2003-04-04 Universal script editor Ceased EP1490791A2 (en)

Applications Claiming Priority (3)

Application Number Priority Date Filing Date Title
US116602 1987-11-02
US10/116,602 US7197744B2 (en) 2002-04-04 2002-04-04 Universal script editor
PCT/US2003/010321 WO2003085549A2 (en) 2002-04-04 2003-04-04 Universal script editor

Publications (1)

Publication Number Publication Date
EP1490791A2 true EP1490791A2 (en) 2004-12-29

Family

ID=28674025

Family Applications (1)

Application Number Title Priority Date Filing Date
EP03716980A Ceased EP1490791A2 (en) 2002-04-04 2003-04-04 Universal script editor

Country Status (4)

Country Link
US (1) US7197744B2 (en)
EP (1) EP1490791A2 (en)
AU (1) AU2003220662A1 (en)
WO (1) WO2003085549A2 (en)

Families Citing this family (24)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20070038661A1 (en) * 2003-01-21 2007-02-15 Junya Kaku Data structure of menu display control data and menu display device
US8010952B2 (en) * 2004-06-08 2011-08-30 Cisco Technology, Inc. Method and apparatus for configuration syntax and semantic validation
US20060015591A1 (en) * 2004-06-08 2006-01-19 Datla Krishnam R Apparatus and method for intelligent configuration editor
US7680927B2 (en) 2005-11-17 2010-03-16 Bea Systems, Inc. System and method for providing testing for a communities framework
US20070112913A1 (en) * 2005-11-17 2007-05-17 Bales Christopher E System and method for displaying HTML content from portlet as a page element in a communites framework
US20070112799A1 (en) * 2005-11-17 2007-05-17 Bales Christopher E System and method for providing resource interlinking for a communities framework
US8046696B2 (en) * 2005-11-17 2011-10-25 Oracle International Corporation System and method for providing active menus in a communities framework
US8185643B2 (en) * 2005-11-17 2012-05-22 Oracle International Corporation System and method for providing security in a communities framework
US8255818B2 (en) 2005-11-17 2012-08-28 Oracle International Corporation System and method for providing drag and drop functionality in a communities framework
US8078597B2 (en) * 2005-11-17 2011-12-13 Oracle International Corporation System and method for providing extensible controls in a communities framework
US7805459B2 (en) 2005-11-17 2010-09-28 Bea Systems, Inc. Extensible controls for a content data repository
US20070226542A1 (en) * 2006-03-24 2007-09-27 International Business Machines Corporation Simulated message generation for simulation testing of a node operation
US8850388B2 (en) * 2006-09-07 2014-09-30 Microsoft Corporation Controlling application features
US7895179B2 (en) * 2007-06-25 2011-02-22 Microsoft Corporation Asynchronous updating of web page data views
US8504985B2 (en) * 2009-04-30 2013-08-06 Adobe Systems Incorporated Context sensitive script editing for form design
US9262138B2 (en) * 2010-05-27 2016-02-16 Salesforce.Com, Inc. Adding directives for JavaScript files directly into source code in a multi-tenant database environment
US20120291011A1 (en) * 2011-05-12 2012-11-15 Google Inc. User Interfaces to Assist in Creating Application Scripts
US9529704B2 (en) * 2012-09-07 2016-12-27 Aai Corporation Graphical conversion between test program languages
US9367415B1 (en) * 2014-01-20 2016-06-14 Google Inc. System for testing markup language applications on a device
CN105589709A (en) * 2014-12-24 2016-05-18 中国银联股份有限公司 Device and method for changing menu of point of sale (POS) terminal
CN109445835A (en) * 2018-09-03 2019-03-08 平安普惠企业管理有限公司 Method, terminal device and the computer readable storage medium of building project frame
US11875137B2 (en) * 2020-12-07 2024-01-16 Texas Instruments Incorporated Method and apparatus for adding new inline prompts to a program development environment
CN114168223B (en) * 2021-12-06 2023-11-03 福建天晴数码有限公司 Technical method and system for improving resource preview speed in editing
CN115952103A (en) * 2023-03-10 2023-04-11 北京全路通信信号研究设计院集团有限公司 Test script editing method, device, medium and electronic equipment

Family Cites Families (9)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US5715373A (en) * 1994-10-20 1998-02-03 Tandem Computers Incorporated Method and apparatus for preparing a suite of test scripts for testing a proposed network management application
US5652884A (en) * 1994-11-14 1997-07-29 Object Technology Licensing Corp. Method and apparatus for dynamic update of an existing object in an object editor
US5950002A (en) * 1996-08-13 1999-09-07 General Electric Company Learn mode script generation in a medical imaging system
US6061695A (en) * 1996-12-06 2000-05-09 Microsoft Corporation Operating system shell having a windowing graphical user interface with a desktop displayed as a hypertext multimedia document
EP0895195A1 (en) * 1997-01-24 1999-02-03 Sony Corporation Pattern data generator, pattern data generating method and its medium
US6002871A (en) * 1997-10-27 1999-12-14 Unisys Corporation Multi-user application program testing tool
US6311320B1 (en) * 1998-12-07 2001-10-30 Lsi Logic Corporation Alterable scripting tool and method
US6775824B1 (en) * 2000-01-12 2004-08-10 Empirix Inc. Method and system for software object testing
US7546298B2 (en) * 2001-01-09 2009-06-09 Nextair Corporation Software, devices and methods facilitating execution of server-side applications at mobile devices

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
See references of WO03085549A2 *

Also Published As

Publication number Publication date
WO2003085549A2 (en) 2003-10-16
WO2003085549A3 (en) 2004-03-18
US20030192030A1 (en) 2003-10-09
AU2003220662A8 (en) 2003-10-20
US7197744B2 (en) 2007-03-27
AU2003220662A1 (en) 2003-10-20

Similar Documents

Publication Publication Date Title
US7197744B2 (en) Universal script editor
US6496872B1 (en) Computer system for automatically instantiating tasks designated by a user
US5732221A (en) Electronic documentation system for generating written reports
US7934158B2 (en) Graphical user interface (GUI) script generation and documentation
EP0367709B1 (en) Customization of user interface for application programs
US7286999B2 (en) Integrated project management and development environment for determining the time expended on project tasks
AU2003233573B2 (en) System and method for making user interface elements known to an application and user
US5680617A (en) Computer-human interface which provides for user customization of object behavior
US7367017B2 (en) Method and apparatus for analyzing machine control sequences
KR101323011B1 (en) Command user interface for displaying selectable functionality controls in a database application
US5465358A (en) System for enhancing user efficiency in initiating sequence of data processing system user inputs using calculated probability of user executing selected sequences of user inputs
US6311320B1 (en) Alterable scripting tool and method
US7228542B2 (en) System and method for dynamically creating a customized multi-product software installation plan as a textual, non-executable plan
US6046741A (en) Visual command sequence desktop agent
US20080141226A1 (en) System and method for controlling trace points utilizing source code directory structures
CN101223495A (en) Control panel framework
EP0621527A1 (en) Hierarchically grouped macroinstructions for a graphical user interface
KR950702720A (en) Sequential Information Integration Service for Intergrating Transfer of Files or other Date Entities between A Plurality of Program Modules and a Storage in a Computer)
JPH08179896A (en) Logging data analysis system
CN102929517A (en) Triggering prompt method in mouse click method
JP2864528B2 (en) Message management method
CN117742834A (en) Method and device for configuring page component of low-code platform
Reiss et al. The Debugger Interface
KR19990025079A (en) Script File Creator for Hard Disk Master Production System
JPH0667908A (en) Error information analysis program starting control system for information processor

Legal Events

Date Code Title Description
PUAI Public reference made under article 153(3) epc to a published international application that has entered the european phase

Free format text: ORIGINAL CODE: 0009012

17P Request for examination filed

Effective date: 20041001

AK Designated contracting states

Kind code of ref document: A2

Designated state(s): AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HU IE IT LI LU MC NL PT RO SE SI SK TR

AX Request for extension of the european patent

Extension state: AL LT LV MK

RIN1 Information on inventor provided before grant (corrected)

Inventor name: HOSTETTLER, RANDY, W.

17Q First examination report despatched

Effective date: 20050520

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: THE APPLICATION HAS BEEN REFUSED

18R Application refused

Effective date: 20060602