'Re: advice needed: where to put doc files for ioslaves ?'

[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-core-devel
Subject:    Re: advice needed: where to put doc files for ioslaves ?
From:       aleXXX <alexander.neundorf () rz ! tu-ilmenau ! de>
Date:       2001-04-17 19:28:37
[Download RAW message or body]

On Tuesday 17 April 2001 20:31, you wrote:
> On Tuesday 17 April 2001 20:55, aleXXX wrote:
> >
> > If I have a docbook file, doesn't it always produce a "book" ?
> > i.e. an index.html and a html file for every chapter ?
>
> chapter doesn't mean a _book_ directly


Well, I still don't know, does it always generate several files ?

It is only to display some information about an ioslave in the control 
center, which you can quickly have a look at, not more.
Example:

<html>
<body>Using the man ioslave you are able to read the man pages installed
on your system. It is easy to use:<br>
<code>man:/</code> see the sections of the manual, click to find the rest<br>
<code>man:fopen</code> see the man page of fopen<br>
<br>
If you don't find all your man pages, adjust the environment 
variables <code>MANPATH</code> and <code>MANSECT</code>.<br>
<br>
As with any other KDE ioslave it is possible to enter an URL like 
<code>man:socket</code> in any KDE 2 app, try it in kwrite, and you will see 
the man page in HTML format.<br>
<br>
Contact: <a href=mailto:kde-devel@kde.org>mailinglist kde-devel@kde.org</a>
</body>
</html>

Compared to QTextView khtml is slow (especially loading and linking to it). 
Actually plain text would be already enough, but for the comment field in the 
.protocol file it might be a bit to much.

Bye
Alex

[prev in list] [next in list] [prev in thread] [next in thread]
Configure | About | News | Add a list | Sponsored by KoreLogic