Git commit 801866ef93ab568fb9886dc1c0a248de0c70a389 by Nicolas Fella. Committed on 18/01/2025 at 20:06. Pushed by nicolasfella into branch 'master'.
Drop documentation for no longer exiting KCMs M +0 -2 doc/kcontrol6/CMakeLists.txt D +0 -2 doc/kcontrol6/cookies/CMakeLists.txt D +0 -208 doc/kcontrol6/cookies/index.docbook D +0 -2 doc/kcontrol6/smb/CMakeLists.txt D +0 -93 doc/kcontrol6/smb/index.docbook https://invent.kde.org/network/kio-extras/-/commit/801866ef93ab568fb9886dc1c0a248de0c70a389 diff --git a/doc/kcontrol6/CMakeLists.txt b/doc/kcontrol6/CMakeLists.txt index 6c2f21b07..3e9df70e2 100644 --- a/doc/kcontrol6/CMakeLists.txt +++ b/doc/kcontrol6/CMakeLists.txt @@ -1,6 +1,4 @@ -add_subdirectory(cookies) add_subdirectory(netpref) add_subdirectory(proxy) -add_subdirectory(smb) add_subdirectory(trash) add_subdirectory(webshortcuts) diff --git a/doc/kcontrol6/cookies/CMakeLists.txt b/doc/kcontrol6/cookies/CMakeLists.txt deleted file mode 100644 index dd5bb6aef..000000000 --- a/doc/kcontrol6/cookies/CMakeLists.txt +++ /dev/null @@ -1,2 +0,0 @@ -########### install files ############### -kdoctools_create_handbook(index.docbook INSTALL_DESTINATION ${KDE_INSTALL_DOCBUNDLEDIR}/en SUBDIR kcontrol6/cookies) diff --git a/doc/kcontrol6/cookies/index.docbook b/doc/kcontrol6/cookies/index.docbook deleted file mode 100644 index 66a0a23c4..000000000 --- a/doc/kcontrol6/cookies/index.docbook +++ /dev/null @@ -1,208 +0,0 @@ -<?xml version="1.0" ?> -<!DOCTYPE article PUBLIC "-//KDE//DTD DocBook XML V4.5-Based Variant V1.1//EN" -"dtd/kdedbx45.dtd" [ -<!ENTITY % addindex "IGNORE"> -<!ENTITY % English "INCLUDE" > <!-- change language only here --> -]> - -<article id="cookies" lang="&language;"> -<articleinfo> -<title>Cookies</title> -<authorgroup> -<author>&Krishna.Tateneni; &Krishna.Tateneni.mail;</author> -<author>&Jost.Schenck; &Jost.Schenck.mail;</author> -<!-- TRANS:ROLES_OF_TRANSLATORS --> -</authorgroup> - -<date>2016-11-10</date> -<releaseinfo>Frameworks 5.29</releaseinfo> - -<keywordset> -<keyword>KDE</keyword> -<keyword>Systemsettings</keyword> -<keyword>cookie</keyword> -</keywordset> - -</articleinfo> - -<sect1 id="cookie"> -<title>Cookies</title> - -<para>Cookies are a mechanism used by web sites to store and retrieve -information using your browser. For example, a web site may allow you -to customize the content and layout of the pages you see, so that your -choices are persistent across different visits to that web site.</para> - -<para>The web site is able to remember your preferences by storing a -cookie on your computer. Then, on future visits, the web site retrieves -the information stored in the cookie to format the content of the site -according to your previously specified preferences.</para> - -<para>Thus, cookies play a very useful role in web browsing. -Unfortunately, web sites often store and retrieve information in cookies -without your explicit knowledge or consent. Some of this information may -be quite useful to the web site owners, for example, by allowing them to -collect summary statistics on the number of visits different areas of -the web sites get, or to customize banner advertising.</para> - -<para>The cookies page allows you to set policies -for the use of cookies when you are browsing the web with the -&konqueror; web browser.</para> - -<warning><para>Note that the policies that you set using this control -module will <emphasis>not</emphasis> apply to other web browsers such -as &firefox;.</para></warning> - -<sect2 id="cookie-policy"> - -<title>Policy</title> - -<para>Using the <guilabel>Policy</guilabel> tab, you can configure the -&kde; applications that will handle cookies. You can do this by specifying a -general cookie policy as well as special cookie policies for certain -domains or hosts.</para> - -<para>The top of the policy tab has a check box labeled <guilabel>Enable -cookies</guilabel>. If you leave this unchecked, cookies will be -completely disabled. However, this may make browsing rather -inconvenient, especially as some web sites require the use of browsers -with cookies enabled.</para> - -<para>You will probably want to enable cookies and then set -specific policies on how you want them to be handled.</para> - -<para>The first group of options create settings that apply to all cookies.</para> - -<variablelist> -<varlistentry> -<term><guilabel>Only accept cookies from originating server</guilabel></term> -<listitem> -<para>Some pages try to set cookies from servers other than the one -you are seeing the &HTML; page from. For example, -they show you advertisements, and the advertisements are from another -computer, often one that belongs to a large advertising group. These -advertisements may try to set a cookie which would allow them to -track the pages you view across multiple web sites.</para> -<para>Enabling this option will mean only cookies that come from the -same web server as you are explicitly connecting to will be -accepted.</para> -</listitem> -</varlistentry> -<varlistentry> -<term><guilabel>Automatically accept session cookies</guilabel></term> -<listitem> - -<para>An increasingly common use for cookies is not to track your -movements across many visits to a web site, but to just follow what you -do during one single visit. Session cookies are saved as long as you -are looking at the site, and deleted when you leave it.</para> - -<para>Web sites can use this information for various things, most -commonly it is a convenience so that you do not have to keep logging in -to view pages. For example, on a webmail site, without some kind of -session <acronym>ID</acronym>, you would have to give your password -again for each email you want to read. There are other ways to -achieve this, but cookies are simple and very common.</para> - -<para>Enabling this option means that session cookies are always -accepted, even if you don't accept any other kind, and even if you -choose to reject cookies from a particular site, session cookies from -that site will be accepted.</para> -</listitem> -</varlistentry> -</variablelist> - -<para>The section for <guilabel>Default Policy</guilabel> sets some -further options that are mutually exclusive — you can choose only one -of these options as the default, but you are free to set a different -option for any specific web server.</para> -<note><para>Site specific policies always take precedence over the default -policy.</para></note> - -<variablelist> -<varlistentry> -<term><guilabel>Accept all cookies</guilabel></term> -<listitem> -<para>If this option is selected, all cookies will be accepted without -asking for confirmation.</para> -</listitem> -</varlistentry> -<varlistentry> -<term><guilabel>Accept until end of session</guilabel></term> -<listitem> -<para>Cookies will be accepted, but they will expire at the end -of the session.</para> -</listitem> -</varlistentry> -<varlistentry> -<term><guilabel>Ask for confirmation</guilabel></term> -<listitem> -<para>If this option is selected, you will be asked for confirmation -every time a cookie is stored or retrieved. You can selectively accept -or reject each cookie. The confirmation dialog will also allow you to -set a domain specific policy, if you do not want to confirm each -cookie for that domain.</para> -</listitem> -</varlistentry> -<varlistentry> -<term><guilabel>Reject all cookies</guilabel></term> -<listitem> -<para>If this option is selected, all cookies will be rejected without -asking for confirmation.</para> -</listitem> -</varlistentry> -</variablelist> - -<para>In addition to the default policy for handling of cookies, which you can -set by selecting one of the three options described above, you can also set -policies for specific host domains using the controls in the <guilabel>Site -Policy</guilabel> group.</para> - -<para>The Ask, Accept, Accept until end of session, or Reject policy can be applied to a specific -domain by clicking on the <guibutton>New...</guibutton> button, which -brings up a dialog. In this dialog, you can type the name of the -domain (with a leading dot), then select the policy you want to apply -to this domain. Note that entries may also get added while you are -browsing, if the default policy is to ask for confirmation, and you -choose a general policy for a specific host (for example, by selecting -<guilabel>Reject</guilabel> when asked to -confirm a cookie).</para> - -<para>You can also select a specific host domain from the list and click the -<guibutton>Change...</guibutton> button to choose a different policy for that -domain than the one shown in the list.</para> - -<para>To delete a domain specific policy, choose a domain from the list, and -then click the <guibutton>Delete</guibutton> button. The default policy will -apply to domains which have been deleted from the list.</para> - -</sect2> - -<sect2 id="cookie-management"> -<title>Management</title> - -<para>In the <guilabel>Management</guilabel> tab you can browse and selectively -delete cookies that have been set in the past.</para> - -<para>In the upper part of this dialog, you can see a list of domains displayed - as a tree. Click on the little <guiicon>></guiicon> next to a domain to see all -cookies that have been set for this particular target domain. If you select one -of these cookies, you will notice that its contents will show up in the frame -<guilabel>Details</guilabel> below.</para> - -<para>By clicking the <guibutton>Delete</guibutton> button you can now delete the selected -cookie. Click <guibutton>Delete All</guibutton> to delete all cookies stored.</para> - -<para>If a domain is selected, you can use <guibutton>Configure Policy...</guibutton> to set -a site policy.</para> - -<para>Choose <guibutton>Reload List</guibutton> to reload the list -from your hard disk. You might want to do this if you have had the -module open and are testing web sites, or have made many changes in the -module itself.</para> - -</sect2> - -</sect1> - -</article> diff --git a/doc/kcontrol6/smb/CMakeLists.txt b/doc/kcontrol6/smb/CMakeLists.txt deleted file mode 100644 index 557477f2f..000000000 --- a/doc/kcontrol6/smb/CMakeLists.txt +++ /dev/null @@ -1,2 +0,0 @@ -########### install files ############### -kdoctools_create_handbook(index.docbook INSTALL_DESTINATION ${KDE_INSTALL_DOCBUNDLEDIR}/en SUBDIR kcontrol6/smb) diff --git a/doc/kcontrol6/smb/index.docbook b/doc/kcontrol6/smb/index.docbook deleted file mode 100644 index d4b126b1f..000000000 --- a/doc/kcontrol6/smb/index.docbook +++ /dev/null @@ -1,93 +0,0 @@ -<?xml version="1.0" ?> -<!DOCTYPE article PUBLIC "-//KDE//DTD DocBook XML V4.5-Based Variant V1.1//EN" -"dtd/kdedbx45.dtd" [ -<!ENTITY % addindex "IGNORE"> -<!ENTITY % English "INCLUDE" > <!-- change language only here --> -]> - -<article id="smb" lang="&language;"> -<articleinfo> -<title>&Windows; Shares</title> -<authorgroup> -<author>&Mike.McBride; &Mike.McBride.mail;</author> -<author>&Jost.Schenck; &Jost.Schenck.mail;</author> -<!-- TRANS:ROLES_OF_TRANSLATORS --> -</authorgroup> - -<date>2016-11-10</date> -<releaseinfo>Frameworks 5.29</releaseinfo> - -<keywordset> -<keyword>KDE</keyword> -<keyword>Systemsettings</keyword> -<keyword>Windows shares</keyword> -</keywordset> -</articleinfo> -<sect1 id="windows-shares"> -<title>&Windows; Shares</title> - -<sect2 id="windows-shares-intro"> -<title>Introduction</title> - -<para>In many small local area networks, the &SMB; -protocol is used to offer network services. Names like -<quote>&Windows; Network</quote> or <quote>&Windows; for Workgroups -Network</quote> or <quote>LanManager</quote> are often used as -well. Using &SMB; you can access so-called -<quote>shares</quote> (&ie; folders made available by the server) -as well as printers.</para> - -<para>&kde; comes with built-in support for the &SMB; -protocol. As &kde; is network-transparent that means you can access -&SMB; shares from everywhere you can access your -local files, for example in the &konqueror; file manager and in the -file dialog. To make use of this you should provide &kde; with some -information on your &SMB; network. But don't worry, -this is normally pretty simple as, for example, all the &Windows; -clients in your network need and have the same information.</para> - -<!-- Don't know if the following info should go in the base -documentation --> - -<!-- this smb KIO worker doesn't support showing a list -of hosts (like e.g. smb:/), for this you need the lan or rlan KIO worker, -very cool thing (TM) btw. If you want to write some documentation for -this one too, have a look at kdenetwork/lanbrowsing/lisa/README and -contact me if you have questions. --> - -<note><para>For the &SMB; protocol to work, it is -required to have &Samba; correctly installed.</para></note> - -<!-- TODO: link to some place which explains USING SMB, i.e. konqueror -or file dialog manual --> - -</sect2> - -<sect2 id="windows-shares-use"> -<title>Use</title> - -<para>Although there are a lot of insecure &SMB; -networks out there which allow access to anyone, in principle you have -to authenticate yourself to access the services of an -&SMB; server. By default, &kde; will use the data -entered in the <guilabel>Default user name:</guilabel> and -<guilabel>Default password:</guilabel> fields to authenticate itself on -&SMB; hosts. If you leave the field <guilabel>Default -user name:</guilabel> empty, &kde; will try to access -&SMB; hosts without a username. If you leave the -default password empty, it will try without a password. If &kde; is -unsuccessful accessing the host using these settings, you will be -asked for a username and a password.</para> - -<important><para>While it makes things more comfortable if &kde; -stores your &SMB; password, this may be a security -problem. If you are using &SMB; in a security -conscious environment, you should not store your password here but -rather enter it anew every time you need to access an -&SMB; host.</para></important> - -</sect2> - -</sect1> - -</article>
