Changeset 176

Timestamp:

09/13/06 16:17:41 (18 years ago)

Author:

smasson

Message:

Update xml documentation files

Location:

trunk/SRC/Documentation/xmldoc

Files:

• faqsaxo.xml (modified) (2 diffs)
• figpng/pltv.png (added)
• figpng/xxx_0206a.png (modified) (previous)
• figpng/xxx_0701.png (modified) (previous)
• figpng/xxx_0702.png (modified) (previous)
• figpng/xxx_0901.png (modified) (previous)
• figpng/xxx_0902.png (modified) (previous)
• figpng/xxx_0903.png (modified) (previous)
• firststeps.xml (modified) (2 diffs)
• mini_notice.xml (modified) (22 diffs)
• savesaxo.sh (modified) (2 diffs)
• websaxo.xml (modified) (1 diff)
• whatsnew.xml (modified) (5 diffs)

trunk/SRC/Documentation/xmldoc/faqsaxo.xml

@@ -2 +2 @@
 <!DOCTYPE article PUBLIC "-//OASIS//DTD DocBook XML V4.2//EN"
 "http://www.oasis-open.org/docbook/xml/4.2/docbookx.dtd"
-[]>
+[
+<!ENTITY promptidl "idl&gt;">
+]>
 <!--
 en s'inspirant de
@@ -175 +177 @@
 <answer>
 <para>
-Yes. produced by <application>IDLdoc</application>. 
-</para>
-<para>
-You can access to this documentation set during your IDL session with this 
-command :
- <screen format="linespecific">
-  <prompt>IDL</prompt> <userinput><command>ONLINE_HELP</command>,<option>book="<replaceable>SAXO_basedirectory</replaceable>/SAXO_DIR/SRC/Documentation/idldoc_assistant_output/idldoc-lib.adp"</option></userinput>
-</screen>
+Yes, if you use at least IDL 6.2. It is produced by <application><ulink url="http://www.ittvis.com/codebank/search.asp?FID=100">IDLdoc</ulink></application>. SAXO and IDL online_help have been merged, you can simply get the help by typing:
+     <screen format="linespecific">
+       <prompt>&promptidl;</prompt> <userinput><command>?</command></userinput>
+     </screen>
 </para>
 </answer>

trunk/SRC/Documentation/xmldoc/firststeps.xml

@@ -326 +326 @@
       <sect3 id="tvplus">
         <title>
-          Quick look at 2D arrays: tvplus
+          Quick look and explore 2D arrays: tvplus
         </title>
         <para>
           <command>tvplus</command> is a enhanced version of tvscl and allow you to have a quick look and perform basic exploration of 2D arrays.
           <screen format="linespecific">
-            <prompt>&promptidl;</prompt> <userinput><command>tvplus, dist(20)</command></userinput> <ulink url="figpng/tvplus.png?format=raw">&showfig;</ulink>
+  <prompt>&promptidl;</prompt> <userinput><command>tvplus, dist(20)</command></userinput> <ulink url="figpng/tvplus.png?format=raw">&showfig;</ulink>
   <computeroutput>left button  : mouse position and associated array value</computeroutput>
   <computeroutput>middle button: use it twice to define a zoom box</computeroutput>
@@ -341 +341 @@
           <screen format="linespecific">
   <prompt>&promptidl;</prompt> <userinput><command>xhelp, 'tvplus'</command></userinput>
+          </screen>
+          To sse the source code of <command>tvplus</command>, try:
+          <screen format="linespecific">
+  <prompt>&promptidl;</prompt> <userinput><command>xfile, 'tvplus'</command></userinput>
+          </screen>
+          <note><title>New Feature</title><para>
+          If you use an IDL 6.2 or later revision, you can simply get the help of any command by typing ?<replaceable>command_name</replaceable>, for example:
+          <screen format="linespecific">
+  <prompt>&promptidl;</prompt> <userinput><command>?tvplus</command></userinput>
+          </screen>
+          </para></note>
+        </para>
+      </sect3>
+
+      <sect3 id="pltv">
+        <title>
+          Formal quick look at 2D arrays: pltv
+        </title>
+        <para>
+          <command>pltv</command> is a mix between <link linkend="tvplus">tvplus</link> and <link linkend="plt">plt</link> and allow you to have formal quick look of 2D arrays.
+          <screen format="linespecific">
+  <prompt>&promptidl;</prompt> <userinput><command>pltv, dist(20)</command></userinput> <ulink url="figpng/pltv.png?format=raw">&showfig;</ulink>
           </screen>
         </para>

trunk/SRC/Documentation/xmldoc/mini_notice.xml

@@ -50 +50 @@
         <revremark>HTML to XML/Docbook migration by Françoise Pinsard</revremark>
       </revision>
+      <revision>
+        <revnumber>1.0</revnumber>
+        <date>August, 2006</date>
+        <revremark>Major update by Steve Navarro</revremark>
+      </revision>
+      <revision>
+        <revnumber>1.1</revnumber>
+        <date>September, 2006</date>
+        <revremark>Review by Sébastien Masson</revremark>
+      </revision>
      </revhistory>
      <pubdate>$Id$</pubdate>
