Differences between revisions 7 and 25 (spanning 18 versions)
⇤ ← Revision 7 as of 2012-01-17 20:20:38 →
Size: 2790
Editor: KaiJaeger
Comment:
← Revision 25 as of 2017-07-11 10:03:21 → ⇥
Size: 3684
Editor: KaiJaeger
Comment:
Deletions are marked like this. Additions are marked like this.
Line 1: Line 1:
== Fire == = Fire =

~-<<SeeSaw(section="table-of-contents", show="true", seesaw="false", toshow="<<(Show>> table-of-contents)", tohide="<<(Hide>> table-of-contents)", speed="Slow")>>-~
Line 5: Line 7:
/!\ Under construction {{{Fire}}} is part of the CategoryAplTree project.
Line 7: Line 9:
'''''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.

== Preconditions ==

Preconditions changes with version, there see the [[Fire/ProjectPage|project page]] for details.
Line 15: Line 21:
 * 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 restrict the search by:
    * ignoring code
    * ignoring comments
    * ignoring text (=everything between quotes)
 * Use regular expression in your search string (`⎕S, ⎕R`)
 * Negate a search ("every object that does '''not''' contain...)
 * Search only the hits of the last search		  * You can restrict the search to one or more of these:
    * Functions, operators, classes, interfaces and namespace scripts.
    * Name search (`⎕NL`).
 * You can search any combination of
    * the APL source code (that's everything but stuff within quotes (text) and comments.
    * comments.
    * text.
 * Negate a search ("all objects that do '''not''' contain...").
 * Search only the hits of the last search.
Line 30: Line 31:
== Difference between Dyalog's build-in Search tool and Fire == == Difference between Dyalog's built-in Search tool and Fire ==
Line 33: Line 34:
 * Fire reports a WS FULL only when it is reasonable to do so
Line 40: Line 42:
Specifying anything into the "Start looking here" control is supported by autocomplete: this box offers all ordinary namespaces matching the characters in "Start looking here". 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".
Line 43: Line 45:

After having performed a search one might want to look at the lines carrying the hits. This can be achieved by selecting the "Report hits" menu command from the "Report" menu:

{{attachment:HitReport.png}}

The report offers a context menu on the items of the left:

{{attachment:ReportHitsContextMenu.png}}
Line 50: Line 61:
There are two mode available: There are two modes available:
Line 52: Line 63:
 * 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 55: Line 66:
==== Batch mode ==== ==== "All in one go" mode ====
Line 57: Line 68:
This is the first step of three steps in Batch mode:

This is the first of two steps in Batch mode:		 When you select the "Preview" button you get this:
Line 63: Line 72:
It allows you to check whether everything is okay or not. Here we see a "compressed" report: it contains only the potentially changed lines. 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. You cannot change anything at this stage but you can exclude certain objects from the "Replace" operation by un-ticking the check box.
Line 69: Line 78:
This allows to either fix all changes objects or discard the changes. This allows you to either change and fix all objects or not.
Line 77: Line 86:
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 85: Line 94:
== How to get Fire ==

 * Download the zip file (link see below)
 * Unzip it
 * Read `HowToInstall.html` and follow the instructions
Line 91: Line 106:
----
CategoryAplTree

Fire

(Hide table-of-contents)

Contents

  1. Fire
    1. Preconditions
    2. Features
    3. Difference between Dyalog's built-in Search tool and Fire
    4. Fire's GUI
      1. Main Window
      2. The "Replace" feature
        1. "All in one go" mode
        2. One by one
    5. Project Page
    6. How to get Fire
    7. Version Information

Fire is part of the CategoryAplTree project.

fire.png Fire stands for FInd and REplace. It's designed to search and replace strings in the workspace.

Preconditions

Preconditions changes with version, there see the project page for details.

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:
    • Functions, operators, classes, interfaces and namespace scripts.

    • Name search (⎕NL).

  • You can search any combination of
    • the APL source code (that's everything but stuff within quotes (text) and comments.
    • comments.
    • text.

  • Negate a search ("all objects that do not contain...").

  • Search only the hits of the last search.

Difference between Dyalog's built-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

Fire_01.png

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".

Fire_02.png

After having performed a search one might want to look at the lines carrying the hits. This can be achieved by selecting the "Report hits" menu command from the "Report" menu:

HitReport.png

The report offers a context menu on the items of the left:

ReportHitsContextMenu.png

The "Replace" feature

The Replace feature allows you to change the workspace on a global level:

Replace.png

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

When you select the "Preview" button you get this:

Batch_02.png

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. You cannot change anything at this stage but you can exclude certain objects from the "Replace" operation by un-ticking the check box.

This is the second and last step:

Batch_03.png

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:

OneByOne_01.png

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:

OneByOne_02.png

Project Page

For bug reports, future enhancements and a full version history see Fire/ProjectPage

How to get Fire

  • Download the zip file (link see below)
  • Unzip it

  • Read HowToInstall.html and follow the instructions

Version Information

Original author:

KaiJaeger

Responsible:

KaiJaeger

Email:

kai@aplteam.com

CategoryAplTree

Fire (last edited 2018-03-03 11:50:12 by KaiJaeger)