[anjuta] Review of pages existing so far
- From: Sebastien Granjoux <sgranjoux src gnome org>
- To: commits-list gnome org
- Cc:
- Subject: [anjuta] Review of pages existing so far
- Date: Sun, 1 May 2011 20:50:47 +0000 (UTC)
commit a3ba627b9f65e694d77b096d564c1c5b19eacaf0
Author: Philip Chimento <philip chimento gmail com>
Date: Thu Apr 28 23:28:43 2011 +0200
Review of pages existing so far
manuals/anjuta-manual/C/anjuta-build-run.page | 2 +-
.../anjuta-manual/C/anjuta-code-indentation.page | 2 +-
manuals/anjuta-manual/C/anjuta-code-symbols.page | 2 +-
manuals/anjuta-manual/C/anjuta-debug-crash.page | 2 +-
manuals/anjuta-manual/C/anjuta-glade-signals.page | 4 +-
.../anjuta-manual/C/autotools-project-backend.page | 30 ++++++------
.../anjuta-manual/C/directory-project-backend.page | 22 ++++----
manuals/anjuta-manual/C/introduction.page | 8 ++--
.../anjuta-manual/C/makefile-project-backend.page | 24 +++++-----
manuals/anjuta-manual/C/project-import.page | 33 +++++++------
manuals/anjuta-manual/C/project-manager-file.page | 23 +++++----
.../anjuta-manual/C/project-manager-library.page | 45 +++++++++---------
.../anjuta-manual/C/project-manager-module.page | 49 ++++++++++----------
.../anjuta-manual/C/project-manager-package.page | 20 ++++----
.../anjuta-manual/C/project-manager-target.page | 22 ++++----
manuals/anjuta-manual/C/project-manager.page | 10 ++--
manuals/anjuta-manual/C/project-wizard-create.page | 27 ++++++-----
.../anjuta-manual/C/project-wizard-template.page | 8 ++--
18 files changed, 170 insertions(+), 163 deletions(-)
---
diff --git a/manuals/anjuta-manual/C/anjuta-build-run.page b/manuals/anjuta-manual/C/anjuta-build-run.page
index f57fe1c..fb764c5 100644
--- a/manuals/anjuta-manual/C/anjuta-build-run.page
+++ b/manuals/anjuta-manual/C/anjuta-build-run.page
@@ -11,7 +11,7 @@
</credit>
</info>
- <title>Running your application</title>
+ <title>Run your application</title>
<section>
<title>Configure the program parameters</title>
diff --git a/manuals/anjuta-manual/C/anjuta-code-indentation.page b/manuals/anjuta-manual/C/anjuta-code-indentation.page
index 4f5568b..23c111b 100644
--- a/manuals/anjuta-manual/C/anjuta-code-indentation.page
+++ b/manuals/anjuta-manual/C/anjuta-code-indentation.page
@@ -11,7 +11,7 @@
</credit>
</info>
- <title>Auto indentation</title>
+ <title>Auto-indentation</title>
<section>
<title>Configuring auto-indentation</title>
diff --git a/manuals/anjuta-manual/C/anjuta-code-symbols.page b/manuals/anjuta-manual/C/anjuta-code-symbols.page
index f787151..587b77f 100644
--- a/manuals/anjuta-manual/C/anjuta-code-symbols.page
+++ b/manuals/anjuta-manual/C/anjuta-code-symbols.page
@@ -11,7 +11,7 @@
</credit>
</info>
- <title>Code navigation using the symbol-browser</title>
+ <title>Code navigation using the symbol browser</title>
<section>
<title>Using the symbol browser</title>
diff --git a/manuals/anjuta-manual/C/anjuta-debug-crash.page b/manuals/anjuta-manual/C/anjuta-debug-crash.page
index 602d094..666366b 100644
--- a/manuals/anjuta-manual/C/anjuta-debug-crash.page
+++ b/manuals/anjuta-manual/C/anjuta-debug-crash.page
@@ -11,7 +11,7 @@
</credit>
</info>
- <title>Debug crashes in your applicatoin</title>
+ <title>Debug crashes in your application</title>
<section>
<title>Using the stack trace</title>
diff --git a/manuals/anjuta-manual/C/anjuta-glade-signals.page b/manuals/anjuta-manual/C/anjuta-glade-signals.page
index 98320d6..16f50a3 100644
--- a/manuals/anjuta-manual/C/anjuta-glade-signals.page
+++ b/manuals/anjuta-manual/C/anjuta-glade-signals.page
@@ -11,10 +11,10 @@
</credit>
</info>
- <title>Auto-connecting signals</title>
+ <title>Autoconnecting signals</title>
<section>
-<title>Add signals to the signal-editor</title>
+<title>Add signals to the signal editor</title>
</section>
<section>
diff --git a/manuals/anjuta-manual/C/autotools-project-backend.page b/manuals/anjuta-manual/C/autotools-project-backend.page
index bcee48b..e470cee 100644
--- a/manuals/anjuta-manual/C/autotools-project-backend.page
+++ b/manuals/anjuta-manual/C/autotools-project-backend.page
@@ -5,7 +5,7 @@
<info>
<link type="guide" xref="project-manager#backend"/>
<desc>
- Autotools project back end.
+ Autotools project backend.
</desc>
<credit type="author">
<name>Sébastien Granjoux</name>
@@ -13,32 +13,34 @@
</credit>
</info>
- <title>GNU Autotools Project Back end Plugin</title>
+ <title>GNU Autotools project backend plugin</title>
<p>
This is the most common project format on Linux. It has been designed to
- distribute source code packages on a wide range of Unix like systems.
- If you have already install a program using <cmd>configure</cmd>,
+ distribute source code packages on a wide range of Unix-like systems.
+ If you have ever installed a program using <cmd>configure</cmd>,
<cmd>make</cmd> and <cmd>make install</cmd>, you probably have already
- used it as an user.
+ used it as a user.
</p>
<p>
It is typically a bit more difficult to use as a developer.
- Hopefully, it is the default and the more advanced back end for
- <app>Anjuta</app>. All features of the project manager are enabled
+ However, it is the default backend for <app>Anjuta</app>, which has features
+ that make it easier to use. All the project manager's features are enabled
when using it.
- You should be able to have a project using it without writing a line in
- <file>configure.ac</file> nor any <file>Makefile.am</file> files.
+ You should be able to maintain a project using the Autotools backend without
+ writing a line in <file>configure.ac</file> or any <file>Makefile.am</file> files.
</p>
<note style="bug">
<p>
- Autotools files give more information than makefile but the back end
- does not support every tricks. If you find a project that
- cannot be read correctly, filling a bug report will be appreciate.
- In the meantime, as a work around, you can use the directory back end
- project instead, it much more limited but should find all source files.
+ Autotools files give more information than a makefile, but the backend
+ does not support all the possible tricks. If you find a project that
+ cannot be read correctly, filing a <link
+ href="https://bugzilla.gnome.org/browse.cgi?product=anjuta";>bug report</link>
+ will be appreciated.
+ In the meantime, as a workaround, you can use the directory project backend
+ instead. It is much more limited but should find all source files.
</p>
</note>
diff --git a/manuals/anjuta-manual/C/directory-project-backend.page b/manuals/anjuta-manual/C/directory-project-backend.page
index 658232c..8f26240 100644
--- a/manuals/anjuta-manual/C/directory-project-backend.page
+++ b/manuals/anjuta-manual/C/directory-project-backend.page
@@ -5,7 +5,7 @@
<info>
<link type="guide" xref="project-manager#backend"/>
<desc>
- Directory project back end.
+ Directory project backend.
</desc>
<credit type="author">
<name>Sébastien Granjoux</name>
@@ -13,27 +13,27 @@
</credit>
</info>
- <title>Directory Project Back end Plugin</title>
+ <title>Directory project backend plugin</title>
<p>
- This is the simplest project back end. There is no project file. It
- works like a file viewer considering as source files, all files matching
- some typical source extensions by example <file>.c</file>,
- <file>.py</file>.
+ This is the simplest project backend. There is no project file. It
+ works like a file viewer, considering all files matching
+ typical source extensions (for example <file>.c</file>,
+ <file>.py</file>) to be source files.
Directories are kept in order to group source files but there is no
target.
</p>
<p>
- This back end is an useful work around if your project has not a
- corresponding back end in <app>Anjuta</app> or if this back end
+ This backend is a useful workaround if your project does not have a
+ corresponding backend in <app>Anjuta</app> or if the appropriate backend
does not fully support your project.
</p>
<p>
- It is not possible to add or change anything with such project. But
- if you create a source file in the project directory with the
- right extension it will be added automatically.
+ It is not possible to add or change anything with a project using this backend. But
+ if you create a source file in the project directory, with the
+ right extension, it will be added automatically.
</p>
</page>
diff --git a/manuals/anjuta-manual/C/introduction.page b/manuals/anjuta-manual/C/introduction.page
index d9bb929..fd5836c 100644
--- a/manuals/anjuta-manual/C/introduction.page
+++ b/manuals/anjuta-manual/C/introduction.page
@@ -14,16 +14,16 @@
<p>
<app>Anjuta</app> is a versatile Integrated Development Environment (IDE)
for the GNOME desktop. It features a number of advanced programming
- facilities includes project management, application wizards, interactive
+ facilities including project management, application wizards, interactive
debugging, integrated Glade UI designer, integrated Devhelp API help, class
generator, powerful source editor, symbols browsing, Git support,
- C/C++, python and Vala support and more.
+ C/C++, Python and Vala support and more.
</p>
<p>
<app>Anjuta</app> has a flexible and advanced docking system
- that allows you to lay out all views in whatever way you like. You can drag
- and drop the views using drag bars and rearrange the layout
+ that allows you to lay out all the views in whatever way you like. You can drag
+ and drop the views using drag bars and rearrange the layout.
</p>
<p>
diff --git a/manuals/anjuta-manual/C/makefile-project-backend.page b/manuals/anjuta-manual/C/makefile-project-backend.page
index 99ff070..b6e55e4 100644
--- a/manuals/anjuta-manual/C/makefile-project-backend.page
+++ b/manuals/anjuta-manual/C/makefile-project-backend.page
@@ -5,7 +5,7 @@
<info>
<link type="guide" xref="project-manager#backend"/>
<desc>
- Makefile project back end.
+ Makefile project backend.
</desc>
<credit type="author">
<name>Sébastien Granjoux</name>
@@ -13,37 +13,37 @@
</credit>
</info>
- <title>Makefile Project Back end Plugin</title>
+ <title>Makefile project backend plugin</title>
<p>
- A makefile is probably the most common way to build a software on all
- kind of platforms. A makefile contains a list or rules describing which
+ A makefile is probably the most common way to build software on all
+ kinds of platforms. A makefile contains a list or rules describing which
commands have to be run in order to generate a target from a list of
dependencies. When building a program, the target is an object file
and the dependencies are the source files. The target of one rule
- can be a dependency of another one, allowing to carry on several rules
- to make a final target.
+ can be a dependency of another one, allowing several rules to be chained
+ in order to make a final target.
</p>
<p>
- It is a low level and general tool making it difficult to find all
+ It is a low-level, general tool, making it difficult to find all
source files and targets of a project.
- So <app>Anjuta</app> has a limited support of makefile, reading only one
+ So <app>Anjuta</app> has limited support for makefiles, reading only one
makefile in the top project directory and extracting source files
and targets.
</p>
<note style="bug">
<p>
- If the project back end is not able to find all source files you can
- try to use the directory back end instead. It does not recognize any
+ If the project backend is not able to find all the source files, you can
+ try to use the directory backend instead. It does not recognize any
targets but should get all source files.
</p>
</note>
<p>
- Changing properties, adding or removing targets and source files are
- disabled with this back end as writing the makefile is not implemented.
+ Changing properties, or adding or removing targets and source files are
+ disabled with this backend, as automatically editing the makefile is not implemented.
It has to be changed by hand using the text editor.
When the makefile is saved, it is automatically reloaded though.
</p>
diff --git a/manuals/anjuta-manual/C/project-import.page b/manuals/anjuta-manual/C/project-import.page
index de35c71..11d9546 100644
--- a/manuals/anjuta-manual/C/project-import.page
+++ b/manuals/anjuta-manual/C/project-import.page
@@ -19,13 +19,13 @@
<title>Import a project</title>
<p>
- <app>Anjuta</app> does not have his own project format. It load projects
- using already existing format, like makefile or autotools, and does not
- require that others developers use it.
- Its own settings are stored in a file with <file>.anjuta</file> extension
+ <app>Anjuta</app> does not have its own project format. It loads projects
+ using already existing formats, like makefile or autotools, and does not
+ require that other developers use it.
+ Anjuta's own settings are stored in a file with the <file>.anjuta</file> extension
and a hidden directory created in the project directory.
- You need to import a project to create these files and use it in
- <app>Anjuta</app>, this will not modify any project files.
+ To use a project in <app>Anjuta</app> and create these settings files, you
+ will need to import the project. This will not modify any project files.
</p>
<steps>
@@ -45,26 +45,27 @@
</p>
<p>
Or Select <gui>Import from version control system</gui> if the
- project need to be checkout from a server. Then select the
- version control system, the server address and the directory
+ project needs to be checked out from a server. Then select the
+ version control system, the server address and the destination directory
on your computer.
</p>
</item>
<item>
<p>
- After selecting the existing project, the <gui>Project name</gui>
- text box should be filled with project name but you can change it.
- When it's done right click on <gui>Import</gui> button to download the
+ After selecting an existing project, the <gui>Project name</gui>
+ text box should be filled with the name of the project's directory,
+ but you can change it.
+ When it's done, click on the <gui>Import</gui> button to download the
project if needed and create the files needed by <app>Anjuta</app>.
</p>
</item>
<item>
<p>
- <app>Anjuta</app> try to automatically find the project back end
- used by your project. But if several back ends are possible,
- you will get a dialog asking you to choose a project back end
- plugin. Read the project back end page to know which one is more
- suitable.
+ <app>Anjuta</app> tries to automatically find the project backend
+ used by your project. But if several backends are possible,
+ you will get a dialog asking you to choose a project backend
+ plugin. Read the project backend description to find out which one to
+ choose.
</p>
</item>
</steps>
diff --git a/manuals/anjuta-manual/C/project-manager-file.page b/manuals/anjuta-manual/C/project-manager-file.page
index e122af5..3a830c6 100644
--- a/manuals/anjuta-manual/C/project-manager-file.page
+++ b/manuals/anjuta-manual/C/project-manager-file.page
@@ -8,7 +8,7 @@
<link type="seealso" xref="project-manager-target"/>
<revision pkgversion="3.0" version="0.1" date="2011-03-27" status="incomplete"/>
<desc>
- Add or remove files to a project.
+ Add or remove files from a project.
</desc>
<credit type="author">
<name>Sébastien Granjoux</name>
@@ -19,7 +19,7 @@
<title>Add or remove files</title>
<p>
- If the project back end supports it you can add or remove files in your
+ If the project backend supports it, you can add or remove files in your
project without editing the project file.
</p>
@@ -41,10 +41,11 @@
<note style="tip">
<p>
- The target allows you to group file and has a type defining the
- use of the files inside. A program target contains source file
- those will be compiled to create the target. While a data target
- only group data files those will be installed in a common place.
+ The target allows you to group files, and has a type which defines
+ how the files are used inside. A program target contains source
+ files, which will be compiled to create the target.
+ On the other hand, a data target only groups data files which will
+ be installed in the same place.
</p>
</note>
</item>
@@ -53,21 +54,21 @@
You can select another target in the top <gui>target tree view</gui>.
</p>
<p>
- Click on <gui>Select file to add</gui> button to get a file
+ Click on the <gui>Select file to add</gui> button to get a file
chooser dialog where you can select several files.
</p>
</item>
<item>
<p>
- When the target and the files are chosen click on <gui>Add</gui>
- button to add those files in your project.
+ When you have chosen the target and the files, click on the <gui>Add</gui>
+ button to add those files to your project.
</p>
</item>
</steps>
<note style="tip">
<p>
- Some project format requires that the file is under the project
+ Some project formats require the file to be under the project
directory. Added source files outside the project directory are
automatically copied inside to fulfill this requirement.
</p>
@@ -88,7 +89,7 @@
</item>
<item>
<p>
- Confirm the removal. The file will only be removed from the project
+ Confirm the removal. The file will only be removed from the project,
not from your disk.
</p>
</item>
diff --git a/manuals/anjuta-manual/C/project-manager-library.page b/manuals/anjuta-manual/C/project-manager-library.page
index 9ebaa98..ff3ed54 100644
--- a/manuals/anjuta-manual/C/project-manager-library.page
+++ b/manuals/anjuta-manual/C/project-manager-library.page
@@ -5,7 +5,7 @@
<info>
<revision pkgversion="3.0" version="0.1" date="2011-03-27" status="incomplete"/>
<desc>
- Add or remove a non packaged libraries to a project.
+ Add or remove non-packaged libraries from a project.
</desc>
<credit type="author">
<name>Sébastien Granjoux</name>
@@ -13,14 +13,14 @@
</credit>
</info>
- <title>Add or remove non packaged libraries</title>
+ <title>Add or remove non-packaged libraries</title>
<section>
- <title>Add a non packaged library in a target</title>
+ <title>Add a non-packaged library to a target</title>
<p>
- In order to use a library in C, you need to tell to the compiler
- where are the header files and to the linker where are the
+ In order to use a library in C, you need to tell the compiler
+ where the header files are, and tell the linker where to find the
needed libraries. The issue is that your program will not compile
on another computer if the header and the libraries are elsewhere.
</p>
@@ -35,29 +35,30 @@
</p>
<p>
Or from the <gui>main menu</gui>, select <guiseq><gui>Project</gui>
- <gui>Properties</gui></guiseq>. By default, It edits the
+ <gui>Properties</gui></guiseq>. By default, it edits the
properties of the currently selected item in the project view.
You can select a different node, by expanding
- <gui>Browse other nodes</gui> and select another one.
+ <gui>Browse other nodes</gui> and selecting another one.
</p>
</item>
<item>
<p>
If the header files are installed in a standard location
- (<file>/usr/include</file>) you don't have to set this. Else
+ (<file>/usr/include</file>) you don't have to set this. If not,
you need to add <input>-I<var>include_path</var></input> in
- the <gui>C preprocessor flags</gui> property when using
- <app>gcc</app>. You can add several paths separated with
- space. These options will be used for all targets inside this
+ the <gui>C preprocessor flags</gui> property if you are using
+ <app>gcc</app> as your compiler. You can add several paths separated with
+ spaces. These options will be used for all targets inside this
directory.
</p>
<p>
- You could have to expand the <gui>More options</gui> to see this.
- Click on <gui>Apply</gui> button when it's done.
+ You might have to expand the <gui>More options</gui> button to see this.
+ Click on the <gui>Apply</gui> button when you are done.
</p>
</item>
<item>
<p>
+ Next, you need to add the library to a target.
Select the target where you want to
add the library in the <gui>project view</gui>, click on the
right mouse button to make the <gui>project context menu</gui>
@@ -65,16 +66,16 @@
</p>
<p>
Or from the <gui>main menu</gui>, select <guiseq><gui>Project</gui>
- <gui>Properties</gui></guiseq>. By default, It edits the
+ <gui>Properties</gui></guiseq>. By default, it edits the
properties of the currently selected item in the project view.
You can select a different node, by expanding
- <gui>Browse other nodes</gui> and select another one.
+ <gui>Browse other nodes</gui> and selecting another one.
</p>
</item>
<item>
<p>
- You need to set the <gui>Linker flags</gui> properties adding
- <input>-l<var>library_name</var></input> for <app>gcc</app>.
+ You need to set the <gui>Linker flags</gui> property, adding
+ <input>-l<var>library_name</var></input> if your compiler is <app>gcc</app>.
<var>library_name</var> is the name of the library file without the
<file>lib</file> prefix and without the <file>.a</file> or
<file>.so</file> extension.
@@ -94,18 +95,18 @@
<steps>
<item>
<p>
- Select the target having the library you want to remove in the
- <gui>project view</gui> , click on the right mouse button to
+ Select the target that has the library you want to remove in the
+ <gui>project view</gui>, click on the right mouse button to
make the <gui>project context menu</gui> appear and select
<gui>Properties</gui>.
</p>
</item>
<item>
<p>
- Remove the properties the library from the
+ Remove the library from the
<gui>C preprocessor flags</gui> and <gui>Linker flags</gui>
- properties. Click on <gui>Apply</gui> button to write the
- changes in the project files.
+ properties. Click on the <gui>Apply</gui> button to write the
+ changes to the project files.
</p>
</item>
</steps>
diff --git a/manuals/anjuta-manual/C/project-manager-module.page b/manuals/anjuta-manual/C/project-manager-module.page
index fbcc936..1c18cdf 100644
--- a/manuals/anjuta-manual/C/project-manager-module.page
+++ b/manuals/anjuta-manual/C/project-manager-module.page
@@ -8,7 +8,7 @@
<link type="seealso" xref="project-manager-library"/>
<revision pkgversion="3.0" version="0.1" date="2011-03-27" status="incomplete"/>
<desc>
- Add or remove libraries to a project.
+ Add or remove libraries from a project.
</desc>
<credit type="author">
<name>Sébastien Granjoux</name>
@@ -20,17 +20,18 @@
<p>
On Linux, most libraries are packaged to be easily used.
- When you need such library, <app>Anjuta</app> provides
- a easy interface to add it. If not check the Add not
- packaged libraries page.
+ When you need one of these libraries, <app>Anjuta</app> provides
+ an easy interface to add it. If the library you need is not one of these,
+ check the <link xref="project-manager-library">Add non-packaged
+ libraries</link> page.
</p>
<section>
- <title>Add packaged libraries in a new Module</title>
+ <title>Add packaged libraries in a new module</title>
<p>
- Such library cannot be added directly to your program you need to first
- create a module for it which is just a group of libraries.
+ A library cannot be added directly to your program; you first need to
+ create a module for it, which is just a group of libraries.
</p>
<steps>
@@ -38,18 +39,18 @@
<p>
Select the program where you want to add the new library in
the <gui>project view</gui>, click on the right mouse button to
- make the <gui>project context menu</gui> appear and select
+ make the <gui>project context menu</gui> appear, and select
<gui>Add Library</gui>. Then click on the <gui>New Library</gui>
button on this dialog.
</p>
<p>
Or from the <gui>main menu</gui>, select <guiseq><gui>Project</gui>
- <gui>New Library</gui></guiseq>
+ <gui>New Library...</gui></guiseq>
</p>
</item>
<item>
<p>
- You will get a list of all packaged libraries installed on your
+ You will get a list of all the packaged libraries installed on your
system. You can check one or more libraries.
</p>
<note style="tip">
@@ -58,22 +59,22 @@
is because it is not installed on your system.
Launch the application you
use to install new programs and search for the library name.
- The needed package often have a "dev" or "devel" suffix and
+ The package you need often has a "dev" or "devel" suffix and
should include header files and a pkg-config file with a
<file>.pc</file> extension.
</p>
</note>
<p>
- After selecting a first library, a module name will be
- automatically generated but you can change it. When it is
- done, click on <gui>Add</gui> button to create the new module
+ After selecting one library, a module name will be
+ automatically generated but you can change it. When you are
+ done, click on the <gui>Add</gui> button to create the new module
with the selected libraries.
</p>
</item>
<item>
<p>
- Look at the next page to know how to add this new module
- to your target.
+ Read the <link xref="project-manager-package">next page</link> to
+ find out how to add this new module to your target.
</p>
</item>
</steps>
@@ -81,7 +82,7 @@
</section>
<section>
- <title>Add packaged libraries in an existing Module</title>
+ <title>Add packaged libraries in an existing module</title>
<steps>
<item>
@@ -93,21 +94,21 @@
</p>
<p>
Or from the <gui>main menu</gui>, select <guiseq><gui>Project</gui>
- <gui>New Library</gui></guiseq>
+ <gui>New Library...</gui></guiseq>
</p>
</item>
<item>
<p>
In the list of all packaged libraries, check the additional
libraries wanted. Check that expected module name is selected
- is the bottom text box.
- Then click on <gui>Add</gui> button to update the module.
+ in the bottom text box.
+ Then click on the <gui>Add</gui> button to update the module.
</p>
</item>
<item>
<p>
- Look at the next page to know how to add the module
- to your target.
+ Read the <link xref="project-manager-package">next page</link> to
+ find out how to add the module to your target.
</p>
</item>
</steps>
@@ -115,7 +116,7 @@
</section>
<section>
- <title>Remove a packaged library from a Module</title>
+ <title>Remove a packaged library from a module</title>
<steps>
<item>
@@ -129,7 +130,7 @@
<item>
<p>
Confirm the removal. This library will be removed from the project
- files.
+ file.
</p>
</item>
</steps>
diff --git a/manuals/anjuta-manual/C/project-manager-package.page b/manuals/anjuta-manual/C/project-manager-package.page
index c6b6f9d..1d178ab 100644
--- a/manuals/anjuta-manual/C/project-manager-package.page
+++ b/manuals/anjuta-manual/C/project-manager-package.page
@@ -6,7 +6,7 @@
<revision pkgversion="3.0" version="0.1" date="2011-03-27" status="incomplete"/>
<link type="seealso" xref="project-manager-library"/>
<desc>
- Add or remove packaged libraries to a target.
+ Add or remove packaged libraries from a target.
</desc>
<credit type="author">
<name>Sébastien Granjoux</name>
@@ -17,16 +17,16 @@
<title>Add or remove packaged libraries</title>
<p>
- When you have created a module containing one or more libraries you can
+ When you have created a module containing one or more libraries, you can
add it to a target.
</p>
<section>
- <title>Add a packaged library in a target</title>
+ <title>Add a packaged library to a target</title>
<p>
- Libraries cannot be added directly in target, you need to put them
- first in a module and add this module to the target.
+ Libraries cannot be added directly to a target. You need to put them
+ into a module first and add this module to the target.
</p>
<steps>
@@ -39,18 +39,18 @@
</p>
<p>
Or from the <gui>main menu</gui>, select <guiseq><gui>Project</gui>
- <gui>Add Library</gui></guiseq>
+ <gui>Add Library...</gui></guiseq>
</p>
</item>
<item>
<p>
You need to select the target where you want to add the module
- in the <gui>target view</gui> above and select the module that
+ in the <gui>target view</gui> above, and select the module that
you want to add in the <gui>module view</gui> below. If you
select a library inside a module, the parent module will be added.
</p>
<p>
- When it is done, click on <gui>Add</gui> button to add the module.
+ When you are done, click on the <gui>Add</gui> button to add the module.
</p>
</item>
</steps>
@@ -64,8 +64,8 @@
<item>
<p>
Select the library you want to remove in the
- <gui>project view</gui> , click on the right mouse button to
- make the <gui>project context menu</gui> appear and select
+ <gui>project view</gui>, click on the right mouse button to
+ make the <gui>project context menu</gui> appear, and select
<gui>Remove</gui>.
</p>
</item>
diff --git a/manuals/anjuta-manual/C/project-manager-target.page b/manuals/anjuta-manual/C/project-manager-target.page
index cf921de..728cace 100644
--- a/manuals/anjuta-manual/C/project-manager-target.page
+++ b/manuals/anjuta-manual/C/project-manager-target.page
@@ -7,7 +7,7 @@
<link type="seealso" xref="project-manager"/>
<revision pkgversion="3.0" version="0.1" date="2011-03-27" status="incomplete"/>
<desc>
- Add or remove target to a project.
+ Add or remove a target from a project.
</desc>
<credit type="author">
<name>Sébastien Granjoux</name>
@@ -18,10 +18,10 @@
<title>Add or remove targets</title>
<p>
- If the project back end supports it you can add or remove targets in your
+ If the project backend supports it, you can add or remove targets in your
project without editing the project file. A target groups
- files, it is typically used to represent a program, having as children
- all its source files.
+ files together. It is typically used to represent a program, with
+ all its source files as its children.
</p>
<section>
@@ -37,7 +37,7 @@
</p>
<p>
Or from the <gui>main menu</gui>, select <guiseq><gui>Project</gui>
- <gui>New Target</gui></guiseq>
+ <gui>New Target...</gui></guiseq>
</p>
</item>
<item>
@@ -46,19 +46,19 @@
</p>
<p>
Enter a target name and select the type of the target in the
- drop-down list below. Depending on your project back end, various
- type of target are possible.
+ drop-down list below. Depending on your project backend, various
+ types of target are possible.
</p>
<note style="tip">
<p>
- Target name could are typically restricted to letters, digits and
- underscore, so it's safer to avoid other characters.
+ Target names are typically restricted to letters, digits and
+ the underscore, so it's safer to avoid other characters.
</p>
</note>
</item>
<item>
<p>
- When the target name, type and parent are chosen click on
+ When you have chosen the target name, type and parent, click on the
<gui>Add</gui> button to create this new target.
</p>
</item>
@@ -81,7 +81,7 @@
<item>
<p>
Confirm the removal. The target and all its properties will be
- remove from the project file. All files stay untouched on your
+ removed from the project file. All its files stay untouched on your
hard disk.
</p>
</item>
diff --git a/manuals/anjuta-manual/C/project-manager.page b/manuals/anjuta-manual/C/project-manager.page
index 1f6df2e..db6b21e 100644
--- a/manuals/anjuta-manual/C/project-manager.page
+++ b/manuals/anjuta-manual/C/project-manager.page
@@ -15,18 +15,18 @@
<title>Project manager plugin</title>
<p>
- <app>Anjuta</app> supports several already existing project format
- through plugin back ends. The main one is the autotools format commonly
+ <app>Anjuta</app> supports several already existing project formats
+ through plugin backends. The main one is the autotools format commonly
used on Linux.
</p>
<p>
- Whatever is the underline back end, the graphical interface is the same
- but some functions can be disabled.
+ Whatever the underlying backend, the graphical interface is the same
+ but some functions might be disabled.
</p>
<section id="backend" >
- <title>Project Back end Plugin</title>
+ <title>Project Backend Plugin</title>
</section>
</page>
diff --git a/manuals/anjuta-manual/C/project-wizard-create.page b/manuals/anjuta-manual/C/project-wizard-create.page
index f00d36d..55863e3 100644
--- a/manuals/anjuta-manual/C/project-wizard-create.page
+++ b/manuals/anjuta-manual/C/project-wizard-create.page
@@ -19,7 +19,7 @@
<p>
New projects are created from templates. <app>Anjuta</app> will ask you
- several informations like the type of the project, its name and more.
+ for various information, like the type of the project, its name and more.
</p>
<steps>
@@ -29,37 +29,38 @@
<gui>New</gui><gui>Project</gui></guiseq>.
</p>
<p>
- Or from <gui>Project</gui> from the drop-down list of the
+ Or from the drop-down list of the
<gui>New</gui> button in the <gui>top tool bar</gui>, select
- <guiseq><gui>File</gui><gui>New</gui><gui>Project</gui></guiseq>
+ <gui>Project</gui>
to start the project wizard.
</p>
</item>
<item>
<p>
- Select the icon representing the type of the project who want to
+ Select the icon representing the type of the project you want to
create and click on <gui>Forward</gui>.
</p>
<note style="tip">
<p>
- Let the mouse over a project icon for a second and a small pop-up
- message will appear showing more information about this project.
+ Leave the mouse over a project icon for a second and a small pop-up
+ message will appear showing more information about this type of
+ project.
</p>
</note>
</item>
<item>
<p>
Depending on the selected project type, you will have to enter
- different informations. When it is done click on <gui>Forward</gui>.
+ different information. When you are done, click on <gui>Forward</gui>.
</p>
<p>
All informations are grouped in pages, typically you will have
to fill two or three pages. You can go back at any time using
- the button <gui>Backward</gui>.
+ the button <gui>Back</gui>.
</p>
<note style="tip">
<p>
- Keep the mouse over the editable widget for a second to get a
+ Keep the mouse over the button or typing area for a second to get a
small pop-up message with more details about the corresponding
setting.
</p>
@@ -67,9 +68,9 @@
</item>
<item>
<p>
- After filling all information pages, you will get a summary page listing
- the main information about your project. Nothing is written on your disk
- at this point. Click on <gui>Apply</gui> to write the project and open
+ After filling out all the information pages, you will get a summary page listing
+ the main information about your project. Nothing has been written to your disk
+ yet at this point. Click on <gui>Apply</gui> to save the project and open
it in <app>Anjuta</app>.
</p>
</item>
@@ -79,7 +80,7 @@
<p>
Each project type corresponds to a template. <app>Anjuta</app> already
includes several templates but you can add custom ones and even write
- your own one.
+ your own.
</p>
</note>
diff --git a/manuals/anjuta-manual/C/project-wizard-template.page b/manuals/anjuta-manual/C/project-wizard-template.page
index e320705..6aa8b94 100644
--- a/manuals/anjuta-manual/C/project-wizard-template.page
+++ b/manuals/anjuta-manual/C/project-wizard-template.page
@@ -18,13 +18,13 @@
<p>
A project template is composed of a bunch of files which can be processed
- by a powerful template processing engine called <app>autogen</app>. One
- of this file with a <file>.wiz</file> extension described all project
- properties and needed files.
+ by a powerful template processing engine called <app>autogen</app>. A project
+ template file has a <file>.wiz</file> extension, and describes all the project
+ properties and files needed.
</p>
<p>
- This <file>.wiz</file> file is looking like a XML file and is documented
+ This <file>.wiz</file> file looks like a XML file and is documented
<link href="http://library.gnome.org/devel/libanjuta/stable/project-wizard-format.html";>here</link>.
</p>
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]