@@ -55 +65 @@
 
 
-<!--
-La partie suivante n'a plus tellement de sens maintenant que tout SAXO est disponible sur forge
-<para>
-Where to find the source code
-</para>
-The scripts are available in the IDL_29_5_2000 directory.
-</para>
-<para>
-In this directory are
-<itemizedlist>
-<listitem><para>a tar file IDL_29_5_2000.tar with all the files</para></listitem>
-<listitem><para>the scripts in ASCII, in subdirectories by theme</para></listitem>
-</itemizedlist>
-
-<para>
-This IDL_29_5_2000 directory is available:
-<itemizedlist>
-<listitem><para>at LODYC: adonis.lodyc.jussieu.fr:/usr/home/smasson/IDL_29_5_2000</para></listitem>
-<listitem><para>at IPSL: cook.ipsl.jussieu.fr:/home/smlod/IDL_29_5_2000</para></listitem>
-<listitem><para>at IDRIS: rhodes.idris.fr:/home/rech/eee/reee217/IDL_29_5_2000</para></listitem>
-<listitem><para>on the anonymous ftp site of LODYC (contact <ulink url="mailto:smasson@lodyc.jussieu.fr">smasson@lodyc.jussieu.fr</ulink>
-for access).</para></listitem>
-<listitem><para>soon, from <ulink url="http://www.lodyc.jussieu.fr/~opatlod/SAXO/"/></para></listitem>
-</itemizedlist>
-</para>
-<para>
-This mini guide is also found in the IDL_29_5_2000 directory, in
-different formats.  It is also consultable on the web at:
-</para>
-<para>
-<ulink url="http://www.ipsl.jussieu.fr/~smlod/mini_notice.html"/>
-</para>
-
--->
-<!-- ++ n'a plus rien à faire ici
-<sect1 id="intro"><title>Introduction and assumptions</title>
-
-<para>
-This micro guide is unfortunately not a user's guide for all the
-scripts that have been written for IDL (version 5.2 or higher
-required). The goal is simply to clarify a few points on the use of the <filename>xxx.pro</filename>
-program.
-</para>
-<para>
-For further help on the furnished scripts, here are
-several possibilities:
-
-<itemizedlist>
-<listitem><para>execute in IDL the command
-  <screen format="linespecific">
-<prompt>&promptidl;</prompt> <userinput>xhelp, '<replaceable>script_name</replaceable>'</userinput>
-</screen>
-</para></listitem>
-<listitem><para>consult the IDL online help for scripts whose source is unavailable</para></listitem>
-<listitem><para>
-subscribe to the mailing list for updates and user questions/responses
-</para>
-<para>
-to subscribe, send a mail to: <ulink url="mailto:majordomo@lmd.jussieu.fr">majordomo@lmd.jussieu.fr</ulink>
-with no subject, containing the message:
-<userinput>subscribe forum-idl <replaceable>e-mail address</replaceable></userinput>
-</para></listitem>
-<listitem><para>consult the archives of this mail list:
-    <ulink url="http://www.lmd.jussieu.fr/archives/form-idl/last/mail1.html"/></para></listitem>
-<listitem><para>consult in desperation the feeble web pages we have started to write
-  (while waiting for something better)
-  <ulink url="http://www.ipsl.jussieu.fr/~smlod/"/></para></listitem>
-<listitem><para>wait until we write a full user's manual!</para></listitem>
-</itemizedlist>
-</para>
-
-<para>
-The XXX widget is a layer on top of the scripts in the <application>SAXO</application> package
-(themselves layered on top of IDL). It is designed to permit the
-visualization and rapid exploration of data, offering a maximum in
-options, while not necessarily all those offered by the package and by
-IDL.
-</para>
-<para>
-Based on the use of files in the NetCDF format, it can easily work
-with other file formats.  For this, all that is necessary is to write
-an IDL function capable of extracting a matrix from a file as a
-function of the following parameters: the variable name, two dates, an
-experiment name, and a domain.
-</para>
-<para>
-Developed to visualize the output of the OPA model, the <application>SAXO</application> package was
-conceived to work on C grids.  To use it on grids where the T, U, and
-V points are the same, one must nevertheless declare the parameters of
-the grid that correspond to the U and V points.  Careful, for this
-type of discretization, the calculation scripts of type <filename>div.pro</filename> and
-<filename>curl.pro</filename> are wrong.
-</para>
-<para>
-The averaging routines are not adapted to warped grids, they sum
-following the i, j, and k indices, weighting each point by scale
-factors and the land-sea mask.  Slices and Hovmoellers do not work in
-the diagonal, but are always done following i, j, or k.  When a domain
-is given to one of the scripts, an average over the domain in the
-directions perpendicular to that displayed is automatically made before
-display.
-</para>
-<para>
-Before continuing on to the practical part of this guide, the
-installation and use of the <application>SAXO</application> package, I'd like to thank Guillaume
-Roullet, who also participated in the writing of the scripts in the
-package (notably the drawing of vectors on warped grids).
-</para>
-</sect1>
-
-<sect1 id="beforefirststeps">
-<title>Before this</title>
-<para>
-In this document, we supposed that you followed <ulink url="getsaxo.html?format=raw">Get SAXO</ulink> recommandations.
-</para>
-</sect1>
-
-
-<sect1 id="initfiles"><title>Install the files <filename>init.pro</filename> and
-<filename>initgrid.pro</filename></title>
-
-<para>
-This version of the <application>SAXO</application> package depends a certain number of common
-variables that are primarily environmental parameters (working paths,
-color management, Postscript formatting) and the parameters of the
-grid on which you are working (longitude, latitude, depth, land-sea
-mask, scale factors, position of the zoom in relation to the original
-grid).
-</para>
-<para>
-These two types of parameters are kept separately:
-<itemizedlist>
-<listitem><para>environmental parameters are defined at the very beginning of the
-IDL session, and are in principle never changed.  They are initialized
-by the <filename>init.pro</filename> script.</para></listitem>
-<listitem><para>Those that belong to the grid are reinitialized every time the
-grid is changed.  They can therefore be called at any time during a
-session. These parameters are initialized by the <filename>initgrid.pro</filename>
-scripts, and are specific to each particular grid.
-</para>
-<para>
-For example: <filename>initorca.pro</filename> for the ORCA 2&deg; grid,
-<filename>initorca05.pro</filename> for
-the ORCA 0.5&deg; grid, or <filename>initorcapac.pro</filename> for the ORCA grid zoomed on
-the Pacific.</para></listitem>
-</itemizedlist>
-</para>
-<para>
-To begin, one must therefore copy <filename><replaceable>packagedir</replaceable>/INIT/init.pro</filename>
-into <replaceable>homedir</replaceable>, and create in <replaceable>homedir</replaceable> a script of the
-type <filename>initgrid.pro</filename>.
-</para>
-
-<sect2 id="modifinit"><title>Modification of the <filename>init.pro</filename> script</title>
-
-<para>
-It is necessary to personalize the lines that correspond to the 6
-directories defined in &sect; 1.1.  That is:
-<itemizedlist>
-<listitem><para>The definition of !path.</para><para>
-The first expand_path must contain <replaceable>homedir</replaceable>, the second
-<replaceable>packagedir</replaceable>.  The directory declaration must be preceded by a +
-sign, and must take the form of a character chain. The + sign
-specifies that subdirectories must also be considered.  For those
-working on a Mac, <literallayout>"+':'+"</literallayout> must be replaced by <literallayout>"+','+"</literallayout> and for Windows
-by <literallayout>"+';'+"</literallayout>.</para>
-<warning>
-<para>
-In their definition, the directories must not finish with the
-directory separation character ("/" under UNIX/Linux).
-</para>
-</warning>
-</listitem>
-<listitem><para>Definition of the rest of the directories:</para><para>
-Define as necessary the variables homedir, workdir, iodir, animdir,
-psdir, and imagedir.</para>
-<warning>
-<para>
-Despite precautions taken, in order to avoid bugs it is
-recommended that these directories be defined with the directory
-separation character as the final character ("/" under UNIX/Linux).
-</para>
-</warning>
-</listitem>
-</itemizedlist>
-</para>
-<note>
-<para>
-Depending on the resolution of your screen and the type of
-machine used, it is possible that the graphics window which is created
-will be too large.  If this is the case, change the ccwindowsize
-variable which is a multiplicative coefficient applied to the window
-size.
-</para>
-</note>
-</sect2>
-<sect2 id="modifinitgrid"><title>Modification or creation of the <filename>initgrid.pro</filename> script</title>
-
-<para>
-In the <replaceable>packagedir</replaceable>/INIT directory you will find a certain
-number of scripts associated with the latest grids on which I've
-worked.  If you are also working on one of these grids, for example
-ORCA, copy the file  <filename><replaceable>packagedir</replaceable>/INIT/initorca.pro</filename> to your
-<replaceable>homedir</replaceable>.  If not, copy it nevertheless to use as a model.  In
-the file <filename>initgrid.pro</filename>, adjust the zoom parameters (if it has not
-already been done).
-</para>
-<para>
-Careful: unlike in previous versions of the <application>SAXO</application> package, all the zoom
-parameters must be defined.  If you do not know them in advance,
-define their values to be -1.
-</para>
-<para>
-In the rest of the script, define iodir as <replaceable>iodir</replaceable>, and verify
-the name of the mask file, if one exists.
-</para>
-</sect2>
-</sect1>
--->
-<sect1 id="introxxx"><title>XXX widget functions</title>
-<sect2 id="launchxxx"><title>Launching XXX</title>
-
-<para>
-The first command to type is
-
-  <screen format="linespecific">
-<prompt>&promptidl;</prompt> <userinput>@init</userinput>
-</screen>
-
-</para>
-<para>
-Afterwards, to work directly with XXX, type:
-
-  <screen format="linespecific">
-
-<prompt>&promptidl;</prompt> <userinput>xxx</userinput>
-</screen>
-
-</para>
-
-
-A window will open with 2 lines to complete.
+<sect1 id="launchxxx"><title>Launching XXX</title>
+
+<para>
+There is several ways to launch XXX which we will detail in the next sections:
+  <screen format="linespecific">
+    <prompt>&promptidl;</prompt> <userinput><command>xxx</command></userinput>
+    <prompt>&promptidl;</prompt> <userinput><command>xxx</command>, <parameter>/separate</parameter></userinput>
+    <prompt>&promptidl;</prompt> <userinput><command>xxx</command>, <parameter>restore = 'file.dat'</parameter></userinput>
+    <prompt>&promptidl;</prompt> <userinput><command>xxx</command>, <parameter>'file.nc'</parameter></userinput>
+    <prompt>&promptidl;</prompt> <userinput><command>xxx</command>, <parameter>'file.nc'</parameter>, <parameter>keywd1 = ...</parameter>, <parameter>keywd2 = ...</parameter></userinput>
+    <prompt>&promptidl;</prompt> <userinput><command>xxx</command>, <parameter>'file.nc'</parameter>, <parameter>'initgrid'</parameter></userinput>
+    <prompt>&promptidl;</prompt> <userinput><command>xxx</command>, <parameter>'file.nc'</parameter>, <parameter>'initgrid'</parameter>, <parameter>keywd1 = ...</parameter>, <parameter>keywd2 = ...</parameter></userinput>
+    <prompt>&promptidl;</prompt> <userinput><command>xxx</command>, <parameter>'file.nc'</parameter>, <parameter>'initgrid'</parameter>, <parameter>'arg1, arg2, ...'</parameter></userinput>
+  </screen>
+</para>
+
+<sect2 id="launch_xxx_1"><title><prompt>&promptidl;</prompt> <userinput><command>xxx</command></userinput></title>
+  <para>
+    A window will open with 3 parts to consider.
 <figure id="fig_xxx_0101">
 <title>Window xxx 1</title>
