<?xml version="1.0" ?>
<!DOCTYPE book PUBLIC "-//KDE//DTD DocBook XML V4.2-Based Variant V1.1//EN" "dtd/kdex.dtd" [
  <!-- Define an entity for your application if it is not part of KDE
       CVS -->
  <!ENTITY knetattach "<application>KNetAttach</application>">
  <!ENTITY kappname "&knetattach;">
  <!ENTITY package "kdebase"><!-- I think this came from kdebase... -->
  <!ENTITY % addindex "IGNORE">
  <!ENTITY % English "INCLUDE"> 

  <!-- Do not define any other entities; instead, use the entities
       from entities/general.entities and $LANG/user.entities. -->
]>

<book lang="&language;">

<!-- This header contains all of the meta-information for the document such
as Authors, publish date, the abstract, and Keywords -->

<bookinfo>
<title>The &knetattach; Handbook</title>

<authorgroup>
<author>
&Orville.Bennett; &Orville.Bennett.mail;
</author>
</authorgroup>

<!-- TRANS:ROLES_OF_TRANSLATORS -->

<copyright>
<year>2005</year>
<holder>&Orville.Bennett;</holder>
</copyright>
<legalnotice>&FDLNotice;</legalnotice>

<date>2005-02-09</date>
<releaseinfo>1.01.00</releaseinfo>

<abstract>
<para>
&knetattach; is an application which makes it easier to integrate your 
network resources with your &kde; Desktop.
</para>
</abstract>

<!-- This is a set of Keywords for indexing by search engines.
Please at least include KDE, the KDE package it is in, the name
 of your application, and a few relevant keywords. -->

<keywordset>
<keyword>KDE</keyword>
<keyword>kdebase</keyword>
<keyword>knetattach</keyword>
<keyword>Network Folders</keyword>
<keyword>Network Folder Wizard</keyword>
<keyword>KDE Network Folder Wizard</keyword>
</keywordset>

</bookinfo>

<!-- The contents of the documentation begin here.  Label
each chapter so with the id attribute. This is necessary for two reasons: it
allows you to easily reference the chapter from other chapters of your
document, and if there is no ID, the name of the generated HTML files will vary
from time to time making it hard to manage for maintainers and for the CVS
system. Any chapter labelled (OPTIONAL) may be left out at the author's
discretion. Other chapters should not be left out in order to maintain a
consistent documentation style across all KDE apps. -->

<chapter id="introduction">
<title>Introduction</title>

<para>
The &knetattach; program, affectionately and hereafter known as the 
Network Folder Wizard, allows easy addition and integration of various 
network folders with your &kde; desktop. Please report any problems or 
feature requests for it to the &kde; mailing lists.
</para>
</chapter>

<chapter id="using-knetattach">
<title>Using &knetattach;</title>

<!-- This chapter should tell the user how to use your app. You should use as
many sections (Chapter, Sect1, Sect3, etc...) as is necessary to fully document
your application. -->

<para>
As you will see in the screenshot below, the Network Folder Wizard currently allows 
you to add four types of network folders: WebDav, FTP, 
<trademark class="registered">Microsoft</trademark> 
<trademark class="registered">Windows</trademark> network drives and SSH.

<screenshot>
<screeninfo>Here's a screenshot of &knetattach;</screeninfo>
<mediaobject>
<imageobject>
<imagedata fileref="screenshot.png" format="PNG"/>
</imageobject>
<textobject>
<phrase>Screenshot</phrase>
</textobject>
<caption>
<para>Network Folder Wizard main window</para>
</caption>
</mediaobject>
</screenshot>
</para>


<sect1 id="knetattach-features">
<title>Adding network folders</title>

