topbanner_forum
  *

avatar image

Welcome, Guest. Please login or register.
Did you miss your activation email?

Login with username, password and session length
  • Friday March 29, 2024, 4:27 am
  • Proudly celebrating 15+ years online.
  • Donate now to become a lifetime supporting member of the site and get a non-expiring license key for all of our programs.
  • donate

Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.


Messages - stahlworks [ switch to compact view ]

Pages: [1]
1
Depeche View Lite is a high speed text file search tool for source code, text data (XML, CSV, SQL) and log files.

Main features:
  • loads all text files of a folder into memory
  • shows all file contents in one window as one long text
  • fly over all text by dragging the mouse, like on a Smartphone
  • search as you type, across all files, instantly
  • search a word by clicking on it, instantly
  • side by side view of same text in multiple windows
  • no installation, instant use
  • Free for personal, non commercial use

[attach=#1][/attach]

The download is available here.


2
> Is there any reason the '*' in front of directory inclusions is needed? From the help it seems it is not required
> in the workspace options dialog, but it is from the command line?

the reason is: on the command line, you can specify two kinds of things can be supplied after -dir :
root directory names, and sub folder masks. the latter are identified by "!" or a wildcard "*" anywhere in their name.
For example,
-dir source include *.svn
loads text from root directories source and include if it's located within .svn sub folders.

In the workspace options dialog, it is not possible to supply multiple root directories in the sub directory filter,
as this would be too complicated. instead, every word in "sub directory filter" is auto prefixed by "*" internally,
to make sure it's used as a sub dir filter.

In a nutshell, the command line is more flexible, but for that it requires a more complex syntax.
And the GUI version is reduced but easier to use and understand.

> Would it be possible to add a recently used folder list of some kind?

I'll put it on the todo, but this will take some time.

What can be done right now, especially with DView Pro, is to simply load everything you might need together into memory,
with a long list of -dir folder1 folder2 folder3 -file ... -dir ... -file ... statements, or by specifying a fileset definition file
(dview -h then search for "defining filesets").

Even faster: create snapfiles with SFK, which are archive files containting many text files,
then load that with DView. Snapfiles can also be created from fileset definition files (sfk snapto=cache.txt -fileset myset.txt).

This way, I load a set of 20000 files everyday, containing everything I might need (sourcecode of multiple projects, include files
of different operating systems, open source libraries ...) and then I set the path mask to where I really need to search.

> use the open dialog instead of the browse for folder dialog

I use "GetOpenFileName" for the file open dialog, which cannot be used to select folders.
Also I don't see a big difference: no matter if you select "Load folder" or "Load file",
in both cases you can copy/paste a path into the given text entry field.

3
There is now a pre-release available for download here,
with completely reworked sub folder and file selection.
to select all dirs of current dir except something:
-dir . !foo       -> exclude subdirs like *foo*
-dir . !.foo      -> exclude with extension .foo
-dir . !\foo      -> exclude starting with foo
-dir . !foo\      -> exclude ending with foo
-dir . !\foo\     -> exclude exactly foo
-dir . !\foo\bar\ -> exclude subdir combi
-dir . !*.foo*    -> exclude with .foo anywhere

to select only sub dirs of current dir with something:
-dir . *foo*      -> include paths having *foo*
-dir . *\foo      -> include paths having *\foo
-dir . *foo\      -> include paths having *foo
-dir . *\foo\     -> include paths exactly foo
-dir . *.foo      -> include with extension .foo
-dir . *\foo\bar\ -> include subdir combi

exclusion by filename:
-file !foo        -> exclude all files like *foo*
-file !\foo       -> exclude starting with foo
-file !foo\       -> exclude ending with foo
-file !\foo\      -> exclude exactly foo
-file !.foo       -> exclude extension foo

inclusion by filename:
-file foo         -> include all files like *foo*
-file \foo        -> include starting with foo
-file foo\        -> include ending with foo
-file \foo\       -> include exactly foo
-file .foo .bar   -> select .foo and .bar files
whoever cares, please test:
- loading from command line using -dir ... -file ... parameters.
- running dview without parameters, then configure Setup / Workspace, then load interactively.
- the help text, as shown in Setup / Workspace.
- the help text via help button, then search for "loading filters".
give feedback if the functionality is working as expected, and if it matches the documentation.

4
Please create a config file, then search for "run" or "runback".
I use DView everyday in a multi server environment, running batch files that sync source files to a server,
run a remote compile, then download the results and display that in DView. For example,
on key xbutton1up
   set first.findmask = ""
   set first.pathmask = "c:\project\log.txt"
   first.runback -min "c:\project\zz-compile.bat"
   first.monitor "c:\project\log.txt" delay=300 maxwait=5000 show=bottom
Runs a batch on the 2nd top button of a Razer Naga mouse.
This batch produces an output file "log.txt" which is reloaded and displayed
in the first DView window as long as the file changes.

You may test this all with the 30-days Trial Demo from:
http://stahlworks.co...ViewProDemoSetup.exe

To repeat, this is typically used to call batch files; try yourself if it allows a smooth
TFS integration, and if you think external command execution could be done better,
please give feedback.

5
No, that's good, you even analyzed all possible workarounds yourself already. Fact is,

> It seems like there is no way to exclude an exact folder name that is a direct subfolder of the
> root of the tree that dview reads?

is true and this is a shortcoming that will be fixed - not just in DView, but also in my command line tool SFK.
I'll keep you updated when it is done!

6
OK, as it is now, it makes a difference if you

1) load something instantly when running DView from the command line