@@ -311 +98 @@
 <calloutlist>
 <callout arearefs="datafile">
-<para>Data file</para>
+<para>Data file name</para>
 </callout>
 <callout arearefs="initmethod">
-<para>Init method</para>
+<para>Grid initialization method</para>
 </callout>
 <callout arearefs="initprogram">
-<para>Init program</para>
+<para>Grid initialization parameters</para>
 </callout>
 </calloutlist>
@@ -326 +113 @@
 </mediaobjectco>
 </figure>
-<sect3 id="datafiletxt"><title>File name</title>
+  </para>
+
+<sect3 id="datafiletxt"><title>Data file name</title>
   <para>
-    the name of the data file. The name can be typed directly in the window
-    provided, or selected with the help of the <guibutton>browse</guibutton> button.
-</para>
-</sect3>
-<sect3 id="initmethodtxt"><title>Grid initalization method</title>
+    The name of the data file. It can be typed directly in the window provided, or selected with the help of the <guibutton>browse</guibutton> button.
+  </para>
+</sect3>
+<sect3 id="initmethodtxt"><title>Grid initialization method</title>
   <para>
-    By default, "automatic grid construction with initncdf.pro" is checked.
+    For visualising grilled data, you need to <ulink url="firststeps.html?format=raw#load_grid">define the grid</ulink> on which are located the data. By default, "automatic grid construction with initncdf.pro" is checked. This means that the grid will be defined by using the informations contained in the data file (through the IDL prodecure <command>initncdf</command>) without needing any other auxillary file. If you checked "grid construction with other IDL batch or procedure", this means that you don't want to use the default <command>initncdf</command> procedure to define the grid and you will provide your own IDL procedure or the so-called IDL batch file (a file which is called by using @, see IDL documentation).
   </para>
+</sect3>
+<sect3 id="initprogramtxt"><title>Grid initialization parameters</title>
   <para>
-    But you can choose an other grid by checking "grid construction with other IDL batch or procedure"  
-  </para>
-</sect3>
-<sect3 id="initprogramtxt"><title>Grid initalization parameters</title>
-  <para>
+    This third part allows you to specify the name, the argument and the keywords of the routine you want to use to initialize the grid.  By default the name of the procedure is <command>initncdf</command>, its argument will be automatically defined so you cannot change them. If you If you checked "grid construction with other IDL batch or procedure", you have to select the name of the IDL procedure or batch file and its suitable arguments and keywords. Note that if you select an IDL batch file you cannot give any parameter or keyword.
     <figure id="fig_xxx_0102">
       <title>Window xxx 1</title>
@@ -354 +140 @@
   </para>
   <para>
-    the second the name of
-    the <filename>initgrid.pro</filename> script which will permit the reading and processing of the
-    grid associated with the data file.
-  </para>
-  <para>
     Once these two lines have been completed, click on <guibutton>let's go</guibutton>.
   </para>
-  <para>For example, we choose the mask "tst_initlev". Compare the result with "automatic grid construction with initncdf.pro" checked. Cf <xref linkend="fig_xxx_0404"/> </para>
+  <para>For example, we choose the IDL batch file "tst_initlev". Compare the result with "automatic grid construction with initncdf.pro" checked. Cf <xref linkend="fig_xxx_0404"/> </para>
 <para>
   <figure id="fig_xxx_0103">
