Quantcast
Channel: VFPX
Viewing all articles
Browse latest Browse all 3798

Updated Wiki: GoFish 5 Enhancements

$
0
0

GoFish 4 introduced the blindingly fast GoFish Search Engine.

In GoFish 5, the Search Engine is essentially unchanged, but a suite of improvements provide a range of new features: (I think that  the bold bullets below should be linked to their detail further on, but I always forget how to do that)

  • Saved Search History– You can now save the history of your searches, either automatically (for all searches) or selectively, and can restore the search parameters and results grid from these saved searches.  You can also selectively delete your saved searches or use the GF Janitor to automatically delete old ones.
  • Handling of PRG-based classes– Special attention has been paid to matches in PRG-based classes, which now are treated as much as possible like VCX-based classes. Their names appear in the “Class” column (are there other columns?) and also in the new category “Classes” in the Treeview.
  • Column Changes  – There are two new columns, “Parent Class VCX” and “Containing Class”; the column headings for some of the other columns have been reworded; and the contents of some of the class-related columns have been enhanced.
  • Treeview changes– There are a few new categories: “Classes”, “Menus”, and “Projects”. The “Classes” category, unlike all the other categories which have files as sub-nodes, has classes as the sub-nodes. 
  • More powerful filter options– You can filter on secondary matches in the code “in the neighborhood” (that is, in the same statement or same procedure) of the original match; the filter form has been re-organized to provide clarity; and filters can be combined using logical operators AND or OR.
  • Plug-In to control the grid display– You can set the use the plug-in to set the Dynamic* (or any other) properties of the grid. The sample provided changes the colors used for each row.
  • Other UI changes– There are many, many other UI changes, including the ability to select the location of the code preview window relative to the grid.

 

Saved Search History

You can save the history of your searches, either automatically (for all searches) or selectively, and can restore the search parameters and results grid from these saved searches.  When search results are restored, the results grid and all search parameters (as are now visible at top right of the form) are restored to their saved values. You can also selectively delete your saved searches or use the GF Janitor to automatically delete old ones.

On the Preferences page of the Options form you can enable the retention of your saved searches and also whether the most recent saved search is to be restored when you start GoFish.

SNAGHTML15ac047b

 

The context on the new “History” button includes those options and two others having to do with the last saved search.

image

 

Clicking the “History” button brings up the form from which you can choose which saved search to restore, showing when it was saved, what was searched for, what project or folder was searched, and how many matches were found.  Double-clicking a row causes the row to be restored.  You can also delete rows singly by clicking the row and then the “Delete” button

SNAGHTML15bb4071

 

You can also use the GoFish Janitor to automatically delete old searches by setting values on the Janitor page on the Options form.

image

 

Handling of PRG-based classes

Special attention has been paid to matches in PRG-based classes, which now are treated as much as possible like VCX-based classes. Their names appear in the “Class” column (are there other columns?) and also in the new category “Classes” in the Treeview.

 

Column Changes:

There are two new columns, “Parent Class VCX” and “Containing Class”.  While you can choose to display all 30+ columns in the results grid, the following columns (some with slightly modified captions) contain the most relevant search information.(perhaps re-ordered?  did I miss any)

  • Match Line
  • Match Type (“Code”, “Property Def”, “Method Def”, and so on)
  • Method/Property Name (name of the Method, Procedure, Method, or Property where match found)
  • Name (name of the object where match found … (any other use?  If not, why not “Object Name”?)
  • Class (in which match found, including both PRG ad VCX-based classes)
  • Base Class (of the object in which match was found)
  • Parent Class (of the object in which match was found)
  • Parent Class VCX (of the object in which match was found)
  • Containing Class
  • File Name
  • File Name with Path
  • Timestamp (for VCXs and SCXs, timestamp when the row in the VCX/SCX was saved)

 

    <!--EndFragment-->
    <!--EndFragment-->

Treeview Changes:

The Treeview on the left now has the following categories:

  • Classes
  • ClassLibs
  • Forms
  • Programs
  • Reports
  • Tables
  • Projects
  • Other

The “Classes” category shows the names of classes, found in either PRGs or VCXs.  Nodes for PRG-based classes only appear under the “Classes” category.  Nodes for VCX-based classes appear under the “Classes” category and also under the “ClassLibs” category.

As before, clicking on any node in the Treeview filters the results grid appropriately.

 

More powerful filter options

Special attention has been paid to matches in PRG-based classes, which now are treated as much as possible like

 

Plug-In to control the grid display

Special attention has been paid to matches in PRG-based classes, which now are treated as much as possible like

 

Other UI Changes

Special attention has been paid to matches in PRG-based classes, which now are treated as much as possible like


Viewing all articles
Browse latest Browse all 3798

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>