tweak documentation

VDServer.cs: remove debug message box

Author: rainers

doc/Editor.dd

@@ -50,34 +50,91 @@ $(PRE
 string
 )
 
-$(H2 More features)
+$(H2 Code Completion and Navigation)
+$(P Selecting "Open Language options" from the Visual D Menu will take you directly to the global options page
+for code completion.
+)
+   $(IMG_CENTER images/intellisense_options2.png)
 
+This is where you can configure what happens if you want to see code completion.
 
-You might want to check the following features:
 $(UL
- $(LI simple word-completion will show identifiers in the vicinity of the caret from the same buffer (default short-cut Ctrl-Space). If you press the short-cut again, identifiers from JSON files are also displayed.)
- $(LI import statement completion: pressing Ctrl-Space in an import statement will complete the token from the files and folders available in the import directories.
+  $(LI Expansions from semantic analysis:
+    the semantic engine will try its best to figure out the current scope of the edited text and
+    find valid identifiers. If no matching identifier is found or if you trigger expansion again,
+    expansions from the text buffer or JSON browse information will be added.
+  )
+  $(LI Expansions from text buffer:
+    completion will show identifiers in the vicinity of the caret from the same buffer 
+    (default short-cut Ctrl-Space). If no matching identifier is found or if you press the short-cut 
+    again, identifiers from JSON files are also displayed.
+  )
+  $(LI Expansions from JSON browse information:
+    completion will show matching identifiers from the compiler generated JSON files. No information
+    about the current edit scope will be used.
+  )
+  $(LI Show expansion when: sets the trigger for showing the code completion popup. Using a mode
+    that displays completion more often also includes the other triggers, i.e. hitting Ctrl+Space is
+    always possible to display completions.
+  )
+  $(LI Show type of expressions in tool tip:
+    Display information about the hovered identifier in a tool tip.
+  )
+  $(LI Use semantic analysis for "Goto Definition":
+    goto definition (default short-cut F12) can either request the location of the definition of
+    a symbol from the semantic engine or takes information from compiler generated JSON files.
+    A successful build with JSON output enabled is necessary for the laytter. JSON files can also 
+    be precompiled and placed into the directories given in the $$(DDLINK GlobalOptions,global options).
+    If there are multiple 
+    definitions for the identifier at the caret position, the $(DDLINK Search,Search Window) will show up.
+  )
+  $(LI Use Alexander Bothe's D parsing engine:
+    Use the semantic engine that also powers Mono-D and D-IDE. It is more powerful than the 
+    engine that is part of Visual D. You must have installed it from within the Visual D installer.
+  )
+)
+
+$(P Triggering completion an import statement will always complete the token from the files and folders available 
+in the import directories.
    $(IMG_CENTER images/import_completion.png)
  )
- $(LI goto definition (default short-cut F12) takes information from compiler generated JSON files. A successful build with JSON output enabled is necessary for this function. JSON files can also be precompiled and placed into the directories given in the global options. If there are multiple definitions for the identifier at the caret position, the [wiki:Tour/Search Search Window] will show up.)
+
+$(H2 More features)
+
+You might want to check the following features:
+$(UL
  $(LI smart indentation will indent nicely after pressing Return. )
  $(LI comment/uncomment a selection of lines)
  $(LI highlight/jump-to matching braces (default shortcut Ctrl-$(ACUTE)))
- $(LI code snippets: let's you select from a list of snippets, some of them allowing token replacements (default shortcut Ctrl-K Ctrl-X). You can also insert code-snippets by writing its shortcut, then pressing the key for command "Edit.!InvokeSnippetFromShortcut". For example, shortcut "for" yields
+ $(LI code snippets: let's you select from a list of snippets, some of them allowing token 
+   replacements (default shortcut Ctrl-K Ctrl-X). You can also insert code-snippets by writing its 
+   shortcut, then pressing the key for command "Edit.!InvokeSnippetFromShortcut". For example, 
+   shortcut "for" yields
    $(IMG_CENTER images/codesnippet.png)
  )
- $(LI parameter info tooltips (default short-cut Ctrl-Shift-Space) showing function prototype and highlighting current position in argument list. As with "goto definition" this feature relies on JSON files being generated.
+ $(LI parameter info tooltips (default short-cut Ctrl-Shift-Space) showing function prototype and 
+   highlighting current position in argument list. As with "goto definition" this feature relies 
+   on JSON files being generated.
    $(IMG_CENTER images/parameterinfo.png)
  )
- $(LI show scope in status line: to avoid navigating through a larger file to figure out what class the current function belongs to, command "VisualD.!ShowScope" displays the class, function, etc. at the caret position:
+ $(LI show scope in status line: to avoid navigating through a larger file to figure out what 
+   class the current function belongs to, command "VisualD.ShowScope" displays the class, function, 
+   etc. at the caret position:
    $(IMG_CENTER images/showscope.png)
    This command is also accessible from the Visual D menu, but it is best to assign it to some keyboard shortcut.
  )
  $(LI Outlining of curly braced declarations and statements and multi-line comments
    $(IMG_CENTER images/outlining.png)
-   Automatic outlining can be disabled on the global configuration page "Tools->Options->Text Editor->D->Colorizer". Using command "Outlining->Collapse to Definitions" will enable it for the current text buffer.
+   Automatic outlining can be disabled on the global configuration page 
+   "Tools->Options->Text Editor->D->Colorizer". Using command "Outlining->Collapse to Definitions" 
+   will enable it for the current text buffer.
  )
- $(LI show the clipboard ring in a context menu to paste from. This operation is invoked by the "Edit->Cycle Clipboard Ring" command.
+ $(LI Two commands are added to the "Edit->Outlining" menu: "Collapse unittests" will fold away 
+   unittest blocks that might obfuscate the actual code if they become excessive. "Collapse disabled code" 
+   will hide code blocks actually not compiled due to version or debug conditions helping you concentrate on
+   the active code.)
+ $(LI show the clipboard ring in a context menu to paste from. This operation is invoked by 
+   the "Edit->Cycle Clipboard Ring" command.
    $(IMG_CENTER images/pastemenu.PNG)
  )
 )

doc/GlobalOptions.dd

@@ -35,12 +35,26 @@ $(UL
     that the compiler is found as <DMD install path>\bin\ldc2.exe )
   )
  )
- $(LI Executable paths: Directories to be added to the PATH environment variable before executing build commands.)
  $(LI Import paths: Directories to be added to the import paths specified in the project configuration and in the
       DMD configuration file (also used for import statement completion and finding symbol definition).)
+ $(LI Executable paths: Directories to be added to the PATH environment variable before executing build commands.)
  $(LI Library paths: Directories to be added to the LIB environment variable before executing build commands.)
 )
-
+Executable and library search paths are given depending on the target architecture. When using DMD for Win64,
+options from its configuration file can be overwritten by specifying the linker to be used and additional options.
+$(UL
+ $(LI override sc.ini: $(P The latest Windows installer for DMD modifies the default sc.ini by expanding variables
+   according to the most recent Visual C++ installation and Windows SDK installation directories. This is necessary
+   to allow building Win64 executables from the command line without having additional environment variables set.
+   Unfortunately this makes it difficult to use libraries from the current Visual C++ installation if you have
+   multiple Visaul Studio versions installed.
+   )
+   $(P Enabling this option allows to override the linker settings from sc.ini. At the same time the
+    library search paths are added to the command line.
+    Also note that using a 32-bit linker executable is necessary to monitor link dependencies.
+   )
+ )
+)
 $(P Available text replacements: )
 $(UL
  $(LI $(DOLLAR)(DMDINSTALLDIR): DMD Install path from the "DMD directories page" )
@@ -49,12 +63,13 @@ $(UL
  $(LI $(DOLLAR)(WINDOWSSDKDIR): Windows SDK Directory )
  $(LI $(DOLLAR)(DEVENVDIR): Directory of Visual Studio executable devenv.exe )
  $(LI $(DOLLAR)(VSINSTALLDIR): Root directory of Visual Studio installation )
+ $(LI $(DOLLAR)(VCINSTALLDIR): The directory of the Visual C installation that comes with the running Visual Studio)
  $(LI $(DOLLAR)(VISUALDINSTALLDIR): Installation folder of Visual D )
  $(LI any variable from the system environment enclosed in $(DOLLAR)() )
 )
 
 $(P Please note that you'll also find a new entry "D" in the Text Editor branch to setup 
-[wiki:Tour/Editor syntax highlighting] and more. )
+$(DDLINK Editor,syntax highlighting) and more. )
 
 Macros:
 	TITLE=Global Options

doc/images/dmd_directories.png

@@ -154,7 +154,7 @@ public void ConfigureSemanticProject(string filename, string imp, string stringI
 		}
 		public void ClearSemanticProject()
 		{
-			MessageBox.Show("ClearSemanticProject()");
+			//MessageBox.Show("ClearSemanticProject()");
 			//throw new NotImplementedException();
 		}
 		public void UpdateModule(string filename, string srcText, bool verbose)