-      <title>Oceania at 125 metters of depth with a mask</title>
+      <title>Oceania at 125 metters of depth with proper grid initialization</title>
         <imageobject>
           <imagedata fileref="figpng/xxx_0103.png"/>
@@ -373 +154 @@
 </sect2>
 
-<sect2 id="wigdets"><title>Description of XXX window</title>
-
-<para>
-Now the XXX window will open.
+<sect2 id="launch_xxx_2"><title><prompt>&promptidl;</prompt> <userinput><command>xxx</command>, <parameter>/separate</parameter></userinput></title>
+<para>
+This is the same as the simple <link linkend="launch_xxx_1"><prompt>&promptidl;</prompt> <userinput><command>xxx</command></userinput></link> except that once the xxx window open, you will have 2 separate windows (command and plotting window) instead of one.
+</para>
+</sect2>
+
+<sect2 id="launch_xxx_3"><title><prompt>&promptidl;</prompt> <userinput><command>xxx</command>, <parameter>restore = 'file.dat'</parameter></userinput></title>
+<para>
+In that case xxx window will open directly in the same state as it was when the file "file.dat" was created. see <link linkend="restore">+++++++</link>
+</para>
+</sect2>
+
+<sect2 id="launch_xxx_4"><title><prompt>&promptidl;</prompt> <userinput><command>xxx</command>, <parameter>'file.nc'</parameter></userinput></title>
+<para>
+In this case, the xxx window directly open the data file 'file.nc' and build the grid automatically with the IDL procedure <command>initncdf</command>. For example:
+  <screen format="linespecific">
+    <prompt>&promptidl;</prompt> <userinput><command>xxx</command>, <parameter>'Levitus98_1m_01_12_Temperature_Pot_1x1.nc'</parameter></userinput>
+  </screen>
+</para>
+</sect2>
+
+<sect2 id="launch_xxx_5"><title><prompt>&promptidl;</prompt> <userinput><command>xxx</command>, <parameter>'file.nc'</parameter>, <parameter>keywd1 = ...</parameter>, <parameter>keywd2 = ...</parameter></userinput></title>
+<para>
+In this case, the xxx window directly open the data file 'file.nc', build the grid automatically with the IDL procedure <command>initncdf</command> and use the keywords <userinput><parameter>keywd1 = ...</parameter>, <parameter>keywd2 = ...</parameter></userinput> in the call of <command>initncdf</command>. For example:
+  <screen format="linespecific">
+    <prompt>&promptidl;</prompt> <userinput><command>xxx</command>, <parameter>'Levitus98_1m_01_12_Temperature_Pot_1x1.nc'</parameter>, <parameter>useasmask = 'votemper'</parameter>, <parameter>missing_value = 31.0720</parameter></userinput>
+  </screen>
+</para>
+</sect2>
+
+<sect2 id="launch_xxx_6"><title><prompt>&promptidl;</prompt> <userinput><command>xxx</command>, <parameter>'file.nc'</parameter>, <parameter>'initgrid'</parameter></userinput></title>
+<para>
+In this case, the xxx window directly open the data file 'file.nc' and build the grid directly with the IDL procedure or batch file <command>initgrid</command>
+  <screen format="linespecific">
+    <prompt>&promptidl;</prompt> <userinput><command>xxx</command>, <parameter>'Levitus98_1m_01_12_Temperature_Pot_ORCA2.nc'</parameter>, <parameter>'tst_initorca2'</parameter></userinput>
+  </screen>
+</para>
+</sect2>
+
+<sect2 id="launch_xxx_7"><title><prompt>&promptidl;</prompt> <userinput><command>xxx</command>, <parameter>'file.nc'</parameter>, <parameter>'initgrid'</parameter>, <parameter>keywd1 = ...</parameter>, <parameter>keywd2 = ...</parameter></userinput></title>
+<para>
+In this case, the xxx window directly open the data file 'file.nc', build the grid directly with the IDL procedure <command>initgrid</command> and use the keywords <userinput><parameter>keywd1 = ...</parameter>, <parameter>keywd2 = ...</parameter></userinput> in the call of <command>initgrid</command>.
+</para>
+</sect2>
+
+<sect2 id="launch_xxx_8"><title><prompt>&promptidl;</prompt> <userinput><command>xxx</command>, <parameter>'file.nc'</parameter>, <parameter>'initgrid'</parameter>, <parameter>'arg1, arg2, ...'</parameter></userinput></title>
+<para>
+In this case, the xxx window directly open the data file 'file.nc', build the grid directly with the IDL procedure <command>initgrid</command> and use the string <userinput><parameter>'arg1, arg2, ...'</parameter></userinput> to specify the input arguments in the call of <command>initgrid</command>.
+</para>
+</sect2>
+
+</sect1>
+
+<sect1 id="wigdets"><title>Description of XXX window</title>
+
+<para>
 <!-- cf example in http://www.docbook.org/tdg/en/html/area.html
 sauf que dans l'exemple en question on ne donne que 2 nombres et pas 4
@@ -442 +275 @@
 </figure>
 </para>
-<para>
-It's configuration will change
-depending on whether you are in portrait or in landscape, but here are
-the different parts available for your use.
-</para>
-
-<sect3 id="plottypetxt"><title>Plot type list</title>
+
+<sect2 id="plottypetxt"><title>Plot type list</title>
 <para>allows specification of the type of plot desired.</para>
 <para>
@@ -463 +291 @@
 is made by mouse. Cf <xref linkend="mouse"/></para>
 </note>
-</sect3>
-
-<sect3 id="menutxt"><title>The menu bar made up of 3 submenus</title>
-<sect4 id="filesubmenu"><title><guisubmenu>File</guisubmenu> submenu</title>
+</sect2>
+
+<sect2 id="menutxt"><title>The menu bar made up of 3 submenus</title>
+<sect3 id="filesubmenu"><title><guisubmenu>File</guisubmenu> submenu</title>
 <para>
     <figure id="fig_xxx_0203">
@@ -475 +303 @@
     </figure>
 </para>
-
 <para>
 <itemizedlist>
-<listitem>
-<para>
-<menuchoice><guimenuitem>Open:</guimenuitem></menuchoice> to open a second file.  Same procedure as during the
-launching of XXX.  The new file can be on a different grid, with
-different variables, with a different time base.
-</para></listitem>
-<listitem><para><menuchoice><guimenuitem>New XXX:</guimenuitem></menuchoice> to open a second XXX window identical to the first.</para></listitem>
-<listitem><para><menuchoice><guimenuitem>Quit:</guimenuitem></menuchoice> to close the XXX window.</para></listitem>
+<listitem><para><menuchoice><guibutton>Open:</guibutton></menuchoice> to open a new file. Same procedure as during the <link linkend="launch_xxx_1">launch of XXX</link>.  The new file can be on a different grid, with different variables, with a different time base...
+</para></listitem>
+<listitem><para><menuchoice><guibutton>New XXX:</guibutton></menuchoice> to open a second XXX window identical to the first one.</para></listitem>
+<listitem><para><menuchoice><guibutton>Quit:</guibutton></menuchoice> to close the XXX window.</para></listitem>
 </itemizedlist>
 </para>
