Differences between revisions 12 and 14 (spanning 2 versions)
Revision 12 as of 2012-03-20 11:25:29
Size: 3143
Editor: KaiJaeger
Comment:
Revision 14 as of 2012-04-27 07:52:19
Size: 3017
Editor: KaiJaeger
Comment:
Deletions are marked like this. Additions are marked like this.
Line 26: Line 26:
 * Use regular expression in your search string (`⎕S, ⎕R`)
Line 30: Line 29:
== Difference between Dyalog's build-in Search tool and Fire == == Difference between Dyalog's built-in Search tool and Fire ==
Line 68: Line 67:
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 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.

Fire

fire.png 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
  • 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

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

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:

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.

This is the third 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

Version Information

Original author:

KaiJaeger

Responsible:

KaiJaeger

Email:

kai@aplteam.com


CategoryAplTree

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