ELOG/elog
0
1
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

V2.0

Browse Source 
SVN revision: 91
This commit is contained in:
ritt
2002-06-10 10:03:49 +00:00
parent f2ebe0072f
commit 7c19eb4cbc
6 changed files with 167 additions and 71 deletions
Download Patch File Download Diff File Expand all files Collapse all files
doc/faq.html
+25 -3
View File
@@ -18,7 +18,7 @@
&nbsp;[<a class=nav href="userguide.html">User's Guide</a>]&nbsp;
&nbsp;[<a class=nav href="adminguide.html">Administrator's Guide</a>]&nbsp;
&nbsp;[FAQ]&nbsp;
&nbsp;[<a class=nav href="http://midas.psi.ch:8000">DEMO</a>]&nbsp;
&nbsp;[<a class=nav href="http://midas.psi.ch/elogdemo/">DEMO</a>]&nbsp;
&nbsp;[<a class=nav href="download.html">Download</a>]&nbsp;
</div>
<p>
@@ -27,6 +27,28 @@
<UL>
<LI><b>How does one configure elog to display a listing of all messages by default instead the last message</b>
<p>
This can be done with the <b><code>Start page</code></b> option. The entry:<p>
<code>
Start page = last10
</code><p>
shows the last 10 entries as the default. To show all messages, one can use:
<code><p>
Start page = ?cmd=Search&mode=summary&all=1<p>
</code><p>
This shows all messages from all logbooks (<i>all=1</i>). It is a good idea to have logbook tabs one here:<p>
<code><p>
Logbook tabs = 1
</code><p>
and to have additional menu command in the search page like:<p>
<code><p>
Find menu commands = New, Find, Last x, Last day, Last 10, Config, Help
</code><p>
To have the described behaviour for all logbooks, the above statements can be placed in the <b><code>[global]</code></b> section.
<p>
<LI><b>Are there any plans to implement a MySQL back end?</b>
<p>
No. The idea behind <b>ELOG</b> is that it is a <I>simple to use, simple to install</I> application. Many people use <b>ELOG</b> under Windows, and they even don't know what MySQL means. Other people like the flat file database format, because it's simple, easily accessible from other programs, and it's easy to backup certain days or months of the database (since the filenames contain the date). Since <b>ELOG</b> should be independent of any other package, some "switchable" backend between native <b>ELOG</b> format and MySQL would be needed, which is lots of work and not planned right now.
@@ -135,10 +157,10 @@ a feature you find useful on the list, there is a good chance that it will appea
<tr><td>Add email address field to user file, so that user name can be
specified for "Email &lt;attribute&gt; &lt;value&gt; =" option
which gets automatically substituted by email address<td>1</tr>
<tr><td>Change internal database format from offset oriented to
index oriented (lots of work, need also conversion program)<td>2</tr>
<tr><td>Implement new listing mode in between "summary only" and "full listing"
where a few text lines are displayed below the attribute fields<td>1</tr>
<tr><td>Define lists for logbooks used in the "copy to" and "move to" commands<td>1</tr>
<tr><td>Let user self-register new account<td>1</tr>
</table></center><p>