-
-</sect4>
-<sect4 id="saveassubmenu"><title><guisubmenu>Save As</guisubmenu> submenu</title>
+</sect3>
+<sect3 id="saveassubmenu"><title><guisubmenu>Save As</guisubmenu> submenu</title>
 <para>
     <figure id="fig_xxx_0204">
@@ -499 +321 @@
     </figure>
 </para>
-
 <para>
 <itemizedlist>
-<listitem><para><menuchoice><guimenuitem>Postscript:</guimenuitem></menuchoice> to save in Postscript format</para></listitem>
-<listitem><para><menuchoice><guimenuitem>Animated gif:</guimenuitem> </menuchoice>to create an animation from the XXX window.
-Careful, the creation of an animation is only possible if none of the
-plots have a time axis, and if the plots are all on the same time base
-(calendar).  On the other hand, animations of horizontal and vertical
-plots, with different color palettes (for those not on an X-terminal),
-are possible.
-<note>
-<para>
-the creation of animations has a tendency to saturate the video
-memory of X-terminals, crashing the entire program...</para>
-</note>
-</para></listitem>
-<listitem><para><menuchoice><guimenuitem>Gif:</guimenuitem></menuchoice> to save a gif of the XXX graphics window.</para></listitem>
-<listitem><para><menuchoice><guimenuitem>IDL procedure:</guimenuitem></menuchoice> to save the command history that has created the
-plot.  For example if I save the commands in <filename>xxx_figure.pro</filename>, I can
-then launch a new IDL session and type:
+<listitem><para><menuchoice><guibutton>Postscript:</guibutton></menuchoice> to save the plotting window in Postscript format</para></listitem>
+<listitem><para><menuchoice><guibutton>Animated gif:</guibutton></menuchoice> to create an animation of the plotting window.
+<note><para>The creation of an animation is only possible if none of the plots have a time axis, and if the plots are all on the same time base (calendar). On the other hand, animations of horizontal and vertical plots, with different color palettes (for those not on an X-terminal), are possible.</para></note>
+<note><para> the creation of animations has a tendency to saturate the video memory of X-terminals, crashing the entire program...</para></note>
+</para></listitem>
+<listitem><para><menuchoice><guibutton>Gif:</guibutton></menuchoice> to save a gif of the plotting window.</para></listitem>
+<listitem><para><menuchoice><guibutton>IDL procedure:</guibutton></menuchoice> to save the command history that has created the plot in an IDL procedure that can be reexecuted later. For example if I save the commands in <filename>xxx_figure.pro</filename> file, when ever I want, I can then launch a new IDL session and type:
   <screen format="linespecific">
 <prompt>&promptidl;</prompt> <userinput>@init</userinput>
 <prompt>&promptidl;</prompt> <userinput>xxx_figure</userinput>
 </screen>
-</para>
-<para>
 and I'll obtain the saved figure.
   <screen format="linespecific">
@@ -533 +342 @@
 <prompt>&promptidl;</prompt> <userinput>@ps</userinput>
 </screen>
-will then create a Postscript file of the figure.</para><para></para></listitem>
-<listitem><para><menuchoice><guimenuitem>RESTORE kwd of xxx:</guimenuitem></menuchoice></para></listitem>
-<listitem><para><menuchoice><guimenuitem>Print to prompt:</guimenuitem></menuchoice> lists in the IDL window the command history that
-created the last plot.  Useful primarily for debugging...</para></listitem>
+will then create a Postscript file of the figure.
+</para></listitem>
+<listitem><para id='restore'><menuchoice><guibutton>RESTORE kwd of xxx:</guibutton></menuchoice> to save the xxx widget (all buttons and parameters storeed in memory...) in a binary file in order to quit xxx and relauch it later with <link linkend="launch_xxx_3"><prompt>&promptidl;</prompt> <userinput><command>xxx</command>, <parameter>restore = 'file.dat'</parameter></userinput></link> and get exactly the same configuration.</para></listitem>
+<listitem><para><menuchoice><guibutton>Print to prompt:</guibutton></menuchoice> lists in the IDL window the command history that created the last plot. Useful primarily for debugging...</para></listitem>
 </itemizedlist>
 </para>
-</sect4>
-<para>Test the various possibilities in the <guimenu>Save As</guimenu> menu.</para>
-<sect4 id="flagsubmenu"><title><guisubmenu>Flag options</guisubmenu> submenu</title>
+</sect3>
+<sect3 id="flagsubmenu"><title><guisubmenu>Flag options</guisubmenu> submenu</title>
 <para>
     <figure id="fig_xxx_0205">
@@ -550 +358 @@
     </figure>
 </para>
-
 <para>
 <itemizedlist>
 <listitem><para><guibutton>Portrait/Landscape:</guibutton> changes the configuration of the plot.</para></listitem>
 <listitem><para><guibutton>Overlay:</guibutton> to plot contours of a different field on top the
-one represented as color-filled contours.  It is necessary to relaunch the
-entire plot to make this work!</para></listitem>
+one represented as color-filled contours. It is necessary to relaunch the entire plot to make this work!</para></listitem>
 <listitem><para><guibutton>Vecteur:</guibutton> to plot a vector field on top of contours. Only
-works on horizontal plots (<filename>plt.pro</filename>).  As for Overlay, a relaunch of
-the entire plot is necessary.</para></listitem>
-<listitem><para><guibutton>Longitude / x index:</guibutton> switches longitude labelling of the plot
-subdomain from degrees to indices following i. </para></listitem>
-<listitem><para><guibutton>Latitude / y index:</guibutton> switches latitude labelling of the plot
-subdomain from degrees to indices following j. </para></listitem>
+works on horizontal plots (<filename>plt.pro</filename>).  As for Overlay, a relaunch of the entire plot is necessary.</para></listitem>
+<listitem><para><guibutton>Longitude / x index:</guibutton> switches longitude labelling of the plot subdomain from degrees to indices following i. </para></listitem>
+<listitem><para><guibutton>Latitude / y index:</guibutton> switches latitude labelling of the plot subdomain from degrees to indices following j. </para></listitem>
 </itemizedlist>
 </para>
-</sect4>
-<para>
-Test the various possibilities in the <guimenu>Flag options</guimenu> menu.
-</para>
-<caution>
-<para>
-Careful, a selected option remains selected until it is reclicked.
-</para>
-</caution>
-</sect3>
-
-<sect3 id="oktxt"><title>OK button</title>
+<caution><para>Careful, a selected option remains selected until it is reclicked.</para></caution>
+</sect3>
+</sect2>
+
+<sect2 id="oktxt"><title>OK button</title>
 <para>click on this <guibutton>OK</guibutton> button is required to make a new plot appear</para>
