anjuta r4172 - in trunk: . manuals/anjuta-manual manuals/anjuta-manual/C manuals/anjuta-manual/C/figures

[sgranjoux svn gnome org]

Author: sgranjoux
Date: Thu Aug 21 15:53:10 2008
New Revision: 4172
URL: http://svn.gnome.org/viewvc/anjuta?rev=4172&view=rev

Log:
	* manuals/anjuta-manual/C/debugger.xml,
	(deleted) manuals/anjuta-manual/C/figures/arguments.png,
	manuals/anjuta-manual/C/projects.xml,
	manuals/anjuta-manual/Makefile.am:
	Update debugger documentation


Removed:
   trunk/manuals/anjuta-manual/C/figures/arguments.png
Modified:
   trunk/ChangeLog
   trunk/manuals/anjuta-manual/C/debugger.xml
   trunk/manuals/anjuta-manual/C/projects.xml
   trunk/manuals/anjuta-manual/Makefile.am

Modified: trunk/manuals/anjuta-manual/C/debugger.xml
==============================================================================
--- trunk/manuals/anjuta-manual/C/debugger.xml	(original)
+++ trunk/manuals/anjuta-manual/C/debugger.xml	Thu Aug 21 15:53:10 2008
@@ -45,42 +45,57 @@
   <sect2 id="debug-run">
    <title>Running an executable</title>
    <para>
-    Choose the menu item
-    <menuchoice><guisubmenu>Debug</guisubmenu><guimenuitem>Run Target&hellip;</guimenuitem></menuchoice>
-    to display a dialog box where you can select:
-    <itemizedlist>
-     <listitem><para>The program that you want to debug</para></listitem>
-     <listitem><para>The command line parameters</para></listitem>
-     <listitem><para>If you want a terminal or not (the Anjuta terminal plugin is used)</para></listitem>
-     <listitem><para>If you want to stop the program at the beginning or not</para></listitem>
-    </itemizedlist>
-   </para>
-   <para>
-    The drop-down menu of the target drop-down combination box 
-    is already filled with all executables of the current project. But you
-    can select another executable not part of the project. The debugger accepts libtool
-    executable, it means script,generated by libtool, wrapping the real executable.
-    Note that an URI is expected here, not a file path even if the debugger currently
-    supports only local files.
-   </para>
-   <para>
-    When you have set everything you can click on <guibutton>Execute</guibutton>
-    to start the debugger, load your program and stop at its beginning if requested.
+     Running a program with or without the debugger uses the same menu, selects  
+     <menuchoice><guisubmenu>Run</guisubmenu><guimenuitem>Run Program</guimenuitem></menuchoice> 
+     to run a program without the debugger and
+     <menuchoice><guisubmenu>Run</guisubmenu><guimenuitem>Debug Program</guimenuitem></menuchoice>
+     to run it with the debugger.
    </para>
    <note>
     <para>
      In order to better user the debugger, it is strongly recommended to debug program
-     with debugging information (-g for gcc) and no optimization (-O0 for gcc).
+     with debugging information (-g for gcc) and no optimization (-O0 for gcc). This can be
+     done by selecting the Debug configuration before building the program for the first time.
     </para>
    </note>
+   <para>
+    You can select which program to run and its environment using
+    <menuchoice><guisubmenu>Run</guisubmenu><guimenuitem>Program Parameters&hellip;</guimenuitem></menuchoice>. 
+    You can choose:
+    <itemizedlist>
+     <listitem><para>The program that you want to debug</para>
+      <para>
+       The drop-down menu of the target drop-down combination box 
+       is already filled with all executables of the current project. But you
+       can select another executable not part of the project. The debugger accepts libtool
+       executable, it means script,generated by libtool, wrapping the real executable.
+       Note that an URI is expected here, not a file path even if the debugger currently
+       supports only local files.
+      </para>
+     </listitem>
+     <listitem><para>The command line parameters</para></listitem>
+     <listitem><para>The program working directory</para></listitem>
+     <listitem><para>Add or remove some environment variables</para>
+      <para>
+       The environment variables in light gray are the current environment variables. You can
+       add new one, modify existing one or remove their values.
+      </para>
+      <tip>
+       To debug Anjuta using Anjuta, you can use a different theme to recognize the
+       instance under debugging immediatly adding by example "GTK2_RC_FILES=/usr/share/themes/Crux/gtk-2.0/gtkrc".
+      </tip>	
+     </listitem>
+     <listitem><para>If you want a terminal or not (the Anjuta terminal plugin is used)</para></listitem>
+    </itemizedlist>
+   </para>
   </sect2>
 	
   <sect2 id="debug-attach">
   <title>Attaching to a Process</title>
    <para>
     It is also possible to attach to a running process and debugging it by choosing the menu item
