[Lxr-commits] CVS: html/prototype advancedconfig.shtml, 1.4, 1.5 bugsandlimits.shtml, 1.15, 1.16 in
Brought to you by:
ajlittoz
Menu
▾
▴
[Lxr-commits] CVS: html/prototype advancedconfig.shtml, 1.4, 1.5 bugsandlimits.shtml, 1.15, 1.16 index.shtml, 1.11, 1.12 installNavBtn.shtml, 1.1, 1.2 logos.shtml, 1.2, 1.3 newfeatures.shtml, 1.15, 1.16 numbering.shtml, 1.1, 1.2 styles.shtml, 1.2, 1.3 troubleshooting.shtml, 1.5, 1.6
|
From: Andre-Littoz <ajl...@us...> - 2014-01-18 09:54:20
|
Update of /cvsroot/lxr/html/prototype In directory sfp-cvs-1.v30.ch3.sourceforge.com:/tmp/cvs-serv25121/prototype Modified Files: advancedconfig.shtml bugsandlimits.shtml index.shtml installNavBtn.shtml logos.shtml newfeatures.shtml numbering.shtml styles.shtml troubleshooting.shtml Log Message: Switching to HTML5: directory prototype/ for translation in any language Index: advancedconfig.shtml =================================================================== RCS file: /cvsroot/lxr/html/prototype/advancedconfig.shtml,v retrieving revision 1.4 retrieving revision 1.5 diff -u -d -r1.4 -r1.5 --- advancedconfig.shtml 3 Nov 2012 21:07:08 -0000 1.4 +++ advancedconfig.shtml 18 Jan 2014 09:54:16 -0000 1.5 @@ -1,130 +1,113 @@ -<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01//EN"> -<!-- $Id$ --> -<html> <!--#set var="pageLang" value="en" --> -<head> - <meta http-equiv="content-type" content="text/html; charset=UTF-8"> - <meta http-equiv="Content-Language" content="<!--#echo var="pageLang" -->"> - <title>LXR Advanced Configuration</title> - <link rel="stylesheet" type="text/css" href="/backstore/LXRweb.css"> - <link rel="icon" type="image/x-icon" href="/backstore/LXRlogo2.ico"> -</head> - -<body> - <!--#set var="pageHeaderTitle" value="LXR Advanced Configuration" --> - <!--#set var="homePageHeader" value="0" --> - <!--#include virtual="/backstore/header.shtml" --> +<!--#set var="pageMetaTitle" value="LXR Advanced Configuration" --> +<!--#set var="pageHeaderTitle" value="LXR Advanced Configuration" --> +<!--#set var="homePageHeader" value="0" --> +<!--#include virtual="/backstore5/header.shtml" --> +<!-- $Id$ --> +<section> <p class="normal"> -LXR operation is driven from 4 sources: +LXR operation is driven from 4 sources. +Customisable configuration files are located in the <em>templates/</em> directory. +However, +<em>generic.conf</em> is in the <em>lib/LXR/Lang/</em> directory, +next to the <em>Generic.pm</em> driver. </p> - <ol> - <li>main configuration file <em>lxr.conf</em> - <ul> - <li><a href="LxrConf/lxrconfstruct.shtml"> - Global architecture</a> - of this file - <p class="comment"> - Reading highly recommended before other sub-topics - </p> - </li> - <li><a href="LxrConf/lxrconfglobparms.shtml"> - Global parameters</a> - </li> - <li><a href="LxrConf/lxrconftreeparms.shtml"> - Tree-specific parameters</a> - </li> - <li> - Clarification on - <a href="LxrConf/lxrconffilepaths.shtml">file paths</a> - <p class="comment"> - To be read carefully - if you want to mix LXR within an englobing server - </p> - </li> - <li><a href="LxrConf/lxrconfmtsdb.shtml"> - Multiple projects, single database</a> - <p class="comment"> - Possible but not really recommended, - can lead to indexing errors - </p> - </li> - <li><a href="LxrConf/lxrconfmtmdb.shtml">Multiple projects, multiple databases</a> - </li> - <li><a href="LxrConf/lxrconfoverride.shtml">Overriding global parameters</a> for a single tree - </li> - <li><a href="LxrConf/lxrconfexclude.shtml">Excluding subdirectories</a> from view - </li> - <li><a href="LxrConf/lxrconfexclude.shtml#excludeFiles">Excluding files</a> from view - <p class="comment"> -Not recommended unless you know what you're doing - </p> - </li> - <li><a href="LxrConf/lxrconfinclude.shtml">Setting include paths</a> - </li> - <li>Defining <a href="LxrConf/lxrconfmaps.shtml">rewrite rules for include paths</a></li> - <li><a href="LxrConf/lxrconfcondvars.shtml">Conditional variables</a></li> - <li><a href="LxrConf/lxrconfgraphics.shtml">Displaying graphics files</a></li> - <li>Using <a href="LxrConf/lxrconfcusticons.shtml">custom icons</a> in directory listing</li> - </ul> + <div class="boxed"> + <p class="comment"> + <span class="caution">Remember the golden rule:</span> +always copy ANY template to <em>custom.d/</em> directory +(<em>lxrconf.d/</em> in releases 0.11, +LXR root directory in older releases) +before editing it. +Then update its location in <em>lxr.conf</em>. + </p> + </div> + <h1>Main configuration file <em>lxr.conf</em></h1> + <ul> + <li><a href="LxrConf/lxrconfstruct.shtml"> +Global architecture</a> +of this file + <p class="comment"> +Reading highly recommended before other sub-topics + </p> </li> - <li>HTML styles definition file <em>lxr.css</em> + <li><a href="LxrConf/lxrconfglobparms.shtml"> +Global parameters</a> + </li> + <li><a href="LxrConf/lxrconftreeparms.shtml"> +Tree-specific parameters</a> + </li> + <li> +Clarification on +<a href="LxrConf/lxrconffilepaths.shtml">file paths</a> <p class="comment"> -Refer to the User's Manual for the definition and usage +To be read carefully +if you want to mix LXR within an englobing server + </p> + </li> + <li><a href="LxrConf/lxrconfmtsdb.shtml"> +Multiple projects, single database</a> + <p class="comment"> +Possible but not really recommended, +can lead to indexing errors + </p> + </li> + <li><a href="LxrConf/lxrconfmtmdb.shtml">Multiple projects, multiple databases</a> + </li> + <li><a href="LxrConf/lxrconfoverride.shtml">Overriding global parameters</a> for a single tree + </li> + <li><a href="LxrConf/lxrconfexclude.shtml">Excluding subdirectories</a> from view + </li> + <li><a href="LxrConf/lxrconfexclude.shtml#excludeFiles">Excluding files</a> from view + <p class="comment"> +Not recommended unless you know what you're doing + </p> + </li> + <li><a href="LxrConf/lxrconfinclude.shtml">Setting include paths</a> + </li> + <li>Defining <a href="LxrConf/lxrconfmaps.shtml">rewrite rules for include paths</a></li> + <li><a href="LxrConf/lxrconfcondvars.shtml">Conditional variables</a></li> + <li><a href="LxrConf/lxrconfgraphics.shtml">Displaying graphics files</a></li> + <li>Using <a href="LxrConf/lxrconfcusticons.shtml">custom icons</a> in directory listing</li> + </ul> + <h1>HTML styles definition file <em>lxr.css</em></h1> + <p class="comment"> +Refer to the <cite>User's Manual</cite> for the definition and usage of the numerous styles. The file is organized to take advantage of <em>cascading</em>. Study carefully before making changes. - </p> + </p> + <h1>Templates for pages composition <em>html-x.html</em></h1> + <ul> + <li><a href="Templ/templref.shtml">Reference from <em>lxr.conf</em></a> </li> - <li>templates for pages composition <em>html-x.html</em> - <ul> - <li><a href="Templ/templref.shtml">Reference from <em>lxr.conf</em></a> - </li> - <li><a href="Templ/templvar.shtml">Variants</a> - </li> - <li>Own templates - <p class="comment"> -Read carefully the User's Manual and study the + <li><a href="Templ/templvar.shtml">Variants</a> + </li> + <li>Own templates + <p class="comment"> +Read carefully the <cite>User's Manual</cite> and study the examples shipping with each release - </p> - </li> - </ul> + </p> </li> - <li>language definitions file <em>generic.conf</em> - <span class="normal caution"> - (do not interfere with it unless you know what you are doing) - </span> - <ul> - <li><a href="GenConf/genericconfstruct.shtml">Global architecture</a> - of this file - <p class="comment"> + </ul> + <h1>Language definitions file <em>generic.conf</em></h1> + <span class="normal caution"> +Do not interfere with it unless you know what you are doing. + </span> + <ul> + <li><a href="GenConf/genericconfstruct.shtml">Global architecture</a> +of this file + <p class="comment"> Reading highly recommended before other sub-topics - </p> - </li> - <li>Understanding a <a href="GenConf/genconflang.shtml">language description</a> - </li> - <li>Adding a new language - <p class="comment"> -highly technical, to be provided later - </p> - </li> - </ul> + </p> </li> - </ol> - <p class="normal"> -They are located in the <em>templates/</em> directory. - </p> - <p class="comment"> -Up to release 0.10, <em>generic.conf</em> was in the <em>lib/LXR/Lang</em> directory. - </p> - <div class="boxed"> - <p class="comment"> -<span class="caution">Remember the golden rule:</span> -always copy ANY template to <em>custom.d/</em> directory -(<em>lxrconf.d/</em> in releases 0.11, -LXR root directory in older releases) -before editing it. -Then update its location in <em>lxr.conf</em>. - </p> - </div> - -<!--#include virtual="/backstore/footer.shtml" --> + <li>Understanding a <a href="GenConf/genconflang.shtml">language description</a> + </li> + <li>Adding a new language + <p class="comment"> +Highly technical, to be provided later. + </p> + </li> + </ul> +</section> +<!--#include virtual="/backstore5/footer.shtml" --> Index: bugsandlimits.shtml =================================================================== RCS file: /cvsroot/lxr/html/prototype/bugsandlimits.shtml,v retrieving revision 1.15 retrieving revision 1.16 diff -u -d -r1.15 -r1.16 --- bugsandlimits.shtml 7 Nov 2013 16:17:53 -0000 1.15 +++ bugsandlimits.shtml 18 Jan 2014 09:54:17 -0000 1.16 @@ -1,181 +1,206 @@ -<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01//EN"> -<!-- $Id$ --> -<html> <!--#set var="pageLang" value="en" --> -<head> - <meta http-equiv="content-type" content="text/html; charset=UTF-8"> - <meta http-equiv="Content-Language" content="<!--#echo var="pageLang" -->"> - <title>Known Bugs and Limitations in LXR</title> - <link rel="stylesheet" type="text/css" href="/backstore/LXRweb.css"> - <link rel="icon" type="image/x-icon" href="/backstore/LXRlogo2.ico"> -</head> - -<body> - <!--#set var="pageHeaderTitle" value="Known Bugs and Limitations in LXR" --> - <!--#set var="homePageHeader" value="0" --> - <!--#include virtual="/backstore/header.shtml" --> - <p class="comment"> +<!--#set var="pageMetaTitle" value="Known Bugs and Limitations in LXR" --> +<!--#set var="pageHeaderTitle" value="Known Bugs and Limitations in LXR" --> +<!--#set var="homePageHeader" value="0" --> +<!--#include virtual="/backstore5/header.shtml" --> +<!-- $Id$ --> +<p class="comment"> The following list does not pretend to be exhaustive. It is intended to give some information in current work direction. - </p> - <h2>Known bugs</h2> - <ul> - <li>Ubuntu - <ul> - <li>Apache web server - <p class="normal"> +</p> +<section> + <h1>Known bugs</h1> + <ul> + <li>Ubuntu + <ul> + <li>Apache web server + <p class="normal"> A configuration file is dependent upon <em>mod_version</em> Apache module but Ubuntu Apache (reported at least for Ubuntu 12.04 LTS) does not load the module by default. + <p class="comment"> To enable it run the following command: - </p> + </p> <pre class="shell"> $ <kbd>sudo a2enmod version</kbd> </pre> - <p class="normal"> + <p class="comment"> and restart the server. - </p> - </li> - <li>Templates not found (weird screen) - <p class="normal"> + </p> + </li> + <li>Templates not found (weird screen) + <p class="normal"> When LXR scripts are launched, the current working directory is not set to the <em>LXR root directory</em>. OS-relative file paths in <em>lxr.conf</em> cannot be correctly resolved. - </p> - <p class="normal"> + </p> + <p class="normal"> To fix the problem, edit <em>custom.d/lxr.conf</em>, "HTML subsection", and add the OS-absolute path of the LXR root directory in front of all HTML template designations. When done, copy the modified file to its final destination as usual. - </p> - <p class="comment caution"> + </p> + <p class="comment caution"> DO NOT CHANGE parameters <code>'stylesheet'</code> and <code>'alternate_stylesheet'</code> which are not file paths but HTML references. - </p> - <p class="comment"> + </p> + <p class="comment"> +Fixed in release 2.0.0. This bug may also be Apache specific. - </p> - </li> - </ul> - </li> - <li>Release 1.1.0 - <ul> - <li class="normal"> -Java parser incompletely handles <code>import</code> statement - <p class="normal"> -If your Java code contains <code>import static</code> statements, -the parser fails on <code>static</code> keyword -and enters an endless loop -which freezes the screen on the previous line. - </p> - <p class="comment"> -This bug will be corrected soon in release <del>1.1.1</del> -<ins>1.2.0</ins>. -If it is a serious concern for you, -look at the -<a href="http://sourceforge.net/p/lxr/bugs/">LXR bugs page</a>. -Comment for bug #231 contains a patch for release 1.1.0. - </p> - </li> - <li class="normal">HTML parser may loop endlessly - <p class="comment"> -Bug also present in release 1.0.0 - </p> - <p class="normal"> -When trying to hyperlink <code><A></code> or <code><IMG></code> elements, -the generic-based HTML parser may fail and not recover, -leading to an endless loop. -It is also not protected against "external" URI -(such as <code>http://…</code>) -where the double slash is taken for an empty file path. - </p> - </li> - <li class="normal">Depending on Perl interpreter, -identifier search may error out - <p class="normal"> -Two lines (419 and 485) in <em>ident</em> use relaxed Perl syntax -instead of "bullet-proof" code. -Comment for bug #233 contains a patch. - </p> - </li> - </ul> - </li> - <li>MySQL - <ul> - <li class="normal"> + </p> + </li> + </ul> + </li> + <li>MySQL + <ul> + <li class="normal"> Default storage engine - <p class="normal"> + <p class="normal"> As of MySQL 5.5.5, default storage engine changed from <strong>MyISAM</strong> to <strong>InnoDB</strong>. Despite an improvement in transaction reliability, performance has drastically degraded: indexing by <em>genxref</em> is now twice as long. - </p> - <p class="comment"> + </p> + <p class="comment"> Release 1.0 explicitly requests the <strong>MyISAM</strong> storage engine. - </p> - </li> - </ul> - </li> - <li>PostgreSQL - <ul> - <li class="normal"> + </p> + </li> + </ul> + </li> + <li>PostgreSQL + <ul> + <li class="normal"> Connection method - <p class="normal"> + <p class="normal"> PostgreSQL offers several methods to connect to a database. The default one use Unix-domain sockets. Under some circumstances, the Perl DB library may fail to access the LXR database. The work-around is to request explicitly the TCP access method in the <code>'dbname'</code> configuration parameter by adding: - </p> + </p> <pre class="example"> ;host=localhost </pre> - <p class="comment"> + <p class="comment"> Release 1.0 is changed to use the TCP access method. If Unix domain sockets work for you, remove the <code>host=</code> sub-parameter. - </p> - </li> - </ul> - </li> - <li>Releases 0.11.x - <ul> - <li class="normal"> + </p> + </li> + </ul> + </li> + <li>Supported languages + <p class="normal"> +Many language descriptions are faulty or, at best, incomplete. +Only <strong>C</strong>, <strong>C++</strong> and <strong>Perl</strong> +can be considered reliable. + </p> + <p class="comment"> +The present maintainer does not master all languages. +Do not hesitate to submit bugs. + </p> + </li> + <li>Identifiers not highlighted + <p class="normal"> +This is not really an LXR bug. +<strong>ctags</strong> uses elementary parsers for secondary +languages (read: not C nor C++). +These parsers do not implement complete language grammar. + </p> + </li> + <li>Git support + <p class="normal"> +<del>Not working at all. +The CPAN library module is broken.</del> + </p> + <p class="comment"> +Fixed in release 1.0 + </p> + </li> + <li>Release 1.1.0 + <ul> + <li class="normal"> +Java parser incompletely handles <code>import</code> statement + <p class="normal"> +If your Java code contains <code>import static</code> statements, +the parser fails on <code>static</code> keyword +and enters an endless loop +which freezes the screen on the previous line. + </p> + <p class="comment"> +Fixed in release 1.2.0. + </p> + </li> + <li class="normal">HTML parser may loop endlessly + <p class="comment"> +Bug also present in release 1.0.0 + </p> + <p class="normal"> +When trying to hyperlink <code><A></code> or <code><IMG></code> elements, +the generic-based HTML parser may fail and not recover, +leading to an endless loop. +It is also not protected against "external" URI +(such as <code>http://…</code>) +where the double slash is taken for an empty file path. + </p> + <p class="comment"> +Fixed in release 1.2.0 through implementation of a dedicated parser. + </p> + </li> + <li class="normal">Depending on Perl interpreter, +identifier search may error out + <p class="normal"> +Two lines (419 and 485) in <em>ident</em> use relaxed Perl syntax +instead of "bullet-proof" code. +Comment for bug #233 contains a patch. + </p> + <p class="comment"> +Fixed in release 1.2.0. + </p> + </li> + </ul> + </li> + <li>Releases 0.11.x + <p class="comment caution"> +These releases are deprecated. + </p> + <ul> + <li class="normal"> <em>genxref</em> script for <strong>swish-e</strong> users - <p class="normal"> + <p class="normal"> A clumsy typo was left at line 240, which should read: - </p> + </p> <pre class="example"> $toolloc = `which swish-e 2>/dev/null`; </pre> - <p class="normal"> + <p class="normal"> i.e. remove the extraneous "h". - </p> - <p class="comment"> + </p> + <p class="comment"> This typo prevents detection of the <em>swish-e</em> engine when it has been installed in a "standard" location. - </p> - <p class="normal"> + </p> + <p class="normal"> A space is also missing at line 518, which should read: - </p> + </p> <pre class="example"> - . " -f ".$config->swhishdir."/".$releaseid.".index" + . " -f ".$config->swhishdir."/".$releaseid.".index" </pre> - <p class="comment"> + <p class="comment"> The <code>-f</code> is catenated to the directory name, giving a non-existent directory and leading to incorrect parsing of the rest of the arguments. The command then always fails and the search database is not initialised. - </p> - </li> - <li class="normal"> + </p> + </li> + <li class="normal"> New <em>initial-config.sh</em> script erroneously leaves <em>templates/</em> directory with <code>r--r--r--</code> permissions preventing any access to it. @@ -183,26 +208,26 @@ <pre class="shell"> <samp>$ </samp><kbd>chmod -R a+x templates/</kbd> </pre> - <p class="normal"> + <p class="normal"> After any copy from <em>templates/</em> directory, fix file permissions to allow write/update: - </p> + </p> <pre class="shell"> <samp>$ </samp><kbd>cp templates/<em>some_file</em> lxrconf.d/</kbd> <samp>$ </samp><kbd>chmod u=rwx lxrconf.d/<em>some_file</em></kbd> </pre> - <p class="comment"> + <p class="comment"> Note: this is not a <em>bug</em> but a consequence of the "read-only" state of <em>templates/</em> directory. - </p> - </li> - <li class="normal"> + </p> + </li> + <li class="normal"> In <em>lxr.conf</em>, parameter <code>'stylesheet'</code> is defined as <code>'templates<strong>/html</strong>/lxr.css'</code> instead of <code>'<strong>/</strong>templates/lxr.css'</code>. - </li> - <li class="normal"> + </li> + <li class="normal"> Under some Linux distributions, in single tree context (the most frequent case), <strong>Apache</strong> does not access the LXR root directory @@ -211,207 +236,187 @@ directive (line 28) of file <em>templates/Apache/apache-lxrserver.conf</em> to read: <pre class="example"> - Alias /lxr "<em>your_LXR_root_directory</em>" + Alias /lxr "<em>your_LXR_root_directory</em>" </pre> - </li> - </ul> - </li> - <li>Releases 0.10.x - <p class="normal"> + </li> + </ul> + </li> + <li>Releases 0.10.x + <p class="comment caution"> +These releases are deprecated. + </p> + <ul> + <li class="normal"> Due to shameful haste and quality assurance breach, version 0.10 was released with an unforgivable bug. 0.10.1 corrected it but introduced another one. 0.10.2 partially corrected it, leaving a misplaced <code>%</code> character in a critical subroutine. - </p> - <p class="comment"> -Better wait for 0.11 release. - </p> - </li> - <li>Browsing <em>include</em> files - <p class="normal"> + <p class="comment"> +Upgrade to latest release. + </p> + </li> + <li>Browsing <em>include</em> files + <p class="normal"> If you change the value of any <em>variable</em> (<em>i.e.</em> version, architecture, …) after clicking on an <em>include</em> link, you may get a <em>"file does not exist"</em> error message because the rewrite rules are not correctly recomputed. - </p> - <p class="comment"> -Corrected in 0.11 - </p> - </li> - <li>Supported languages - <p class="normal"> -Many language descriptions are faulty or, at best, incomplete. -Only <strong>C</strong>, <strong>C++</strong> and <strong>Perl</strong> - can be considered reliable. - </p> - <p class="comment"> -The present maintainer does not master all languages. -Do not hesitate to submit bugs. - </p> - </li> - <li>Identifiers not highlighted - <p class="normal"> -This is not really an LXR bug. -<strong>ctags</strong> uses elementary parsers for secondary -languages (read: not C nor C++). -These parsers do not implement the complete language grammar. - </p> - </li> - <li>Git support - <p class="normal"> -Not working at all. -The CPAN library module is broken. - </p> - <p class="comment"> -Fixed in 1.0 - </p> - </li> - </ul> - <h2>Limitations</h2> - <ul> - <li><em>templates/</em> directory - <p class="normal"> + </p> + <p class="comment"> +Fixed in release 0.11 + </p> + </li> + </ul> + </li> + </ul> +</section> + +<section> + <h1>Limitations</h1> + <ul> + <li><em>templates/</em> directory + <p class="normal"> Starting with release 0.11, this directory is set to "read-only" mode to discourage people from making changes. It thus becomes a reliable reference for stored files. Any LXR customisation must be done in the <em>custom.d</em> directory (<em>lxrconf.d/</em> prior to release 1.0). - </p> - <p class="comment"> + </p> + <p class="comment"> Consequence: any file extracted from <em>templates/</em> is tagged "read-only" and its permissions must be reset before making changes. - </p> + </p> <pre class="shell"> <samp>$ </samp><kbd>cp templates/<em>some_file</em> custom.d/</kbd> <samp>$ </samp><kbd>chmod u=rwx custom.d/<em>some_file</em></kbd> </pre> - </li> - <li>Version control systems (CVS, Git, …) - <p class="normal"> + </li> + <li>Version control systems (CVS, Git, …) + <p class="normal"> Free-text search is unavailable due to the specific format of the VCS database (read: they do not use plain files). - </p> - </li> - <li>Directories in CVS - <p class="normal"> + </p> + </li> + <li>Directories in CVS + <p class="normal"> CVS does not manage version for directories. If you change version for something other than <code>HEAD</code>, you get the infamous <em>"file does not exist"</em> error message. - </p> - </li> - <li>Mercurial support - <ul> - <li class="classics"> + </p> + </li> + <li>Mercurial support + <ul> + <li class="classics"> Files may erroneously appear empty in some revisions - </li> - <li class="classics">Directory listing extremely slow - <p class="normal"> + </li> + <li class="classics">Directory listing extremely slow + <p class="normal"> Approximately 0.5 second per line (on a 3.4 GHz processor!); but do not blame Mercurial, something is wrong in LXR code interfacing with the system. - </p> - <p class="comment"> + </p> + <p class="comment"> Please, help to improve performance. - </p> - </li> - </ul> - </li> - <li>Language parsers - <p class="normal"> -They are not compiler grade (and very far from that). + </p> + </li> + </ul> + </li> + <li>Language parsers + <p class="normal"> +They are not compiler-grade (and very far from that). They are limited to lexically extracting runs of characters looking like identifiers (independently of their semantics). - </p> - <ul> - <li>Generic parser (presently used for all languages) - <p class="normal"> + </p> + <ul> + <li>Generic parser (presently used for all languages) + <p class="normal"> Ignores an eventual <em>sigil</em> when assembling identifiers. This results in confusion of symbols with different roles into a single highlighting. - </p> - <p class="comment"> + </p> + <p class="comment"> <em>Sigils</em> are used in Perl to differentiate functions, scalars, arrays and <em>hashes</em>. Similarly, in PHP, variables are prefixed with <code>$</code> while functions have no prefix. - </p> - <p class="normal"> + </p> + <p class="normal"> Ignores identifier classification since it does not manage semantics. This results too in confusion of symbols with different roles into a single highlighting. - </p> - <p class="comment"> + </p> + <p class="comment"> In HTML, tags and attributes with similar symbol have the same highlighting. - </p> - </li> - <li>HTML - <p class="normal"> + </p> + </li> + <li>HTML + <p class="normal"> URI references are hyperlinked only if they point to another document in the source tree. - </p> - <p class="normal"> + </p> + <p class="normal"> The parser gets easily confused if the content part (outside HTML tags) contains quotes or double quotes. It causes an <em>out-of-sync</em> situation. - </p> - </li> - <li>Perl - <p class="normal"> + </p> + </li> + <li>Perl + <p class="normal"> Due to <strong>ctags</strong> limitation, only <code>sub</code>s and no variables are indexed. Variables are accidentally highlighted if their name, without <em>sigil</em>, is the same as a function. - </p> - <p class="normal"> + </p> + <p class="normal"> Occurrences of characters such as <code>#</code>, <code>'</code> or <code>"</code> in patterns are likely to cause <em>out-of-sync</em> situations. - </p> - </li> - <li>PHP - <p class="normal"> + </p> + </li> + <li>PHP + <p class="normal"> <code>include</code> or <code>require</code> will hyperlink to the target file only if the name is a string relative to source-tree root. Also, the name cannot contain quotes (<code>'</code>) or double quotes (<code>"</code>). - </p> - </li> - <li>Python - <p class="normal"> + </p> + </li> + <li>Python + <p class="normal"> Multiple includes from a single <code>import</code> or <code>from</code> instruction are not handled. - </p> - </li> - </ul> - </li> - <li>Difference markup - <ul> - <li><em>Link</em> interface - <p class="normal"> + </p> + </li> + </ul> + </li> + <li>Difference markup + <ul> + <li><em>Link</em> interface + <p class="normal"> You can compare two files differing in only one variable. - </p> - </li> - <li><em>Buttons-and-menus</em> interface - <p class="normal"> + </p> + </li> + <li><em>Buttons-and-menus</em> interface + <p class="normal"> You can compare two files differing in any number of variables provided you set all required variables before clicking on the "Change" button. - </p> - </li> - <li>Changing variable value while displaying differences - <p class="normal"> + </p> + </li> + <li>Changing variable value while displaying differences + <p class="normal"> The new differences will be computed between the most recently selected version and the newly requested, not between the base version (the one active when you clicked on the "diff markup" link) and the newly requested version. - </p> - </li> - </ul> - </li> - </ul> - -<!--#include virtual="/backstore/footer.shtml" --> + </p> + </li> + </ul> + </li> + </ul> +</section> +<!--#include virtual="/backstore5/footer.shtml" --> Index: index.shtml =================================================================== RCS file: /cvsroot/lxr/html/prototype/index.shtml,v retrieving revision 1.11 retrieving revision 1.12 diff -u -d -r1.11 -r1.12 --- index.shtml 31 Dec 2013 15:12:33 -0000 1.11 +++ index.shtml 18 Jan 2014 09:54:17 -0000 1.12 @@ -1,37 +1,62 @@ -<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01//EN"> -<!-- $Id$ --> -<html> <!--#set var="pageLang" value="en" --> -<head> - <meta http-equiv="content-type" content="text/html; charset=UTF-8"> - <meta http-equiv="Content-Language" content="<!--#echo var="pageLang" -->"> - <title>The LXR Project</title> - <link rel="stylesheet" type="text/css" href="/backstore/LXRweb.css"> - <link rel="icon" type="image/x-icon" href="/backstore/LXRlogo2.ico"> - <meta name="keywords" - content="lxr howto" - > -</head> - -<body> - <!--#set var="pageHeaderTitle" value="The LXR project web-site" --> - <!--#set var="homePageHeader" value="1" --> - <!--#include virtual="/backstore/header.shtml" --> +<!--#set var="pageMetaTitle" value="The LXR Project" --> +<!--#set var="pageHeaderTitle" value="The LXR project web-site" --> +<!--#set var="homePageHeader" value="1" --> +<!--#include virtual="/backstore5/header.shtml" --> +<!-- $Id$ --> <h1>Welcome to the official LXR information site</h1> <p class="comment"> Information on this site comes from the LXR developers and is maintained as close as possible to the current version. </p> - <div class="newsframe"> - <h1>Latest news</h1> - <div class="newstext"> +<aside class="newsframe"> + <style scoped type="text/css"> + aside.newsframe + { float: right + ; clear: both + ; margin-left: 1em + ; margin-top: 18px + ; max-height: 550px + ; border: 4pt solid blue + ; background-color: #CCEEFF + ; vertical-align: top + ; padding: 3pt + ; width: 20em + ; max-width: 30% + } + + section.newstext + { width: 98% + ; min-height: 150px + ; max-height: 500px + ; height: auto + ; overflow-x: hidden + } + + h1 + { padding: 6pt + ; margin: 3pt + ; background-color: yellow + ; text-align: center + ; font-size: 14pt + ; font-weight: bold + } + + p + { margin: 2pt 4pt + ; font-size: 80% + } + </style> + <h1>Latest news</h1> + <section class="newstext"> <!--#include virtual="/news.html" --> - </div> - </div> + </section> +</aside> +<article> <p class="normal"> -<strong class="gothics">LXR</strong> +<b class="gothics">LXR</b> is a general purpose source code indexer and cross-referencer that provides web-based browsing of source code with links to the definition and usage of any identifier. @@ -70,51 +95,55 @@ It is also very useful to study source-code from scratch. In this case, your learning curve is very steep. </p> +</article> - <h2>Available topics:</h2> +<nav> + <h1>Available topics</h1> <ul> - <li> - <a href="1-0-InstallSteps/1-0-install.shtml"> - Installation instructions + <li><a href="1-0-InstallSteps/1-0-install.shtml"> +Installation instructions </a> <p class="normal"> This is a step-by-step <em>How to install LXR</em> guide for the latest release. </p> - <ul>Follow these links for previous releases: + <p class="normal"> +Follow these links for previous releases: + </p> + <ul> <li><a href="0-11-InstallSteps/0-11-install.shtml">0.11</a></li> <li><a href="InstallSteps/install.shtml">0.9.x and 0.10.x</a></li> <li>Older releases, read <em>INSTALL</em> file that ships with the software</li> </ul> </li> - <li> - <a href="advancedconfig.shtml"> - Advanced configuration - </a> + <li><a href="advancedconfig.shtml">Advanced configuration</a> </li> - <li> - <a href="troubleshooting.shtml"> - Troubleshooting - </a> + <li><a href="troubleshooting.shtml">Troubleshooting</a> <p class="normal"> - What to do when something goes wrong? +What to do when something goes wrong? </p> </li> - <li> - <a href="/lxr_inline_doc">Technical information</a> + <li><a href="/lxr_inline_doc">Technical information</a> <p class="normal"> This documentation is automatically extracted from the code. It gives summary information about the LXR browsing components. -Full technical information will soon be available in the -<em>Developer's Manual</em>. +Full technical information is available in the +<a href="http://sourceforge.net/projects/lxr/files/doc/" title="Download page for the manual"> +<cite>Developer's Manual</cite></a>. + </p> + </li> + <li><a href="usermanual.shtml">Online user manual</a> + <p class="normal"> +<span class="caution">Not yet "online"</span>, +this link leads you to a nice Error-404 page instead! </p> </li> <li>PDF version of the <a href="LXRUserManual-beta.pdf">user manual</a> for the next "beta" release -<span class="comment">(link is dead when there is no scheduled -next release. +<span class="comment"> +(link is dead when there is no scheduled next release) It may also happen that the "beta" manual has not been translated; see then the <a href="/en/<!--#echo var="pageDir" --><!--#echo var="pageFile" -->">English version</a> of this page)</span> @@ -132,7 +161,7 @@ <a href="http://sourceforge.net/p/lxr/bugs">bug tracker</a> and you may even ask for <a href="http://sourceforge.net/p/lxr/feature-requests">feature request</a> -if a topic is missing) +if a topic is missing). </p> </li> <li><a href="Tips/tips.shtml">Tips</a> for efficient use @@ -141,36 +170,31 @@ </li> <li><a href="newfeatures.shtml">Next features</a> </li> - <li> - <a href="numbering.shtml"> - Release numbering scheme - </a> + <li><a href="numbering.shtml">Release numbering scheme</a> </li> - <li><a href="styles.shtml"> - Typographical conventions - </a> - of this site + <li><a href="styles.shtml">Typographical conventions</a> +of this site </li> - <li><a href="logos.shtml"> - Candidate logos - </a> + <li><a href="logos.shtml">Candidate logos</a> </li> </ul> +</nav> - <h2>Demo: the LXR tree cross-referenced by LXR itself</h2> +<section> + <h1>Demo: the LXR tree cross-referenced by LXR itself</h1> <p class="comment"> -Releases 0.9.8 to 1.2.0 can be displayed and compared. +Releases 0.9.8 to 2.0.0 can be displayed and compared. </p> <p class="comment"> This demo exhibits two tree-variants: </p> <ul> <li> -<a href="/lxr/source/">"classical" plain files tree</a> +<a href="/demo/source/lxr">"classical" plain files tree</a> containing several released versions </li> <li> -<a href="/cvs/source">CVS repository tree</a> +<a href="/demo/source/cvs">CVS repository tree</a> containing all development history <p class="normal"> Due to SourceForge restrictions, it is only a snapshot. @@ -199,18 +223,24 @@ (<em>e.g.</em> annotations in file display under CVS). </li> </ul> +</section> - <h2>Download and summary information</h2> +<section> + <h1>Download and summary information</h1> <p class=normal> See the <a href="http://sourceforge.net/projects/lxr">project site</a> on SourceForge or have a look at the <a href="http://lxr.linux.no">old project site</a>. </p> +</section> - <h2>Contact the developers</h2> +<section> + <h1>Contact the developers</h1> <p class="normal"> -The developers can be reached through the forum or the trackers. - </p> - -<!--#include virtual="/backstore/footer.shtml" --> +The developers can be reached through the +<a href="http://sourceforge.net/p/lxr/discussion">forum</a> +or the +<a href="http://sourceforge.net/p/lxr/_list/tickets">trackers</a>. +</section> +<!--#include virtual="/backstore5/footer.shtml" --> Index: installNavBtn.shtml =================================================================== RCS file: /cvsroot/lxr/html/prototype/installNavBtn.shtml,v retrieving revision 1.1 retrieving revision 1.2 diff -u -d -r1.1 -r1.2 --- installNavBtn.shtml 11 Mar 2012 14:49:16 -0000 1.1 +++ installNavBtn.shtml 18 Jan 2014 09:54:17 -0000 1.2 @@ -1,5 +1,4 @@ <!--#set var="prevBtn" value="Previous" --> -<!-- $Id$ --> <!--#set var="indexBtn" value="Installation<br>index" --> <!--#set var="nextBtn" value="Next" --> -<!--#include virtual="/backstore/NavBtnTable.shtml" --> \ No newline at end of file +<!--#include virtual="/backstore5/NavBtnTable.shtml" --> \ No newline at end of file Index: logos.shtml =================================================================== RCS file: /cvsroot/lxr/html/prototype/logos.shtml,v retrieving revision 1.2 retrieving revision 1.3 diff -u -d -r1.2 -r1.3 --- logos.shtml 23 Sep 2012 16:48:10 -0000 1.2 +++ logos.shtml 18 Jan 2014 09:54:17 -0000 1.3 @@ -1,69 +1,63 @@ -<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01//EN"> -<!-- $Id$ --> -<html> <!--#set var="pageLang" value="en" --> -<head> - <meta http-equiv="content-type" content="text/html; charset=UTF-8"> - <meta http-equiv="Content-Language" content="<!--#echo var="pageLang" -->"> - <title>LXR Logos</title> - <link rel="stylesheet" type="text/css" href="/backstore/LXRweb.css"> - <link rel="icon" type="image/x-icon" href="/backstore/LXRlogo2.ico"> -</head> - -<body> - <!--#set var="pageHeaderTitle" value="LXR Logos" --> - <!--#set var="homePageHeader" value="0" --> - <!--#include virtual="/backstore/header.shtml" --> +<!--#set var="pageMetaTitle" value="LXR Logos" --> +<!--#set var="pageHeaderTitle" value="LXR Logos" --> +<!--#set var="homePageHeader" value="0" --> +<!--#include virtual="/backstore5/header.shtml" --> +<!-- $Id$ --> +<section> <p class="normal"> - LXR is quite mature now and deserves a decent logo - (and maybe also a decent name <em>in lieu</em> its acronym). +<em>LXR</em> is quite mature now and deserves a decent logo +(and maybe also a decent name <em>in lieu</em> its acronym). </p> <p class="normal"> - There has not been many attempts to create art for LXR. - This page shows them. +There have not been many attempts to create art for LXR. +This page shows them. </p> - <table> - <tr> - <td> - <table> - <tr> - <td> - <img src="/backstore/logo_mbox.gif" - alt="First tentative logo by mbox" - > - </td> - <td> - <p class="normal"> - This one is due to <strong>mbox</strong>. - He designed it in 2009 when launching discussion about the logo. - </p> - </td> - </tr> - </table> - </td> - <td> - <table> - <tr> - <td> - <img src="/backstore/LXRlogo2.png" - alt="2011 logo by ajlittoz" - > - </td> - <td> - <p class="normal"> - This is a quick and dirty attempt - when <strong>ajlittoz</strong> needed a logo for the 2011 LXR web site. - Only half an hour work! - </p> - </td> - </tr> - </table> - </td> - </tr> - </table> + <section class="gallery"> + <style scoped type="text/css"> + section.gallery, .subgallery +{ display: table table-row +} + .gallery > .subgallery +{ display: table-cell +; padding: 1cm 1.5cm 1cm 0cm +} + .subgallery > div +{ display: table-cell +; vertical-align: bottom +; padding: 6pt +} + </style> + <section class="subgallery"> + <div> + <img src="/backstore/logo_mbox.gif" + alt="First tentative logo by mbox" + > + </div> + <div> + <p class="normal"> +This one is due to <strong>mbox</strong>. +He designed it in 2009 when launching discussion about the logo. + </p> + </div> + </section> + <section class="subgallery"> + <div> + <img src="/backstore/LXRlogo2.png" + alt="2011 logo by ajlittoz" + > + </div> + <div> + <p class="normal"> +This is a quick and dirty attempt +when <strong>ajlittoz</strong> needed a logo for the 2011 LXR web site. +Only half an hour work! + </p> + </div> + </section> + </section> <p class="normal"> -As Malcolm pointed out <em>"I'm no graphic artist"</em>, -neither am I (ajlittoz). +Neither Malcolm nor I (ajlittoz) are graphic artist. Consequently, you are welcome to try and design a neat logo. Subscribe to the <em>lxr-general</em> mailing list @@ -79,14 +73,14 @@ <p class="normal"> No answer since it was launched on April 1, 2009! I know, it was April Fool's day. -But LXR really needs a logo. +But <em>LXR</em> really needs a logo. </p> <p class="normal"> -And why not also a new name? +And also what about a new name? <br> We could elaborate on the three historical letters. Here is a proposal <em class="defn">eLiXiR</em>. Comment on the mailing-list. </p> - -<!--#include virtual="/backstore/footer.shtml" --> +</section> +<!--#include virtual="/backstore5/footer.shtml" --> Index: newfeatures.shtml =================================================================== RCS file: /cvsroot/lxr/html/prototype/newfeatures.shtml,v retrieving revision 1.15 retrieving revision 1.16 diff -u -d -r1.15 -r1.16 --- newfeatures.shtml 7 Nov 2013 16:17:53 -0000 1.15 +++ newfeatures.shtml 18 Jan 2014 09:54:17 -0000 1.16 @@ -1,207 +1,185 @@ -<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01//EN"> -<!-- $Id$ --> -<html> <!--#set var="pageLang" value="en" --> -<head> - <meta http-equiv="content-type" content="text/html; charset=UTF-8"> - <meta http-equiv="Content-Language" content="<!--#echo var="pageLang" -->"> - <title>LXR Next Features</title> - <link rel="stylesheet" type="text/css" href="/backstore/LXRweb.css"> - <link rel="icon" type="image/x-icon" href="/backstore/LXRlogo2.ico"> -</head> - -<body> - <!--#set var="pageHeaderTitle" value="Features for next LXR Releases" --> - <!--#set var="homePageHeader" value="0" --> - <!--#include virtual="/backstore/header.shtml" --> -<ul> - <li><strong>Release 2.0</strong> - <ul> - <li class="classics"><del><em>genxref</em> goes parallel</del> - <p class="normal"> -Careful optimisation of current code dwindles the interest of multi-thread technology. -Multi-thread code is more complex and needs sophisticated database table locking strategy. -Experiments have shown this added complexity brings little gain on big projects -and slightly longer indexing times on small projects. - </p> - <p class="normal"> -However, this work uncovered very subtle bugs, or rather inaccuracies, -in the parser. - </p> - <p class="comment"> -As a net result, <em>genxref</em> performance is now x1.5 over release 1.2.0. -Indexing times are shortened by 33%. - </p> - </li> - <li class="classics">Multiple-trees context - <p class="normal"> +<!--#set var="pageMetaTitle" value="LXR Next Features" --> +<!--#set var="pageHeaderTitle" value="Features for next LXR Releases" --> +<!--#set var="homePageHeader" value="0" --> +<!--#include virtual="/backstore5/header.shtml" --> +<!-- $Id$ --> +<section> + <h1>Release 2.0</h1> + <ul> + <li class="classics">Multiple-trees context + <p class="normal"> Tree designation in URL moved into <code>PATH_INFO</code> instead of <code>SERVER_NAME</code> or <code>SCRIPT_NAME</code>. - </p> - <p class="comment"> + </p> + <p class="comment"> This is a new possibility, you do not need to modify your present trees. This designation variant offers simpler and more robust web server configuration. Adding or removing a tree is consequently only a matter of editing <em>lxr.conf</em> without reconfiguring the web server. - </p> - </li> - <li class="classics">Better HTTP initialisation - <p class="normal"> -Printing a message on screen under catastrophic events during -initialisation now possible, avoiding the disturbing "blank screen" situation. - </p> - </li> - <li class="classics">Better error handling - <p class="normal"> -<em>Browsing</em>: errors and warnings are also printed on screen, -reducing the necessity to read them from the server log files. - </p> - <p class="normal"> -<em>Configuration</em>: most user data is now checked against expected format -thus detecting early some trivial mistakes. - </p> - </li> - <li class="classics">Experimental support of + </p> + </li> + <li class="classics">Better HTTP initialisation + <p class="normal"> +Printing a message on screen under catastrophic events during initialisation +now possible, avoiding the disturbing "blank screen" situation. + </p> + </li> + <li class="classics">Better error management + <p class="normal"> +<em>Browsing</em>: errors and warnings are now sent both to log file and screen, +thus reducing the need to retrieve them from the web server log files. + </p> + <p class="normal"> +<em>Configuration</em>: most user entries are checked against the expected format, +etecting early trivial errors or mispellings. + </p> + </li> + <li class="classics">Experimental support of <strong>Nginx</strong>, <strong>Cherokee</strong> and <strong>thttpd</strong> web servers - </li> - <li class="classics"><em>User's Manual</em> updated - </li> - <li class="classics"><em>Developer's Manual</em> available - </li> - <li class="classics">Bug fixes - </li> - </ul> - </li> - <li><strong>Release 1.2</strong> - <ul> - <li class="classics">Generic parser include feature rearchitectured - <p class="normal"> + </li> + <li>Heavily commented source code</li> + <li class="classics"><cite>User's Manual</cite> updated + </li> + <li class="classics"><cite>Developer's Manual</cite> released + </li> + <li class="classics">Bug fixes + </li> + </ul> +</section> +<section> + <h1>Release 1.2</h1> + <ul> + <li class="classics">Generic parser <em>include</em> feature rearchitectured + <p class="normal"> To facilitate implementation of new language parsers, a common utility function has been inserting in the generic parser to build hyperlinks to every component of the included file path. All parsers now reference this function. - </p> - </li> - <li class="classics">New C parser - <p class="normal"> + </p> + </li> + <li class="classics">New C parser + <p class="normal"> C processing has been separated from the generic parser to improve reliability and readability of the latter. - </p> - </li> - <li class="classics">Change of generic include processing - <p class="normal"> + </p> + </li> + <li class="classics">Change of generic <em>include</em> processing + <p class="normal"> Since C is now an independent parser, default <em>include</em> syntax is <em>keyword</em>, as defined by the language description, followed by the <em>bare filename</em>, without any delimiters such as quotes or double quotes. - </p> - <p class="comment"> + </p> + <p class="comment"> This can be changed through an <code>'include'</code> specification in configuration file <em>generic.conf</em>. - </p> - </li> - <li class="classics">Changes in generic include syntax description - <p class="normal"> + </p> + </li> + <li class="classics">Changes in generic <em>include</em> syntax description + <p class="normal"> Keywords <code>'first'</code> and <code>'last'</code> have been renamed <code>'pre'</code> and <code>'post'</code> to emphasize their roles in <em>pre</em>- and <em>post</em>-processing the filename. - </p> - <p class="normal"> + </p> + <p class="normal"> New keyword <code>'separator'</code> defines path separator in the language dialect. It is replaced by the OS path separator (<code>/</code>) to access the included file. - </p> - <p class="comment"> + </p> + <p class="comment"> This allows faster processing than using a <code>'global'</code> substitution rule. - </p> - </li> - <li class="classics"><em>User's Manual</em> updated - </li> - <li class="classics">Bug fixes - <p class="normal"> -Removal of a bad handling situation in include processing + </p> + </li> + <li class="classics"><em>User's Manual</em> updated + </li> + <li class="classics">Bug fixes + <p class="normal"> +Removal of a bad handling situation in <em>include</em> processing causing an infinite loop (notably in <strong>Java</strong>) - </p> - </li> - </ul> - </li> - <li><strong>Release 1.1</strong> - <ul> - <li class="classics">Visual indication of inaccurate cross-references - <p class="normal"> + </p> + </li> + </ul> +</section> +<section> + <H1>Release 1.1</H1> + <ul> + <li class="classics">Visual indication of inaccurate cross-references + <p class="normal"> Per user request, directory and file view, identifier and free-text search have been modified to show that cross-references in the database refer to an earlier state of the file. This situation arises in development phase when files are modified and <em>genxref</em> has not yet been rerun. - </p> - </li> - <li class="classics">New <code>'ignorefiles'</code> parameter - <p class="normal"> + </p> + </li> + <li class="classics">New <code>'ignorefiles'</code> parameter + <p class="normal"> Upon user request, this parameter allows to selectively ignore files which name matches a pattern (internally used to ignore compiler-binary files, can be extended to ignore document files for instance). - </p> - </li> - <li class="classics">Interactive installation script - <p class="normal"> + </p> + </li> + <li class="classics">Interactive installation script + <p class="normal"> Configuration templates now use a consistent well defined scripting language. This allows to share blocks of configuration among templates, resulting in easier management of similar templates. - </p> - <p class="normal"> + </p> + <p class="normal"> To a certain extent, web server setup is now under control of the interactive configurator. However, only the most common cases are covered. Read the User's Manual for the necessary checks. - </p> - <p class="normal"> + </p> + <p class="normal"> Configurator can disable free-text search if neither <strong>Glimpse</strong> nor <strong>Swish-E</strong> is detected. This allows to have a try with LXR without the pain of installing a text search engine. Of course, the feature becomes unavailable until you install one and update <em>lxr.conf</em>. - </p> - </li> - <li class="classics">Experimental <strong>Mercurial</strong> support added - <p class="normal"> + </p> + </li> + <li class="classics">Experimental <strong>Mercurial</strong> support added + <p class="normal"> As per design choice, access is limited to local repositories. - </p> - <p class="comment"> + </p> + <p class="comment"> This is very experimental: the current developer is not familiar with Mercurial and directory listing runs horribly slow. Suggestions for improvement are welcome. - </li> - <li class="classics">New version of the <em>User's Manual</em> - </li> - <li class="classics">Bug fixes - <p class="normal"> + </li> + <li class="classics">New version of the <em>User's Manual</em> + </li> + <li class="classics">Bug fixes + <p class="normal"> Among these, fix for the case when the web site is totally devoted to LXR, <em>i.e.</em> when LXR is at the root of site. - </p> - </li> - </ul> - </li> - <li><strong>Release 1.0</strong> - <p class="comment"> + </p> + </li> + </ul> +</section> +<section> + <h1>Release 1.0</h1> + <p class="comment"> Considering the number of new features, release number jumps to 1.0, not 0.12. - </p> - <div class="boxed"> - <p class="normal caution">IMPORTANT!</p> - <p class="normal"> + </p> + <div class="boxed"> + <p class="normal caution">IMPORTANT!</p> + <p class="normal"> Finer grained language support make it impossible to maintain <strong>Perl 5.8 compatibility</strong>. Stated otherwise, @@ -209,196 +187,191 @@ frame of the present <em>SimpleParse.pm</em> lexical scanner. They can indeed be described by complex regular expressions but they break the capture mechanism of the scanner. - </p> - <p class="normal caution"> + </p> + <p class="normal caution"> Upgrade your Perl to version <strong>5.10</strong> at least. - </p> - </div> - <ul> - <li class="classics">Language support improved and extended - </li> - <li class="classics">Interactive installation script - <p class="normal"> + </p> + </div> + <ul> + <li class="classics">Language support improved and extended + </li> + <li class="classics">Interactive installation script + <p class="normal"> Reliably configures LXR and its database in a matter of minutes, suppresses the neeed to edit <em>lxr.conf</em> (but for advanced tuning of course). - </p> - </li> - <li class="classics"><strong>Git</strong> support fixed - </li> - <li class="classics"><strong>Subversion</strong> support added - <p class="normal"> + </p> + </li> + <li class="classics"><strong>Git</strong> support fixed + </li> + <li class="classics"><strong>Subversion</strong> support added + <p class="normal"> As per design choice, access is limited to local repositories (i.e. URL is of the form <code>file:///...</code>). - </p> - </li> - <li class="classics"><strong>SQLite</strong> database support added - <p class="normal"> + </p> + </li> + <li class="classics"><strong>SQLite</strong> database support added + <p class="normal"> Offers an alternative for small trees (not to be reasonably considered for medium and large trees because of poor performance). - </p> - </li> - <li class="classics">Database backend restructured - <p class="normal"> + </p> + </li> + <li class="classics">Database backend restructured + <p class="normal"> Results in a global performance boost despite the number of new features. - </p> - </li> - <li class="classics"><em>genxref</em> incremental indexing fixed - <p class="normal"> + </p> + </li> + <li class="classics"><em>genxref</em> incremental indexing fixed + <p class="normal"> When indexing without <code>--reindexall</code> option, former definitions and references are now correctly erased from the database, leaving no false duplicates. - </p> - </li> - <li class="classics"><em>genxref</em> performance improvement - <p class="normal"> + </p> + </li> + <li class="classics"><em>genxref</em> performance improvement + <p class="normal"> In the common case where source tree is stored in plain ordinary files, suppress file copying and work directly on original files. - </p> - </li> - <li class="classics">New configuration file template and script - for kernel browsing - <p class="normal"> + </p> + </li> + <li class="classics">New configuration file template and script + for kernel browsing + <p class="normal"> Correctly configuring LXR for the Linux kernel has always been a nightmare. The new configuration template contains plethora of <code>'variables'</code> to resolve the virtual <code>#include</code>s present in the source. - </p> - </li> - <li class="classics">Guaranteed application order of <code>'maps'</code> rules - </li> - <li class="classics">Conditional <code>'variables'</code> - <p class="normal"> + </p> + </li> + <li class="classics">Guaranteed application order of <code>'maps'</code> rules + </li> + <li class="classics">Conditional <code>'variables'</code> + <p class="normal"> New <code>'when'</code> clause tells when context is meaningful for the variable. - </p> - </li> - <li class="classics"><em>search</em> - <p class="normal"> + </p> + </li> + <li class="classics"><em>search</em> + <p class="normal"> <em>Case insensitive</em> search now really case-insensitive. - </p> - </li> - <li class="classics"><em>diff</em> - <p class="normal"> + </p> + </li> + <li class="classics"><em>diff</em> + <p class="normal"> Can compare two files differing in any number of <code>'variables'</code> if it makes sense (only under <em>buttons-and-menus</em> interface). - </p> - </li> - <li class="classics">Many bug fixes - </li> - </ul> - </li> - <li><strong>Release 0.11</strong> - <ul> - <li class="classics">New organisation of LXR root directory - <p class="normal"> + </p> + </li> + <li class="classics">Many bug fixes + </li> + </ul> +</section> +<section> + <h1>Release 0.11</h1> + <ul> + <li class="classics">New organisation of LXR root directory + <p class="normal"> More subdirectories so that only the main scripts remain at the root. - </p> - </li> - <li class="classics">Scripts to facilitate configuration - <p class="normal"> + </p> + </li> + <li class="classics">Scripts to facilitate configuration + <p class="normal"> First step towards automated installation. - </p> - </li> - <li class="classics">Better compatibility with <strong>Apache</strong> - <p class="normal">Can work with <em>Prefork</em> and <em>Worker</em> MPM</p> - </li> - <li class="classics">Experimental support of <strong>lighttpd</strong> web server - </li> - <li class="classics">Multiple trees configuration - <p class="normal">Integrated tree switching.</p> - </li> - <li class="classics">Possibility to have several stylesheets - <p class="normal"> + </p> + </li> + <li class="classics">Better compatibility with <strong>Apache</strong> + <p class="normal">Can work with <em>Prefork</em> and <em>Worker</em> MPM</p> + </li> + <li class="classics">Experimental support of <strong>lighttpd</strong> web server + </li> + <li class="classics">Multiple trees configuration + <p class="normal">Integrated tree switching.</p> + </li> + <li class="classics">Possibility to have several stylesheets + <p class="normal"> Selection of actual style done by user in compatible browsers. - </p> - </li> - <li class="classics"><strong>CVS</strong> support improved - <p class="normal"> + </p> + </li> + <li class="classics"><strong>CVS</strong> support improved + <p class="normal"> Side branches now accessed and indexed - </p> - </li> - <li class="classics">Bug fixes - </li> - </ul> - </li> - <li><strong>Release 0.10</strong> - <ul> - <li class="classics">Buttons-and-menus interface</li> - <li class="classics"><code>'variables'</code> can have any name - <p class="normal">Internal arguments used in the URL + </p> + </li> + <li class="classics">Bug fixes + </li> + </ul> +</section> +<section> + <h1>Release 0.10</h1> + <ul> + <li class="classics">Buttons-and-menus interface</li> + <li class="classics"><code>'variables'</code> can have any name + <p class="normal">Internal arguments used in the URL are now prefixed with <code>_</code> (underscore) so that they will never conflict with a configuration <code>'variables'</code> - </p> - <p class="comment">Note to + </p> + <p class="comment">Note to <span class="caution">CodeStriker</span> users: This breaks current integration with LXR. - </p> - </li> - <li class="classics"><em>diff markup</em> - <p class="normal">Background colours to highlight differences, + </p> + </li> + <li class="classics"><em>diff markup</em> + <p class="normal">Background colours to highlight differences, set with CSS - </p> - <p class="normal">Ability to change width of left column + </p> + <p class="normal">Ability to change width of left column through a configuration parameter and an URL arg - </p> - </li> - <li class="classics"><em>identifier search</em> - <p class="normal">Ability to limit search to declarations only, + </p> + </li> + <li class="classics"><em>identifier search</em> + <p class="normal">Ability to limit search to declarations only, default set by a configuration parameter - </p> - <p class="normal">Results presented in a table to avoid + </p> + <p class="normal">Results presented in a table to avoid bad looking ragged presentation - </p> - </li> - <li class="classics"><em>free-text search</em> - <p class="normal">Results presented in a table to avoid + </p> + </li> + <li class="classics"><em>free-text search</em> + <p class="normal">Results presented in a table to avoid bad looking ragged presentation - </p> - <p class="normal">With <strong>Glimpse</strong>, + </p> + <p class="normal">With <strong>Glimpse</strong>, searched string is highlighted in the hit text fragment - </p> - </li> - <li class="classics">Language... [truncated message content] |