-</sect3>
-
-<sect3 id="pagelayouttxt"><title>Page Layout</title>
+</sect2>
+
+<sect2 id="pagelayouttxt"><title>Page Layout</title>
 <para>specify the number of columns and rows for plots on the sheet of paper.</para>
 <para>
@@ -591 +387 @@
     </figure>
 </para>
-<para>For example: For 2 cln and 2 row. For explanations, see further.</para>
 <para>
     <figure id="fig_xxx_0206a">
-      <title>A frame with several graphics</title>
+      <title>Example: For 2 cln and 2 row</title>
           <imageobject>
             <imagedata fileref="figpng/xxx_0206a.png"/>
@@ -600 +395 @@
     </figure>
 </para>
-</sect3>
-
-<sect3 id="variableslisttxt"><title><guimenuitem>List of variables</guimenuitem></title>
+</sect2>
+
+<sect2 id="variableslisttxt"><title><guimenuitem>List of variables</guimenuitem></title>
 <para> you can choose the variable to work on.</para>
 <para>
     <figure id="fig_xxx_0207">
-      <title>differents Variables avaible</title>
+      <title>Example of differents Variables avaible</title>
           <imageobject>
             <imagedata fileref="figpng/xxx_0207.png"/>
@@ -612 +407 @@
     </figure>
 </para>
-</sect3>
-
-<sect3 id="fileslisttxt"><title><guimenuitem>List of open files</guimenuitem></title>
+</sect2>
+
+<sect2 id="fileslisttxt"><title><guimenuitem>List of open files</guimenuitem></title>
 <para> you can choose the file to work on.</para>
 <para>
     <figure id="fig_xxx_0208">
-      <title>List of open files</title>
+      <title>Example of list of open files</title>
           <imageobject>
             <imagedata fileref="figpng/xxx_0208.png"/>
@@ -624 +419 @@
     </figure>
 </para>