-    <menuchoice><guisubmenu>Debug</guisubmenu>
-	<guimenuitem>Attach to Process &hellip;</guimenuitem></menuchoice>. A list of all the
+    <menuchoice><guisubmenu>Run</guisubmenu>
+	<guimenuitem>Debug Process &hellip;</guimenuitem></menuchoice>. A list of all the
     process running on the system will appear. 
    </para>
    <figure id="attach">
@@ -102,25 +117,14 @@
    </note>
   </sect2>
   
-  <sect2 id="debug-restart">
-   <title>Restarting an executable</title>
-   <para>
-    After running an executable at least one time, you can
-    choose the menu item <menuchoice><guisubmenu>Debug</guisubmenu>
-    <guimenuitem>Restart Target</guimenuitem></menuchoice> to restart your program.
-    It is just a shortcut that will stop the debugger if it is currently running
-    and restart it with the last executable without displaying the start dialog.
-   </para>
-  </sect2>
-
   <sect2 id="debug-stop">
    <title>Stopping the Debugger</title>
-   <para>
-    Choose the menu item <menuchoice><guisubmenu>Debug</guisubmenu>
-    <guimenuitem>Stop Debugger</guimenuitem></menuchoice> to stop the debugger.
-    This option will kill the program which is being debugged. If the debugger has
-    been attached to a running process, it will just detach from it without killing
-    it. You will get a confirmation box if a program is currently attached or running.
+    <para>
+     Choose the menu item <menuchoice><guisubmenu>Run</guisubmenu>
+     <guimenuitem>Stop Debugger</guimenuitem></menuchoice> to stop the debugger.
+     This option will kill the program which is being debugged. If the debugger has
+     been attached to a running process, it will just detach from it without killing
+     it. You will get a confirmation box if a program is currently attached or running.
    </para>
   </sect2>
 

Modified: trunk/manuals/anjuta-manual/C/projects.xml
==============================================================================
--- trunk/manuals/anjuta-manual/C/projects.xml	(original)
+++ trunk/manuals/anjuta-manual/C/projects.xml	Thu Aug 21 15:53:10 2008
@@ -977,31 +977,4 @@
     </para>
    </sect2>
   </sect1>
- <sect1 id="executing-program">
- <title>Executing program</title>
-   <para>
-    Once an executable is ready after the build, you can execute it by choosing the menu item
-    <menuchoice><guisubmenu>Build</guisubmenu><guimenuitem>Execute</guimenuitem></menuchoice>, 
-    or pressing <keycap>F3</keycap>. You can specify which executable you want to use in case your project
-    provides more than one and specify command line arguments. 
-   </para>
-   <note>
-   <title>Dependencies</title>
-   <para>
-    Unlike the build stage, execution doesn't check for dependencies 
-	(at least for the time being). In other words, it does not check if the 
-	executable is up-to-date before it executes the program. 
-	So, <emphasis>you must take care of that yourself.</emphasis>
-   </para>
-   </note>
-   <para>
-  </para>
-  <figure id="params">
-   <title>Choose executable and set program parameters</title>
-   <screenshot>
-   <screeninfo>Setting program parameters</screeninfo>
-    <graphic fileref="figures/arguments.png" format="PNG" srccredit="jhs"></graphic>
-   </screenshot>
-  </figure>
- </sect1>
  </chapter>

Modified: trunk/manuals/anjuta-manual/Makefile.am
==============================================================================
--- trunk/manuals/anjuta-manual/Makefile.am	(original)
+++ trunk/manuals/anjuta-manual/Makefile.am	Thu Aug 21 15:53:10 2008
@@ -8,7 +8,6 @@
 DOC_AM_CPPFLAGS =
 DOC_FIGURES = figures/add_edit_macro.png \
               figures/anjuta-in-action.png \
-              figures/arguments.png \
               figures/attach.png\
               figures/brk_add.png\
               figures/brk_dlg.png\