The current SkookumIDE does not have a "find all in files" though it eventually will.
We didn't want to spend a lot of time reinventing the wheel with such common features so we tried to make it easy to integrate existing tools with the SkookumIDE.
The quickest way to get "find all in files" working with the current SkookumIDE is to associate another text editor with
.sk files. (I use Notepad++ it is pretty good and free.) Then when you are in the SkookumIDE and on some
.sk file in the Console workspace or some other file in the Browser editor you can press the
Ehotkey and it will open it with that
.sk associated editor.
Then you can use all the many features of your other editor including "find all in files".
You can add all sorts of SkookumScript superpowers to other editors including toggling back to the SkookumIDE.
Also check out this post which discusses the related topic of enabling another text editor to run SkookumScript commands just like the SkookumIDE Console.
Symbolic Searching (Goto)
[Note this is in the old SkookumIDE that uses the WinAPI for its UI. The new SkookumIDE that uses the Slate API for its UI does its searching by looking for substrings typed into the search field at the top of the "Classes" and "Members" tabs.]
The SkookumIDE (old WinAPI UI) does have a symbolic search mechanism to find the source for a particular class, data member or routine. This is probably the reverse that you are looking for though it is very useful. There are several variations and you can see all of them by looking at the SkookumIDE "Goto" menu.
The simplest way to use it is to press
G on some text in the SkookumIDE workspace or editor. (If you are familiar with it, this is similar to Visual Assist.) It will pop you right to where that class, data member or routine is defined. You can also use the "Goto" menu or its various hotkeys to bring up a dialog to specify what you want to search for. For example
G searches for routine matches and
C searches for class matches. Once the "Go To" dialog is up you can press other hot keys to change its mode.
Here are the rules used by the symbolic search:
abc plain text will try to match anything that has it as a sub-string
abc* ending with an asterisk
* indicates that matches should start with the sub-string
*abc starting with an asterisk
* indicates that matches should end with the sub-string
"abc" quoted text looks for an exact symbol match and not a sub-string.
MyClass.abc an initial class will only look for matches in classes that match the initial text - which may also follow the same rules
If a single match is found it will immediately jump to the match. If multiple matches are found then a list of matches will be displayed. If you right mouse click on a match in the list you can see a number of choices that you can make including a double click to jump to that particular match.