APL Wiki|
Size: 3042
Comment:
|
Size: 3143
Comment:
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 1: | Line 1: |
| == Fire == | ## page was renamed from APLTree/Fire = Fire = |
| Line 5: | Line 6: |
| /!\ Under construction '''''Fire''''' stands for for FInd and REplace. It's designed to search and replace strings in the workspace. |
{{attachment:fire.png||align="middle"}} '''''Fire''''' stands for FInd and REplace. It's designed to search and replace strings in the workspace. |
| Line 16: | Line 15: |
| * traditional functions & operators * direct functions & operators |
* Traditional functions & operators * Direct functions & operators |
| Line 28: | Line 27: |
| * Negate a search ("every object that does '''not''' contain...) | * Negate a search ("all objects that do '''not''' contain...") |
| Line 34: | Line 33: |
| * Fire reports a WS FULL only when it is reasonable to do so | |
| Line 53: | Line 53: |
| * In batch mode you can check all changes in one go and then either accept or discard them. | * "All in one go" allows you to check all changes first and then either accept or discard them. |
| Line 56: | Line 56: |
| ==== Batch mode ==== | ==== "All in one go" mode ==== |
| Line 58: | Line 58: |
| This is the first of three steps in Batch mode: | This is the first of three steps: |
| Line 62: | Line 62: |
| It's a reminder that for "Replace" it's always the whole hit list that is processed, not only the selection. | This is a reminder that for "Replace" it's always the whole hit list that is processed, not only the selection. |
| Line 64: | Line 64: |
| This is the second step in Batch mode: | This is the second step: |
| Line 68: | Line 68: |
| It allows you to check whether everything is okay or not. Here we see a "compressed" report: it contains only the potentially changed lines plus the object names plus the headers for all traditional functions and operators in order to make checking local variables easy. The full report would show all lines of all objects involved. You cannot change anything at this stage. | This allows you to check whether everything is okay or not. Here we see a "compressed" report: it contains only the lines which would change plus the object names plus the headers for all traditional functions and operators in order to make checking local variables easy. The full report would show all lines of all objects involved. You cannot change anything at this stage. |
| Line 74: | Line 74: |
| This allows you to either fix all objects or discard all changes. | This allows you to either change and fix all objects or not. |
| Line 82: | Line 82: |
| In the next step you can either fix the changes are skip this object and carry on with the next one or cancel the rest of the Replace operation: | In the next step you can either fix the changes or skip this object and carry on with the next one or cancel the whole operation: |
| Line 96: | Line 96: |
| ---- CategoryAplTree |
Fire
Contents
Fire stands for FInd and REplace. It's designed to search and replace strings in the workspace.
Features
Fire's main feature is the "Replace" command which allows you in an easy yet powerful way to replace certain strings in all or selected objects.
Other features are:
- You can restrict the search to one or more of these object classes:
Traditional functions & operators
Direct functions & operators
- Classes
- Interfaces
- Scripted namespaces
- Variables
- You can search...
- the full source code
- the full source code but comments
- comments only
- text only
Use regular expression in your search string (⎕S, ⎕R)
Negate a search ("all objects that do not contain...")
- Search only the hits of the last search
Difference between Dyalog's build-in Search tool and Fire
Fire handles circular references correctly (thanks to PhilLast)
- Fire reports a WS FULL only when it is reasonable to do so
Fire's GUI
Main Window
Specifying anything in the "Start looking here" control is supported by autocomplete: this box offers all ordinary namespaces matching the characters in "Start looking here".
The "Replace" feature
The Replace feature allows you to change the workspace on a global level:
There are two modes available:
- "All in one go" allows you to check all changes first and then either accept or discard them.
- "One-by-one" allows you to compare and edit one object after the other.
"All in one go" mode
This is the first of three steps:
This is a reminder that for "Replace" it's always the whole hit list that is processed, not only the selection.
This is the second step:
This allows you to check whether everything is okay or not. Here we see a "compressed" report: it contains only the lines which would change plus the object names plus the headers for all traditional functions and operators in order to make checking local variables easy. The full report would show all lines of all objects involved. You cannot change anything at this stage.
This is the third and last step:
This allows you to either change and fix all objects or not.
One by one
In one-by-one mode you can check and edit a single object:
In the next step you can either fix the changes or skip this object and carry on with the next one or cancel the whole operation:
Project Page
For bug reports, future enhancements and a full version history see Fire/ProjectPage
Version Information
Original author: |
|
Responsible: |
|
Email: |