2) or run DView without parameters, and then load something interactively by "Open",
   or by reloading the workspace from Setup.

In case 1), DView will ignore your Setup / workspace filter settings.
This is because you should specify all filters directly on the command line.
Please try this:

   
dview -dir . !*.hg

And it should work. The whole formal syntax is:

   
dview -dir rootFolder1 [root2] ... [!dirmask1] [!dirmask2] ...
         -file includePattern [include2] ... [!excludePattern] ...

You may also download the Swiss File Knife, then type sfk help select or sfk list
for syntax and examples of file selection - but I see that neither the DView or SFK help text
tell anything about the exclusion of sub folders by file extension. This will be fixed.

7
If you add literally "!\.hg" it will skip all sub folders called exactly ".hg" but not, for example, "foo.hg".
If that's what you intend, it should work.

According to SFK syntax (which DView uses), if you add instead "!.hg" it should skip all sub folders
ending with ".hg". However, there is a bug somewhere, so actually that doesn't work right now.

But you may use this workaround: "!*.hg" and then it should skip all sub folders ending with ".hg".

Please try and give feedback.

8
Announce Your Software/Service/Product / Version 1.5.0 released
« on: September 14, 2011, 11:35 PM »
Version 1.5.0 was released,
featuring reduced text file loading times (about 50 percent with DView Lite).

When using the global search autosuggest dictionary with DView Pro (or Pro Demo),
loading times are reduced even more, as the dictionary is now created after loading.

9
Release 1.4.9 is about making it easier for first time users.
By default, DView comes with a new assistance mode.

   -  left click on a word brings up a search popup menu: search this word now,
      search it in a different window, copy to clipboard, create bookmark, ...

      You may also mark a phrase: left button down on first word, keep button pressed,
      move to the right to another word, then release button. Again the menu comes up.

   -  right click on blank space produces a navigation menu: jump to next/previous search result,
      jump to next file, narrow search to current file ...

   -  right click on blank space in a filtered result view produces another menu:
      show that text location, show it in another window, ...

   -  extra buttons at the right top: filter text for results, jump to next/previous result.

   -  scrollbars in every window.

[attach=#1][/attach]

Experienced DView users may prefer to work without assistance, as it takes more clicks to run a search,
and one click search is not possible. Therefore this can all be switched off in different ways,
the fastest one being to press CONTROL+SHIFT+P (power settings).

10
I use Fruityloops or FL Studio since 10 years now. I like their pattern based composing, and it also has powerful software synths.

11
Yes, the whole site content is from me, therefore "Art and Technology".
I try to get some web hits through the desktop backgrounds and stuff.



You may type "dview . .py" to load all .py files, then type "def primesbelow" interactively.

The find command above can be reformulated using Swiss File Knife like:
sfk find -dir . -file .py -pat "def primesbelow" +view

or shorter, searching all text files of the current directory tree:
sfk ftext . "def primesbelow" +view


12
Dear coders,

I want to introduce my source code viewer, Depeche View.

Main features:
  • loads all text files of a folder into memory,
    showing all content in one window, as if they were one large text.
  • search as you type, across all files.
  • may show only the result lines (filtered view).
  • side by side view of same text in multiple windows.
  • portable, without installation.

[attach=#1][/attach]

The freeware version, Depeche View Base, is available here:

http://stahlworks.co...ev/depeche-view.html

It allows to load up to 1000 files, and can be sufficient for medium size projects
if you always edit and compile within some IDE running in parallel.

Depeche View has a radical input concept different to any IDE or editor.

The most important moves are:
  • SHIFT key and mouse click on a word searches it in the same window.
  • RIGHT click on a word searches it in a different window.
  • CONTROL click on a phrase or lines copies to clipboard.
  • ALT click on a phrase creates a bookmark.
  • left click on blank space, keep mouse button pressed,
    then move the mouse vertical to surf through the text.

This requires a bit of training, but then it allows to click through
dependencies in software projects very fast.

I would be happy about any comment, especially about
the pros and cons of the user interface.

Pages: [1]