<para>
Network folders show up in a special location of konqueror called a <emphasis>virtual folder</emphasis>.
This virtual folder is accessed by typing <userinput>remote:/</userinput> in the 
<interface>Location bar</interface>. You will then be able to see any folders which have been 
previously added or use the wizard to add new ones.
</para>
<para>
Speaking of wizards, the Network Folder Wizard aims at being very easy to use. Don't worry if 
you are having some problems though, that's what we're here for. :-)
After opening the wizard you must choose the type of network folder you would like to
access. When you move on to the next screen you will just need to 
fill in the requested information and the worst will be over.  The final step is entering your 
username and login password for the network share you've chosen to access.
</para>
<para>
Below is a list of the information needed by the wizard to create the network folders. If an option is not 
available for a particular folder it does not have to be entered. e.g. The <trademark class="registered">Microsoft</trademark>
<trademark class="registered">Windows</trademark> network drives folder does not require a <guilabel>Port</guilabel> entry.
</para>

<para>
<variablelist>
<varlistentry>
<term><guilabel>Name:</guilabel></term>
<listitem>
<para>
This is where you give a name to the network connection. It is limited only by 
your imagination (or alphabet).
</para>
</listitem>
</varlistentry>
<varlistentry>
<term>Server</term>
<listitem>
<para>
This is the address of the server you are attempting to add. It can be an 
IP address or domain name.
</para>
</listitem>
</varlistentry>
<varlistentry>
<term><guilabel>Port:</guilabel></term>
<listitem>
<para>
Here you enter the port number you wish to connect to. The defaults are usually 
sufficient.
<note>
<para>
Not available for <trademark class="registered">Microsoft</trademark> 
<trademark class="registered">Windows</trademark> folders.
</para>
</note>
</para>
</listitem>
</varlistentry>
<varlistentry>
<term><guilabel>Folder:</guilabel></term>
<listitem>
<para>
The path to the folder you wish to connect to should go here.
</para>
</listitem>
</varlistentry>
<varlistentry>
<term><guilabel>Create an icon for this remote folder</guilabel></term>
<listitem>
<para>
If this box is checked an icon will be created allowing access through the 
remote:/ virtual folder. If it is not checked, a connection will be possible
but it will not be accessible from remote:/.
<note>
<para>
The <guilabel>Recent connection:</guilabel> option allows you to re-connect to the 
last network mount point you connected to using the wizard whether an icon is created or not.
</para>
</note>
</para>
</listitem>
</varlistentry>
<varlistentry>
<term><guilabel>Use encryption</guilabel></term>
<listitem>
<para>
If checked the ability to make a secure connection will be enabled.
<note>
<para>Available only for WebDav folders.</para>
</note>
</para>
</listitem>
</varlistentry>
</variablelist>
</para>

</sect1>
</chapter>


<chapter id="credits">

<!-- Include credits for the programmers, documentation writers, and
contributors here. The license for your software should then be included below
the credits with a reference to the appropriate license file included in the KDE
distribution. -->

<title>Credits and License</title>

<para>
&knetattach;
</para>
<para>
Program copyright 1997 John Q. Hacker <email>jqh@kde.org</email>
</para>
<para>
Contributors:
<itemizedlist>
<listitem><para>Konqui the KDE Dragon <email>konqui@kde.org</email></para>
</listitem>
<listitem><para>Tux the Linux Penguin <email>tux@linux.org</email></para>
</listitem>
</itemizedlist>
</para>

<para>
Documentation Copyright &copy; 2005 &Orville.Bennett; &Orville.Bennett.mail;
</para>

<!-- TRANS:CREDIT_FOR_TRANSLATORS -->

&underFDL;               <!-- FDL: do not remove -->

<!-- Determine which license your application is licensed under,
     and delete all the remaining licenses below:

     (NOTE:  All documentation are licensed under the FDL,
     regardless of what license the application uses) -->

&underGPL;        	 <!-- GPL License -->
&underBSDLicense;        <!-- BSD License -->
&underArtisticLicense;   <!-- BSD Artistic License -->
&underX11License;        <!-- X11 License  -->

</chapter>

&documentation.index;
</book>

<!--
Local Variables:
mode: xml
sgml-minimize-attributes:nil
sgml-general-insert-case:lower
sgml-indent-step:0
sgml-indent-data:nil
End:

vim:tabstop=2:shiftwidth=2:expandtab
kate: space-indent on; indent-width 2; tab-width 2; indent-mode none;
-->
