How to do things
AI Noob vs. Pro

List biggest files
List newest files
Show subdir sizes
Search in files
Replace word in files
List dir differences
Send files in LAN

Free Open Source:

Swiss File Knife

a command line
multi function tool.

remove tabs
list dir sizes
find text
filter lines
find in path
collect text
instant ftp or
http server
file transfer
send text
patch text
patch binary
run own cmd
convert crlf
dup file find
md5 lists
fromto clip
split files
list latest
compare dirs
save typing
trace http
echo colors
head & tail
dep. listing
find classes
speed shell
zip search
zip dir list

Depeche View
Source Research
First Steps

windows GUI

command line
file encryption

free external tools,
zero install effort,
usb stick compliant:

zip and unzip
diff and merge
reformat xml
reformat source

cpp sources

log tracing
mem tracing
using printf


stat. c array
stat. java array
var. c array
var. java array
view all text
as you type
surf over text
find by click
quick copy
multi view
find nearby
find by path
location jump
skip accents
clip match
filter lines
edit text
load filter
hotkey list
receive text
send in C++
send in Java
smooth scroll
touch scroll
fly wxWidgets
fly over Qt
search Java

Defining A Workspace: How to define in detail from where to load text files,
i.e. from which directories, and from which file groups within those directories. how to load only specific file types

If you open or append a directory by a button click, ALL text files from within that directory tree will be loaded. In many cases, this is too much. Especially when searching in a huge source code base, you may want to load all .java or .cpp files, but not every .xml or .tmp file.

defining filesets

This can be achieved by defining "file sets", which are simply text files containing

- directory names to include or exclude

- filename patterns or extensions to include or exclude

-------- file mywork1.txt begin ----------

      # within this directory tree
      -dir  mysrc\baselib

         # take .h .c .txt files
         # but exclude .hpp and .cpp
         -file .h .c .txt !.hpp !.cpp

      # within this directory tree
      -dir  mysrc\foobank

         # exclude all save and tmp dirs

         # then take only .hpp and .cpp files
         -file .hpp .cpp

      # from this directory tree
      -dir  mysrc\formats

         # take all files except .bak
         -file -all !.bak

-------- file mywork1.txt end ----------
As you may guess, lines having '#' as first character are remarks.

using workspace definitions from the command line

So the above fileset defines 3 directories, and what to load and not to load from those directories. Now copy the above text into a file "mywork1.txt", then run dview from the command line:

dview -fileset mywork1.txt

And dview will load the text files as defined in mywork1.txt.

using workspace definitions when starting by icon

But you may also create a Depeche View Icon on the desktop, via the Icon button, then open the Icon properties, and change the Icon's "target" field. For example, if dview is located in C:\app\bin, you may change it to

C:\app\bin\dview.exe -cfg1 -fileset mywork1.txt

Then, a double click onto that icon will load that workspace. (-cfg1 is not strictly required, but recommended as it tells the tool that it's started by an Icon.)

bookmark filename definition with filesets

When using filesets, what will be the bookmark filename? Just as if you say "-dir mydir1 -dir mydir2" on the commandline, the first directory tree will be taken to build the bookmark file base name, all others will be ignored.

In the example

      -dir  mysrc\baselib
         -file .h .c .txt !.hpp !.cpp

      -dir  mysrc\foobank
         -file .hpp .cpp

      -dir  mysrc\formats
         -file -all !.bak

the bookmark filenames would be

If you want to locate the bookmarks somewhere else, use the -book option as described here.

using plain filename lists

Sometimes you may want to load files whose names are listed in a simple text file, called a file list. This can be done by

dview -flist names.txt

Next chapter: Tips and Tricks.