From 711915589ca4cc6f61ed33d7a17606dc25b52bf3 Mon Sep 17 00:00:00 2001 From: halw Date: Thu, 18 Aug 2011 19:47:24 +0000 Subject: [PATCH] Author:Peter Gummer Date:2011-08-14T10:58:06.000000Z git-svn-id: https://svn.eiffel.com/eiffel-org/trunk@954 abb3cda0-5349-4a8f-a601-0c33ac3a8c38 --- .../producing-and-exporting-documentation.wiki | 7 +++---- .../general-target-options/index.wiki | 2 +- 2 files changed, 4 insertions(+), 5 deletions(-) diff --git a/documentation/current/eiffelstudio/eiffelstudio-guided-tour/producing-and-exporting-documentation.wiki b/documentation/current/eiffelstudio/eiffelstudio-guided-tour/producing-and-exporting-documentation.wiki index b70bca75..37d8fdfe 100644 --- a/documentation/current/eiffelstudio/eiffelstudio-guided-tour/producing-and-exporting-documentation.wiki +++ b/documentation/current/eiffelstudio/eiffelstudio-guided-tour/producing-and-exporting-documentation.wiki @@ -1,7 +1,6 @@ [[Property:title|Producing and Exporting Documentation]] [[Property:weight|-7]] [[Property:uuid|ca43a3c2-9e1a-a69f-81cf-55d0b12294ea]] - Software development is, most of the time, cooperative work. You must tell the rest of the team what you're up to, and find out what they can offer you. Bring in distributed development -- increasingly common these days, with some people working at headquarters, others at home, others traveling, an offshore team half a world away ... -- and the problem becomes even more critical. EiffelStudio provides unique facilities to make such distributed development possible in a safe, effective, harmonious way. Some of the key criteria are: @@ -52,11 +51,11 @@ Let's select the most obviously attractive of the predefined filters: HTML with [[Image:index-38]] -This is to let you decide which clusters of your system the documentation will include. Initially all clusters/libraries appear in the Include list on the right; but you might want to exclude some standard libraries or other clusters from the documentation. +In this pane you select which parts of your system you want to be included in the documentation. By default, all library and cluster names are checked. You should uncheck any that you do not want included. -To move a cluster from the right column to the left one, click it to select it, and click the left arrow button; for the reverse, use the right arrow. +Note that each library or cluster name must be checked or unchecked individually. For example, unchecking "base" will not automatically deselect "elks" and "ise" which appear under "base". -You can play with moving a couple of clusters back and forth, but for this Tour we'll want to generate everything, including EiffelBase, so make sure that in the end all clusters appear in the right column, as on the last figure. Then click Next. +For this Tour we'll want to generate everything, including EiffelBase, so make sure that in the end all library and cluster names are checked, as in the figure. Then click Next. ==Generating Metatags from Note entries== diff --git a/documentation/current/eiffelstudio/eiffelstudio-reference/eiffelstudio-project-settings-window/general-target-options/index.wiki b/documentation/current/eiffelstudio/eiffelstudio-reference/eiffelstudio-project-settings-window/general-target-options/index.wiki index 10616502..7692b10d 100644 --- a/documentation/current/eiffelstudio/eiffelstudio-reference/eiffelstudio-project-settings-window/general-target-options/index.wiki +++ b/documentation/current/eiffelstudio/eiffelstudio-reference/eiffelstudio-project-settings-window/general-target-options/index.wiki @@ -43,7 +43,7 @@ It is also possible to add conditions to a file rule (set of include and exclude [[Image:condition-dialog|Condition dialog]] -Conditioning possibilities are platform (e.g. only Windows or everything but windows), kind of build, .NET generation, dynamic runtime, multithreaded, version of compiler and version of msil clr. It is also possible to specify custom conditions where a user defined variable has to have a certain value. +Conditioning possibilities are platform (e.g. only Windows or everything but windows), kind of build, .NET generation, dynamic runtime, multithreaded, version of compiler and version of msil clr. It is also possible to specify custom conditions where a [[variables|user defined variable]] has to have a certain value. Further options are * Profiling: turn on the Eiffel profiler during the application execution (C code generation mode only). The results can be seen at the end of the execution in the profiler window.