[Laszlo-checkins] r10679 - openlaszlo/trunk/WEB-INF/lps/lfc/data

[dda@openlaszlo.org]

Author: dda
Date: 2008-08-13 13:09:53 -0700 (Wed, 13 Aug 2008)
New Revision: 10679

Modified:
   openlaszlo/trunk/WEB-INF/lps/lfc/data/LzDatapath.lzs
   openlaszlo/trunk/WEB-INF/lps/lfc/data/LzDatapointer.lzs
Log:
Change 20080813-dda-A by dda at lester.local on 2008-08-13 15:46:48 EDT
    in /Users/dda/laszlo/src/svn/openlaszlo/trunk-doc2
    for http://svn.openlaszlo.org/openlaszlo/trunk

Summary: quick fix for unnamed links

New Features:

Bugs Fixed: (LPP-6429) refguide. <datapath> page differences.

Technical Reviewer: (pending)
QA Reviewer: (pending)
Doc Reviewer: liorio (pending)

Documentation:

Release Notes:

Details:
    Certain links using <xref> to an attribute name, using linkend="ClassName.__ivars__.attrname",
    can show up as valid links, but with the title of the link being '???'.  I'm not sure exactly
    what the trouble is, there are some indications that linking has been reworked in DocBook5:
    see http://www.sagehill.net/docbookxsl/Db5Tools.html#Db5UnivLinking .  I played a little
    with rewriting the <xref> links using <link>.  At any rate, an acceptable workaround is
    to replace any <xref> references to attributes to use <link> with an explicit name.
    For example:
          <xref linkend="LzDatapointer.__ivars__.rerunxpath"/>
    can be rewritten as:
          <link linkend="LzDatapointer.__ivars__.rerunxpath">rerunxpath</link> 
    I don't know why, but references to methods work (maybe because the ID names for them
    are more straightforward?).

Tests:
    Rebuilt docs, checked by eye.



Modified: openlaszlo/trunk/WEB-INF/lps/lfc/data/LzDatapath.lzs
===================================================================
--- openlaszlo/trunk/WEB-INF/lps/lfc/data/LzDatapath.lzs	2008-08-13 20:09:25 UTC (rev 10678)
+++ openlaszlo/trunk/WEB-INF/lps/lfc/data/LzDatapath.lzs	2008-08-13 20:09:53 UTC (rev 10679)
@@ -38,8 +38,8 @@
   * <p>
   * A node can only have one datapath, and datapaths always have the name
   * <code>datapath</code>.  Additional options available on datapath such
-  * as <xref linkend="LzDatapath.__ivars__.pooling"/> and 
-  * <xref linkend="LzDatapath.__ivars__.replication"/> are specified 
+  * as <link linkend="LzDatapath.__ivars__.pooling">pooling</link> and 
+  * <link linkend="LzDatapath.__ivars__.replication">replication</link> are specified 
   * by writing the <tagname>datapath</tagname> tag as a separate node.
   * </p>
   * 

Modified: openlaszlo/trunk/WEB-INF/lps/lfc/data/LzDatapointer.lzs
===================================================================
--- openlaszlo/trunk/WEB-INF/lps/lfc/data/LzDatapointer.lzs	2008-08-13 20:09:25 UTC (rev 10678)
+++ openlaszlo/trunk/WEB-INF/lps/lfc/data/LzDatapointer.lzs	2008-08-13 20:09:53 UTC (rev 10679)
@@ -23,7 +23,7 @@
   * a notation similar to the UNIX file-system to refer to nodes within a
   * dataset. Once a datapointer is bound to a node in a dataset it will
   * keep pointing to that node until it is moved. If the dataset is edited,
-  * the behavior of the datapointer will be controlled by its <xref linkend="LzDatapointer.__ivars__.rerunxpath"/> attribute. If this attribute is
+  * the behavior of the datapointer will be controlled by its <link linkend="LzDatapointer.__ivars__.rerunxpath">rerunxpath</link> attribute. If this attribute is
   * true, it will continue pointing to its current
   * node as long as it is valid.</p>
   *