-</sect3>
-
-<sect3 id="commandtexttxt"><title><guimenuitem>Command text</guimenuitem></title>
-<para>To specify the computation you want to do. 
-Examples: </para>
-<sect4 id="withoutcommandtexttxt"><title><guimenuitem> Without any Command Text</guimenuitem></title>
-<para>
-    <figure id="fig_xxx_0209">
-      <title>Graphic by default</title>
-          <imageobject>
-            <imagedata fileref="figpng/xxx_0209.png"/>
-          </imageobject>
-    </figure>
-</para>
-</sect4>
-
-<sect4 id="withrealcont"><title><guimenuitem> With the command text /realcont</guimenuitem></title>
-<para>
-    <figure id="fig_xxx_0210a">
-      <title>Command text area</title>
-          <imageobject>
-            <imagedata fileref="figpng/xxx_0210a.png"/>
-          </imageobject>
-    </figure>
-</para>
-<para>
-    <figure id="fig_xxx_0210">
-      <title>Graphic with the command text "/realcont"</title>
-          <imageobject>
-            <imagedata fileref="figpng/xxx_0210.png"/>
-          </imageobject>
-    </figure>
-</para>
-</sect4>
-
-<sect4 id="withmaportho"><title><guimenuitem>With the command text /realcont+ map=[90,0,0]+ /ortho+ cell_fill=2.</guimenuitem></title>
-<para>
-    <figure id="fig_xxx_0211a">
-      <title>Command text area with the right syntax</title>
-          <imageobject>
-            <imagedata fileref="figpng/xxx_0211a.png"/>
-          </imageobject>
-    </figure>
-</para>
-<para>
-    <figure id="fig_xxx_0211">
-      <title>Polar Projection</title>
-          <imageobject>
-            <imagedata fileref="figpng/xxx_0211.png"/>
-          </imageobject>
-    </figure>
-</para>
-</sect4>
-
-<note><para>In the default case, the name given to a field is of no importance.</para></note>
-</sect3>
-
-<sect3 id="calendartxt"><title>Calendar</title>
-<para>
-The calendar is made up of two droplists, which allow specification of
-two dates, the beginning and end of a time series, or the period over
-which to average before plotting.</para>
-<para>Example: The first plot is during January.</para>
-<para>         The second plot is from January to December.</para>
+</sect2>
+
+<sect2 id="commandtexttxt"><title><guimenuitem>Command text</guimenuitem></title>
+<para>
+To specify in the widget part number 7 the computation you want to do on the data
+<note><para>In all cases bellow, the name given to a field (a, b, c,...) is of no importance.</para></note>
+</para>
+<sect3 id="commandtext1"><title><guimenuitem>Linear calculation</guimenuitem></title>
+<para>
+If you want to make basic linear computation (like difference between fields, add/multiply by a constant...). you can simply put the following commands: <screen format="linespecific">a - b</screen><screen format="linespecific">numb1*a</screen><screen format="linespecific">a + numb</screen> or any command with the following format <screen format="linespecific">numb1*a + numb2*b  + numb3*c ... + numb</screen> where numb1, numb2,... correspond to numbers and a, b, c... will be the data to read.
+</para>
+</sect3>
+<sect3 id="commandtext1"><title><guimenuitem>Any kind of computation calculation</guimenuitem></title>
+<para>
+If you want to make a computation more complicated than a basic linear you must put designate the data you want to read between "" (with anything inbetween the "). For example: <screen format="linespecific">"a"^2</screen><screen format="linespecific">"a" - abs("b")</screen><screen format="linespecific">grad("a", 'x')</screen>...
+</para>
+</sect3>
+</sect2>
+
+<sect2 id="calendartxt"><title>Calendar</title>
+<para>
+The calendar is made up of two droplists, which allow specification of two dates, the beginning and end of a time series, or the period over which to average before plotting.</para>
 <para>
     <figure id="fig_xxx_0301">
-      <title>Graphic with 2 different period of study</title>
+      <title>Example: first plot in January, second plot is from January to December</title>
           <imageobject>
             <imagedata fileref="figpng/xxx_0301.png"/>
@@ -696 +449 @@
     </figure>
 </para>
-</sect3>
-
-<sect3 id="domdeftxt"><title>Define the domain</title>
-<para>
-A series of widgets that allow specification of the min/max limits of
-the domain in longitude/x-index, latitude/y-index, and depth in levels
-or meters.  For depth, one can specify in levels for a horizontal
-plot, and in meters for a vertical plot.
-</para>
-
-<sect4 id="withoutdomainspecification"><title><guimenuitem>Without any domain specification</guimenuitem></title>
-<para>
-    <figure id="fig_xxx_0210">
-      <title>Domain by default</title>
-          <imageobject>
-            <imagedata fileref="figpng/xxx_0210.png"/>
-          </imageobject>
-    </figure>
-</para>
-</sect4>
-
-<sect4 id="withzoom"><title><guimenuitem>With a zoom on Oceania</guimenuitem></title>
-<para>We can zoom, between 0 and 1 meter of depth, on the Oceania, by playing with the part Domdef, with this configuration</para>
-<para>
-    <figure id="fig_xxx_0401">
-      <title>Change Domain area</title>
+</sect2>
+
+<sect2 id="domdeftxt"><title>Define the domain</title>
+<para>
+  A series of widgets that allow specification of the min/max limits of the domain in longitude/x-index, latitude/y-index, and depth in levels or meters.
+  <figure id="fig_xxx_0210">
+    <title>Domain by default</title>
+    <imageobject>
+      <imagedata fileref="figpng/xxx_0210.png"/>
+    </imageobject>
+  </figure>
+  <figure id="fig_xxx_0401">
+    <title>Change Domain area: zoom on Oceania</title>
           <imageobject>
             <imagedata fileref="figpng/xxx_0401.png"/>
           </imageobject>
-    </figure>
-</para>
-<para>This configuration give us:</para>
-<para>
-    <figure id="fig_xxx_0402">
-      <title>Graphic with a specified domain</title>
-          <imageobject>
-            <imagedata fileref="figpng/xxx_0402.png"/>
-          </imageobject>
-    </figure>
-</para>
-</sect4>
-</sect3>
-
-<sect4 id="depthspecificationtxt"><title><guimenuitem>With the specification of the depth</guimenuitem></title>
-<para>If we want to see the temperature of the ocean between 125 and 126 meters of depth</para>
-<para>
-    <figure id="fig_xxx_0403">
-      <title>Change depth area</title>
-          <imageobject>
-            <imagedata fileref="figpng/xxx_0403.png"/>
-          </imageobject>
-    </figure>
-</para>
-<para>
-    <figure id="fig_xxx_0404">
-      <title>Oceania at 125 metters of depth without a mask</title>
-          <imageobject>
-            <imagedata fileref="figpng/xxx_0404.png"/>
-          </imageobject>
-    </figure>
-</para>
-<para>As you can see, at this depth, we can see the difference between the continent at the surface and the real goegraphy of the terrain. If we want to see only the terrain at the specified depth, we have to put a mask. Cf <xref linkend="fig_xxx_0103"/></para>  
-<para>You can define precisely the depth you want to see:</para>
-<para>
-    <figure id="fig_xxx_0405">
-      <title>The Precise Depth menu</title>
-          <imageobject>
-            <imagedata fileref="figpng/xxx_0405.png"/>
-          </imageobject>
-    </figure>
-</para>
-</sect4>
-
-
-<sect3 id="specificationstxt"><title>specify your plot</title>
-<sect4 id="minmaxintervaltxt"><title><guimenuitem>Specify the min, the max and the interval</guimenuitem></title>
-<para>
-You can specify the min, max, and contour interval by filling out the
-provided boxes!
-</para>
-<para>
-You can restore configuration by default by pressing the "default" button.
-</para>
-<para>
-    <figure id="fig_xxx_0501">
-      <title>Specification area</title>
-          <imageobject>
-            <imagedata fileref="figpng/xxx_0501.png"/>
-          </imageobject>
-    </figure>
-</para>
-</sect4>
-
-<sect4 id="colortxt"><title><guimenuitem>Specify the palette to be used</guimenuitem></title>
-<para>For the color palette, you can either specify the name
-or go search for one among the palettes available.
-</para>
+  </figure>
+  <figure id="fig_xxx_0402">
+    <title>This configuration give us:</title>
+    <imageobject>
+      <imagedata fileref="figpng/xxx_0402.png"/>
+    </imageobject>
+  </figure>
+  <figure id="fig_xxx_0403">
+    <title>Change depth area: between depth 125 and 126</title>
+    <imageobject>
+      <imagedata fileref="figpng/xxx_0403.png"/>
+    </imageobject>
+  </figure>
+  <figure id="fig_xxx_0404">
+    <title>temperature of the ocean at depth 125 meters without proper land/sea mask</title>
+    <imageobject>
+      <imagedata fileref="figpng/xxx_0404.png"/>
+    </imageobject>
+  </figure>
+  As you can see, at this depth, we better define a land/sea mask when loading the grid. Cf <xref linkend="fig_xxx_0103"/>
+</para>
+</sect2>
+
+<sect2 id="specificationstxt"><title>specify your plot</title>
+
+<sect3 id="minmaxintervaltxt"><title><guimenuitem>Specify min, max and contour interval</guimenuitem></title>
+<para>
+  <figure id="fig_xxx_0501">
+    <title>min, max, and contour interval specifications</title>
+    <imageobject>
+      <imagedata fileref="figpng/xxx_0501.png"/>
+    </imageobject>
+  </figure>
+  You can restore configuration by default by pressing the "default" button.
+  <note><para>The path of the file <ulink url="../../ToBeReviewed/WIDGET/AUTOUR_de_XXX/definedefaultextra.pro?format=raw"><filename>definedefaultextra.pro</filename></ulink> that defines the default values for each variable names is displayed when the cursor hovers over the button Default. This file contains a case statement based on the name of the variable and defining the min, max, contour interval and other keywords that should be used as default for the specified variable. You can copy this file in your own <filename class="directory"><envar>${HOME}</envar>/My_IDL/</filename> directory and easily modify it to suit your favorite default values.</para></note>
+</para>
+</sect3>
+
+<sect3 id="colortxt"><title><guimenuitem>Specify the palette to be used</guimenuitem></title>
+<para>For the color palette, you can either specify the name or go search for one among the palettes available.</para>
 <para>
     <figure id="fig_xxx_0502">
@@ -801 +513 @@
     </figure>
 </para>
-</sect4>
-
-<para>
-The "keywords" window allows specification of all desired
-keywords. These keywords can be those of
-<filename>plt.pro</filename>, <filename>pltt.pro</filename>, <filename>pltz.pro</filename>,
-<filename>plt1d.pro</filename>, or those of contour, plot, or all other programs that are
-used. Cf <xref linkend="commandtexttxt"/> 
-</para>
-</sect3>
-
-
+</sect3>
+
+<sect3 id="kwdtxt"><title><guimenuitem>Add any keyword</guimenuitem></title>
+<para>
+  The "keywords" window allows specification of all desired keywords. There is a few examples of the use of this "keywords" window.
+  <figure id="fig_xxx_0209">
+    <title>Without any additional keyword</title>
+    <imageobject>
+      <imagedata fileref="figpng/xxx_0209.png"/>
+    </imageobject>
+  </figure>
+  <figure id="fig_xxx_0210a">
+    <title>add "/realcont" keyword</title>
+    <imageobject>
+      <imagedata fileref="figpng/xxx_0210a.png"/>
+    </imageobject>
+  </figure>
+  <figure id="fig_xxx_0210">
+    <title>Graphic with "/realcont" keyword</title>
+    <imageobject>
+      <imagedata fileref="figpng/xxx_0210.png"/>
+    </imageobject>
+  </figure>
+  <figure id="fig_xxx_0211a">
+    <title>add "/realcont, map=[90,0,0], /ortho, cell_fill=2" keywords</title>
+    <imageobject>
+      <imagedata fileref="figpng/xxx_0211a.png"/>
+    </imageobject>
+  </figure>
+  <figure id="fig_xxx_0211">
+    <title>Graphic with "/realcont, map=[90,0,0], /ortho, cell_fill=2" keywords</title>
+    <imageobject>
+      <imagedata fileref="figpng/xxx_0211.png"/>
+    </imageobject>
+  </figure>
+</para>
+</sect3>
 </sect2>
 </sect1>
+
 <sect1 id="mouseactions"><title>Mouse Actions</title>
 
@@ -987 +725 @@
 <step>
 <para>
+load xxx with the command:
+  <screen format="linespecific">
+    <prompt>&promptidl;</prompt> <userinput><command>xxx</command>, <parameter>'Levitus98_1m_01_12_Temperature_Pot_ORCA05.nc'</parameter>, <parameter>'tst_initorca05'</parameter></userinput>
+  </screen>
+</para>
+</step>
+<step>
+<para>
 Select a 3-D field and create 6 frames for the sheet of paper.
 </para>
@@ -1055 +801 @@
 <procedure>
 <para>
-in frame 5, let's create the same plot as in frame 2 except with different dates
+in frame 5, let's create the same plot as in frame 2 except we use pltv instead of plt
 </para>
 <step>
@@ -1069 +815 @@
 <step>
 <para>
-change the date
+change plt for pltv
 </para>
 </step>
@@ -1094 +840 @@
 <listitem>
 <para>
+in the IDL window type (as many time you click on a button since a problem occurs in xxx !!!), 
+  <screen format="linespecific">
+<prompt>&promptidl;</prompt> <userinput>retall</userinput>
+</screen>
+</para></listitem>
+<listitem>
+<para>
 in the IDL window, type
   <screen format="linespecific">
-<prompt>&promptidl;</prompt> <userinput>retall</userinput>
+<prompt>&promptidl;</prompt> <userinput>domdef</userinput>
 </screen>
 </para></listitem>

trunk/SRC/Documentation/xmldoc/savesaxo.sh

@@ -3 +3 @@
 # update :
 # $Id$
+# smasson Wed Sep 13 14:18:02 CEST 2006
+# add the directory-overview.html from dir-files.html in idldoc_html_output
 # fplod 2006-09-07T08:09:47Z aedon.locean-ipsl.upmc.fr (Darwin)
 # main is rename to websaxo
@@ -367 +369 @@
      mv ${file_html}_modify ${file_html}
     done
+    # add the directory-overview.html from dir-files.html in idldoc_html_output
+    list_html=$(find ../idldoc_html_output -name dir-files.html)
+    for file_html in ${list_html}
+    do
+      fout=../idldoc_assistant_output/${file_html#../idldoc_html_output/*}
+      fout=${fout%/*}/directory-overview.html 
+      sed -e 's/?format=raw//g' ${file_html} > ${fout}
+    done
     echo "iii : you can see log file in ${log}"
     echo "iii : and look ${output}/idldoc-warnings.html#undoc"

trunk/SRC/Documentation/xmldoc/websaxo.xml

@@ -34 +34 @@
   </articleinfo>
 
+  <note><para>
+This page is a miror of <ulink url="http://forge.ipsl.jussieu.fr/saxo">SAXO web page</ulink> and allows you to browse IDL help pages in local.
+  </para></note>
 
 <sect1 id="whatissaxo">

trunk/SRC/Documentation/xmldoc/whatsnew.xml

@@ -42 +42 @@
 </para>
 </sect1>
+
+<sect1 id="changeset175">
+<title>Changeset 175 (2006-09-13)</title>
+<para>
+Merge SAXO and IDL online_help (needs at least IDL 6.2 to work).
+</para>
+<para>
+Details can be seen in <ulink url="http://forge.ipsl.jussieu.fr/saxo/changeset/175">Changeset 175</ulink>.
+</para>
+</sect1>
+
+<sect1 id="changeset174">
+<title>Changeset 172-174 (2006-09-11/12)</title>
+<para>
+ROMS output compatibility
+</para>
+<para>
+Details can be seen in <ulink url="http://forge.ipsl.jussieu.fr/saxo/changeset/172">Changeset 172</ulink>, <ulink url="http://forge.ipsl.jussieu.fr/saxo/changeset/173">Changeset 173</ulink>, <ulink url="http://forge.ipsl.jussieu.fr/saxo/changeset/174">Changeset 174</ulink>.
+</para>
+</sect1>
+
+<sect1 id="changeset163">
+<title>Changeset 163 (2006-08-29)</title>
+<para>
+Last major commit related to the english translation of headers and their format. Better <ulink url="http://forge.ipsl.jussieu.fr/saxo/browser/trunk/SRC/Documentation/idldoc_html_output/index.html?format=raw">idldoc html documentationb </ulink> and introduce SAXO online_help created by idldoc assistant.
+</para>
+<para>
+Details can be seen in <ulink url="http://forge.ipsl.jussieu.fr/saxo/changeset/163">Changeset 163</ulink>.
+</para>
+</sect1>
+
+<sect1 id="changeset152">
+<title>Changeset 152 (2006-08-10)</title>
+<para>
+This revision includes new <ulink url="http://forge.ipsl.jussieu.fr/saxo/browser/trunk/SRC/ToBeReviewed/PLOTS/DESSINE/pltv.pro">pltv</ulink> (a bix between plt and tvplus) plotting procedure.
+</para>
+<para>
+Details can be seen in <ulink url="http://forge.ipsl.jussieu.fr/saxo/changeset/152">Changeset 152</ulink>.
+</para>
+</sect1>
+
 <sect1 id="changeset114">
 <title>Changeset 114 (2006-06-19)</title>
@@ -51 +92 @@
 </para>
 </sect1>
+
 <sect1 id="changeset73">
 <title>Changeset 73 (2006-05-22)</title>
@@ -60 +102 @@
 </para>
 </sect1>
+
 <sect1 id="changeset69">
 <title>Changeset 69 (2006-05-11)</title>
@@ -83 +126 @@
 </para>
 </sect1>
+
 <sect1 id="changeset7">
 <title>Changeset 7 (2006-04-24)</title>
@@ -92 +136 @@
 </para>
 </sect1>
+
 <sect1 id="changeset2">
 <title>Changeset 2 (revision date=2002-09-11 actually done 2006-04-13)</title>