Using a local editor: Difference between revisions
(Created page with "__TOC__ <span class="f_Para">As described in this section, you can use a local editor to view and modify the workstation text files that the Debugger Client provides for its v...") |
No edit summary |
||
| Line 3: | Line 3: | ||
=== Editing workstation text files === | === Editing workstation text files === | ||
<span class="f_EndTopic">To control the Client, you create and maintain text files on the workstation (e.g., [[ | <span class="f_EndTopic">To control the Client, you create and maintain text files on the workstation (e.g., [[Customize debuggerConfig file|configuration]], [[Running only to listed procedures|white/black lists]], [[Using Debugger Macros|macros]]). By default, the menu items and commands to edit/create these files use the Windows Notepad.</span> | ||
<span class="f_EndTopic">The Debugger configuration file (</span><span class="f_Monospace">debuggerConfig.xml</span><span class="f_Para">) contains an element with which you can specify an alternate text editor to work with the various text files employed by the Client. As described in [[ | <span class="f_EndTopic">The Debugger configuration file (</span><span class="f_Monospace">debuggerConfig.xml</span><span class="f_Para">) contains an element with which you can specify an alternate text editor to work with the various text files employed by the Client. As described in [[Customize debuggerConfig file#Text file editor|this step]] in the configuration of </span><span class="f_Monospace">debuggerConfig.xml,</span><span class="f_Para"> you use the </span><span class="f_Monospace">notepadReplacement</span><span class="f_Para"> element to select your own local editor to replace the </span><var>Notepad</var><span class="f_Para"> editor. </span> | ||
=== Editing procedure files === | === Editing procedure files === | ||
<span class="f_Para">The </span><span class="f_GUIlabel">[[ | <span class="f_Para">The </span><span class="f_GUIlabel">[[Displaying line information and editing procedures|Line Information]]</span><span class="f_Para"> pop up in the Client provides detailed information about a source line, such as the name of the procedure and procedure file from which it comes. You can configure the </span><var>Edit</var><span class="f_Para"> button on this pop up to edit the procedure on your workstation. </span> | ||
<span class="f_Para">From the editor, you can change and save code, and the saved file is returned to the Online to replace the original. To see if the change had the desired results, you may rerun the procedure.</span> | <span class="f_Para">From the editor, you can change and save code, and the saved file is returned to the Online to replace the original. To see if the change had the desired results, you may rerun the procedure.</span> | ||
| Line 18: | Line 18: | ||
<var>Xtend</var><span class="f_ListContinue"> is a GUI editor designed specifically to edit procedures written in SOUL. </span> | <var>Xtend</var><span class="f_ListContinue"> is a GUI editor designed specifically to edit procedures written in SOUL. </span> | ||
< | <var>Xtend</var><span class="f_ListContinue"> transfers files to and from the </span><var>Model 204</var><span class="f_ListContinue"> Online using the HTTP protocol, and you must either define a </span><var>Janus Web Server</var><span class="f_ListContinue"> port or an RCL Connect* connection to use it. This document describes only the Web Server connection (which requires </span><var>Janus Web Server</var><span class="f_ListContinue"> authorization). For information about using RCL Connect*, you must see the </span><var>Xtend</var><span class="f_ListContinue"> documentation. </span> | ||
* UltraEdit</span><span class="f_Para" style="font-size: 9px; vertical-align: super;">®</span><span class="f_ListBul1"> from IDM Computer Solutions, Inc. (http://ultraedit.com)</span> | * UltraEdit</span><span class="f_Para" style="font-size: 9px; vertical-align: super;">®</span><span class="f_ListBul1"> from IDM Computer Solutions, Inc. (http://ultraedit.com)</span> | ||
| Line 27: | Line 27: | ||
These sections follow: | These sections follow: | ||
: [[ | : [[Using Xtend with the Debugger|Using Xtend with the Debugger]] | ||
: [[ | : [[Using UltraEdit with the Debugger|Using UltraEdit with the Debugger]] | ||
[[Category:Debugger Home]] | [[Category:Debugger Home]] | ||
Latest revision as of 16:27, 10 January 2023
As described in this section, you can use a local editor to view and modify the workstation text files that the Debugger Client provides for its various purposes. You can also use a local editor to interactively modify your source code procedure files.
Editing workstation text files
To control the Client, you create and maintain text files on the workstation (e.g., configuration, white/black lists, macros). By default, the menu items and commands to edit/create these files use the Windows Notepad.
The Debugger configuration file (debuggerConfig.xml) contains an element with which you can specify an alternate text editor to work with the various text files employed by the Client. As described in this step in the configuration of debuggerConfig.xml, you use the notepadReplacement element to select your own local editor to replace the Notepad editor.
Editing procedure files
The Line Information pop up in the Client provides detailed information about a source line, such as the name of the procedure and procedure file from which it comes. You can configure the Edit button on this pop up to edit the procedure on your workstation.
From the editor, you can change and save code, and the saved file is returned to the Online to replace the original. To see if the change had the desired results, you may rerun the procedure.
Currently, two editors are supported:
- Xtend® from Yoda Software
Xtend is a GUI editor designed specifically to edit procedures written in SOUL.
Xtend transfers files to and from the Model 204 Online using the HTTP protocol, and you must either define a Janus Web Server port or an RCL Connect* connection to use it. This document describes only the Web Server connection (which requires Janus Web Server authorization). For information about using RCL Connect*, you must see the Xtend documentation.
- UltraEdit® from IDM Computer Solutions, Inc. (http://ultraedit.com)
UltraEdit is a GUI editor that is designed to edit program source code from a wide variety of languages.
UltraEdit transfers files to and from the Model 204 Online using the FTP protocol, and you must define a Janus FTP Server port to use it. This means you must be authorized for Janus Sockets.
These sections follow: