mirror of
https://bitbucket.org/smil3y/kde-workspace.git
synced 2025-02-24 02:42:50 +00:00
removed docs, man kioslave part and khelpcenter
This commit is contained in:
Ivailo Monev
parent
9886abc654
commit
fde6c98cb2
543 changed files with 0 additions and 56104 deletions
|
|
@ -237,9 +237,6 @@ macro_optional_add_subdirectory(freespacenotifier)
|
|||
macro_optional_add_subdirectory(kscreensaver)
|
||||
macro_optional_add_subdirectory(kinfocenter)
|
||||
|
||||
# data
|
||||
macro_optional_add_subdirectory(doc)
|
||||
|
||||
if (Q_WS_X11)
|
||||
macro_optional_add_subdirectory(ktouchpadenabler)
|
||||
endif (Q_WS_X11)
|
||||
|
|
|
|||
|
|
@ -1,28 +0,0 @@
|
|||
add_subdirectory(kdm)
|
||||
add_subdirectory(klipper)
|
||||
add_subdirectory(kfontview)
|
||||
add_subdirectory(kmenuedit)
|
||||
add_subdirectory(ksysguard)
|
||||
add_subdirectory(plasma-desktop)
|
||||
add_subdirectory(kcontrol)
|
||||
add_subdirectory(systemsettings)
|
||||
add_subdirectory(kinfocenter)
|
||||
|
||||
if(POLKITQT_FOUND)
|
||||
add_subdirectory(PolicyKit-kde)
|
||||
endif(POLKITQT_FOUND)
|
||||
|
||||
if ( UNIX )
|
||||
add_subdirectory(kdesu)
|
||||
endif ( UNIX )
|
||||
|
||||
add_subdirectory(kcontrol)
|
||||
add_subdirectory(glossary)
|
||||
add_subdirectory(kdebugdialog)
|
||||
add_subdirectory(khelpcenter)
|
||||
add_subdirectory(kioslave)
|
||||
add_subdirectory(knetattach)
|
||||
add_subdirectory(onlinehelp)
|
||||
add_subdirectory(documentationnotfound)
|
||||
add_subdirectory(fundamentals)
|
||||
add_subdirectory(plasmapkg)
|
||||
|
|
@ -1 +0,0 @@
|
|||
kde4_create_handbook(index.docbook INSTALL_DESTINATION ${HTML_INSTALL_DIR}/en)
|
||||
Binary file not shown.
|
Before Width: | Height: | Size: 34 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 27 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 29 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 32 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 29 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 28 KiB |
|
|
@ -1,112 +0,0 @@
|
|||
<chapter id="authorization">
|
||||
<title>Authorization manager</title>
|
||||
|
||||
<sect1 id="authorization-manual">
|
||||
<title>Manual</title>
|
||||
|
||||
<para>
|
||||
The Authorization manager is the application that system administrators can
|
||||
use to easily change the default behavior of any actions. This page does not
|
||||
aim to explain how to create new actions or define new <quote>.policy</quote>
|
||||
files.</para>
|
||||
|
||||
<para>
|
||||
The Authorization screen is divided in two parts, at the left we have all the
|
||||
actions that PolicyKit knows, you are able to search the actions using the search
|
||||
bar at the top, and at the right we have the selected action.
|
||||
This screenshot shows the main Authorization screen:
|
||||
</para>
|
||||
|
||||
<para>
|
||||
<screenshot>
|
||||
<mediaobject>
|
||||
<imageobject><imagedata fileref="authorization_1.png" format="PNG"/></imageobject>
|
||||
<textobject><phrase>Main window with source device</phrase></textobject>
|
||||
</mediaobject>
|
||||
</screenshot>
|
||||
</para>
|
||||
|
||||
<para>
|
||||
When you select an action it's details will be shown at the right side,
|
||||
the action might have an icon, a description and the vendor name. Next
|
||||
in the view we have the <quote>Implicit Authorizations</quote> and
|
||||
<quote>Explicit Authorizations</quote>.
|
||||
</para>
|
||||
|
||||
<para>
|
||||
The <quote>Implicit Authorizations</quote> are authorizations automatically
|
||||
given to users based on certain criteria such as if they are on the local
|
||||
console. These authorizations are read from the <quote>.policy</quote> files
|
||||
that the given application defined, they are the defaults settings of the action.
|
||||
These are the valid values
|
||||
</para>
|
||||
|
||||
<itemizedlist>
|
||||
<listitem><para>no</para></listitem>
|
||||
<listitem><para>auth_self_one_shot</para></listitem>
|
||||
<listitem><para>auth_self</para></listitem>
|
||||
<listitem><para>auth_self_keep_session</para></listitem>
|
||||
<listitem><para>auth_self_keep_always</para></listitem>
|
||||
<listitem><para>auth_admin_one_shot</para></listitem>
|
||||
<listitem><para>auth_admin</para></listitem>
|
||||
<listitem><para>auth_admin_keep_session</para></listitem>
|
||||
<listitem><para>auth_admin_keep_always</para></listitem>
|
||||
<listitem><para>yes</para></listitem>
|
||||
</itemizedlist>
|
||||
|
||||
<para>
|
||||
You can change these defaults values simply by changing it on the combo box,
|
||||
the not bold value is the default one so if you want to change one value back
|
||||
you can select it, to make you selection take effect you have to click on the
|
||||
<quote>Modify</quote> button. The <quote>Revert to defaults</quote> can be used
|
||||
to change all <quote>Implicit Authorizations</quote> to it's defaults values.
|
||||
Note that both <quote>Modify</quote> and <quote>Revert to defaults</quote>
|
||||
requires you to issue the PolicyKit <quote>org.freedesktop.policykit.modify-defaults</quote>
|
||||
action which might ask a password.
|
||||
</para>
|
||||
|
||||
<para>
|
||||
The <quote>Explicit Authorizations</quote> are authorizations that are either
|
||||
obtained through authentication process or specifically given to the action
|
||||
in question. The default behavior is to only show the current user explicit
|
||||
authorizations; if you want to see others users explicit authorizations
|
||||
click on the <quote>Show authorizations from all users</quote>, note that this
|
||||
requires you to issue the PolicyKit <quote>org.freedesktop.policykit.read</quote>
|
||||
action which might ask a password.
|
||||
Blocked authorizations are marked with a <quote>STOP</quote> sign.
|
||||
</para>
|
||||
|
||||
<para>
|
||||
The <quote>Revoke</quote> button is used to revoke an explicit authorization.
|
||||
Note that this requires you to issue the PolicyKit
|
||||
<quote>org.freedesktop.policykit.revoke</quote> action which might ask a password.
|
||||
</para>
|
||||
|
||||
<para>
|
||||
If you want to specifically grant or block a given user of performing a given action
|
||||
you can click on the <quote>Grant</quote> or <quote>Block</quote>.
|
||||
The following screenshot you see the Grant/Block dialog:
|
||||
</para>
|
||||
|
||||
<para>
|
||||
<screenshot>
|
||||
<mediaobject>
|
||||
<imageobject><imagedata fileref="authorization_2.png" format="PNG"/></imageobject>
|
||||
<textobject><phrase>Grant/Block explicit authorizations dialog</phrase></textobject>
|
||||
</mediaobject>
|
||||
</screenshot>
|
||||
</para>
|
||||
|
||||
<para>
|
||||
To grant/block explicit authorizations you have to select the user that will
|
||||
receive the authorization. You can also select the <quote>Constraints</quote>
|
||||
to limit the authorization such that it only applies under certain circumstances.
|
||||
<warning><para>Be aware that explicit blocking and authorization might self lock you
|
||||
of performing the given action so be sure of what you are doing</para></warning>
|
||||
Note that this requires you to issue the PolicyKit
|
||||
<quote>org.freedesktop.policykit.grant</quote> action which might ask a password.
|
||||
</para>
|
||||
|
||||
</sect1>
|
||||
|
||||
</chapter>
|
||||
Binary file not shown.
|
Before Width: | Height: | Size: 99 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 48 KiB |
|
|
@ -1,120 +0,0 @@
|
|||
<chapter id="authorizationagent">
|
||||
<title>Authorization Agent</title>
|
||||
|
||||
<sect1 id="authorizationagent-overview">
|
||||
<title>Manual</title>
|
||||
|
||||
<para>
|
||||
The Authorization Agent is the application that is called whenever an user
|
||||
wants to obtain a given authorization. It's a &DBus; activated daemon which
|
||||
uses <quote>libpolkit-grant</quote> that in turn uses PAM for authentication
|
||||
services (however, other authentication back-ends can be plugged in as required).
|
||||
</para>
|
||||
</sect1>
|
||||
|
||||
<sect1 id="authorizationagent-dialog">
|
||||
<title>Authorization Agent dialog</title>
|
||||
|
||||
<para>
|
||||
The appearance of the authentication dialog depends on the result from PolicyKit
|
||||
and also whether administrator authentication is defined as <quote>authenticate as
|
||||
the root user</quote> or <quote>authenticate as one of the users from UNIX group
|
||||
wheel</quote> or however the PolicyKit library is configured (see the
|
||||
PolicyKit.conf(5) manual page for details). Note that some of the screenshots below
|
||||
were made on a system set up to use the
|
||||
<ulink url="http://thinkfinger.sourceforge.net/">ThinkFinger</ulink>
|
||||
PAM module. The text shown in the authentication dialogs stems from the PolicyKit
|
||||
.policy XML files residing in /usr/share/PolicyKit/policy and is read by the
|
||||
authentication daemon when an applications asks to obtain an authorization.
|
||||
Thus, what the user sees is not under application control
|
||||
(e.g. it's not passed from the application) which rules out a class of attacks
|
||||
where applications are trying to fool the user into gaining a privilege.
|
||||
</para>
|
||||
|
||||
<para>The authentication dialog where the user is asked to authenticate as root
|
||||
using the password or swiping the finger.
|
||||
The details shows the application that's requesting the action, the action
|
||||
itself and the action vendor. If clicking in the action link it will open the
|
||||
authorization manager pointing to the given action, and the vendor might also
|
||||
provide a link for the given action that will be fired when clicking on the
|
||||
<quote>Vendor</quote> link:</para>
|
||||
<para>
|
||||
<screenshot>
|
||||
<mediaobject>
|
||||
<imageobject><imagedata fileref="authdialog_1.png" format="PNG"/></imageobject>
|
||||
<textobject><phrase>
|
||||
The authentication dialog asking for root, swipe finger and showing descriptions
|
||||
</phrase></textobject>
|
||||
</mediaobject>
|
||||
</screenshot>
|
||||
</para>
|
||||
|
||||
<para>Authentication dialog where the user is asked to authenticate as an administrative
|
||||
user and PolicyKit is configured to use the root password for this:</para>
|
||||
<para>
|
||||
<screenshot>
|
||||
<mediaobject>
|
||||
<imageobject><imagedata fileref="authdialog_2.png" format="PNG"/></imageobject>
|
||||
<textobject><phrase>
|
||||
The authentication dialog asking for root
|
||||
</phrase></textobject>
|
||||
</mediaobject>
|
||||
</screenshot>
|
||||
</para>
|
||||
|
||||
<para>Authentication dialog where the user is asked to authenticate as an administrative
|
||||
user and PolicyKit is configured to use a group for this:</para>
|
||||
<para>
|
||||
<screenshot>
|
||||
<mediaobject>
|
||||
<imageobject><imagedata fileref="authdialog_3.png" format="PNG"/></imageobject>
|
||||
<textobject><phrase>
|
||||
The authentication dialog asking for a user of the administrative group
|
||||
</phrase></textobject>
|
||||
</mediaobject>
|
||||
</screenshot>
|
||||
</para>
|
||||
|
||||
<para>Same authentication dialog, showing drop down box where the user can be selected:</para>
|
||||
<para>
|
||||
<screenshot>
|
||||
<mediaobject>
|
||||
<imageobject><imagedata fileref="authdialog_4.png" format="PNG"/></imageobject>
|
||||
<textobject><phrase>
|
||||
Same authentication dialog, showing drop down box where the user can be selected
|
||||
</phrase></textobject>
|
||||
</mediaobject>
|
||||
</screenshot>
|
||||
</para>
|
||||
|
||||
|
||||
<para>Authentication dialog showing an Action where the privilege can be retained indefinitely:</para>
|
||||
<para>
|
||||
<screenshot>
|
||||
<mediaobject>
|
||||
<imageobject><imagedata fileref="authdialog_5.png" format="PNG"/></imageobject>
|
||||
<textobject><phrase>
|
||||
Authentication dialog showing an Action where the privilege can be retained indefinitely
|
||||
</phrase></textobject>
|
||||
</mediaobject>
|
||||
</screenshot>
|
||||
</para>
|
||||
|
||||
|
||||
<para>Authentication dialog showing an Action where the privilege can be retained only
|
||||
for the remainder of the desktop session:</para>
|
||||
<para>
|
||||
<screenshot>
|
||||
<mediaobject>
|
||||
<imageobject><imagedata fileref="authdialog_6.png" format="PNG"/></imageobject>
|
||||
<textobject><phrase>
|
||||
Authentication dialog showing an Action where the privilege can be retained only
|
||||
for the remainder of the desktop session
|
||||
</phrase></textobject>
|
||||
</mediaobject>
|
||||
</screenshot>
|
||||
</para>
|
||||
|
||||
</sect1>
|
||||
|
||||
</chapter>
|
||||
|
|
@ -1,53 +0,0 @@
|
|||
<chapter id="howitworks">
|
||||
<title>How it works</title>
|
||||
|
||||
<sect1 id="howitworks-overview">
|
||||
<title>Overview</title>
|
||||
|
||||
<para>PolicyKit has a simple way of working, but it requires some
|
||||
design changes from the applications that want to use it to request
|
||||
passwords.</para>
|
||||
</sect1>
|
||||
|
||||
<sect1 id="howitworks-problem">
|
||||
<title>The problem</title>
|
||||
|
||||
<para>In GUI applications the common way to gain root privileges is to start
|
||||
it as root, but there are several security risks in doing this method and
|
||||
it does not allow a good actions mapping. There is no way to separate actions
|
||||
like package-install of system-upgrading.
|
||||
All the users who want to use it must have the root password. Another common
|
||||
approach is using sudo but once you start an application with sudo you will
|
||||
have all the rights the root user will have.
|
||||
If for example the GUI application has a dialog to select files that dialog
|
||||
is running as root which means that the user might be able to delete any file
|
||||
on his machine or even coping others user files.
|
||||
</para>
|
||||
</sect1>
|
||||
|
||||
<sect1 id="howitworks-solution">
|
||||
<title>The solution</title>
|
||||
|
||||
<para>With PolicyKit this problem is solved. The application in question
|
||||
just need to separate the privileged code into another application,
|
||||
often called helper (which will not have a GUI), then maps the desired
|
||||
actions into a <quote>.policy</quote> file. PolicyKit then loads this file
|
||||
and it can now authenticate applications to use those actions.
|
||||
The use of &DBus; activated applications is the best if not the only,
|
||||
way of putting an helper application to run with root privileges.</para>
|
||||
|
||||
<para>With this design the GUI application calls an action of the helper
|
||||
application through &DBus;, which will start the helper with root privileges,
|
||||
and informing it which action was requested and which application has requested
|
||||
it. The helper application now calls the PolicyKit agent to see if that application
|
||||
can do the given task, the helper should report if it could do the requested action.
|
||||
In case the helper saw that the application didn't have enough rights the GUI
|
||||
will then need to ask PolicyKit to obtain an authorization.</para>
|
||||
|
||||
<para>When PolicyKit receives the request to obtain an authorization it issues an
|
||||
available Agent, which might happen to be &policykit-kde; if available. After a successful
|
||||
authentication the GUI application needs to call the helper repeating the
|
||||
same operation again.</para>
|
||||
</sect1>
|
||||
|
||||
</chapter>
|
||||
|
|
@ -1,88 +0,0 @@
|
|||
<?xml version="1.0" ?>
|
||||
<!DOCTYPE book PUBLIC "-//KDE//DTD DocBook XML V4.2-Based Variant V1.1//EN" "dtd/kdex.dtd" [
|
||||
<!ENTITY policykit-kde "<application>PolicyKit-kde</application>">
|
||||
<!ENTITY policykit "<application>PolicyKit</application>">
|
||||
<!ENTITY kappname "&policykit-kde;">
|
||||
<!ENTITY policykit-kde-introduction SYSTEM "introduction.docbook">
|
||||
<!ENTITY policykit-kde-howitworks SYSTEM "howitworks.docbook">
|
||||
<!ENTITY policykit-kde-authorization SYSTEM "authorization.docbook">
|
||||
<!ENTITY policykit-kde-authorizationagent SYSTEM "authorizationagent.docbook">
|
||||
<!ENTITY % English "INCLUDE" > <!-- change language only here -->
|
||||
<!ENTITY % addindex "IGNORE">
|
||||
]>
|
||||
|
||||
<book id="PolicyKit-kde" lang="&language;">
|
||||
|
||||
<bookinfo>
|
||||
<title>The &policykit-kde; manual</title>
|
||||
|
||||
<authorgroup>
|
||||
<author>
|
||||
<firstname>Daniel</firstname>
|
||||
<surname>Nicoletti</surname>
|
||||
</author>
|
||||
<!-- TRANS:ROLES_OF_TRANSLATORS -->
|
||||
</authorgroup>
|
||||
|
||||
<copyright>
|
||||
<year>2008-2009</year>
|
||||
<holder>Daniel Nicoletti</holder>
|
||||
</copyright>
|
||||
|
||||
<legalnotice>&FDLNotice;</legalnotice>
|
||||
|
||||
<date>2009-01-25</date>
|
||||
<releaseinfo>0.9.0</releaseinfo>
|
||||
|
||||
<abstract>
|
||||
<para>&policykit-kde; is a &kde; front end to the PolicyKit
|
||||
system that is used to manages authentication.</para>
|
||||
<para>&policykit; is a toolkit designed to allow unprivileged processes
|
||||
to speak to privileged processes. It does that by centralizing information of
|
||||
actions and authorized applications.</para>
|
||||
</abstract>
|
||||
|
||||
<keywordset>
|
||||
<keyword>KDE</keyword>
|
||||
<keyword>System</keyword>
|
||||
<keyword>Password</keyword>
|
||||
<keyword>Admin</keyword>
|
||||
<keyword>Authentication</keyword>
|
||||
<keyword>polkit</keyword>
|
||||
<keyword>policykit</keyword>
|
||||
<keyword>policy</keyword>
|
||||
<keyword>policies</keyword>
|
||||
</keywordset>
|
||||
|
||||
</bookinfo>
|
||||
|
||||
&policykit-kde-introduction;
|
||||
&policykit-kde-howitworks;
|
||||
&policykit-kde-authorization;
|
||||
&policykit-kde-authorizationagent;
|
||||
|
||||
<chapter id="credits">
|
||||
<title>Credits and License</title>
|
||||
|
||||
<para>
|
||||
&policykit-kde;
|
||||
</para>
|
||||
<para>
|
||||
Program copyright 2008-2009 Daniel Nicoletti
|
||||
</para>
|
||||
<para>
|
||||
Documentation copyright 2008-2009 Daniel Nicoletti
|
||||
</para>
|
||||
|
||||
<!-- TRANS:CREDIT_FOR_TRANSLATORS -->
|
||||
&underFDL; <!-- FDL: do not remove -->
|
||||
|
||||
</chapter>
|
||||
|
||||
&documentation.index;
|
||||
|
||||
</book>
|
||||
|
||||
<!--
|
||||
vim:tabstop=2:shiftwidth=2:expandtab
|
||||
-->
|
||||
|
|
@ -1,28 +0,0 @@
|
|||
<chapter id="introduction">
|
||||
<title>Overview</title>
|
||||
|
||||
<para>&policykit-kde; is a implementation of PolicyKit tool to the look and feel
|
||||
of KDE.</para>
|
||||
|
||||
<para>PolicyKit allows easy and secure password management, it can be used by
|
||||
applications to ask their users for a password. Each application defines a set
|
||||
of actions that can be executed by their program.
|
||||
The application will call PolicyKit to see if the user can perform a given
|
||||
action, if not, the application can issue the auth dialog where the user
|
||||
can enter his/her password, root password, the password of a given group
|
||||
of users or even swipe the finger.</para>
|
||||
|
||||
<para>&policykit-kde; consists of two applications:
|
||||
The Authorization agent that receives requests for authentication, and shows
|
||||
a dialog asking for a password.
|
||||
The Authorization manager that is used to manage the authorizations, it is
|
||||
mainly used by system administrators that may want to change the default behavior
|
||||
of a program policies.</para>
|
||||
|
||||
<para>For Qt/KDE developers there is Qt library to allow easy integration with
|
||||
you application and PolicyKit.</para>
|
||||
|
||||
<para>For more information of how PolicyKit works, it's design and API visit
|
||||
<ulink url="http://hal.freedesktop.org/docs/PolicyKit/">PolicyKit Library Reference Manual</ulink></para>
|
||||
|
||||
</chapter>
|
||||
|
|
@ -1,25 +0,0 @@
|
|||
## Warn about everything, just like in kdelibs.
|
||||
WARN_IF_UNDOCUMENTED = YES
|
||||
## Be strict, we want all parameters
|
||||
## to be documented as well.
|
||||
WARN_NO_PARAMDOC = YES
|
||||
|
||||
## Sort methods to make 'same as above' easier.
|
||||
SORT_MEMBER_DOCS = YES
|
||||
|
||||
## Remove unsightly export macros
|
||||
PREDEFINED = Q_EXPORT="" \
|
||||
Q_GUI_EXPORT="" \
|
||||
KWIN_EXPORT="" \
|
||||
KFONTINST_EXPORT="" \
|
||||
PLASMA_EXPORT="" \
|
||||
LIBDOLPHINPRIVATE_EXPORT="" \
|
||||
KONQSIDEBAR_EXPORT="" \
|
||||
KONQSIDEBARPLUGIN_EXPORT="" \
|
||||
SOLIDCONTROL_EXPORT="" \
|
||||
SOLIDCONTROLIFACES_EXPORT="" \
|
||||
KNEPREGCORE_EXPORT= "" \
|
||||
KDEUI_EXPORT="" \
|
||||
KDE_EXPORT="" \
|
||||
Q_SLOTS="slots" \
|
||||
Q_SIGNALS="signals"
|
||||
|
|
@ -1,2 +0,0 @@
|
|||
########### install files ###############
|
||||
kde4_create_handbook(index.docbook INSTALL_DESTINATION ${HTML_INSTALL_DIR}/en SUBDIR khelpcenter/documentationnotfound)
|
||||
|
|
@ -1,66 +0,0 @@
|
|||
<?xml version="1.0" ?>
|
||||
<!DOCTYPE article PUBLIC "-//KDE//DTD DocBook XML V4.2-Based Variant V1.1//EN"
|
||||
"dtd/kdex.dtd" [
|
||||
<!ENTITY % addindex "IGNORE">
|
||||
<!ENTITY % English "INCLUDE">
|
||||
]>
|
||||
<article id="documentationnotfound" lang="&language;">
|
||||
<title>Documentation not Found</title>
|
||||
<articleinfo>
|
||||
<authorgroup>
|
||||
<author><firstname>Jack</firstname>
|
||||
<surname>Ostroff</surname>
|
||||
<affiliation>
|
||||
<address><email>ostroffjh@users.sourceforge.net</email></address>
|
||||
</affiliation>
|
||||
</author>
|
||||
<!-- TRANS:ROLES_OF_TRANSLATORS -->
|
||||
</authorgroup>
|
||||
|
||||
<date>2010-09-21</date>
|
||||
<releaseinfo>&kde; 4.5</releaseinfo>
|
||||
|
||||
</articleinfo>
|
||||
|
||||
<para>The requested documentation was not found on your computer.
|
||||
Normally, &kde; looks for application handbooks in a location that depends
|
||||
on how &kde; was installed on your computer. There are a number of
|
||||
possible reasons why it could not find the documentation you
|
||||
requested. The document might not exist, or it may not have been
|
||||
installed along with the application.</para>
|
||||
|
||||
<para>How to solve this issue:</para>
|
||||
|
||||
<para>Start by searching the <ulink url="http://docs.kde.org/">KDE
|
||||
Documentation site</ulink> for the requested documentation. If you find
|
||||
the documentation on that site, your distribution might ship a separate
|
||||
package for documentation (⪚ called kdepim-doc for all applications
|
||||
from the kdepim module, like &kmail;, &kontact;, &etc;). Please use the
|
||||
package manager of your distribution to find and install the missing
|
||||
documentation.</para>
|
||||
|
||||
<para>If you use a source based distribution, such as Gentoo, be sure that
|
||||
there are not any configuration settings (USE flags in Gentoo) that
|
||||
might have disabled the installation of the documentation.
|
||||
</para>
|
||||
|
||||
<para>If you have done that, but still get this page displayed instead of the
|
||||
application handbook, you probably found a bug in the &kde; help
|
||||
system. In this case, please report this on the <ulink
|
||||
url="http://bugs.kde.org/">KDE Bug Tracker</ulink>.
|
||||
</para>
|
||||
|
||||
<para>If you do not find any documentation on the <ulink
|
||||
url="http://docs.kde.org/">KDE Documentation site</ulink>, the
|
||||
application may not have offline documentation. Please report this on
|
||||
the <ulink url="http://bugs.kde.org/">KDE Bug Tracker</ulink>.
|
||||
</para>
|
||||
|
||||
<para>In case the application does not have offline documentation, you should
|
||||
use the online resources <ulink
|
||||
url="http://userbase.kde.org/">UserBase Documentation</ulink> and
|
||||
<ulink url="http://forum.kde.org/">KDE Community Forums</ulink> to get
|
||||
help.
|
||||
</para>
|
||||
|
||||
</article>
|
||||
|
|
@ -1 +0,0 @@
|
|||
kde4_create_handbook(index.docbook INSTALL_DESTINATION ${HTML_INSTALL_DIR}/en)
|
||||
Binary file not shown.
|
Before Width: | Height: | Size: 48 KiB |
|
|
@ -1,391 +0,0 @@
|
|||
<chapter id="config">
|
||||
<title>Customizing &kde; software</title>
|
||||
|
||||
<sect1 id="toolbars">
|
||||
<sect1info>
|
||||
<authorgroup>
|
||||
<author>&TC.Hollingsworth; &TC.Hollingsworth.mail;</author>
|
||||
<!-- TRANS:ROLES_OF_TRANSLATORS -->
|
||||
</authorgroup>
|
||||
</sect1info>
|
||||
<title>Customizing Toolbars</title>
|
||||
|
||||
<!--FIXME link from korganizer config-toolbars section-->
|
||||
<!--FIXME link from <sect2 id="configtoolbars"> in sheets/config.docbook> -->
|
||||
<!--FIXME link from <sect2 id="configuration-toolbars"> in extragear/multimedia-git/kplayer/doc/en_US/configuration.docbook -->
|
||||
<screenshot id="screenshot-toolbars-toolbar">
|
||||
<screeninfo>The &gwenview; Toolbar</screeninfo>
|
||||
<mediaobject>
|
||||
<imageobject><imagedata fileref="toolbars-toolbar.png" format="PNG"/></imageobject>
|
||||
<textobject><phrase>The &gwenview; toolbar.</phrase></textobject>
|
||||
<caption><para>The toolbar in
|
||||
<ulink url="http://kde.org/applications/graphics/gwenview/">&gwenview;</ulink>.
|
||||
</para></caption>
|
||||
</mediaobject>
|
||||
</screenshot>
|
||||
|
||||
<sect2 id="toolbars-items">
|
||||
<title>Modifying Toolbar Items</title>
|
||||
|
||||
<para>To customize an application's toolbars, go to
|
||||
<menuchoice><guimenu>Settings</guimenu><guimenuitem>Configure
|
||||
Toolbars...</guimenuitem></menuchoice> or right-click on a toolbar and select
|
||||
<guimenuitem>Configure Toolbars...</guimenuitem>.</para>
|
||||
|
||||
<para>On the left side of the toolbar configuration panel, the available items
|
||||
that you can put in your toolbar are shown. On the right, the ones that already
|
||||
appear on the toolbar are shown. At the top, you can select the toolbar
|
||||
you wish to modify or view.</para>
|
||||
|
||||
<para>Above each side of the panel there is a <guilabel>Filter</guilabel> text
|
||||
box you can use to easily find items in the list.</para>
|
||||
|
||||
<screenshot id="screenshot-toolbars-customize">
|
||||
<screeninfo>The Customize Toolbars Window</screeninfo>
|
||||
<mediaobject>
|
||||
<imageobject><imagedata fileref="toolbars-configure.png" format="PNG"/></imageobject>
|
||||
<textobject><phrase>The Customize Toolbars window.</phrase></textobject>
|
||||
<caption><para>The Customize Toolbars window in &gwenview; with the
|
||||
<guibutton>Previous</guibutton> button selected.</para></caption>
|
||||
</mediaobject>
|
||||
</screenshot>
|
||||
|
||||
<sect3 id="toolbars-items-add">
|
||||
<title>Adding an Item</title>
|
||||
<para>You can add an item to your toolbar by selecting it from the left side and
|
||||
clicking on the right arrow button.</para>
|
||||
</sect3>
|
||||
|
||||
<sect3 id="toolbars-items-remove">
|
||||
<title>Removing an Item</title>
|
||||
<para>You can remove an item by selecting it and clicking the left arrow
|
||||
button.</para>
|
||||
</sect3>
|
||||
|
||||
|
||||
<sect3 id="toolbars-items-rearrange">
|
||||
<title>Changing the Position of Items</title>
|
||||
|
||||
<para>You can change the position of the items by moving them lower or higher in
|
||||
the list. To move items lower, press the down arrow button, while to move items
|
||||
higher press the up arrow button. You can also change items' position by
|
||||
dragging and dropping them.</para>
|
||||
|
||||
<para>On horizontal toolbars, the item that's on top will be the one on the left.
|
||||
On vertical toolbars, items are arranged as they appear in the toolbar.</para>
|
||||
|
||||
</sect3>
|
||||
|
||||
<sect3 id="toolbars-items-separator">
|
||||
<title>Adding a Separator</title>
|
||||
<para>You can add separator lines between items by adding a
|
||||
<guilabel>--- separator ---</guilabel> item to the toolbar.</para>
|
||||
</sect3>
|
||||
|
||||
<sect3 id="toolbars-items-defaults">
|
||||
<title>Restoring Defaults</title>
|
||||
|
||||
<para>You can restore your toolbar to the way it was when you installed the
|
||||
application by pressing the <guibutton>Defaults</guibutton> button at the bottom
|
||||
of the window and then confirming your decision.</para>
|
||||
|
||||
</sect3>
|
||||
|
||||
<sect3 id="toolbars-items-text-icons">
|
||||
<title>Changing Text and Icons</title>
|
||||
|
||||
<para>You can change the icon and text of individual toolbar items by selecting
|
||||
an item and clicking either the <guibutton>Change Icon...</guibutton> or
|
||||
<guibutton>Change Text...</guibutton> button.</para>
|
||||
<!--FIXME Icon selection and icon categories -> own section?
|
||||
Change Text -> Option "Hide text when toolbar shows text alongside icons"
|
||||
-->
|
||||
</sect3>
|
||||
</sect2>
|
||||
|
||||
<sect2 id="toolbars-appearance">
|
||||
<title>Customizing Toolbar Appearance</title>
|
||||
|
||||
<para>You can change the appearance of toolbars by right-clicking on a toolbar
|
||||
to access it's context menu.</para>
|
||||
<!-- settings for each toolbar separately-->
|
||||
<sect3 id="toolbars-appearance-text-position">
|
||||
<title>Text Position</title>
|
||||
|
||||
<para>You can change the appearance of text on toolbars in the
|
||||
<guisubmenu>Text Position</guisubmenu> submenu of a toolbar's context menu.</para>
|
||||
|
||||
<para>You can choose from:</para>
|
||||
<itemizedlist>
|
||||
|
||||
<listitem><para>
|
||||
<guimenuitem>Icons</guimenuitem> -
|
||||
only the icon for each toolbar item will appear.
|
||||
</para></listitem>
|
||||
|
||||
<listitem><para>
|
||||
<guimenuitem>Text</guimenuitem> -
|
||||
only the text label for each toolbar item will appear.
|
||||
</para></listitem>
|
||||
|
||||
<listitem><para>
|
||||
<guimenuitem>Text Alongside Icons</guimenuitem> -
|
||||
<!--this may need to be changed to 'left' for RTL languages-->
|
||||
the text label will appear to the right of each toolbar item's icon
|
||||
</para></listitem>
|
||||
|
||||
<listitem><para>
|
||||
<guimenuitem>Text Under Icons</guimenuitem> -
|
||||
the text label will appear underneath each toolbar item's icon
|
||||
</para></listitem>
|
||||
|
||||
</itemizedlist>
|
||||
|
||||
<para>You can also show or hide text for individual toolbar items by
|
||||
right-clicking on an item and checking or unchecking the item under
|
||||
<guilabel>Show Text</guilabel>.</para>
|
||||
|
||||
</sect3>
|
||||
|
||||
<sect3 id="toolbars-appearance-icon-size">
|
||||
<title>Icon Size</title>
|
||||
|
||||
<para>You can change the size of toolbar items' icons by selecting
|
||||
<guisubmenu>Icon Size</guisubmenu> from the toolbar's context menu.</para>
|
||||
|
||||
<para>You can choose from the following options: (each lists the icon size
|
||||
in pixels)</para>
|
||||
|
||||
<itemizedlist>
|
||||
<listitem><para><guimenuitem>Small (16x16)</guimenuitem></para></listitem>
|
||||
<listitem><para><guimenuitem>Medium (22x22)</guimenuitem>
|
||||
[the default value]</para></listitem>
|
||||
<listitem><para><guimenuitem>Large (32x32)</guimenuitem></para></listitem>
|
||||
<listitem><para><guimenuitem>Huge (48x48)</guimenuitem></para></listitem>
|
||||
</itemizedlist>
|
||||
|
||||
</sect3>
|
||||
|
||||
<sect3 id="toolbars-appearance-move">
|
||||
<title>Moving Toolbars</title>
|
||||
|
||||
<para>In order to move toolbars, you must <quote>unlock</quote> them. To do
|
||||
so, uncheck <guimenuitem>Lock Toolbar Positions</guimenuitem> from a toolbar's
|
||||
context menu. To restore the lock, simply recheck this menu item.</para>
|
||||
|
||||
<para>You can change a toolbar's position from the
|
||||
<guisubmenu>Orientation</guisubmenu> submenu of its context menu.</para>
|
||||
|
||||
<para>You can choose from:</para>
|
||||
<itemizedlist>
|
||||
<listitem><para><guimenuitem>Top</guimenuitem>
|
||||
[the default in many applications]</para></listitem>
|
||||
<listitem><para><guimenuitem>Left</guimenuitem></para></listitem>
|
||||
<listitem><para><guimenuitem>Right</guimenuitem></para></listitem>
|
||||
<listitem><para><guimenuitem>Bottom</guimenuitem></para></listitem>
|
||||
</itemizedlist>
|
||||
|
||||
<para>You can also move a toolbar by clicking and holding onto the dotted line
|
||||
at the left of horizontal toolbars or the top of vertical toolbars and dragging
|
||||
it to your desired location.</para>
|
||||
|
||||
</sect3>
|
||||
|
||||
<sect3 id="toolbars-appearance-show-hide">
|
||||
<title>Show/Hide Toolbars</title>
|
||||
|
||||
<para>If your application has only one toolbar, you can hide a toolbar by
|
||||
deselecting <guimenuitem>Show Toolbar</guimenuitem> from either the toolbar's
|
||||
context menu or the <guimenu>Settings</guimenu> menu. To restore the toolbar,
|
||||
select <guimenuitem>Show Toolbar</guimenuitem> from the <guimenu>Settings</guimenu>
|
||||
menu. Note that toolbars must be <quote>unlocked</quote> to hide them from their
|
||||
context menu; see <xref linkend="toolbars-appearance-move"/> for more
|
||||
information.</para>
|
||||
|
||||
<para>If your application has more than one toolbar, a submenu called
|
||||
<guisubmenu>Toolbars Shown</guisubmenu> will appear in the context menu and
|
||||
<guimenu>Settings</guimenu> menu instead of the above menu entry. From that
|
||||
menu you may select individual toolbars to hide and show.</para>
|
||||
|
||||
</sect3>
|
||||
</sect2>
|
||||
|
||||
<sect2 id="toolbars-ack">
|
||||
<title>Thanks and Acknowledgments</title>
|
||||
<para>Thanks to an anonymous Google Code-In 2011 participant for writing much
|
||||
of this section.</para>
|
||||
</sect2>
|
||||
|
||||
</sect1>
|
||||
|
||||
|
||||
<sect1 id="shortcuts">
|
||||
<sect1info>
|
||||
<authorgroup>
|
||||
<author><firstname>Alexey</firstname> <surname>Subach</surname></author>
|
||||
<author>&TC.Hollingsworth; &TC.Hollingsworth.mail;</author>
|
||||
<!-- TRANS:ROLES_OF_TRANSLATORS -->
|
||||
</authorgroup>
|
||||
</sect1info>
|
||||
|
||||
<!--FIXME link from
|
||||
<sect2 id="configshort"> in tables/config.docbook>
|
||||
<sect2 id="configuration-shortcuts"> in extragear/multimedia-git/kplayer/doc/en_US/configuration.docbook
|
||||
-->
|
||||
<!--FIXME explain Alternate + Global shortcuts in Screenshot and
|
||||
another place to change Global Shortcuts (Systemsettings)-->
|
||||
<title>Using and Customizing Shortcuts</title>
|
||||
|
||||
<sect2 id="shortcuts-intro">
|
||||
<title>Introduction</title>
|
||||
|
||||
<para>Many &kde; applications allow you to configure keyboard shortcuts. To open
|
||||
the standard keyboard shortcuts configuration panel, go to
|
||||
<menuchoice><guimenu>Settings</guimenu><guimenuitem>Configure
|
||||
Shortcuts...</guimenuitem></menuchoice>.</para>
|
||||
|
||||
<para>In the Configure Shortcuts window, you will see a list of all the shortcuts
|
||||
available in the current application. You can use the search box at the top to
|
||||
search for the shortcut you want.</para>
|
||||
|
||||
<screenshot id="screenshot-shortcuts-search">
|
||||
<screeninfo>The Customize Shortcuts Window</screeninfo>
|
||||
<mediaobject>
|
||||
<imageobject><imagedata fileref="shortcuts-search.png" format="PNG"/></imageobject>
|
||||
<textobject><phrase>The Customize Shortcuts window.</phrase></textobject>
|
||||
<caption><para>Searching for shortcuts with <userinput>file</userinput> in
|
||||
<ulink url="http://kde.org/applications/system/dolphin/">&dolphin;</ulink>.
|
||||
</para></caption>
|
||||
</mediaobject>
|
||||
</screenshot>
|
||||
|
||||
</sect2>
|
||||
|
||||
<sect2 id="shortcuts-change">
|
||||
<title>Changing a Shortcut</title>
|
||||
|
||||
<para>To change a shortcut, first click on the name of a shortcut you want to change.
|
||||
You will see a radio group where you can choose whether to set the shortcut to its
|
||||
default value, or select a new shortcut for the selected action. To set a new shortcut,
|
||||
choose <guilabel>Custom</guilabel> and click on the button next to it. Then just
|
||||
type the shortcut you would like to use, and your changes will be saved.</para>
|
||||
|
||||
<screenshot id="screenshot-shortcuts-set">
|
||||
<screeninfo>Setting a Shortcut</screeninfo>
|
||||
<mediaobject>
|
||||
<imageobject><imagedata fileref="shortcuts-set.png" format="PNG"/></imageobject>
|
||||
<textobject><phrase>The Customize Shortcuts window demonstrating how to
|
||||
set a shortcut.</phrase></textobject>
|
||||
</mediaobject>
|
||||
</screenshot>
|
||||
|
||||
</sect2>
|
||||
|
||||
<sect2 id="shortcuts-reset">
|
||||
<title>Resetting Shortcuts</title>
|
||||
<para>There is a button at the bottom of the window, called <guibutton>Reset to
|
||||
Defaults</guibutton>. Clicking on this button will reset all your custom shortcuts
|
||||
to their default values.</para>
|
||||
|
||||
<para>You can also reset an individual shortcut to its default value by selecting
|
||||
it, and choosing the <guilabel>Default</guilabel> radio button.</para>
|
||||
|
||||
</sect2>
|
||||
|
||||
<sect2 id="shortcuts-delete">
|
||||
<title>Removing a Shortcut</title>
|
||||
|
||||
<para>To remove a shortcut, select it from the list, then click the remove icon (a
|
||||
black arrow with a cross) to the right of the button that allows you to select
|
||||
a shortcut.</para>
|
||||
|
||||
</sect2>
|
||||
|
||||
<sect2 id ="shortcuts-schemes">
|
||||
<title>Working with Schemes</title>
|
||||
|
||||
<para>Schemes are keyboard shortcuts configuration profiles, so you can create
|
||||
several profiles with different shortcuts and switch between these profiles
|
||||
easily.</para>
|
||||
|
||||
<warning><para>This feature is under development. It is not possible to import
|
||||
schemes using a &GUI; at this time.</para></warning>
|
||||
|
||||
<screenshot id="screenshot-shortcuts-schemes">
|
||||
<screeninfo>Working with Schemes</screeninfo>
|
||||
<mediaobject>
|
||||
<imageobject><imagedata fileref="shortcuts-schemes.png" format="PNG"/></imageobject>
|
||||
<textobject><phrase>The Customize Shortcuts window displaying the scheme
|
||||
editing tools.</phrase></textobject>
|
||||
<caption><para>Editing a scheme called <userinput>work</userinput>.</para></caption>
|
||||
</mediaobject>
|
||||
</screenshot>
|
||||
|
||||
<para>To see a menu allowing you to edit schemes, click on the
|
||||
<guibutton>Details</guibutton> button at the bottom of the form. The following
|
||||
options will appear:</para>
|
||||
|
||||
<variablelist>
|
||||
|
||||
<varlistentry>
|
||||
<term><guilabel>Current Scheme</guilabel></term>
|
||||
<listitem><para>Allows you to switch between your schemes.</para></listitem>
|
||||
</varlistentry>
|
||||
|
||||
<varlistentry>
|
||||
<term><guibutton>New...</guibutton></term>
|
||||
<listitem><para>Creates a new scheme. This opens a window that lets you select
|
||||
a name for your new scheme.</para></listitem>
|
||||
</varlistentry>
|
||||
|
||||
<varlistentry>
|
||||
<term><guibutton>Delete</guibutton></term>
|
||||
<listitem><para>Deletes the current scheme.</para></listitem>
|
||||
</varlistentry>
|
||||
|
||||
<varlistentry>
|
||||
<term><guibutton>More Actions</guibutton></term>
|
||||
<listitem>
|
||||
<para>Opens the following menu:</para>
|
||||
<variablelist>
|
||||
|
||||
<varlistentry>
|
||||
<term><guimenuitem>Save as Scheme Defaults</guimenuitem></term>
|
||||
<listitem><para>Sets the current scheme as the default for all new schemes.</para></listitem>
|
||||
</varlistentry>
|
||||
|
||||
<varlistentry>
|
||||
<term><guimenuitem>Export Scheme...</guimenuitem></term>
|
||||
<listitem><para>Exports the current scheme to a file named <filename><replaceable>applicationname</replaceable><replaceable>schemename</replaceable>shortcuts.rc</filename>.</para>
|
||||
<para>
|
||||
Move this file to the folder <filename class="directory">$KDEDIR/apps/applicationname/</filename>
|
||||
and the exported scheme will be available in the drop down box labelled <guilabel>Current Scheme</guilabel>
|
||||
</para></listitem>
|
||||
</varlistentry>
|
||||
|
||||
</variablelist>
|
||||
</listitem>
|
||||
</varlistentry>
|
||||
</variablelist>
|
||||
|
||||
</sect2>
|
||||
|
||||
<sect2 id="shortcuts-print">
|
||||
<title>Printing Shortcuts</title>
|
||||
|
||||
<para>You can print out a list of shortcuts for easy reference by clicking the
|
||||
<guibutton>Print</guibutton> button at the bottom of the window.</para>
|
||||
|
||||
</sect2>
|
||||
|
||||
<sect2 id="shortcuts-ack">
|
||||
<title>Thanks and Acknowledgments</title>
|
||||
|
||||
<para>Special thanks to Google Code-In 2011 participant Alexey Subach for
|
||||
writing much of this section.</para>
|
||||
|
||||
</sect2>
|
||||
|
||||
</sect1>
|
||||
|
||||
</chapter>
|
||||
Binary file not shown.
|
Before Width: | Height: | Size: 18 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 16 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 2.5 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 17 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 43 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 48 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 6.5 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 28 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 47 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 13 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 36 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 33 KiB |
|
|
@ -1,147 +0,0 @@
|
|||
<?xml version="1.0" ?>
|
||||
<!DOCTYPE book PUBLIC "-//KDE//DTD DocBook XML V4.2-Based Variant V1.1//EN"
|
||||
"dtd/kdex.dtd" [
|
||||
<!ENTITY kappname "&kde-sc;">
|
||||
<!ENTITY % addindex "IGNORE">
|
||||
<!--FIXME: these entities should be added to kdoctools-->
|
||||
<!ENTITY kde-sc "&i18n-kde-sc;">
|
||||
<!ENTITY plasma-workspaces "&i18n-plasma-workspaces;">
|
||||
<!ENTITY plasma-desktop "&i18n-plasma-desktop;">
|
||||
<!ENTITY plasma-active "&i18n-plasma-active;">
|
||||
<!ENTITY gwenview '<application>Gwenview</application>'>
|
||||
<!ENTITY Meta "&i18n-Meta;">
|
||||
<!--/end entities that need to be added to kdoctools-->
|
||||
<!--make some of the above entities translatable in the interim-->
|
||||
<!ENTITY i18n-kde-sc "&kde; Software Collection">
|
||||
<!ENTITY i18n-plasma-workspaces "&kde; &plasma; Workspaces">
|
||||
<!ENTITY i18n-plasma-desktop "<application>&kde; &plasma; Desktop</application>">
|
||||
<!ENTITY i18n-plasma-active "<application>&plasma; Active</application>">
|
||||
<!ENTITY i18n-Meta "<keysym>Meta</keysym>">
|
||||
<!--/end temporary translatable entities-->
|
||||
<!ENTITY ui-chapter SYSTEM "ui.docbook">
|
||||
<!ENTITY tasks-chapter SYSTEM "tasks.docbook">
|
||||
<!ENTITY config-chapter SYSTEM "config.docbook">
|
||||
<!ENTITY install-chapter SYSTEM "install.docbook">
|
||||
<!ENTITY % English "INCLUDE"><!-- change language only here -->
|
||||
]>
|
||||
|
||||
<book id="fundamentals" lang="&language;">
|
||||
<title>&kde; Fundamentals</title>
|
||||
|
||||
<bookinfo>
|
||||
<authorgroup>
|
||||
<author>&TC.Hollingsworth; &TC.Hollingsworth.mail;</author>
|
||||
|
||||
<!-- TRANS:ROLES_OF_TRANSLATORS -->
|
||||
</authorgroup>
|
||||
|
||||
<copyright>
|
||||
<year>2011</year><year>2012</year><year>2013</year>
|
||||
<holder>&TC.Hollingsworth;</holder>
|
||||
</copyright>
|
||||
<copyright>
|
||||
<year>2011</year>
|
||||
<holder>Alexey Subach</holder>
|
||||
</copyright>
|
||||
<copyright>
|
||||
<year>2011</year>
|
||||
<holder>Salma Sultana</holder>
|
||||
</copyright>
|
||||
<legalnotice>&FDLNotice;</legalnotice>
|
||||
|
||||
<date>2013-12-08</date>
|
||||
<releaseinfo>&kde; 4.12</releaseinfo>
|
||||
|
||||
<abstract>
|
||||
<para>This guide provides an introduction to the &kde-sc; and describes many
|
||||
common tasks that can be performed in all &kde; applications.</para>
|
||||
</abstract>
|
||||
|
||||
<keywordset>
|
||||
<keyword>KDE</keyword>
|
||||
<keyword>introduction</keyword>
|
||||
<keyword>user interface</keyword>
|
||||
<keyword>menus</keyword>
|
||||
<keyword>files</keyword>
|
||||
<keyword>open</keyword>
|
||||
<keyword>save</keyword>
|
||||
<keyword>spelling</keyword>
|
||||
<keyword>spellcheck</keyword>
|
||||
<keyword>find</keyword>
|
||||
<keyword>replace</keyword>
|
||||
<keyword>colors</keyword>
|
||||
<keyword>configuration</keyword>
|
||||
<keyword>customization</keyword>
|
||||
<keyword>toolbars</keyword>
|
||||
<keyword>installation</keyword>
|
||||
<keyword>compiling</keyword>
|
||||
</keywordset>
|
||||
|
||||
</bookinfo>
|
||||
|
||||
<chapter id="introduction">
|
||||
<title>Introduction</title>
|
||||
<para>Welcome to &kde;!</para>
|
||||
|
||||
<para>This guide will introduce you to the many features of the &kde-sc; and
|
||||
describe many common tasks you can perform in all &kde; applications.</para>
|
||||
|
||||
<para>For more information on &kde;, visit the
|
||||
<ulink url="http://www.kde.org/">KDE website</ulink>.</para>
|
||||
|
||||
</chapter>
|
||||
|
||||
&install-chapter;
|
||||
|
||||
&ui-chapter;
|
||||
|
||||
&tasks-chapter;
|
||||
|
||||
&config-chapter;
|
||||
|
||||
<chapter id="credits">
|
||||
|
||||
<title>Credits and License</title>
|
||||
|
||||
<para>The original idea for this guide was proposed by Chusslove Illich and
|
||||
brought to fruition with input from &Burkhard.Lueck;, Yuri Chornoivan, and
|
||||
&TC.Hollingsworth;</para>
|
||||
|
||||
<para>Much of it was written by participants of
|
||||
<ulink url="http://code.google.com/opensource/gci/2011-12/index.html">Google
|
||||
Code-In 2011</ulink>. Thanks to Google for sponsoring their excellent work!</para>
|
||||
|
||||
<!-- TRANS:CREDIT_FOR_TRANSLATORS -->
|
||||
|
||||
&underFDL; <!-- FDL: do not remove -->
|
||||
&underGPL; <!-- GPL License -->
|
||||
|
||||
</chapter>
|
||||
|
||||
&documentation.index;
|
||||
|
||||
</book>
|
||||
|
||||
<!-- Comments, ideas, policy etc
|
||||
|
||||
Use default appearance + settings of kde compiled from sources
|
||||
|
||||
Style issues:
|
||||
Task oriented
|
||||
Avoid variablelist for obvious terms like e. g. Left/Right
|
||||
|
||||
FIXME missing stuff:
|
||||
|
||||
add a11y docbooks from koffice 1.6?
|
||||
|
||||
-->
|
||||
<!--
|
||||
Local Variables:
|
||||
mode: sgml
|
||||
sgml-namecase-general: t
|
||||
sgml-namecase-entity: nil
|
||||
sgml-general-insert-case: lower
|
||||
sgml-minimize-attributes: nil
|
||||
sgml-omittag: nil
|
||||
End:
|
||||
-->
|
||||
|
|
@ -1,127 +0,0 @@
|
|||
<chapter id="install">
|
||||
<title>Installing the &kde-sc;</title>
|
||||
|
||||
<para>You can install the &kde-sc; on a variety of different platforms, ranging from
|
||||
smartphones and tablets to computers running &Microsoft; &Windows;, &MacOS;,
|
||||
&UNIX;, &BSD; or &Linux;. Binary packages are available for many different
|
||||
platforms and distributions, or advanced users may build the source code.</para>
|
||||
|
||||
<sect1 id="install-packages">
|
||||
<title>Installing Packages</title>
|
||||
|
||||
<para>Hundreds of developers worldwide have done a lot of work to make it easy
|
||||
to install &kde; on a variety of different devices and platforms.</para>
|
||||
|
||||
<sect2 id="install-linux">
|
||||
<title>&Linux;</title>
|
||||
|
||||
<para>Nearly every &Linux; distribution provides binary packages for individual
|
||||
&kde-sc; applications and the &plasma-workspaces; as a whole.</para>
|
||||
|
||||
<para>To install an individual application, look for its name in your
|
||||
distribution's package collection. To install one of the &plasma-workspaces;,
|
||||
like &plasma-desktop;, look for a metapackage or package
|
||||
group, typically <literal>kde-desktop</literal>.</para>
|
||||
|
||||
<note>
|
||||
<para>Some core applications may be installed together with other core
|
||||
applications in a combined package named after the &kde; package they are
|
||||
provided in. For instance, &dolphin; might be found in the
|
||||
<literal>kde-baseapps</literal> package.</para>
|
||||
</note>
|
||||
|
||||
<para>If you have trouble locating &kde; packages for your distribution, please
|
||||
contact their support resources. Many distributions also have a team dedicated
|
||||
to packaging &kde; that can provide assistance specific to &kde;</para>
|
||||
|
||||
<!--FIXME: provide steps for common distributions?-->
|
||||
|
||||
</sect2>
|
||||
|
||||
<sect2 id="install-windows">
|
||||
<title>&Microsoft; &Windows;</title>
|
||||
|
||||
<para>The &kde; on Windows Initiative provides binary packages of &kde-sc;
|
||||
applications for &Microsoft; &Windows;. They also provide a special installer
|
||||
application that permits you to install individual applications or groups and
|
||||
all necessary dependencies easily.</para>
|
||||
|
||||
<para>For more information on the initiative and to download the installer,
|
||||
visit <ulink url="http://windows.kde.org/">the KDE on Windows Initiative</ulink>.
|
||||
</para>
|
||||
|
||||
<!--FIXME: describe how to use the installer?-->
|
||||
|
||||
</sect2>
|
||||
|
||||
<sect2 id="install-mac">
|
||||
<title>&MacOS;</title>
|
||||
|
||||
<para>Individual &kde-sc; applications can be installed through several
|
||||
different <quote>ports</quote> systems available for &MacOS;. Several different
|
||||
&kde; applications also provide their own binary builds for &MacOS;.</para>
|
||||
|
||||
<para>For more information, visit
|
||||
<ulink url="http://mac.kde.org/">&kde; on &MacOS;X</ulink>.</para>
|
||||
|
||||
</sect2>
|
||||
|
||||
<sect2 id="install-bsd">
|
||||
<title>&BSD;</title>
|
||||
|
||||
<para>Most &BSD; distributions allows you to install &kde-sc; applications
|
||||
and the &plasma-workspaces; as a whole through their <quote>ports</quote>
|
||||
system.</para>
|
||||
|
||||
<para>For more information on installing ports, see your &BSD; distribution's
|
||||
documentation.</para>
|
||||
|
||||
<!--FIXME: provide steps/links for common BSDs?-->
|
||||
|
||||
</sect2>
|
||||
|
||||
<sect2 id="install-mobile">
|
||||
<title>Mobile Devices</title>
|
||||
|
||||
<para>&plasma-active; is an exciting initiative to bring a new &kde;
|
||||
experience to mobile devices like smartphones or tablets. Binary releases are
|
||||
provided for several different devices.</para>
|
||||
|
||||
<para>For more information, visit
|
||||
<ulink url="http://plasma-active.org/">&plasma-active;</ulink>.</para>
|
||||
|
||||
</sect2>
|
||||
|
||||
<sect2 id="install-live">
|
||||
<title>Live Media</title>
|
||||
|
||||
<para>Several &Linux; and &BSD; distributions offer live media. This permits you
|
||||
to try out the &plasma-workspaces; without installing anything to your system.
|
||||
All you have to do insert a CD or connect a USB drive and boot from it. If you
|
||||
like what you see, most offer an option to install it to your hard drive.</para>
|
||||
|
||||
<para>There is <ulink url="http://www.kde.org/download/distributions.php">a list
|
||||
of distributions that offer the &kde-sc; on live media</ulink> on the &kde; website.</para>
|
||||
</sect2>
|
||||
|
||||
<sect2 id="install-source">
|
||||
<title>Building from Source Code</title>
|
||||
|
||||
<para>For detailed information on how to compile and install &kde;
|
||||
applications see
|
||||
<ulink url="http://techbase.kde.org/Getting_Started#Building_and_Running_KDE_Software_From_Source">
|
||||
Building and Running &kde; Software From Source on &kde; TechBase</ulink>.</para>
|
||||
|
||||
<para>Since &kde; software uses <command>cmake</command> you should
|
||||
have no trouble compiling it. Should you run into problems please report them to the
|
||||
&kde; mailing lists.</para>
|
||||
</sect2>
|
||||
<!--Fixme more info:
|
||||
Where to get sources (git split)
|
||||
where to get help building from souces
|
||||
kdesrc-build
|
||||
-->
|
||||
|
||||
</sect1>
|
||||
|
||||
</chapter>
|
||||
Binary file not shown.
|
Before Width: | Height: | Size: 18 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 55 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 27 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 57 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 41 KiB |
File diff suppressed because it is too large
Load diff
Binary file not shown.
|
Before Width: | Height: | Size: 64 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 19 KiB |
File diff suppressed because it is too large
Load diff
Binary file not shown.
|
Before Width: | Height: | Size: 2.9 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 1.5 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 13 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 1.1 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 44 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 3.1 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 14 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 32 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 2.2 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 137 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 134 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 84 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 75 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 5.5 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 6.1 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 3.8 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 2 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 22 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 2.4 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 8.5 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 1.3 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 1.5 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 2.5 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 1.8 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 1 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 2.9 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 4.4 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 2.8 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 1 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 7.5 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 7.6 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 30 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 101 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 140 KiB |
|
|
@ -1,2 +0,0 @@
|
|||
########### install files ###############
|
||||
kde4_create_handbook(index.docbook INSTALL_DESTINATION ${HTML_INSTALL_DIR}/en SUBDIR khelpcenter/glossary)
|
||||
|
|
@ -1,10 +0,0 @@
|
|||
#!/bin/sh
|
||||
DEFINED_ENTRIES=`sed -ne "s^.*<glossentry id=\"\(.*\)\">.*^\1^p" *.docbook`
|
||||
REFERENCED_ENTRIES=`sed -ne "s^.*<glossseealso otherterm=\"\(.*\)\">.*^\1^p" *.docbook | uniq`
|
||||
|
||||
# Check for entries which are referenced but not defined.
|
||||
for ENTRY in $REFERENCED_ENTRIES; do
|
||||
if ! echo $DEFINED_ENTRIES | grep $ENTRY - > /dev/null 2>&1; then
|
||||
echo "'$ENTRY' referenced but not defined!"
|
||||
fi
|
||||
done
|
||||
|
|
@ -1,611 +0,0 @@
|
|||
<?xml version="1.0" ?>
|
||||
<!DOCTYPE glossary PUBLIC "-//KDE//DTD DocBook XML V4.2-Based Variant V1.1//EN" "dtd/kdex.dtd" [
|
||||
<!ENTITY % addindex "IGNORE">
|
||||
<!ENTITY % English "INCLUDE">
|
||||
<!ENTITY glossary-kdeprinting SYSTEM "kdeprintingglossary.docbook">
|
||||
<!ENTITY newpara "</p><p>">
|
||||
<!ENTITY linkstart "<a href=">
|
||||
<!ENTITY linkmid ' target="_top">'>
|
||||
<!ENTITY linkend "</a>">
|
||||
|
||||
<!ENTITY emstart '<span class="emphasis"><em>' >
|
||||
<!ENTITY emend '</em></span>'>
|
||||
<!-- acronym, systemitem unchanged
|
||||
itemizedlist+listitem changed to simple para -->
|
||||
]>
|
||||
|
||||
|
||||
<glossary lang="&language;" id="glossary">
|
||||
|
||||
<glossdiv id="glossdiv-technologies">
|
||||
<title>Technologies</title>
|
||||
<glossentry id="gloss-akonadi">
|
||||
<glossterm>Akonadi</glossterm>
|
||||
<glossdef><para>The data storage access mechanism for all PIM (Personal Information Manager) data in &kde; SC 4. One single
|
||||
storage and retrieval system allows efficiency and extensibility not possible under &kde; 3, where each PIM component had
|
||||
its own system. Note that use of Akonadi does not change data storage formats (vcard, iCalendar, mbox, maildir etc.) - it
|
||||
just provides a new way of accessing and updating the data.&newpara;
|
||||
The main reasons for design and development of Akonadi are of technical nature, ⪚ having a unique way to access PIM-data (contacts, calendars, emails..) from different applications (⪚ &kmail;, &kword; &etc;), thus eliminating the need to write similar code here and there.&newpara;
|
||||
Another goal is to de-couple GUI applications like &kmail; from the direct access to external resources like mail-servers - which was a major reason for bug-reports/wishes with regard to performance/responsiveness in the past.&newpara;
|
||||
More info:&newpara;
|
||||
&linkstart;"http://pim.kde.org/akonadi/"&linkmid;Akonadi for KDE's PIM&linkend;&newpara;
|
||||
&linkstart;"http://en.wikipedia.org/wiki/Akonadi"&linkmid;Wikipedia: Akonadi&linkend;&newpara;
|
||||
&linkstart;"http://techbase.kde.org/Projects/PIM/Akonadi"&linkmid;Techbase - Akonadi&linkend;</para>
|
||||
<glossseealso otherterm="gloss-gui">&GUI;</glossseealso>
|
||||
<glossseealso otherterm="gloss-kde">&kde;</glossseealso>
|
||||
</glossdef>
|
||||
</glossentry>
|
||||
<glossentry id="gloss-arts">
|
||||
<glossterm>ARts</glossterm>
|
||||
<glossdef><para>The sound framework in &kde; 2 and 3. Its single-tasking nature caused problems when two sources of sound were encountered. In the &plasma; desktop it is replaced by Phonon.&newpara;
|
||||
More info:&newpara;
|
||||
&linkstart;"http://en.wikipedia.org/wiki/ARts"&linkmid; Wikipedia: ARts&linkend;&newpara;
|
||||
&linkstart;"http://www.arts-project.org"&linkmid;ARts home page&linkend;</para>
|
||||
<glossseealso otherterm="gloss-kde">&kde;</glossseealso>
|
||||
<glossseealso otherterm="gloss-phonon">Phonon</glossseealso>
|
||||
<glossseealso otherterm="gloss-plasma">&plasma;</glossseealso>
|
||||
</glossdef>
|
||||
</glossentry>
|
||||
<glossentry id="gloss-dbus">
|
||||
<glossterm>D-Bus</glossterm>
|
||||
<glossdef><para>D-Bus or Desktop Bus is an inter-service messaging system. Developed by &RedHat;, it was heavily influenced by &kde; 3 DCOP, which it supersedes. Most POSIX operating systems support D-Bus, and a port for Windows exists. It is used by Qt 4 and GNOME.&newpara;
|
||||
More info:&newpara;
|
||||
&linkstart;"http://freedesktop.org/wiki/Software/dbus/"&linkmid;FreeDesktop.org: What is D-Bus?&linkend;&newpara;
|
||||
&linkstart;"http://en.wikipedia.org/wiki/D-Bus"&linkmid;Wikipedia: D-Bus&linkend;</para>
|
||||
<glossseealso otherterm="gloss-dcop">&DCOP;</glossseealso>
|
||||
<glossseealso otherterm="gloss-gnome">GNOME</glossseealso>
|
||||
<glossseealso otherterm="gloss-kde">&kde;</glossseealso>
|
||||
<glossseealso otherterm="gloss-qt">&Qt;</glossseealso>
|
||||
</glossdef>
|
||||
</glossentry>
|
||||
<glossentry id="gloss-dcop">
|
||||
<glossterm>DCOP</glossterm>
|
||||
<glossdef><para><acronym>DCOP</acronym>, which stands for Desktop COmmunication Protocol, is a light-weight interprocess and software componentry communication system used in &kde; 3. Replaced with &DBus; in &kde; SC 4.&newpara;
|
||||
More info:&newpara;
|
||||
&linkstart;"http://en.wikipedia.org/wiki/DCOP"&linkmid;Wikipedia: DCOP&linkend;</para>
|
||||
<glossseealso otherterm="gloss-dbus">D-Bus</glossseealso>
|
||||
<glossseealso otherterm="gloss-kde">&kde;</glossseealso>
|
||||
</glossdef>
|
||||
</glossentry>
|
||||
<glossentry id="gloss-flake">
|
||||
<glossterm>Flake</glossterm>
|
||||
<glossdef><para>Flake is a programming library to be used in &koffice;/Calligra. Functionally, it provides Shapes to display content and Tools to manipulate content. Shapes can be zoomed or rotated and can be grouped to work as a single Shape, around which text flow is possible.&newpara;
|
||||
More info:&newpara;
|
||||
&linkstart;"http://community.kde.org/Calligra/Libs/Flake"&linkmid;&kde; Community Wiki: Flake&linkend;</para>
|
||||
<glossseealso otherterm="gloss-kde">&kde;</glossseealso>
|
||||
<glossseealso otherterm="gloss-kparts">KParts</glossseealso>
|
||||
</glossdef>
|
||||
</glossentry>
|
||||
<glossentry id="gloss-ghns">
|
||||
<glossterm>Get Hot New Stuff</glossterm>
|
||||
<glossdef><para>&emstart;G&emend;et &emstart;H&emend;ot &emstart;N&emend;ew &emstart;S&emend;tuff (GHNS) is an open standard that makes it easy for users to download and install various extensions for their applications. Our implementation of GHNS is used by &plasma; (for example to get new desktop themes), and by many applications and widgets.&newpara;
|
||||
More info:&newpara;
|
||||
&linkstart;"http://ghns.freedesktop.org"&linkmid;Home of GHNS&linkend;&newpara;
|
||||
&linkstart;"http://lwn.net/Articles/227855/"&linkmid;An article on GHNS in &kde; SC 4&linkend;</para>
|
||||
<glossseealso otherterm="gloss-kde">&kde;</glossseealso>
|
||||
<glossseealso otherterm="gloss-plasma">&plasma;</glossseealso>
|
||||
</glossdef>
|
||||
</glossentry>
|
||||
<glossentry id="gloss-ghnsaccr">
|
||||
<glossterm>GHNS</glossterm>
|
||||
<glossdef><para><acronym>GHNS</acronym> is the acronym of Get Hot New Stuff.</para>
|
||||
<glossseealso otherterm="gloss-ghns">Get Hot New Stuff</glossseealso>
|
||||
</glossdef>
|
||||
</glossentry>
|
||||
<glossentry id="gloss-ioslave">
|
||||
<glossterm><acronym>IO</acronym> Slave</glossterm>
|
||||
<glossdef><para><acronym>IO</acronym> Slaves enable &kde; applications to
|
||||
access remote resources as easily as local resources (making them
|
||||
"network transparent"). Remote resources (⪚ files) might
|
||||
be stored on <acronym>SMB</acronym> shares or similar.</para>
|
||||
<glossseealso otherterm="gloss-smb"><acronym>SMB</acronym></glossseealso>
|
||||
<glossseealso otherterm="gloss-kde">&kde;</glossseealso>
|
||||
</glossdef>
|
||||
</glossentry>
|
||||
<glossentry id="gloss-khtml">
|
||||
<glossterm>KHTML</glossterm>
|
||||
<glossdef><para>KHTML is the &HTML; rendering engine for the &kde; &plasma; desktop, as used by the &konqueror; browser. It also provides a KPart that enables all &kde; applications to display web content. A new introduction, &Qt; WebKit is also for Plasma and other application development.</para>
|
||||
<glossseealso otherterm="gloss-kde">&kde;</glossseealso>
|
||||
<glossseealso otherterm="gloss-konqueror">&konqueror;</glossseealso>
|
||||
<glossseealso otherterm="gloss-kparts">KParts</glossseealso>
|
||||
<glossseealso otherterm="gloss-plasma">&plasma;</glossseealso>
|
||||
<glossseealso otherterm="gloss-webkit">WebKit</glossseealso>
|
||||
</glossdef>
|
||||
</glossentry>
|
||||
<glossentry id="gloss-kio">
|
||||
<glossterm><acronym>KIO</acronym></glossterm>
|
||||
<glossdef><para>The &kde; Input/Output system which makes use of so-called
|
||||
"<acronym>IO</acronym> Slaves".</para>
|
||||
<glossseealso otherterm="gloss-ioslave"><acronym>IO</acronym>
|
||||
Slave</glossseealso>
|
||||
<glossseealso otherterm="gloss-kde">&kde;</glossseealso>
|
||||
</glossdef>
|
||||
</glossentry>
|
||||
<glossentry id="gloss-kiosk">
|
||||
<glossterm>Kiosk</glossterm>
|
||||
<glossdef><para>Kiosk is a framework for restricting user capabilities on a &kde; platform system, ideal for use in locked-down environments such as Internet cafés. It is present in &kde; 3 and &kde; 4, but the administration tool, <application>Kiosktool</application> is &kde; 3 only. It can be used to configure &kde; 4 applications, or kiosk configurations can be maintained by editing config files manually.</para>
|
||||
<glossseealso otherterm="gloss-kde">&kde;</glossseealso>
|
||||
</glossdef>
|
||||
</glossentry>
|
||||
<glossentry id="gloss-kparts">
|
||||
<glossterm>KParts</glossterm>
|
||||
<glossdef><para>KParts is an embedding technology which allows &kde;
|
||||
applications to embed other &kde; applications. For example, the text
|
||||
view used by &konqueror; is a KPart.</para>
|
||||
<glossseealso otherterm="gloss-konqueror">&konqueror;</glossseealso>
|
||||
</glossdef>
|
||||
</glossentry>
|
||||
<glossentry id="gloss-ksycoca">
|
||||
<glossterm><acronym>KSycoca</acronym></glossterm>
|
||||
<glossdef><para><acronym>KSycoca</acronym> (&kde; &emstart;Sy&emend;stem
|
||||
&emstart;Co&emend;nfiguration &emstart;Ca&emend;che) is a
|
||||
configuration cache which, for example, guarantees fast access to the menu
|
||||
entries.</para>
|
||||
<glossseealso
|
||||
otherterm="gloss-kbuildsycoca"><application>KBuildSycoca</application></glossseealso>
|
||||
</glossdef>
|
||||
</glossentry>
|
||||
<glossentry id="gloss-phonon">
|
||||
<glossterm>Phonon</glossterm>
|
||||
<glossdef><para>A cross-platform multimedia API, interfacing with existing frameworks, such as gstreamer and xine engines. &kde; 2 and 3 depended on aRts for sound. Phonon replaces it.&newpara;
|
||||
More info:&newpara;
|
||||
&linkstart;"http://en.wikipedia.org/wiki/Phonon_(KDE)"&linkmid; Wikipedia: Phonon (KDE)&linkend;&newpara;
|
||||
&linkstart;"http://phonon.kde.org"&linkmid;Phonon website&linkend;</para>
|
||||
<glossseealso otherterm="gloss-arts">&arts;</glossseealso>
|
||||
<glossseealso otherterm="gloss-kde">&kde;</glossseealso>
|
||||
</glossdef>
|
||||
</glossentry>
|
||||
<glossentry id="gloss-solid">
|
||||
<glossterm>Solid</glossterm>
|
||||
<glossdef><para>Solid provides a single API for hardware management. Hardware is grouped into 'domains'. Since the backends for Solid are pluggable, Solid helps application developers write less code, and have it platform independent.&newpara;
|
||||
More info:&newpara;
|
||||
&linkstart;"http://solid.kde.org"&linkmid;Discover Solid&linkend;</para>
|
||||
<glossseealso otherterm="gloss-kde">&kde;</glossseealso>
|
||||
</glossdef>
|
||||
</glossentry>
|
||||
<glossentry id="gloss-threadweaver">
|
||||
<glossterm>Threadweaver</glossterm>
|
||||
<glossdef><para>This thread programming library spreads work among multiple-core processors where available, prioritizing them before queuing them for execution. ThreadWeaver provides a high-level job interface for multithreaded programming.&newpara;
|
||||
More info:&newpara;
|
||||
&linkstart;"http://www.englishbreakfastnetwork.org/apidocs/apidox-kde-4.0/kdelibs-apidocs/threadweaver/html/Why.html"&linkmid;Why Multithreading?&linkend;</para>
|
||||
<glossseealso otherterm="gloss-kde">&kde;</glossseealso>
|
||||
</glossdef>
|
||||
</glossentry>
|
||||
<glossentry id="gloss-webkit">
|
||||
<glossterm>WebKit</glossterm>
|
||||
<glossdef><para>HTML rendering engine, originating from a fork of KHTML. Adopted by <trademark>Apple</trademark> and developed for <trademark>Safari</trademark>. Webkit brings the whole functionality back to &kde; SC 4, where it is available through &Qt;.&newpara;
|
||||
More info:&newpara;
|
||||
&linkstart;"http://webkit.org/"&linkmid;WebKit home page&linkend;&newpara;
|
||||
&linkstart;"http://en.wikipedia.org/wiki/Webkit"&linkmid;Wikipedia: WebKit&linkend;</para>
|
||||
<glossseealso otherterm="gloss-kde">&kde;</glossseealso>
|
||||
<glossseealso otherterm="gloss-kde">KHTML</glossseealso>
|
||||
</glossdef>
|
||||
</glossentry>
|
||||
</glossdiv>
|
||||
|
||||
<glossdiv id="glossdiv-xorg">
|
||||
<title>X.Org</title>
|
||||
<glossentry id="gloss-antialiasing">
|
||||
<glossterm>Antialiasing</glossterm>
|
||||
<glossdef><para>If mentioned in context with &kde;, anti-aliasing often means
|
||||
the smoothing of the fonts visible on the screen. &Qt; version 3.3
|
||||
or higher used together with X.Org server makes this possible under &kde;
|
||||
as well.</para>
|
||||
<glossseealso otherterm="gloss-kde">&kde;</glossseealso>
|
||||
<glossseealso otherterm="gloss-qt">&Qt;</glossseealso>
|
||||
</glossdef>
|
||||
</glossentry>
|
||||
<glossentry id="gloss-xserver">
|
||||
<glossterm>&X-Server;</glossterm>
|
||||
<glossdef><para>The &X-Server; represents a basic layer upon which the
|
||||
various &GUI;s like &kde; are built. It manages the
|
||||
basic mouse and keyboard input (from the local host as well as from
|
||||
remote hosts) and provides elementary graphic routines to draw
|
||||
rectangles and other primitives.</para>
|
||||
<glossseealso otherterm="gloss-kde">&kde;</glossseealso>
|
||||
<glossseealso otherterm="gloss-gui">&GUI;</glossseealso>
|
||||
</glossdef>
|
||||
</glossentry>
|
||||
</glossdiv>
|
||||
|
||||
<glossdiv id="glossdiv-applications">
|
||||
<title>Applications</title>
|
||||
<glossentry id="gloss-dolphin">
|
||||
<glossterm>Dolphin</glossterm>
|
||||
<glossdef><para>The default file manager in &kde; SC 4. It has a side panel (Places), but navigation is mainly by the 'breadcrumb' trail above the main window. Split windows are possible, and views can be applied to individual windows. Mounting and unmounting <acronym>USB</acronym> devices can be done in the side panel. Other directories can be added to the Places panel. A Tree view is also possible.&newpara;
|
||||
More info:&newpara;
|
||||
&linkstart;"http://en.wikipedia.org/wiki/Dolphin_(software)"&linkmid;Wikipedia: Dolphin&linkend;&newpara;
|
||||
&linkstart;"http://introducingkde4.blogspot.com/2007/12/dolphin.html"&linkmid;Introducing KDE 4 Blog - Dolphin&linkend;&newpara;
|
||||
&linkstart;"http://userbase.kde.org/Tutorials/File_Management"&linkmid;Userbase: File Management Tutorial&linkend;</para>
|
||||
<glossseealso otherterm="gloss-kde">&kde;</glossseealso>
|
||||
<glossseealso otherterm="gloss-konqueror">&konqueror;</glossseealso>
|
||||
</glossdef>
|
||||
</glossentry>
|
||||
<glossentry id="gloss-kbuildsycoca">
|
||||
<glossterm><application>KBuildSycoca</application></glossterm>
|
||||
<glossdef><para><application>KBuildSycoca4</application> is a command line
|
||||
program and regenerates the
|
||||
so-called <acronym>KSycoca</acronym>. This is useful, for example, if some
|
||||
or all modules in
|
||||
&systemsettings; are missing.</para>
|
||||
<glossseealso otherterm="gloss-ksycoca"><acronym>KSycoca</acronym></glossseealso>
|
||||
<glossseealso otherterm="gloss-systemsettings">&systemsettings;</glossseealso>
|
||||
</glossdef>
|
||||
</glossentry>
|
||||
<glossentry id="gloss-kinfocenter">
|
||||
<glossterm>KInfoCenter</glossterm>
|
||||
<glossdef><para>Kinfocenter originated as part of Kcontrol standing alone from KDE 3.1. In KDE SC 4 it is replaced by modules configured in System Settings, notably Solid, and is being reintroduced as an application in &kde; SC 4.5.&newpara;
|
||||
More info:&newpara;
|
||||
&linkstart;"http://en.wikipedia.org/wiki/Kinfocenter"&linkmid;Wikipedia: KInfoCenter&linkend;</para>
|
||||
<glossseealso otherterm="gloss-kde">&kde;</glossseealso>
|
||||
<glossseealso otherterm="gloss-solid">Solid</glossseealso>
|
||||
<glossseealso otherterm="gloss-systemsettings">&systemsettings;</glossseealso>
|
||||
</glossdef>
|
||||
</glossentry>
|
||||
<glossentry id="gloss-konqueror">
|
||||
<glossterm>&konqueror;</glossterm>
|
||||
<glossdef><para>&konqueror; is a web browser, picture viewer, file manager
|
||||
and more, and a core part of the &kde; project. You can
|
||||
find more information about &konqueror; at &linkstart;"http://www.konqueror.org"&linkmid;www.konqueror.org&linkend;.</para>
|
||||
<glossseealso otherterm="gloss-kde">&kde;</glossseealso>
|
||||
</glossdef>
|
||||
</glossentry>
|
||||
<glossentry id="gloss-krunner">
|
||||
<glossterm>KRunner</glossterm>
|
||||
<glossdef><para>The mini-command-line that is accessed from the Classic menu, the keyboard shortcut &Alt;+<keycap>F2</keycap>, or a right-click on the desktop. In &kde; SC 4 a partial name will display all possible matches.&newpara;
|
||||
More info:&newpara;
|
||||
&linkstart;"http://userbase.kde.org/Tutorials/Krunner"&linkmid;UserBase: KRunner Usage&linkend;</para>
|
||||
<glossseealso otherterm="gloss-kde">&kde;</glossseealso>
|
||||
<glossseealso otherterm="gloss-plasma">&plasma;</glossseealso>
|
||||
</glossdef>
|
||||
</glossentry>
|
||||
<glossentry id="gloss-kwin">
|
||||
<glossterm>KWin</glossterm>
|
||||
<glossdef><para>KWin is the window manager. This is where window decorations can be changed and themes applied. &kde; SC 4 extends KWin to provide support for 3D Compositing effects on the desktop.&newpara;
|
||||
More info:&newpara;
|
||||
&linkstart;"http://userbase.kde.org/KWin"&linkmid;UserBase: KWin&linkend;</para>
|
||||
<glossseealso otherterm="gloss-kde">&kde;</glossseealso>
|
||||
<glossseealso otherterm="gloss-xserver">&X-Server;</glossseealso>
|
||||
</glossdef>
|
||||
</glossentry>
|
||||
<glossentry id="gloss-minicli">
|
||||
<glossterm>Mini-CLI</glossterm>
|
||||
<glossdef><para>Mini &emstart;C&emend;ommand &emstart;L&emend;ine &emstart;I&emend;nterface. Synonym to KRunner.</para>
|
||||
<glossseealso otherterm="gloss-krunner">KRunner</glossseealso>
|
||||
</glossdef>
|
||||
</glossentry>
|
||||
<glossentry id="gloss-pager">
|
||||
<glossterm>Pager</glossterm>
|
||||
<glossdef><para>A pager is a small program or panel applet which shows the position of windows on your desktop and usually if you have several Virtual Desktops gives an overview over all.</para>
|
||||
<glossseealso otherterm="gloss-kde">&kde;</glossseealso>
|
||||
<glossseealso otherterm="gloss-kickoff">Kickoff</glossseealso>
|
||||
<glossseealso otherterm="gloss-kicker">Kicker</glossseealso>
|
||||
<glossseealso otherterm="gloss-panel">Panel</glossseealso>
|
||||
<glossseealso otherterm="gloss-plasma">&plasma;</glossseealso>
|
||||
<glossseealso otherterm="gloss-virtualdesktops">Virtual Desktops</glossseealso>
|
||||
</glossdef>
|
||||
</glossentry>
|
||||
<glossentry id="gloss-systemsettings">
|
||||
<glossterm>&systemsettings;</glossterm>
|
||||
<glossdef><para>This is the project and filename of the &kde; control
|
||||
center. &systemsettings; allows you to customize virtually
|
||||
every configuration option of &kde;.</para>
|
||||
<glossseealso otherterm="gloss-kde">&kde;</glossseealso>
|
||||
<glossseealso otherterm="gloss-kinfocenter">KInfoCenter</glossseealso>
|
||||
</glossdef>
|
||||
</glossentry>
|
||||
</glossdiv>
|
||||
|
||||
<glossdiv id="glossdiv-desktop-terminology">
|
||||
<title>Desktop Terminology</title>
|
||||
<glossentry id="gloss-activities">
|
||||
<glossterm>Activities</glossterm>
|
||||
<glossdef><para>Activities are sets of &plasma; widgets that have their own wallpaper&newpara;
|
||||
A bit like Virtual Desktops, but not quite. For example you have a "work activity" with commit rss feeds, a note with your TODO, a Folder View with your work related files, and a subtle wallpaper.&newpara;
|
||||
Next to it, you have your freetime activity, with previews of family photos and dogs, rss feeds from your favorite blogs, a Folder View showing your movie collection, a twitter applet and of course that Iron Maiden wallpaper you have been loving since the early 80s.&newpara;
|
||||
At 17:00 hours sharp you switch from the work activity to your freetime activity.&newpara;
|
||||
More info:&newpara;
|
||||
&linkstart;"http://userbase.kde.org/Plasma"&linkmid;Plasma FAQ&linkend;</para>
|
||||
<glossseealso otherterm="gloss-kde">&kde;</glossseealso>
|
||||
<glossseealso otherterm="gloss-virtualdesktops">Virtual Desktops</glossseealso>
|
||||
</glossdef>
|
||||
</glossentry>
|
||||
<glossentry id="gloss-containment">
|
||||
<glossterm>Containment</glossterm>
|
||||
<glossdef><para>A Containment is a top level grouping of widgets. Each Containment manages the layout and configuration data of its set of widgets independently from other Containments.&newpara;
|
||||
The end result is that you can group widgets within a Containment according to the significance to your working pattern, rather than by directory grouping.&newpara;
|
||||
More info:&newpara;
|
||||
&linkstart;"http://userbase.kde.org/Plasma"&linkmid;Plasma FAQ&linkend;</para>
|
||||
<glossseealso otherterm="gloss-kde">&kde;</glossseealso>
|
||||
<glossseealso otherterm="gloss-widget">Widget</glossseealso>
|
||||
</glossdef>
|
||||
</glossentry>
|
||||
<glossentry id="gloss-draganddrop">
|
||||
<glossterm>Drag and Drop</glossterm>
|
||||
<glossdef><para>This concept tries to replace many actions like copying
|
||||
files from one place to another by a certain mouse movement, ⪚
|
||||
clicking on an icon in a &konqueror; window, moving the mouse to another
|
||||
window while keeping the mouse button pressed, and releasing the mouse
|
||||
button ("dropping" the object) copies files.</para>
|
||||
<glossseealso otherterm="gloss-konqueror">&konqueror;</glossseealso>
|
||||
</glossdef>
|
||||
</glossentry>
|
||||
<glossentry id="gloss-extender">
|
||||
<glossterm>Extender</glossterm>
|
||||
<glossdef><para>Extenders are a special kind of popup that can grow out of a &plasma; panel for example. Extenders have detachable parts. Extenders are a new concept that arrived in &plasma; for &kde; 4.2. The Kuiserver (the interface that collects all long running jobs and puts them into one window) will make use of extenders so you can detach various jobs and monitor their progress separately.&newpara;
|
||||
More info:&newpara;
|
||||
&linkstart;"http://userbase.kde.org/Plasma"&linkmid;Plasma FAQ&linkend;</para>
|
||||
<glossseealso otherterm="gloss-kde">&kde;</glossseealso>
|
||||
<glossseealso otherterm="gloss-plasma">&plasma;</glossseealso>
|
||||
</glossdef>
|
||||
</glossentry>
|
||||
<glossentry id="gloss-gnome">
|
||||
<glossterm><acronym>GNOME</acronym></glossterm>
|
||||
<glossdef>
|
||||
<para>&emstart;G&emend;NU &emstart;N&emend;etwork &emstart;O&emend;bject
|
||||
&emstart;M&emend;odel &emstart;E&emend;nvironment, one of the
|
||||
leading &UNIX; &GUI;s.</para>
|
||||
<glossseealso otherterm="gloss-gui">&GUI;</glossseealso>
|
||||
</glossdef>
|
||||
</glossentry>
|
||||
<glossentry id="gloss-gui">
|
||||
<glossterm>&GUI;</glossterm>
|
||||
<glossdef><para>Abbreviation for &emstart;G&emend;raphical
|
||||
&emstart;U&emend;ser &emstart;I&emend;nterface. Every desktop
|
||||
environment (like &kde;) is a &GUI;. Most
|
||||
&GUI;s feature mouse support and/or windows to manage
|
||||
the programs.</para>
|
||||
<glossseealso otherterm="gloss-kde">&kde;</glossseealso>
|
||||
</glossdef>
|
||||
</glossentry>
|
||||
<glossentry id="gloss-homedirectory">
|
||||
<glossterm>Home Directory</glossterm>
|
||||
<glossdef><para>That's the place in system, where all your files are kept. You can write your files outside of this folder, but all applications are configured to propose this folder as place to write your files to. And this is easier, when you are keeping your things here.&newpara;
|
||||
More info:&newpara;
|
||||
&linkstart;"http://en.wikipedia.org/wiki/Home_directory"&linkmid;Wikipedia: Home Directory&linkend;</para>
|
||||
<glossseealso otherterm="gloss-dolphin">&dolphin;</glossseealso>
|
||||
</glossdef>
|
||||
</glossentry>
|
||||
<glossentry id="gloss-kde">
|
||||
<glossterm>&kde;</glossterm>
|
||||
<glossdef><para>Abbreviation for "K Desktop Environment", a
|
||||
leading &GUI; for &UNIX;-based systems. You can find more
|
||||
detailed information at &linkstart;
|
||||
"http://www.kde.org"&linkmid;www.kde.org&linkend;.&newpara;
|
||||
&kde; is more than just software. It is a community made up of programmers, translators, contributors, artists, writers, distributors, and users from all over the world. Our international technology team is committed to creating the best free software for the desktop. And not only contributors, but users and fans of &kde; software can be found throughout the entire globe, giving help to other users, spreading the news, or just simply enjoying the experience.</para>
|
||||
<glossseealso otherterm="gloss-gui">&GUI;</glossseealso>
|
||||
</glossdef>
|
||||
</glossentry>
|
||||
<glossentry id="gloss-kicker">
|
||||
<glossterm><acronym>&kicker;</acronym></glossterm>
|
||||
<glossdef>
|
||||
<para>In &kde; 3, the relocatable bar, usually at the bottom of the screen (sometimes called the Panel), on which application launchers, the Pager, and buttons for running applications reside.</para>
|
||||
<glossseealso otherterm="gloss-panel">Panel</glossseealso>
|
||||
<glossseealso otherterm="gloss-plasma">&plasma;</glossseealso>
|
||||
</glossdef>
|
||||
</glossentry>
|
||||
<glossentry id="gloss-kickoff">
|
||||
<glossterm><acronym>&kickoff;</acronym></glossterm>
|
||||
<glossdef>
|
||||
<para>In &kde; SC 4 (and some late versions of &kde; 3), a launch menu in which apps are sorted by functional group. 'Favorites' replaces the 'Most used applications' in Classic Menu, and applications can be added to it. Right-click also offers the possibility of adding applications to the desktop or panel. Rapid access to a less-used application can be by the search box. Other menus are being worked on, since &kde; SC 4 can be used with more than one launcher, should that be required.&newpara;
|
||||
More info:&newpara;
|
||||
&linkstart;"http://home.kde.org/~binner/kickoff/sneak_preview.html"&linkmid;Kickoff Sneak Preview&linkend;</para>
|
||||
<glossseealso otherterm="gloss-kde">&kde;</glossseealso>
|
||||
<glossseealso otherterm="gloss-pager">Pager</glossseealso>
|
||||
<glossseealso otherterm="gloss-panel">Panel</glossseealso>
|
||||
<glossseealso otherterm="gloss-plasma">&plasma;</glossseealso>
|
||||
</glossdef>
|
||||
</glossentry>
|
||||
<glossentry id="gloss-oxygen">
|
||||
<glossterm><acronym>Oxygen</acronym></glossterm>
|
||||
<glossdef>
|
||||
<para>Oxygen is the default theme of &kde; SC 4. Designed to bring 'a breath of fresh air' to the desktop by removing the simplistic, cartoonish icons, and replacing them with a clean theme and photo-realistic icons. Oxygen uses a desaturated palette to avoid the icons becoming a distraction and uses detailed scalable graphics (SVG).&newpara;
|
||||
More info:&newpara;
|
||||
&linkstart;"http://en.wikipedia.org/wiki/Oxygen_Project"&linkmid;Wikipedia: Oxygen Project&linkend;&newpara;
|
||||
&linkstart;"http://www.oxygen-icons.org/?cat=3"&linkmid;Oxygen Icons&linkend;</para>
|
||||
<glossseealso otherterm="gloss-kde">&kde;</glossseealso>
|
||||
<glossseealso otherterm="gloss-ksvg">KSVG</glossseealso>
|
||||
<glossseealso otherterm="gloss-plasma">&plasma;</glossseealso>
|
||||
</glossdef>
|
||||
</glossentry>
|
||||
<glossentry id="gloss-panel">
|
||||
<glossterm>Panel</glossterm>
|
||||
<glossdef><para>Refers to the panel which often resides at the bottom of the
|
||||
screen.</para>
|
||||
<glossseealso otherterm="gloss-kde">&kde;</glossseealso>
|
||||
<glossseealso otherterm="gloss-kicker">&kicker;</glossseealso>
|
||||
<glossseealso otherterm="gloss-kickoff">&kickoff;</glossseealso>
|
||||
<glossseealso otherterm="gloss-plasma">&plasma;</glossseealso>
|
||||
</glossdef>
|
||||
</glossentry>
|
||||
<glossentry id="gloss-plasma">
|
||||
<glossterm>Plasma</glossterm>
|
||||
<glossdef><para>In &kde; SC 4 the &plasma; Desktop replaces KDesktop, &kicker; and the SuperKaramba widget engine. The applets are called Plasmoids, and range from informational widgets to mini-apps such as a calculator or dictionary. Widgets from other sources, such as SuperKaramba widgets or <trademark>Google</trademark> Gadgets are also supported.&newpara;
|
||||
More info:&newpara;
|
||||
&linkstart;"http://en.wikipedia.org/wiki/Plasma_(KDE)"&linkmid;Wikipedia: Plasma&linkend;&newpara;
|
||||
&linkstart;"http://plasma.kde.org/cms/1107/"&linkmid;Plasma website&linkend;&newpara;
|
||||
&linkstart;"http://userbase.kde.org/Plasma"&linkmid;Plasma FAQ&linkend;&newpara;
|
||||
&linkstart;"http://userbase.kde.org/Tutorials/TweakingPlasma"&linkmid;Tweaking Plasma&linkend;</para>
|
||||
<glossseealso otherterm="gloss-kde">&kde;</glossseealso>
|
||||
<glossseealso otherterm="gloss-kicker">&kicker;</glossseealso>
|
||||
<glossseealso otherterm="gloss-widget">Widget</glossseealso>
|
||||
</glossdef>
|
||||
</glossentry>
|
||||
<glossentry id="gloss-ripping">
|
||||
<glossterm>Ripping</glossterm>
|
||||
<glossdef><para>The process of reading audio data from a &cdrom; and
|
||||
storing it on the hard disk.</para>
|
||||
</glossdef>
|
||||
</glossentry>
|
||||
<glossentry id="gloss-virtualdesktops">
|
||||
<glossterm>Virtual Desktops</glossterm>
|
||||
<glossdef><para>A popular concept of &UNIX; based window managers is the one of virtual desktops. This means you have not only one screen where you can place your windows on but several. When you switch to a different desktop (usually with a pager) you will only see the windows which you started on your new desktop or moved to it. A window can also be made "sticky" which means it appears on all virtual desktops.&newpara;
|
||||
More info:&newpara;
|
||||
&linkstart;"http://userbase.kde.org/Plasma"&linkmid;Plasma FAQ&linkend;</para>
|
||||
<glossseealso otherterm="gloss-kde">&kde;</glossseealso>
|
||||
<glossseealso otherterm="gloss-kickoff">&kickoff;</glossseealso>
|
||||
<glossseealso otherterm="gloss-pager">Pager</glossseealso>
|
||||
</glossdef>
|
||||
</glossentry>
|
||||
</glossdiv>
|
||||
|
||||
<glossdiv id="kde-development">
|
||||
<title>&kde; Development</title>
|
||||
<glossentry id="gloss-qt">
|
||||
<glossterm>&Qt;</glossterm>
|
||||
<glossdef><para>The &GUI; of &kde; is built on top of
|
||||
the &Qt; toolkit, which provides many graphical elements (so-called
|
||||
"Widgets") which are used to construct the desktop. You
|
||||
can find more information about &Qt; at &linkstart;
|
||||
"http://qt-project.org/"&linkmid;http://qt-project.org/&linkend;.</para>
|
||||
<glossseealso otherterm="gloss-kde">&kde;</glossseealso>
|
||||
<glossseealso otherterm="gloss-gui">&GUI;</glossseealso>
|
||||
<glossseealso otherterm="gloss-widget">Widget</glossseealso>
|
||||
</glossdef>
|
||||
</glossentry>
|
||||
<glossentry id="gloss-git">
|
||||
<glossterm>Git</glossterm>
|
||||
<glossdef><para>Git is a free and open source, distributed version control system designed to handle everything from small to very large projects with speed and efficiency.&newpara;
|
||||
Every Git clone is a full-fledged repository with complete history and full revision tracking capabilities, not dependent on network access or a central server. Branching and merging are fast and easy to do.&newpara;
|
||||
Git is used for version control of files, much like tools such as Mercurial, Bazaar, Subversion, CVS, Perforce, and Visual SourceSafe.&newpara;
|
||||
It was decided that Git will be the main version control system of &kde;, replacement of SVN. It has been already used for some &kde; projects like Konversation and Amarok.&newpara;
|
||||
More info:&newpara;
|
||||
&linkstart;"http://git-scm.com/"&linkmid;Git Homepage&linkend;</para>
|
||||
<glossseealso otherterm="gloss-kde">&kde;</glossseealso>
|
||||
<glossseealso otherterm="gloss-svn">SVN</glossseealso>
|
||||
</glossdef>
|
||||
</glossentry>
|
||||
<glossentry id="gloss-i18n">
|
||||
<glossterm>i18n</glossterm>
|
||||
<glossdef><para>Abbreviation for "internationalization". &kde;
|
||||
supports many different languages, and several i18n techniques make it
|
||||
easy to translate the &GUI; as well as the accompanying
|
||||
documents of &kde; into all these languages. More information about the
|
||||
i18n process is available at &linkstart;
|
||||
"http://l10n.kde.org"&linkmid;l10n.kde.org&linkend;.</para>
|
||||
<glossseealso otherterm="gloss-kde">&kde;</glossseealso>
|
||||
<glossseealso otherterm="gloss-gui">&GUI;</glossseealso>
|
||||
</glossdef>
|
||||
</glossentry>
|
||||
<glossentry id="gloss-kross">
|
||||
<glossterm>Kross</glossterm>
|
||||
<glossdef><para>Kross is a scripting framework, enabling support for multiple scripting languages. A plugin system allows for the support of further languages in the future.</para>
|
||||
<glossseealso otherterm="gloss-kde">&kde;</glossseealso>
|
||||
</glossdef>
|
||||
</glossentry>
|
||||
<glossentry id="gloss-kdom">
|
||||
<glossterm>KDOM</glossterm>
|
||||
<glossdef><para>A KPart module making KHTML <acronym>DOM</acronym> (&emstart;D&emend;ocument &emstart;O&emend;bject &emstart;M&emend;odel) rendering capabilities available to all applications. KSVG2 is built on KDOM for &kde; SC 4.</para>
|
||||
<glossseealso otherterm="gloss-kde">&kde;</glossseealso>
|
||||
<glossseealso otherterm="gloss-khtml">KHTML</glossseealso>
|
||||
<glossseealso otherterm="gloss-kparts">KParts</glossseealso>
|
||||
<glossseealso otherterm="gloss-khtml">KSVG</glossseealso>
|
||||
</glossdef>
|
||||
</glossentry>
|
||||
<glossentry id="gloss-kjs">
|
||||
<glossterm>KJS</glossterm>
|
||||
<glossdef><para>&kde; platform's JavaScript engine.</para>
|
||||
<glossseealso otherterm="gloss-kde">&kde;</glossseealso>
|
||||
<glossseealso otherterm="gloss-kparts">KParts</glossseealso>
|
||||
<glossseealso otherterm="gloss-plasma">&plasma;</glossseealso>
|
||||
</glossdef>
|
||||
</glossentry>
|
||||
<glossentry id="gloss-ksvg">
|
||||
<glossterm>KSVG</glossterm>
|
||||
<glossdef><para>KSVG enables support for scalable vector graphics in a KHTML browser. KSVG2 extends this for &kde; SC 4.</para>
|
||||
<glossseealso otherterm="gloss-kde">&kde;</glossseealso>
|
||||
<glossseealso otherterm="gloss-khtml">KHTML</glossseealso>
|
||||
<glossseealso otherterm="gloss-kparts">KParts</glossseealso>
|
||||
</glossdef>
|
||||
</glossentry>
|
||||
<glossentry id="gloss-l10n">
|
||||
<glossterm>l10n</glossterm>
|
||||
<glossdef><para>Abbreviation for "localization", the process
|
||||
of adapting a program to the local environment. This includes ⪚ the
|
||||
currency used for monetary values or the time format.</para>
|
||||
<glossseealso otherterm="gloss-i18n">i18n</glossseealso>
|
||||
</glossdef>
|
||||
</glossentry>
|
||||
<glossentry id="gloss-strigi">
|
||||
<glossterm>Strigi</glossterm>
|
||||
<glossdef><para>A deep-indexed search daemon, Strigi aims to be fast and light-weight. It also uses SHA-1 hash which will help in the identification of duplicate files.&newpara;
|
||||
More info:&newpara;
|
||||
&linkstart;"http://en.wikipedia.org/wiki/Strigi"&linkmid;Wikipedia: Strigi&linkend;</para>
|
||||
<glossseealso otherterm="gloss-kde">&kde;</glossseealso>
|
||||
</glossdef>
|
||||
</glossentry>
|
||||
<glossentry id="gloss-widget">
|
||||
<glossterm>Widget</glossterm>
|
||||
<glossdef><para>Graphical elements like scrollbars, buttons or input
|
||||
fields which are used by &kde; to construct the &GUI;.
|
||||
</para>
|
||||
<glossseealso otherterm="gloss-kde">&kde;</glossseealso>
|
||||
<glossseealso otherterm="gloss-gui">&GUI;</glossseealso>
|
||||
</glossdef>
|
||||
</glossentry>
|
||||
<glossentry id="gloss-svn">
|
||||
<glossterm><acronym>SVN</acronym></glossterm>
|
||||
<glossdef><para>Abbreviation for &emstart;Subversion&emend;, a version control system. The <acronym>SVN</acronym> is a very elegant way of managing file versions that allow more than one developer to easily work on the same project. You can find a description of how to get the latest (developer) version of the &kde; sources via anonymous <acronym>SVN</acronym> on &linkstart;"http://developer.kde.org/source/anonsvn.html"&linkmid;http://developer.kde.org/source/anonsvn.html&linkend;.&newpara; More about <acronym>SVN</acronym> is available at &linkstart;"http://subversion.tigris.org/"&linkmid;http://subversion.tigris.org/&linkend;.</para>
|
||||
<glossseealso otherterm="gloss-git">Git</glossseealso>
|
||||
</glossdef>
|
||||
</glossentry>
|
||||
<glossentry id="gloss-xmlgui">
|
||||
<glossterm>XMLGUI</glossterm>
|
||||
<glossdef><para>A programmers' framework for designing the user interface. It is extensively used by KParts.&newpara;
|
||||
More info:&newpara;
|
||||
&linkstart;"http://en.wikipedia.org/wiki/XMLGUI"&linkmid;Wikipedia: XMLGUI&linkend;&newpara;
|
||||
&linkstart;"http://en.wikipedia.org/wiki/Qt_Style_Sheets"&linkmid;Wikipedia: Qt Style Sheets&linkend;</para>
|
||||
<glossseealso otherterm="gloss-gui">&GUI;</glossseealso>
|
||||
<glossseealso otherterm="gloss-kparts">Kparts</glossseealso>
|
||||
<glossseealso otherterm="gloss-qt">&Qt;</glossseealso>
|
||||
</glossdef>
|
||||
</glossentry>
|
||||
</glossdiv>
|
||||
|
||||
<glossdiv id="glossdiv-misc">
|
||||
<title>Miscellaneous</title>
|
||||
<glossentry id="gloss-rfc">
|
||||
<glossterm><acronym>RFC</acronym></glossterm>
|
||||
<glossdef><para>&emstart;R&emend;equest &emstart;F&emend;or
|
||||
&emstart;C&emend;omment. A common way to publish new protocol
|
||||
ideas or procedures for evaluation of the Internet community. Though
|
||||
<acronym>RFC</acronym>s are not mandatory, many applications try to
|
||||
adhere to them, once they have been approved by the community.&newpara;
|
||||
More information about <acronym>RFC</acronym>s can be found at the
|
||||
&linkstart;"http://www.rfc-editor.org"&linkmid;RFC Homepage&linkend;.</para>
|
||||
</glossdef>
|
||||
</glossentry>
|
||||
</glossdiv>
|
||||
|
||||
<glossdiv id="glossdiv-protocols">
|
||||
<title>Various protocols</title>
|
||||
<glossentry id="gloss-smb">
|
||||
<glossterm><acronym>SMB</acronym></glossterm>
|
||||
<glossdef><para>&emstart;S&emend;erver &emstart;M&emend;essage
|
||||
&emstart;B&emend;lock. A network protocol used in &Microsoft; &Windows;
|
||||
networks to access the file systems of other computers.</para>
|
||||
<glossseealso otherterm="gloss-ioslave"><acronym>IO</acronym> Slave</glossseealso>
|
||||
</glossdef>
|
||||
</glossentry>
|
||||
<glossentry id="gloss-irc">
|
||||
<glossterm><acronym>IRC</acronym></glossterm>
|
||||
<glossdef><para>&emstart;I&emend;nternet &emstart;R&emend;elay
|
||||
&emstart;C&emend;hat. A protocol defined in <acronym>RFC</acronym>
|
||||
1459, which handles the specification to enable real-time text chat.</para>
|
||||
<glossseealso otherterm="gloss-rfc"><acronym>RFC</acronym></glossseealso>
|
||||
</glossdef>
|
||||
</glossentry>
|
||||
<glossentry id="gloss-host">
|
||||
<glossterm>Host</glossterm>
|
||||
<glossdef><para>This can either be a name from your
|
||||
<filename>/etc/hosts</filename> file
|
||||
(<systemitem class="systemname">mycomputer</systemitem>),
|
||||
an Internet name (<systemitem class="systemname">www.kde.org</systemitem>) or an IP-Address
|
||||
(<systemitem>192.168.0.10</systemitem>).
|
||||
</para>
|
||||
</glossdef>
|
||||
</glossentry>
|
||||
</glossdiv>
|
||||
|
||||
&glossary-kdeprinting;
|
||||
</glossary>
|
||||
|
|
@ -1,941 +0,0 @@
|
|||
|
||||
<!--
|
||||
<?xml version="1.0" ?>
|
||||
<!DOCTYPE glossary PUBLIC "-//KDE//DTD DocBook XML V4.2-Based Variant V1.1//EN"
|
||||
"customization/dtd/kdex.dtd" [
|
||||
<!ENTITY % addindex "IGNORE">
|
||||
<!ENTITY % English "INCLUDE">
|
||||
<!ENTITY glossary-kdeprinting SYSTEM "kdeprintingglossary.docbook">
|
||||
|
||||
]>
|
||||
<glossary id="glossary">
|
||||
-->
|
||||
<glossdiv id="glossdiv-printing">
|
||||
<title>Printing</title>
|
||||
|
||||
|
||||
<glossentry id="gloss-acl">
|
||||
<glossterm><acronym>ACLs</acronym></glossterm>
|
||||
<glossdef><para>Abbreviation for &emstart;A&emend;ccess
|
||||
&emstart;C&emend;ontrol &emstart;L&emend;ists;
|
||||
ACLs are used to check for the access by a given
|
||||
(authenticated) user. A first rough support for ACLs
|
||||
for printing is available from &CUPS;; this will be refined
|
||||
in future versions. </para>
|
||||
<glossseealso otherterm="gloss-authentication">Authentication</glossseealso>
|
||||
</glossdef>
|
||||
</glossentry>
|
||||
|
||||
<glossentry id="gloss-appsocketprotocol">
|
||||
<glossterm>AppSocket Protocol</glossterm>
|
||||
<glossdef><para>AppSocket is a protocol for the transfer of
|
||||
print data, also frequently called "Direct TCP/IP Printing".
|
||||
&Hewlett-Packard; have taken AppSocket, added a few minor
|
||||
extensions around it and been very successful in renaming
|
||||
and marketing it under the brand "&HP; JetDirect"...</para>
|
||||
<glossseealso otherterm="gloss-hpjetdirectprotocol">&HP; JetDirect Protocol</glossseealso>
|
||||
<glossseealso otherterm="gloss-directtcpipprinting">Direct TCP/IP Printing</glossseealso>
|
||||
</glossdef>
|
||||
</glossentry>
|
||||
|
||||
<glossentry id="gloss-apsfilter">
|
||||
<glossterm>APSfilter</glossterm>
|
||||
<glossdef><para>APSfilter is used mainly in the context of "classical"
|
||||
&UNIX; printing (BSD-style LPD). It is a sophisticated shell script,
|
||||
disguised as an "all-in-one" filtering program. In reality,
|
||||
APSfilter calls "real filters" to do the jobs needed. It sends
|
||||
printjobs automatically through these other filters, based on an
|
||||
initial file-type analysis of the printfile.
|
||||
It is written and maintained by Andreas Klemm.&newpara;
|
||||
It is
|
||||
similar to Magicfilter and mostly uses Ghostscript for file conversions.
|
||||
Some Linux Distributions (like &SuSE;) use APSfilter, others
|
||||
Magicfilter (like &RedHat;), some have both for preference selection
|
||||
(like *BSD).&newpara;
|
||||
&CUPS; has &emstart;no&emend; need for APSfilter,
|
||||
as it runs its own file type recognition (based on &MIME; types)
|
||||
and applies its own filtering logic.</para>
|
||||
<glossseealso otherterm="gloss-ghostscript">Ghostscript</glossseealso>
|
||||
<glossseealso otherterm="gloss-magicfilter">Magicfilter</glossseealso>
|
||||
<glossseealso otherterm="gloss-mimetypes">&MIME;-Types</glossseealso>
|
||||
<glossseealso otherterm="gloss-printcap">printcap</glossseealso>
|
||||
</glossdef>
|
||||
</glossentry>
|
||||
|
||||
<glossentry id="gloss-authentication">
|
||||
<glossterm>Authentication</glossterm>
|
||||
<glossdef><para>Proving the identity of a certain person (maybe via username/password
|
||||
or by means of a certificate) is often called authentication. Once you are
|
||||
authenticated, you may or may not get access to a requested resource,
|
||||
possibly based on ACLs.</para>
|
||||
<glossseealso otherterm="gloss-acl">ACLs</glossseealso>
|
||||
</glossdef>
|
||||
</glossentry>
|
||||
|
||||
<glossentry id="gloss-bidirectionalcommunication">
|
||||
<glossterm>Bi-directional communication</glossterm>
|
||||
<glossdef><para>In the context of printing, a server or a host may receive additional
|
||||
information sent back from the printer (status messages &etc;), either
|
||||
upon a query or unrequested. AppSocket ( = &HP; JetDirect), &CUPS; and IPP
|
||||
support bi-directional communication, LPR/LPD and BSD-style printing
|
||||
do not...</para>
|
||||
<glossseealso otherterm="gloss-appsocketprotocol">AppSocket Protocol</glossseealso>
|
||||
<glossseealso otherterm="gloss-cups">&CUPS;</glossseealso>
|
||||
<glossseealso otherterm="gloss-directtcpipprinting">Direct TCP/IP Printing</glossseealso>
|
||||
<glossseealso otherterm="gloss-hpjetdirectprotocol">&HP; JetDirect</glossseealso>
|
||||
<glossseealso otherterm="gloss-ipp">IPP</glossseealso>
|
||||
<glossseealso otherterm="gloss-lprlpd">LPR/LPD</glossseealso>
|
||||
</glossdef>
|
||||
</glossentry>
|
||||
|
||||
<glossentry id="gloss-bsdstyleprinting">
|
||||
<glossterm>BSD-style Printing</glossterm>
|
||||
<glossdef><para>Generic term for different variants of the traditional &UNIX;
|
||||
printing method. Its first version appeared in the early 70s on
|
||||
BSD &UNIX; and was formally described in &linkstart;"http://www.rfc.net/rfc1179.html"&linkmid;RFC 1179&linkend; only as late
|
||||
as 1990.&newpara;
|
||||
At the time when BSD "remote" printing was first designed, printers
|
||||
were serially or otherwise directly connected devices to a host
|
||||
(with the Internet hardly consisting of more than 100 nodes!); printers
|
||||
used hole-punched, continuous paper, fed through by a tractor
|
||||
mechanism, with simple rows of ASCII text mechanically hammered on to
|
||||
the medium, drawn from a cardboard box beneath the table. It came out
|
||||
like a zig-zag folded paper "snake". Remote printing consisted of a
|
||||
neighboring host in the next room sending a file
|
||||
asking for printout.&newpara;
|
||||
How technology has changed! Printers generally use cut-sheet media, they have
|
||||
built-in intelligence to compute the raster images of pages after pages
|
||||
that are sent to them using one of the powerful page description
|
||||
languages (PDL). Many are network nodes in their own right,
|
||||
with CPU, RAM, a hard disk and their own Operation System, and
|
||||
are hooked to a net with potentially millions of users...&newpara;
|
||||
It is a vast proof of the flexible &UNIX; concept for doing things,
|
||||
that it made "Line Printing" reliably work even under these modern
|
||||
conditions. But time has finally come now to go for something new
|
||||
-- the IPP.
|
||||
</para>
|
||||
<glossseealso otherterm="gloss-ipp">IPP</glossseealso>
|
||||
<glossseealso otherterm="gloss-cups">&CUPS;</glossseealso>
|
||||
<glossseealso otherterm="gloss-lprlpd">LPR/LPD printing</glossseealso>
|
||||
</glossdef>
|
||||
</glossentry>
|
||||
|
||||
<glossentry id="gloss-cups">
|
||||
<glossterm>&CUPS;</glossterm>
|
||||
<glossdef><para>Abbreviation for &emstart;C&emend;ommon
|
||||
&emstart;U&emend;NIX &emstart;P&emend;rinting
|
||||
&emstart;S&emend;ystem; &CUPS; is the most modern &UNIX; and Linux
|
||||
printing system, also providing cross-platform print services
|
||||
to &Microsoft; &Windows; and Apple &MacOS; clients. Based on IPP, it does
|
||||
away with all the pitfalls of old-style BSD printing,
|
||||
providing authentication, encryption and ACLs, plus many more
|
||||
features. At the same time it is backward-compatible enough
|
||||
to serve all legacy clients that are not yet up to IPP, via
|
||||
LPR/LPD (BSD-style).&newpara;
|
||||
&CUPS; is able to control any &PostScript; printer by
|
||||
utilizing the vendor-supplied PPD (PostScript Printer
|
||||
Description file), targeted originally for &Microsoft; Windows NT
|
||||
printing only. &kde; Printing is most powerful if based on
|
||||
&CUPS;.&newpara;
|
||||
More info:&newpara;
|
||||
&linkstart;"http://www.cups.org"&linkmid;&CUPS; Homepage&linkend;</para>
|
||||
<glossseealso otherterm="gloss-acl">ACLs</glossseealso>
|
||||
<glossseealso otherterm="gloss-authentication">Authentication</glossseealso>
|
||||
<glossseealso otherterm="gloss-bsdstyleprinting">BSD-style printing</glossseealso>
|
||||
<glossseealso otherterm="gloss-ipp">IPP</glossseealso>
|
||||
<glossseealso otherterm="gloss-lprlpd">LPR/LPD</glossseealso>
|
||||
<glossseealso otherterm="gloss-ppd">PPD</glossseealso>
|
||||
</glossdef>
|
||||
</glossentry>
|
||||
|
||||
|
||||
<glossentry id="gloss-cupsfaq">
|
||||
<glossterm><acronym>&CUPS;-FAQ</acronym></glossterm>
|
||||
<glossdef><para>&linkstart;"http://www.cups.org/articles.php?L+TFAQ"&linkmid;&CUPS;-FAQ&linkend;
|
||||
is a valuable resource to answer many questions that anyone new to
|
||||
&CUPS; printing might have at first.
|
||||
</para>
|
||||
</glossdef>
|
||||
</glossentry>
|
||||
|
||||
<glossentry id="gloss-daemon">
|
||||
<glossterm><acronym>Daemon</acronym></glossterm>
|
||||
<glossdef><para>Abbreviation for &emstart;D&emend;isk
|
||||
&emstart;a&emend;nd &emstart;e&emend;xecution
|
||||
&emstart;mon&emend;itor; <acronym>Daemons</acronym> are present
|
||||
on all &UNIX; systems to perform tasks independent of user
|
||||
intervention. Readers more familiar with &Microsoft; &Windows; might
|
||||
want to compare daemons and the tasks they are responsible
|
||||
with "services".&newpara;
|
||||
One example of a daemon present on most
|
||||
legacy &UNIX; systems is the LPD (Line Printer Daemon); &CUPS; is
|
||||
widely seen as the successor to LPD in the &UNIX; world and
|
||||
it also operates through a daemon. </para>
|
||||
<glossseealso otherterm="gloss-spooling">SPOOLing</glossseealso>
|
||||
</glossdef>
|
||||
</glossentry>
|
||||
|
||||
<glossentry id="gloss-databaselinuxprinting">
|
||||
<glossterm>Database, Linuxprinting.org</glossterm>
|
||||
<glossdef><para>Already years ago, when Linux printing was still really difficult
|
||||
(only command line printing was known to most Linux users, no device
|
||||
specific print options were available for doing the jobs), Grant Taylor,
|
||||
author of the "Linux Printing HOWTO", collected most of the available
|
||||
information about printers, drivers and filters in his database.&newpara;
|
||||
With the emerging
|
||||
&CUPS; concept, extending the use of PPDs even to non-PostScript printers,
|
||||
he realized the potential of this database: if one puts the different
|
||||
datablobs (with content that could be described along the lines
|
||||
"Which device prints with which Ghostscript or other
|
||||
filter?", "How well?", and "What command line switches are available?") into
|
||||
PPD-compatible files, he could have all the power of &CUPS; on top of
|
||||
the traditional printer "drivers".&newpara;
|
||||
This has now developed into a broader
|
||||
concept, known as "Foomatic". Foomatic extends the capabilities
|
||||
of spoolers other than &CUPS; (LPR/LPD, LPRng, PDQ, PPR) to a certain
|
||||
degree ("stealing" some concepts from &CUPS;). The Linuxprinting
|
||||
Database is not a Linux-only stop -- people running other &UNIX;
|
||||
based OSes (like *BSD or &MacOS; X) will also find valuable information
|
||||
and software there.
|
||||
</para>
|
||||
<glossseealso otherterm="gloss-foomatic">Foomatic</glossseealso>
|
||||
<glossseealso otherterm="gloss-linuxprintingdatabase">Linuxprinting database</glossseealso>
|
||||
</glossdef>
|
||||
</glossentry>
|
||||
|
||||
<glossentry id="gloss-directtcpipprinting">
|
||||
<glossterm>Direct TCP/IP Printing</glossterm>
|
||||
<glossdef><para>This is a method that often uses TCP/IP port 9100 to connect
|
||||
to the printer. It works with many modern network printers and has
|
||||
a few advantages over LPR/LPD, as it is faster and provides some
|
||||
"backchannel feedback data" from the printer to the host sending
|
||||
the job.</para>
|
||||
<glossseealso otherterm="gloss-appsocketprotocol">AppSocket Protocol</glossseealso>
|
||||
<glossseealso otherterm="gloss-hpjetdirectprotocol">&HP; JetDirect Protocol</glossseealso>
|
||||
</glossdef>
|
||||
</glossentry>
|
||||
|
||||
|
||||
<glossentry id="gloss-drivers">
|
||||
<glossterm>Drivers, Printer Drivers</glossterm>
|
||||
<glossdef><para>The term "printer drivers", used in the same sense
|
||||
as on the &Microsoft; &Windows; platform, is not entirely applicable
|
||||
to a Linux or &UNIX; platform. A "driver" functionality
|
||||
is supplied on &UNIX; by different modular components working
|
||||
together. At the core of the printer drivers are "filters". Filters convert
|
||||
print files from a given input format to another format that is acceptable
|
||||
to the target printer. In many cases filters may be connected to a whole
|
||||
filter "chain", where only the result of the last conversion is sent to the
|
||||
printer. The actual transfer of the print data to the device is performed by
|
||||
a "backend".
|
||||
</para>
|
||||
<glossseealso otherterm="gloss-filter">Filter</glossseealso>
|
||||
<glossseealso otherterm="gloss-ppd">PPDs</glossseealso>
|
||||
</glossdef>
|
||||
</glossentry>
|
||||
|
||||
<glossentry id="gloss-easysoftwareproducts">
|
||||
<glossterm>Easy Software Products</glossterm>
|
||||
<glossdef><para>Mike Sweet's company, which has contributed a few substantial
|
||||
software products towards the Free Software community; amongst
|
||||
them the initial version of &linkstart;
|
||||
"http://gimp-print.sf.net/"&linkmid;Gimp-Print,&linkend; the &linkstart;
|
||||
"http://www.easysw.com/epm/"&linkmid;EPM software packaging&linkend; tool
|
||||
and &linkstart;"http://www.easysw.com/htmldoc/"&linkmid;HTMLDOC&linkend;
|
||||
(used by the "Linux Documentation Project" to build the PDF versions
|
||||
of the HOWTOs) -- but most importantly: &linkstart;
|
||||
"http://www.cups.org/"&linkmid;&CUPS;&linkend; (the 'Common &UNIX; Printing
|
||||
System').&newpara;
|
||||
ESP financed themselves by selling a commercial version
|
||||
of &CUPS;, called ESP PrintPro,
|
||||
that includes some professional enhancements.
|
||||
ESP Print Pro was purchased by Apple Inc. in February of 2007. ESP Print Pro software and support are no longer available from Easy Software Products. ESP Print Pro users were given non-expiring, floating licenses which may be accessed from the MyESP pages.
|
||||
</para>
|
||||
<glossseealso otherterm="gloss-cups">&CUPS;</glossseealso>
|
||||
<glossseealso otherterm="gloss-esp">ESP</glossseealso>
|
||||
<glossseealso otherterm="gloss-gimpprint">Gimp-Print</glossseealso>
|
||||
</glossdef>
|
||||
</glossentry>
|
||||
|
||||
<glossentry id="gloss-encryption">
|
||||
<glossterm>Encryption</glossterm>
|
||||
<glossdef><para>Encryption of confidential data is an all-important issue if
|
||||
you transfer it over the Internet or even within intranets.&newpara;
|
||||
Printing
|
||||
via traditional protocols is not encrypted at all -- it is very easy
|
||||
to tap and eavesdrop ⪚ into &PostScript; or PCL data transferred
|
||||
over the wire.&newpara;
|
||||
Therefore, in the design of IPP, provision was made for the easy
|
||||
plugin of encryption mechanisms (which can be provided by the same
|
||||
means as the encryption standards for HTTP traffic: SSL and TLS).</para>
|
||||
<glossseealso otherterm="gloss-authentication">Authentication</glossseealso>
|
||||
<glossseealso otherterm="gloss-cups">&CUPS;</glossseealso>
|
||||
<glossseealso otherterm="gloss-ipp">IPP</glossseealso>
|
||||
<glossseealso otherterm="gloss-ssl">SSL</glossseealso>
|
||||
<glossseealso otherterm="gloss-tls">TLS</glossseealso>
|
||||
</glossdef>
|
||||
</glossentry>
|
||||
|
||||
|
||||
<glossentry id="gloss-epson">
|
||||
<glossterm><acronym>Epson</acronym></glossterm>
|
||||
<glossdef><para>Epson inkjets are among the best supported models by Free software
|
||||
drivers, as the company was not necessarily as secretive about their
|
||||
devices and handed technical specification documents to developers.
|
||||
The excellent print quality achieved by Gimp-Print on the Stylus
|
||||
series of printers can be attributed to this openness.
|
||||
</para>
|
||||
</glossdef>
|
||||
</glossentry>
|
||||
|
||||
|
||||
<glossentry id="gloss-escapesequence">
|
||||
<glossterm>Escape Sequences</glossterm>
|
||||
<glossdef><para>The first ever printers printed ASCII data only. To
|
||||
initiate a new line, or eject a page, they included special
|
||||
command sequences, often carrying a leading [ESC]-character.
|
||||
&HP; evolved this concept through its series of PCL language
|
||||
editions until today, having now developed a full-blown
|
||||
Page Description Language (PDL) from these humble beginnings.
|
||||
</para>
|
||||
<glossseealso otherterm="gloss-pcl">PCL</glossseealso>
|
||||
<glossseealso otherterm="gloss-pdl">PDL</glossseealso>
|
||||
</glossdef>
|
||||
</glossentry>
|
||||
|
||||
<glossentry id="gloss-escp">
|
||||
<glossterm><acronym>ESC/P</acronym></glossterm>
|
||||
<glossdef><para>Abbreviation for &emstart;E&emend;pson
|
||||
&emstart;S&emend;tandard &emstart;C&emend;odes for
|
||||
&emstart;P&emend;rinters. Besides &PostScript; and PCL, Epson's ESC/P
|
||||
printer language is one of the best known.</para>
|
||||
<glossseealso otherterm="gloss-pcl">PCL</glossseealso>
|
||||
<glossseealso otherterm="gloss-postscript">&PostScript;</glossseealso>
|
||||
<glossseealso otherterm="gloss-hpgl">hpgl</glossseealso>
|
||||
</glossdef>
|
||||
</glossentry>
|
||||
|
||||
<glossentry id="gloss-esp">
|
||||
<glossterm><acronym>ESP</acronym></glossterm>
|
||||
<glossdef><para>Abbreviation for &emstart;E&emend;asy
|
||||
&emstart;S&emend;oftware &emstart;P&emend;roducts;
|
||||
the company that developed &CUPS; (the "Common &UNIX; Printing System").
|
||||
</para>
|
||||
<glossseealso otherterm="gloss-easysoftwareproducts">Easy Software Products</glossseealso>
|
||||
<glossseealso otherterm="gloss-cups">&CUPS;</glossseealso>
|
||||
</glossdef>
|
||||
</glossentry>
|
||||
|
||||
|
||||
<glossentry id="gloss-filter">
|
||||
<glossterm>Filter</glossterm>
|
||||
<glossdef><para>Filters, in general, are programs that take some input
|
||||
data, work on it and pass it on as their output data. Filters
|
||||
may or may not change the data.&newpara;
|
||||
Filters in the context of printing, are programs that convert
|
||||
a given file (destined for printing, but not suitable in the
|
||||
format it is presently) into a printable format. Sometimes
|
||||
whole "filter chains" have to be constructed to achieve the
|
||||
goal, piping the output of one filter as the input to the next.
|
||||
</para>
|
||||
<glossseealso otherterm="gloss-ghostscript">Ghostscript</glossseealso>
|
||||
<glossseealso otherterm="gloss-rip">RIP</glossseealso>
|
||||
</glossdef>
|
||||
</glossentry>
|
||||
|
||||
<glossentry id="gloss-foomatic">
|
||||
<glossterm>Foomatic</glossterm>
|
||||
<glossdef><para>Foomatic started out as the wrapper name for a set of
|
||||
different tools available from &linkstart;"http://www.linuxfoundation.org/collaborate/workgroups/openprinting/database/foomatic"&linkmid;Linuxprinting.org&linkend;
|
||||
These tools aimed to make the usage of traditional
|
||||
Ghostscript and other print filters easier for users and
|
||||
extend the filters' capabilities by adding more command line
|
||||
switches or explain the driver's execution data.&newpara;
|
||||
More recently, Foomatic gravitated towards becoming a "meta-spooling"
|
||||
system, that allows configuration of the underlying print subsystem
|
||||
through a unified set of commands (however, this is much more
|
||||
complicated than &kde; printing &GUI; interface, which performs a similar
|
||||
task with regards to different print subsystems). </para>
|
||||
</glossdef>
|
||||
</glossentry>
|
||||
|
||||
<glossentry id="gloss-ghostscript">
|
||||
<glossterm>Ghostscript</glossterm>
|
||||
<glossdef><para>Ghostscript is a an interpreter for the &PostScript; language and for PDF or Raster Image Processor (RIP) in software, originally developed by L. Peter Deutsch. There is always a <acronym>GPL</acronym> version
|
||||
of Ghostscript available for free usage and distribution.
|
||||
Ghostscript is widely used inside the Linux and &UNIX; world
|
||||
for transforming &PostScript; into raster data suitable
|
||||
for sending to non-&PostScript; devices.
|
||||
More info:
|
||||
&linkstart;"http://www.ghostscript.com/"&linkmid;Ghostscript Homepage&linkend;</para>
|
||||
<glossseealso otherterm="gloss-postscript">&PostScript;</glossseealso>
|
||||
<glossseealso otherterm="gloss-rip">RIP</glossseealso>
|
||||
</glossdef>
|
||||
</glossentry>
|
||||
|
||||
<glossentry id="gloss-gimpprint">
|
||||
<glossterm>Gimp-Print</glossterm>
|
||||
<glossdef><para>Contrary to its name, Gimp-Print is no longer
|
||||
just the plugin to be used for printing from the popular
|
||||
Gimp program -- its codebase can also serve to be compiled
|
||||
into...&newpara;
|
||||
...a set of PPDs and associated filters that integrate seamlessly
|
||||
into &CUPS;, supporting around 130 different printer models, providing
|
||||
photographic output quality in many cases;&newpara;
|
||||
...a Ghostscript filter that can be used with any other
|
||||
program that needs a software-RIP;&newpara;
|
||||
...a library that can be used by other software applications
|
||||
in need of rasterization functions.</para>
|
||||
<glossseealso otherterm="gloss-lexmark">Lexmark Drivers</glossseealso>
|
||||
<glossseealso otherterm="gloss-rip">RIP</glossseealso>
|
||||
<glossseealso otherterm="gloss-ghostscript">Ghostscript</glossseealso>
|
||||
</glossdef>
|
||||
</glossentry>
|
||||
|
||||
<glossentry id="gloss-hp">
|
||||
<glossterm><acronym>&HP;</acronym></glossterm>
|
||||
<glossdef><para>Abbreviation for &emstart;H&emend;ewlett-&emstart;Packard&emend;;
|
||||
one of the first companies to distribute their own Linux printer
|
||||
drivers. -- More recently, the Company has released their
|
||||
"HPIJS" package of drivers, including source code and a Free license.
|
||||
This is the first printer manufacturer to do so. HPIJS supports most
|
||||
current models of HP Ink- and DeskJets.
|
||||
</para>
|
||||
</glossdef>
|
||||
</glossentry>
|
||||
|
||||
|
||||
<glossentry id="gloss-hpgl">
|
||||
<glossterm><acronym>&HP;/GL</acronym></glossterm>
|
||||
<glossdef><para>Abbreviation for &emstart;&HP;&emend;
|
||||
&emstart;G&emend;raphical &emstart;L&emend;anguage;
|
||||
a &HP; printer language mainly used for plotters; many CAD
|
||||
(Computer Aided Design) software programs output &HP;/GL files for
|
||||
printing.</para>
|
||||
<glossseealso otherterm="gloss-escp">ESC/P</glossseealso>
|
||||
<glossseealso otherterm="gloss-pcl">PCL</glossseealso>
|
||||
<glossseealso otherterm="gloss-postscript">&PostScript;</glossseealso>
|
||||
</glossdef>
|
||||
</glossentry>
|
||||
|
||||
<glossentry id="gloss-hpjetdirectprotocol">
|
||||
<glossterm>&HP; JetDirect Protocol</glossterm>
|
||||
<glossdef><para>A term branded by &HP; to describe their implementation
|
||||
of print data transfer to the printer via an otherwise "AppSocket" or
|
||||
"Direct TCP/IP Printing" named protocol.</para>
|
||||
<glossseealso otherterm="gloss-appsocketprotocol">AppSocket Protocol</glossseealso>
|
||||
<glossseealso otherterm="gloss-directtcpipprinting">Direct TCP/IP Printing</glossseealso>
|
||||
</glossdef>
|
||||
</glossentry>
|
||||
|
||||
<glossentry id="gloss-ietf">
|
||||
<glossterm><acronym>IETF</acronym></glossterm>
|
||||
<glossdef><para>Abbreviation for &emstart;I&emend;nternet
|
||||
&emstart;E&emend;ngineering &emstart;T&emend;ask
|
||||
&emstart;F&emend;orce; an assembly of Internet, software
|
||||
and hardware experts that discuss
|
||||
new networking technologies and very often arrive at
|
||||
conclusions that are regarded by many as standards. "TCP/IP"
|
||||
is the most famous example.&newpara;
|
||||
IETF standards, as well as
|
||||
drafts, discussions, ideas and useful tutorials, are
|
||||
put in writing in the famous series of "RFCs", which
|
||||
are available to the public and included in most Linux and
|
||||
BSD distributions.</para>
|
||||
<glossseealso otherterm="gloss-ipp">IPP</glossseealso>
|
||||
<glossseealso otherterm="gloss-pwg">PWG</glossseealso>
|
||||
<glossseealso otherterm="gloss-rfc">RFC</glossseealso>
|
||||
</glossdef>
|
||||
</glossentry>
|
||||
|
||||
<glossentry id="gloss-ipp">
|
||||
<glossterm><acronym>IPP</acronym></glossterm>
|
||||
<glossdef><para>Abbreviation for &emstart;I&emend;nternet
|
||||
&emstart;P&emend;rinting &emstart;P&emend;rotocol;
|
||||
defined in a series of RFCs accepted by the IETF with
|
||||
status "proposed standard"; was designed
|
||||
by the PWG. -- IPP is a completely new design for network printing,
|
||||
but it utilizes a very well-known and proven method for the
|
||||
actual data transfer: HTTP 1.1! By not "re-inventing the wheel",
|
||||
and basing itself on an existing and robust Internet standard,
|
||||
IPP is able to relatively easily bolt other HTTP-compatible standard
|
||||
mechanisms into its framework:&newpara;
|
||||
|
||||
Basic, Digest or Certificate authentication mechanisms&newpara;
|
||||
SSL or TLS for encryption of transferred data&newpara;
|
||||
LDAP for directory services (to publish
|
||||
data on printers, device-options, drivers, costs or
|
||||
also to the network; or to check for passwords while
|
||||
conducting authentication)
|
||||
</para>
|
||||
|
||||
<glossseealso otherterm="gloss-cups">&CUPS;</glossseealso>
|
||||
<glossseealso otherterm="gloss-pwg">PWG</glossseealso>
|
||||
<glossseealso otherterm="gloss-ietf">IETF</glossseealso>
|
||||
<glossseealso otherterm="gloss-rfc">RFC</glossseealso>
|
||||
<glossseealso otherterm="gloss-tls">TLS</glossseealso>
|
||||
</glossdef>
|
||||
</glossentry>
|
||||
|
||||
|
||||
<glossentry id="gloss-lexmark">
|
||||
<glossterm><acronym>Lexmark</acronym></glossterm>
|
||||
<glossdef><para>was one of the first companies to distribute their own Linux printer
|
||||
drivers for some of their models. However, those drivers are binary only
|
||||
(no source code available), and therefore cannot be used to integrate into
|
||||
other Free printing software projects.
|
||||
</para>
|
||||
</glossdef>
|
||||
</glossentry>
|
||||
|
||||
<glossentry id="gloss-linuxprintingorg">
|
||||
<glossterm>Linuxprinting.org</glossterm>
|
||||
<glossdef><para>Linuxprinting.org = not just for Linux; all &UNIX;-like OS-es,
|
||||
like *BSD and commercial Unices may find useful printing
|
||||
information on this site. This web site is the home for the interesting
|
||||
Foomatic project, that strives to develop the "Meta Print Spool and Driver
|
||||
Configuration Toolset" (being able to configure, through one common
|
||||
interface, different print subsystems and their required drivers) with the
|
||||
ability to transfer all queues, printers and configuration files seamlessly
|
||||
to another spooler without new configuration effort. -- Also, they maintain
|
||||
the Printing Database; a collection of driver and device information that
|
||||
enables everybody to find the most current information about printer models,
|
||||
and also generate online the configuration files for any
|
||||
spooler/driver/device combo known to work with one of the common Linux or
|
||||
&UNIX; print subsystems.
|
||||
</para>
|
||||
<glossseealso otherterm="gloss-linuxprintingdatabase">Linuxprinting database</glossseealso>
|
||||
</glossdef>
|
||||
</glossentry>
|
||||
|
||||
|
||||
<glossentry id="gloss-linuxprintingdatabase">
|
||||
<glossterm><acronym>Linuxprinting.org Database</acronym></glossterm>
|
||||
<glossdef><para>&linkstart;"http://www.openprinting.org/printers"&linkmid;Database&linkend; containing printers and drivers that are suitable for them.
|
||||
More info:
|
||||
&linkstart;"http://www.linuxfoundation.org/collaborate/workgroups/openprinting/database/indexfaq"&linkmid;Linuxprinting.org FAQ&linkend;</para>
|
||||
<glossseealso otherterm="gloss-foomatic">Foomatic</glossseealso>
|
||||
</glossdef>
|
||||
</glossentry>
|
||||
|
||||
<glossentry id="gloss-lprlpd">
|
||||
<glossterm><acronym>LPR/LPD</acronym> printing</glossterm>
|
||||
<glossdef><para>LPR == some people translate &emstart;L&emend;ine
|
||||
&emstart;P&emend;rinting &emstart;R&emend;equest, others:
|
||||
&emstart;L&emend;ine &emstart;P&emend;rinter
|
||||
&emstart;R&emend;emote.</para>
|
||||
<glossseealso otherterm="gloss-bsdstyleprinting">BSD-style printing</glossseealso>
|
||||
</glossdef>
|
||||
</glossentry>
|
||||
|
||||
<glossentry id="gloss-magicfilter">
|
||||
<glossterm>Magicfilter</glossterm>
|
||||
<glossdef><para>Similarly to the APSfilter program, Magicfilter
|
||||
provides automatic file type recognition functions and, base
|
||||
on that, automatic file conversion to a printable format,
|
||||
depending on the target printer.</para>
|
||||
<glossseealso otherterm="gloss-apsfilter">APSfilter</glossseealso>
|
||||
</glossdef>
|
||||
</glossentry>
|
||||
|
||||
<glossentry id="gloss-mimetypes">
|
||||
<glossterm>&MIME;-Types</glossterm>
|
||||
<glossdef><para>Abbreviation for &emstart;M&emend;ultipurpose (or
|
||||
Multimedia) &emstart;I&emend;nternet &emstart;M&emend;ail
|
||||
&emstart;E&emend;xtensions; &MIME;-Types were first used to allow
|
||||
the transport of binary data (like mail attachments containing
|
||||
graphics) over mail connections that were normally only transmitting
|
||||
ASCII characters: the data had to be encoded into an ASCII representation.&newpara;
|
||||
Later this concept was extended to describe a data format in
|
||||
a platform independent, but at the same time non-ambiguous, way.
|
||||
From &Windows; everybody knows the .doc extensions for &Microsoft; Word files.
|
||||
This is handled ambiguously on the &Windows; platform: .doc extensions are also
|
||||
used for simple text files or for Adobe Framemaker files. And if a real
|
||||
Word file is renamed with a different extension, it can no longer be
|
||||
opened by the program.&newpara;
|
||||
&MIME; typed files carry a recognition string with them, describing
|
||||
their file format based on &emstart;main_category/sub_category&emend;.
|
||||
Inside IPP, print files are also described using the &MIME; type scheme.
|
||||
&MIME; types are registered with the IANA (Internet Assigning Numbers
|
||||
&emstart;Association&emend;) to keep them unambiguous.&newpara;
|
||||
&CUPS; has some &MIME; types of its own registered, like
|
||||
&emstart;application/vnd.cups-raster&emend; (for the &CUPS;-internal
|
||||
raster image format).
|
||||
</para>
|
||||
<glossseealso otherterm="gloss-cups">&CUPS;</glossseealso>
|
||||
<glossseealso otherterm="gloss-easysoftwareproducts">Easy Software Products</glossseealso>
|
||||
<glossseealso otherterm="gloss-gimpprint">Gimp-Print</glossseealso>
|
||||
</glossdef>
|
||||
</glossentry>
|
||||
|
||||
<glossentry id="gloss-pcl">
|
||||
<glossterm><acronym>PCL</acronym></glossterm>
|
||||
<glossdef><para>Abbreviation for &emstart;P&emend;rinter
|
||||
&emstart;C&emend;ontrol &emstart;L&emend;anguage;
|
||||
developed by &HP;. PCL started off in version 1 as a simple
|
||||
command set for ASCII printing; now,
|
||||
in its versions PCL6 and PCL-X, it is capable of printing graphics
|
||||
and color -- but outside the &Microsoft; &Windows; realm and &HP-UX;
|
||||
(&HP;'s own brand of &UNIX;), it is not commonly used...</para>
|
||||
<glossseealso otherterm="gloss-escp">ESC/P</glossseealso>
|
||||
<glossseealso otherterm="gloss-hpgl">&HP;/GL</glossseealso>
|
||||
<glossseealso otherterm="gloss-pdl">PDL</glossseealso>
|
||||
<glossseealso otherterm="gloss-postscript">&PostScript;</glossseealso>
|
||||
</glossdef>
|
||||
</glossentry>
|
||||
|
||||
<glossentry id="gloss-pdl">
|
||||
<glossterm><acronym>PDL</acronym></glossterm>
|
||||
<glossdef><para>Abbreviation for &emstart;P&emend;age
|
||||
&emstart;D&emend;escription &emstart;L&emend;anguage;
|
||||
PDLs describe, in an abstract way, the graphical representation
|
||||
of a page. - Before it is actually transferred into
|
||||
toner or ink laid down on to paper, a PDL needs to be
|
||||
"interpreted" first. In &UNIX;, the most important PDL
|
||||
is &PostScript;.
|
||||
</para>
|
||||
<glossseealso otherterm="gloss-escp">ESC/P</glossseealso>
|
||||
<glossseealso otherterm="gloss-hpgl">&HP;/GL</glossseealso>
|
||||
<glossseealso otherterm="gloss-pcl">PCL</glossseealso>
|
||||
<glossseealso otherterm="gloss-postscript">&PostScript;</glossseealso>
|
||||
</glossdef>
|
||||
</glossentry>
|
||||
|
||||
<glossentry id="gloss-pixel">
|
||||
<glossterm>Pixel</glossterm>
|
||||
<glossdef><para>Abbreviation for &emstart;Pic&emend;ture
|
||||
&emstart;El&emend;ement; this term describes the smallest
|
||||
part of a raster picture (either as printed on paper
|
||||
or as displayed on a monitor by cathode rays or LCD elements). As
|
||||
any graphical or image representation on those types of output
|
||||
devices is composed of pixels, the values of "ppi" (pixel per inch)
|
||||
and &dpi; (dots per inch) are one important parameter for the
|
||||
overall quality and resolution of an image.</para>
|
||||
<glossseealso otherterm="gloss-filter">Filter</glossseealso>
|
||||
<glossseealso otherterm="gloss-ghostscript">Ghostscript</glossseealso>
|
||||
<glossseealso otherterm="gloss-postscript">&PostScript;</glossseealso>
|
||||
<glossseealso otherterm="gloss-raster">Raster</glossseealso>
|
||||
</glossdef>
|
||||
</glossentry>
|
||||
|
||||
<glossentry id="gloss-pjl">
|
||||
<glossterm><acronym>PJL</acronym></glossterm>
|
||||
<glossdef><para>Abbreviation for &emstart;P&emend;rint
|
||||
&emstart;J&emend;ob &emstart;L&emend;anguage;
|
||||
developed by &HP; to control and influence default and per-job
|
||||
settings of a printer. It may not only be used
|
||||
for &HP;'s own (PCL-)printers; also many &PostScript;
|
||||
and other printers understand PJL commands sent to them
|
||||
inside a print job, or in a separate signal.</para>
|
||||
<glossseealso otherterm="gloss-pcl">PCL</glossseealso>
|
||||
</glossdef>
|
||||
</glossentry>
|
||||
|
||||
<glossentry id="gloss-postscript">
|
||||
<glossterm>&PostScript;</glossterm>
|
||||
<glossdef><para>&PostScript; (often shortened to "PS") is the de-facto
|
||||
standard in the &UNIX; world for printing files. It was
|
||||
developed by Adobe and licensed to printer manufacturers
|
||||
and software companies.&newpara;
|
||||
As the &PostScript; specifications were
|
||||
published by Adobe, there are also "Third Party" implementations
|
||||
of &PostScript; generating and &PostScript; interpreting software
|
||||
available (one of the best-known in the Free software world
|
||||
being Ghostscript, a powerful PS-interpreter).
|
||||
</para>
|
||||
<glossseealso otherterm="gloss-escp">ESC/P</glossseealso>
|
||||
<glossseealso otherterm="gloss-hpgl">&HP;/GL</glossseealso>
|
||||
<glossseealso otherterm="gloss-pcl">PCL</glossseealso>
|
||||
<glossseealso otherterm="gloss-ppd">PPD</glossseealso>
|
||||
</glossdef>
|
||||
</glossentry>
|
||||
|
||||
<glossentry id="gloss-ppd">
|
||||
<glossterm><acronym>PPD</acronym></glossterm>
|
||||
<glossdef><para>Abbreviation for &emstart;P&emend;ostScript
|
||||
&emstart;P&emend;rinter &emstart;D&emend;escription;
|
||||
PPDs are ASCII files storing all information about the special
|
||||
capabilities of a printer, plus definitions of the (PostScript-
|
||||
or PJL-) commands to call on a certain capability (like print
|
||||
duplexing).&newpara;
|
||||
As the explanation of the acronym reveals, PPDs were originally
|
||||
only used for &PostScript; printers. &CUPS; has extended the
|
||||
PPD concept to all types of printers.&newpara;
|
||||
PPDs for &PostScript; printers are provided by the printer
|
||||
vendors. They can be used with &CUPS; and &kde; printing subsystem to have access
|
||||
to the full features of any &PostScript; printer. The &kde; Team
|
||||
recommends using a PPD originally intended for use with
|
||||
&Microsoft; Windows NT.&newpara;
|
||||
PPDs for non-PostScript printers &emstart;need&emend; a
|
||||
companion "filter" to process the &PostScript; print files into
|
||||
a format digestible for the non-PostScript target device. Those
|
||||
PPD/filter combos are not (yet) available from the vendors. After
|
||||
the initiative by the &CUPS; developers to utilize PPDs, the Free
|
||||
Software community was creative enough to quickly come up with
|
||||
support for most of the currently used printer models, through
|
||||
PPDs and classical Ghostscript filters. But note: the printout
|
||||
quality varies from "hi-quality photographic output" (using
|
||||
Gimp-Print with most Epson inkjets) to "hardly readable" (using
|
||||
Foomatic-enabled Ghostscript filters for models rated as
|
||||
"paperweight" in the Linuxprinting.org database).
|
||||
</para>
|
||||
<glossseealso otherterm="gloss-cups">&CUPS;</glossseealso>
|
||||
<glossseealso otherterm="gloss-linuxprintingorg">Linuxprinting.org</glossseealso>
|
||||
<glossseealso otherterm="gloss-postscript">&PostScript;</glossseealso>
|
||||
</glossdef>
|
||||
</glossentry>
|
||||
|
||||
<glossentry id="gloss-printcap">
|
||||
<glossterm>printcap</glossterm>
|
||||
<glossdef><para>In BSD-style print systems, the "printcap" file holds
|
||||
the configuration information; the printing daemon reads this file
|
||||
to determine which printers are available, what filters are to be
|
||||
user for each, where the spooling folder is located,
|
||||
if there are banner pages to be used, and so on...
|
||||
Some applications also depend on read access to the printcap
|
||||
file, to obtain the names of available printers. </para>
|
||||
<glossseealso otherterm="gloss-bsdstyleprinting">BSD-style printing</glossseealso>
|
||||
</glossdef>
|
||||
</glossentry>
|
||||
|
||||
|
||||
<glossentry id="gloss-printermib">
|
||||
<glossterm>Printer-<acronym>MIB</acronym></glossterm>
|
||||
<glossdef><para>Abbreviation for
|
||||
&emstart;Printer&emend;-&emstart;M&emend;anagement
|
||||
&emstart;I&emend;nformation &emstart;B&emend;ase; the
|
||||
Printer-MIB defines a set of parameters that are to be
|
||||
stored inside the printer for access
|
||||
through the network. This is useful if many (in some cases, literally
|
||||
thousands) network printers are managed centrally
|
||||
with the help of SNMP (Simple Network Management Protocol).</para>
|
||||
<glossseealso otherterm="gloss-pwg">PWG</glossseealso>
|
||||
<glossseealso otherterm="gloss-snmp">SNMP</glossseealso>
|
||||
</glossdef>
|
||||
</glossentry>
|
||||
|
||||
<glossentry id="gloss-pwg">
|
||||
<glossterm><acronym>PWG</acronym></glossterm>
|
||||
<glossdef><para>Abbreviation for
|
||||
&emstart;P&emend;rinter &emstart;W&emend;orking
|
||||
&emstart;G&emend;roup; the PWG is a loose grouping of
|
||||
representatives of the printer industry that has, in the past
|
||||
years, developed different standards
|
||||
in relation to network printing. These were later accepted by the
|
||||
IETF as RFC standards, like the "Printer-MIB" and the IPP.</para>
|
||||
<glossseealso otherterm="gloss-postscript">&PostScript;</glossseealso>
|
||||
<glossseealso otherterm="gloss-ipp">IPP</glossseealso>
|
||||
<glossseealso otherterm="gloss-printermib">Printer-MIB</glossseealso>
|
||||
<glossseealso otherterm="gloss-snmp">SNMP</glossseealso>
|
||||
</glossdef>
|
||||
</glossentry>
|
||||
|
||||
<!--
|
||||
<glossentry id="gloss-printkioslave">
|
||||
<glossterm>print:/ KIO Slave</glossterm>
|
||||
<glossdef><para>You can use a syntax of "print:/..." to get quick access
|
||||
to &kde; printing subsystem resources. Typing "print:/manager" as a Konqueror URL
|
||||
address gives administrative access to KDEPrint. Konqueror uses &kde;'s
|
||||
famous "KParts" technology to achieve that. </para>
|
||||
<glossseealso otherterm="gloss-ioslave">IO Slave</glossseealso>
|
||||
<glossseealso otherterm="gloss-kparts">KParts</glossseealso>
|
||||
</glossdef>
|
||||
</glossentry>
|
||||
-->
|
||||
|
||||
<glossentry id="gloss-printerdatabase">
|
||||
<glossterm>Printer Database</glossterm>
|
||||
<glossdef><para>Good database of printer drivers can be found at &linkstart;"http://www.openprinting.org/printers"&linkmid;http://www.openprinting.org/printers&linkend;.</para>
|
||||
<glossseealso otherterm="gloss-linuxprintingdatabase">Linuxprinting Database</glossseealso>
|
||||
</glossdef>
|
||||
</glossentry>
|
||||
|
||||
<glossentry id="gloss-raster">
|
||||
<glossterm>Raster Image</glossterm>
|
||||
<glossdef><para>Every picture on a physical medium
|
||||
is composed of a pattern of discrete dots in different colors and (maybe)
|
||||
sizes. This is called a "raster image".&newpara;
|
||||
This is as opposed to a "vector image"
|
||||
where the graphic is described in terms of continuous curves, shades,
|
||||
forms and filled areas, represented by mathematical formula. Vector images
|
||||
normally have a smaller file size and may be scaled in size
|
||||
without any loss of information and quality --- but they cannot be
|
||||
output directly, but always have to be "rendered" or "rasterized"
|
||||
first to the given resolution that the output device is capable of...&newpara;
|
||||
The rasterization is done by a Raster Image Processor (RIP,
|
||||
often the Ghostscript software) or some other filtering
|
||||
instance.</para>
|
||||
<glossseealso otherterm="gloss-pixel">Pixel</glossseealso>
|
||||
<glossseealso otherterm="gloss-ghostscript">Ghostscript</glossseealso>
|
||||
<glossseealso otherterm="gloss-postscript">&PostScript;</glossseealso>
|
||||
<glossseealso otherterm="gloss-filter">Filter</glossseealso>
|
||||
<glossseealso otherterm="gloss-rip">RIP</glossseealso>
|
||||
</glossdef>
|
||||
</glossentry>
|
||||
|
||||
<glossentry id="gloss-rip">
|
||||
<glossterm><acronym>RIP</acronym></glossterm>
|
||||
<glossdef><para>Abbreviation for
|
||||
&emstart;R&emend;aster &emstart;I&emend;mage
|
||||
&emstart;P&emend;rocess(or); if used in the context of
|
||||
printing, "RIP" means a hardware or software
|
||||
instance that converts &PostScript; (or other print formats
|
||||
that are represented in one of the non-Raster PDLs) into a
|
||||
raster image format in such a way that it is acceptable
|
||||
for the "marking engine" of the printer.&newpara;
|
||||
&PostScript; printers
|
||||
contain their own PostScript-RIPs. A RIP may or may not be located
|
||||
inside a printer.&newpara;
|
||||
For many &UNIX; systems, Ghostscript is the package that provides
|
||||
a "RIP in software", running on the host computer, and pre-digesting
|
||||
the &PostScript; or other data to become ready to be sent to the
|
||||
printing device (hence you may perceive a "grain of truth" in the
|
||||
slogan "Ghostscript turns your printer into a &PostScript;
|
||||
machine", which of course is not correct in the true sense of the
|
||||
meaning).</para>
|
||||
<glossseealso otherterm="gloss-filter">Filter</glossseealso>
|
||||
<glossseealso otherterm="gloss-ghostscript">Ghostscript</glossseealso>
|
||||
<glossseealso otherterm="gloss-postscript">&PostScript;</glossseealso>
|
||||
<glossseealso otherterm="gloss-pdl">PDL</glossseealso>
|
||||
<glossseealso otherterm="gloss-raster">Raster</glossseealso>
|
||||
</glossdef>
|
||||
</glossentry>
|
||||
|
||||
|
||||
<glossentry id="gloss-rlpr">
|
||||
<glossterm><acronym>RLPR</acronym> (Remote LPR)</glossterm>
|
||||
<glossdef><para>Abbreviation for &emstart;R&emend;emote
|
||||
&emstart;L&emend;ine &emstart;P&emend;rinting
|
||||
&emstart;R&emend;equest; this is a BSD-style printing system,
|
||||
that needs no root privileges to be installed, and no "printcap" to
|
||||
work: all parameters may be specified on the command
|
||||
line.&newpara;
|
||||
RLPR comes in handy for many laptop users who are
|
||||
working in frequently changing environments. This is because it
|
||||
may be installed concurrently with every other printing
|
||||
sub system, and allows a very flexible and quick
|
||||
way to install a printer for direct access via LPR/LPD.
|
||||
</para>
|
||||
<glossseealso otherterm="gloss-printcap">printcap</glossseealso>
|
||||
</glossdef>
|
||||
</glossentry>
|
||||
|
||||
|
||||
<glossentry id="gloss-snmp">
|
||||
<glossterm><acronym>SNMP</acronym></glossterm>
|
||||
<glossdef><para>Abbreviation for &emstart;S&emend;imple
|
||||
&emstart;N&emend;etwork &emstart;M&emend;anagement
|
||||
&emstart;P&emend;rotocol; SNMP is widely used to control
|
||||
all types of network node (Hosts, Routers, Switches, Gateways,
|
||||
Printers...) remotely.</para>
|
||||
<glossseealso otherterm="gloss-pwg">PWG</glossseealso>
|
||||
<glossseealso otherterm="gloss-printermib">Printer-MIB</glossseealso>
|
||||
</glossdef>
|
||||
</glossentry>
|
||||
|
||||
<glossentry id="gloss-ssl">
|
||||
<glossterm><acronym>SSL(3)</acronym> encryption</glossterm>
|
||||
<glossdef><para>Abbreviation for &emstart;S&emend;ecure
|
||||
&emstart;S&emend;ocket &emstart;L&emend;ayer;
|
||||
<acronym>SSL</acronym> is a proprietary encryption method for data
|
||||
transfer over HTTP that was developed by Netscape. It is now being
|
||||
replaced by an IETF standard named TLS.
|
||||
</para>
|
||||
<glossseealso otherterm="gloss-tls"><acronym>TLS</acronym></glossseealso>
|
||||
</glossdef>
|
||||
</glossentry>
|
||||
|
||||
|
||||
<glossentry id="gloss-spooling">
|
||||
<glossterm><acronym>SPOOL</acronym>ing</glossterm>
|
||||
<glossdef><para>Abbreviation for &emstart;S&emend;ynchronous
|
||||
&emstart;P&emend;eripheral &emstart;O&emend;perations
|
||||
&emstart;O&emend;n&emstart;L&emend;ine;
|
||||
<acronym>SPOOL</acronym>ing enables printing applications
|
||||
(and users) to continue their work
|
||||
as the job is being taken care of by a system <acronym>daemon</acronym>,
|
||||
which stores the file at a temporary location until the printer is ready
|
||||
to print. </para>
|
||||
<glossseealso otherterm="gloss-daemon"><acronym>Daemon</acronym></glossseealso>
|
||||
</glossdef>
|
||||
</glossentry>
|
||||
|
||||
|
||||
<glossentry id="gloss-tls">
|
||||
<glossterm><acronym>TLS</acronym> encryption</glossterm>
|
||||
<glossdef><para>Abbreviation for &emstart;T&emend;ransport
|
||||
&emstart;L&emend;ayer &emstart;S&emend;ecurity;
|
||||
<acronym>TLS</acronym> is an encryption standard for
|
||||
data transferred over HTTP 1.1; it is defined in RFC 2246;
|
||||
although based on the former SSL development
|
||||
(from Netscape) it is not fully compatible with it.
|
||||
</para>
|
||||
<glossseealso otherterm="gloss-ssl"><acronym>SSL(3)</acronym></glossseealso>
|
||||
</glossdef>
|
||||
</glossentry>
|
||||
|
||||
|
||||
<glossentry id="gloss-systemVstyleprinting">
|
||||
<glossterm>System V-style printing</glossterm>
|
||||
<glossdef><para>This is the second flavor of traditional &UNIX;
|
||||
printing (as opposed to BSD-style printing). It uses
|
||||
a different command set (lp, lpadmin,...) to BSD,
|
||||
but is not fundamentally different from it. However, the
|
||||
gap between the two is big enough to make the two
|
||||
incompatible, so that a BSD-client cannot simply print
|
||||
to a System V style print server without additional
|
||||
tweaking... IPP is supposed to resolve this weakness
|
||||
and more.
|
||||
</para>
|
||||
<glossseealso otherterm="gloss-bsdstyleprinting"><acronym>BSD-style printing</acronym></glossseealso>
|
||||
<glossseealso otherterm="gloss-ipp"><acronym>IPP</acronym></glossseealso>
|
||||
</glossdef>
|
||||
</glossentry>
|
||||
|
||||
<glossentry id="gloss-turboprint">
|
||||
<glossterm>TurboPrint</glossterm>
|
||||
<glossdef><para>Shareware software providing photo quality printing for many
|
||||
inkjet printers. It is useful if you are unable to find a driver for your
|
||||
printer and may be hooked into either a traditional Ghostscript system
|
||||
or a modern &CUPS; system.</para>
|
||||
<glossseealso otherterm="gloss-gimpprint">Gimp-Print</glossseealso>
|
||||
</glossdef>
|
||||
</glossentry>
|
||||
|
||||
<glossentry id="gloss-xpp">
|
||||
<glossterm><acronym>XPP</acronym></glossterm>
|
||||
<glossdef><para>Abbreviation for &emstart;X&emend;
|
||||
&emstart;P&emend;rinting &emstart;P&emend;anel;
|
||||
<acronym>XPP</acronym> was the first Free
|
||||
graphical print command for &CUPS;, written by Till Kamppeter,
|
||||
and in some ways a model for the "kprinter" utility in &kde; 3.</para>
|
||||
</glossdef>
|
||||
</glossentry>
|
||||
<!--
|
||||
<glossentry id="gloss-1">
|
||||
<glossterm>xxxx</glossterm>
|
||||
<glossdef><para>.</para>
|
||||
<glossseealso otherterm="gloss-1">xyz</glossseealso>
|
||||
</glossdef>
|
||||
</glossentry>
|
||||
|
||||
<glossentry id="gloss-3">
|
||||
<glossterm>xxxx</glossterm>
|
||||
<glossdef><para>.</para>
|
||||
<glossseealso otherterm="gloss-1">xyz</glossseealso>
|
||||
</glossdef>
|
||||
</glossentry>
|
||||
|
||||
<glossentry id="gloss-4">
|
||||
<glossterm>xxxx</glossterm>
|
||||
<glossdef><para>.</para>
|
||||
<glossseealso otherterm="gloss-1">xyz</glossseealso>
|
||||
</glossdef>
|
||||
</glossentry>
|
||||
-->
|
||||
</glossdiv>
|
||||
|
||||
|
||||
<!--
|
||||
</glossary>
|
||||
-->
|
||||
|
|
@ -1,65 +0,0 @@
|
|||
add_subdirectory(clock)
|
||||
add_subdirectory(colors)
|
||||
add_subdirectory(desktopthemedetails)
|
||||
add_subdirectory(joystick)
|
||||
add_subdirectory(kcmaccess)
|
||||
add_subdirectory(kcmstyle)
|
||||
add_subdirectory(solid-actions)
|
||||
add_subdirectory(splashscreen)
|
||||
add_subdirectory(powerdevil)
|
||||
add_subdirectory(kwincompositing)
|
||||
add_subdirectory(kwinscreenedges)
|
||||
add_subdirectory(bookmarks)
|
||||
add_subdirectory(icons)
|
||||
add_subdirectory(cookies)
|
||||
add_subdirectory(ebrowsing)
|
||||
add_subdirectory(useragent)
|
||||
add_subdirectory(khtml-general)
|
||||
add_subdirectory(khtml-plugins)
|
||||
add_subdirectory(khtml-java-js)
|
||||
add_subdirectory(khtml-behavior)
|
||||
add_subdirectory(khtml-adblock)
|
||||
add_subdirectory(nepomuk)
|
||||
add_subdirectory(attica)
|
||||
add_subdirectory(kcm_ssl)
|
||||
add_subdirectory(smb)
|
||||
add_subdirectory(emoticons)
|
||||
|
||||
if ( Q_WS_X11 )
|
||||
add_subdirectory(autostart)
|
||||
add_subdirectory(bell)
|
||||
add_subdirectory(cursortheme)
|
||||
add_subdirectory(fonts)
|
||||
add_subdirectory(fontinst)
|
||||
add_subdirectory(keys)
|
||||
add_subdirectory(keyboard)
|
||||
add_subdirectory(kwindecoration)
|
||||
add_subdirectory(desktop)
|
||||
add_subdirectory(mouse)
|
||||
add_subdirectory(paths)
|
||||
add_subdirectory(screensaver)
|
||||
add_subdirectory(windowspecific)
|
||||
add_subdirectory(windowbehaviour)
|
||||
add_subdirectory(kwintabbox)
|
||||
add_subdirectory(kcmsmserver)
|
||||
add_subdirectory(workspaceoptions)
|
||||
add_subdirectory(khotkeys)
|
||||
add_subdirectory(cache)
|
||||
add_subdirectory(filemanager)
|
||||
add_subdirectory(filetypes)
|
||||
add_subdirectory(kcmcgi)
|
||||
add_subdirectory(kcmcss)
|
||||
add_subdirectory(kcmlaunch)
|
||||
add_subdirectory(kcmnotify)
|
||||
add_subdirectory(language)
|
||||
add_subdirectory(netpref)
|
||||
add_subdirectory(performance)
|
||||
add_subdirectory(proxy)
|
||||
add_subdirectory(spellchecking)
|
||||
add_subdirectory(componentchooser)
|
||||
add_subdirectory(kded)
|
||||
add_subdirectory(trash)
|
||||
add_subdirectory(history)
|
||||
add_subdirectory(solid-device-automounter)
|
||||
add_subdirectory(phonon)
|
||||
endif ( Q_WS_X11 )
|
||||
|
|
@ -1,2 +0,0 @@
|
|||
########### install files ###############
|
||||
kde4_create_handbook(index.docbook INSTALL_DESTINATION ${HTML_INSTALL_DIR}/en SUBDIR kcontrol/attica)
|
||||
|
|
@ -1,61 +0,0 @@
|
|||
<?xml version="1.0" ?>
|
||||
<!DOCTYPE article PUBLIC "-//KDE//DTD DocBook XML V4.2-Based Variant V1.1//EN"
|
||||
"dtd/kdex.dtd" [
|
||||
<!ENTITY % addindex "IGNORE">
|
||||
<!ENTITY % English "INCLUDE" > <!-- change language only here -->
|
||||
]>
|
||||
|
||||
<article id="attica" lang="&language;">
|
||||
<articleinfo>
|
||||
|
||||
<title>Social Desktop</title>
|
||||
<authorgroup>
|
||||
<author><personname><firstname>Frederik</firstname><surname>Gladhorn</surname></personname>
|
||||
<email>gladhorn@kde.org</email>
|
||||
</author>
|
||||
|
||||
<!-- TRANS:ROLES_OF_TRANSLATORS -->
|
||||
</authorgroup>
|
||||
|
||||
<date>2013-11-05</date>
|
||||
<releaseinfo>&kde; 4.12</releaseinfo>
|
||||
|
||||
<keywordset>
|
||||
<keyword>KDE</keyword>
|
||||
<keyword>Systemsettings</keyword>
|
||||
<keyword>Social Desktop</keyword>
|
||||
</keywordset>
|
||||
</articleinfo>
|
||||
|
||||
<para>The Social Desktop (Open Collaboration Services) settings module lets you
|
||||
configure your user accounts for Open Collaboration Service Providers.</para>
|
||||
|
||||
<para>At the time of writing <ulink url="http://opendesktop.org/">openDesktop.org
|
||||
</ulink> is the first provider that you can use.
|
||||
You can use the web site or this settings dialog to register and manage your account.
|
||||
</para>
|
||||
|
||||
<para>The benefit is that you can do more things in <quote>Get Hot New Stuff</quote>:
|
||||
vote for items, become a fan of them and upload new content. A configured
|
||||
account also allows you to use the social Plasma widgets (<quote>Community</quote>,
|
||||
<quote>Social News</quote> &etc;) to their full extent.
|
||||
</para>
|
||||
|
||||
<para>Using the &systemsettings; module:</para>
|
||||
|
||||
<para>You can select which provider to configure at the top.
|
||||
Either enter your existing user name and password to let &kde; use them.
|
||||
You can verify that these work by using the <guibutton>Test Login</guibutton> button</para>
|
||||
|
||||
<!--
|
||||
missing:
|
||||
Enable
|
||||
Add/Remove Providers-->
|
||||
|
||||
<para>If you do not have an account yet, use the <guilabel>Register</guilabel> tab.
|
||||
Here you need to fill out all fields.
|
||||
After clicking <guibutton>Register...</guibutton> you will receive an email from the
|
||||
server to activate your account.
|
||||
</para>
|
||||
|
||||
</article>
|
||||
|
|
@ -1,3 +0,0 @@
|
|||
########### install files ###############
|
||||
#
|
||||
kde4_create_handbook(index.docbook INSTALL_DESTINATION ${HTML_INSTALL_DIR}/en SUBDIR kcontrol/autostart)
|
||||
|
|
@ -1,183 +0,0 @@
|
|||
<?xml version="1.0" ?>
|
||||
<!DOCTYPE article PUBLIC "-//KDE//DTD DocBook XML V4.2-Based Variant V1.1//EN"
|
||||
"dtd/kdex.dtd" [
|
||||
<!ENTITY % addindex "IGNORE">
|
||||
<!ENTITY % English "INCLUDE">
|
||||
]>
|
||||
<article id="autostart" lang="&language;">
|
||||
<articleinfo>
|
||||
<title>Autostart</title>
|
||||
<authorgroup>
|
||||
<author>&Anne-Marie.Mahfouf;</author>
|
||||
<!-- TRANS:ROLES_OF_TRANSLATORS -->
|
||||
</authorgroup>
|
||||
|
||||
<date>2013-12-05</date>
|
||||
<releaseinfo>&kde; 4.12</releaseinfo>
|
||||
|
||||
<keywordset>
|
||||
<keyword>KDE</keyword>
|
||||
<keyword>System Settings</keyword>
|
||||
<keyword>autostart</keyword>
|
||||
<keyword>desktop file</keyword>
|
||||
<keyword>script file</keyword>
|
||||
</keywordset>
|
||||
</articleinfo>
|
||||
|
||||
<sect1 id="kcm_autostart">
|
||||
<title>Autostart Manager</title>
|
||||
|
||||
<para>This module is a configuration tool for managing what programs start up with your personal &kde;. It allows you to add programs or scripts so they automatically start during the startup of your &kde; session and to manage them. </para>
|
||||
|
||||
<note><para>Please note that in this module all changes are immediately applied.</para></note>
|
||||
|
||||
<para>The program scans <filename>~/.config/autostart/</filename>, your <filename class="directory">KDE Autostart</filename> folder (<filename class="directory">$KDEHOME/Autostart</filename> as default), <filename class="directory">$KDEHOME/env</filename> and <filename class="directory">$KDEHOME/shutdown</filename> folders to check what programs and scripts are already there and displays them. It allows you to manage them easily.
|
||||
</para>
|
||||
<!--Found this on forum.kde.org:
|
||||
The following folders are all checked for .desktop files:
|
||||
~/[.kde4|.kde]/Autostart
|
||||
~/[.kde4|.kde]/share/autostart
|
||||
~/.config/autostart
|
||||
~/.local/share/autostart
|
||||
~/Desktop/autostart
|
||||
/etc/xdg/autostart
|
||||
/usr/share/autostart
|
||||
see also http://www.sharpley.org.uk/node/8
|
||||
-->
|
||||
<note><para>Note that you can change the location of your <filename class="directory">Autostart</filename>
|
||||
folder in <menuchoice><guimenu>Account Details</guimenu> <guimenuitem>Paths</guimenuitem></menuchoice>
|
||||
in the <guilabel>Common Appearance and Behaviour</guilabel> category of the &systemsettings; and set a different folder
|
||||
than <filename class="directory">$KDEHOME/Autostart</filename>.</para></note>
|
||||
<!-- add info about system autostart desktop files, which are not handled here?
|
||||
eg /usr/share/autostart/kalarm.autostart.desktop installed with kalarm on my 11.04 system
|
||||
kalarm has a settings option "Start at login" which handles the autostart
|
||||
how to prevent eg kopete from autostart at login?
|
||||
-->
|
||||
<sect2 id="current">
|
||||
<title>Files display</title>
|
||||
<para>The main part of the module displays the programs that are loaded when &kde; starts and scripts that are run when &kde; starts, shutdowns or before &kde; starts.</para>
|
||||
|
||||
<variablelist>
|
||||
<varlistentry><term><guilabel>Name</guilabel></term>
|
||||
<listitem>
|
||||
<para>
|
||||
You cannot amend this column. It states the name of the program or script you want to start with &kde;. The name is extracted from the Desktop file from the Name key for a program and is the filename for a script.
|
||||
</para>
|
||||
</listitem>
|
||||
</varlistentry>
|
||||
|
||||
<varlistentry><term><guilabel>Command</guilabel></term>
|
||||
<listitem>
|
||||
<para>
|
||||
This column lists the commands that are run to start the program. Commands can be modified through the <guibutton>Properties</guibutton> button or by double clicking the program/script row. The command is extracted from the Desktop file from the Exec key.
|
||||
</para>
|
||||
<para>
|
||||
For a script the command is the path to the script.
|
||||
</para>
|
||||
</listitem>
|
||||
</varlistentry>
|
||||
|
||||
<varlistentry><term><guilabel>Status</guilabel></term>
|
||||
<listitem>
|
||||
<para>
|
||||
This setting is only available for programs through Desktop files. You can keep a program in the <filename class="directory">Autostart</filename> folder but disable it from being run at &kde; start. Setting the program to <guilabel>Disabled</guilabel> will not run it on start.
|
||||
</para>
|
||||
<para>
|
||||
Setting a program to <guilabel>Disabled</guilabel> sets the Desktop file Hidden property to true in the <filename class="directory">Autostart</filename> folder.
|
||||
</para>
|
||||
</listitem>
|
||||
</varlistentry>
|
||||
|
||||
<varlistentry><term><guilabel>Run On</guilabel></term>
|
||||
<listitem>
|
||||
<para>
|
||||
Programs (Desktop files) can only be run on startup. Scripts can be run on <guilabel>Startup</guilabel>, <guilabel>Shutdown</guilabel> or <guilabel>Pre-KDE Startup</guilabel>. This column allows you to change when your script is run. Startup is when &kde; starts, shutdown is when you log out of &kde; and pre-KDE startup is before &kde; starts.
|
||||
</para>
|
||||
<para>
|
||||
Scripts and desktop files set to run on <guilabel>Startup</guilabel> are copied or symlinked in <filename class="directory">$KDEHOME/Autostart</filename> and will be run during &kde; startup.
|
||||
</para>
|
||||
<para>
|
||||
Scripts set on to be ran on <guilabel>Shutdown</guilabel> are copied or symlinked in the <filename class="directory">$KDEHOME/shutdown</filename> directory and will be automatically run during &kde; shutdown after the user has logged out.
|
||||
</para>
|
||||
<para>
|
||||
Scripts set to run at <guilabel>Pre-&kde; Startup</guilabel> are copied or symlinked in <filename class="directory">$KDEHOME/env</filename> and are sourced during &kde; startup (the <filename>startkde</filename> script will look for scripts here).
|
||||
</para>
|
||||
<note><para>
|
||||
Only scripts with the <filename>sh</filename> extension can be read by &kde; for <guilabel>Pre-&kde; startup</guilabel> and <guilabel>Shutdown</guilabel> modes.
|
||||
</para></note>
|
||||
</listitem>
|
||||
</varlistentry>
|
||||
</variablelist>
|
||||
</sect2>
|
||||
|
||||
<sect2 id="actions">
|
||||
<title>Actions</title>
|
||||
<para>
|
||||
On the right you have some buttons to change the way Autostart is configure. You can add programs or scripts, remove them or change their properties.
|
||||
</para>
|
||||
|
||||
<variablelist>
|
||||
<varlistentry><term><guibutton>Add Program</guibutton></term>
|
||||
<listitem>
|
||||
<para>
|
||||
Clicking this button displays the standard &kde; <guilabel>Choose Application</guilabel> dialog and allows you to choose which program you want to start. After choosing the program, clicking <guibutton>OK</guibutton> brings you the properties for this program.
|
||||
</para>
|
||||
<para>
|
||||
This will copy the program Desktop file in your <filename class="directory">Autostart</filename> folder.
|
||||
</para>
|
||||
</listitem>
|
||||
</varlistentry>
|
||||
|
||||
<varlistentry><term><guibutton>Add Script</guibutton></term>
|
||||
<listitem>
|
||||
<para>
|
||||
This button opens a dialog which asks you for the location of the script you want to add. If you keep <guilabel>Create as symlink</guilabel> checked (default) then the script will be added as a symlink. If you uncheck this option then the script will be copied in the corresponding local folder.
|
||||
</para>
|
||||
</listitem>
|
||||
</varlistentry>
|
||||
<varlistentry><term><guibutton>Remove</guibutton></term>
|
||||
<listitem>
|
||||
<para>
|
||||
Remove will immediately remove the Desktop file for the program or the script or symbolic link in the <filename class="directory">Autostart</filename> folder.
|
||||
</para>
|
||||
</listitem>
|
||||
</varlistentry>
|
||||
<varlistentry><term><guibutton>Properties</guibutton></term>
|
||||
<listitem>
|
||||
<para>
|
||||
This button (only enabled for programs &ie; Desktop files) allows you to change the properties of the program or script. You have general properties, permissions properties, a preview when applicable and properties related to the application for programs.
|
||||
</para>
|
||||
</listitem>
|
||||
</varlistentry>
|
||||
<varlistentry><term><guibutton>Advanced</guibutton></term>
|
||||
<listitem>
|
||||
<para>
|
||||
This button only applies to programs (&ie; Desktop files). A dialog asks you if you only want the program to autostart only in &kde; (and not in other desktop environments you might run). By default, the program will autostart in all desktop environments you might run. Checking <guilabel>Autostart only in KDE</guilabel> will autostart the program only if you start the &kde; desktop environment.
|
||||
</para>
|
||||
<para>
|
||||
This sets the value KDE to the OnlyShowIn key of the program Desktop file.
|
||||
</para>
|
||||
</listitem>
|
||||
</varlistentry>
|
||||
</variablelist>
|
||||
</sect2>
|
||||
</sect1>
|
||||
</article>
|
||||
<!-- see also Service Manager - Startup Services:
|
||||
This shows all KDE services that can be loaded on KDE startup. Checked services will be invoked on next startup.
|
||||
|
||||
and Session Management - Restore sessions?
|
||||
-->
|
||||
|
||||
<!--
|
||||
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;
|
||||
-->
|
||||
|
|
@ -1,2 +0,0 @@
|
|||
########### install files ###############
|
||||
kde4_create_handbook(index.docbook INSTALL_DESTINATION ${HTML_INSTALL_DIR}/en SUBDIR kcontrol/bell)
|
||||
|
|
@ -1,64 +0,0 @@
|
|||
<?xml version="1.0"?>
|
||||
<!DOCTYPE article PUBLIC "-//KDE//DTD DocBook XML V4.2-Based Variant V1.1//EN" "dtd/kdex.dtd" [
|
||||
<!ENTITY % addindex "IGNORE">
|
||||
<!ENTITY % English "INCLUDE" > <!-- change language only here -->
|
||||
]>
|
||||
|
||||
<article lang="&language;" id="system-bell">
|
||||
<title>System Bell</title>
|
||||
<articleinfo>
|
||||
<authorgroup>
|
||||
<author><firstname>Pat</firstname><surname>Dowler</surname></author>
|
||||
<author><firstname>Matthias</firstname><surname>Hoelzer</surname></author>
|
||||
<author><firstname>Mike</firstname><surname>McBride</surname></author>
|
||||
|
||||
<!-- TRANS:ROLES_OF_TRANSLATORS -->
|
||||
</authorgroup>
|
||||
<date>2011-11-28</date>
|
||||
<releaseinfo>&kde; 4.8</releaseinfo>
|
||||
</articleinfo>
|
||||
|
||||
<para>The system bell or beep is a feature of the X server, which
|
||||
attempts to make good use of the available hardware. </para>
|
||||
|
||||
<para>&kde; normally does not use the system bell; instead using its
|
||||
own system notifications, which could include log entries, message
|
||||
popups, or its own beep. You can configure these in the
|
||||
<guilabel>Manage Notifications</guilabel> &systemsettings; module.</para>
|
||||
|
||||
<note><para>It is not always possible for the X server to actually make
|
||||
a beep sound with exactly the parameters selected due to hardware
|
||||
limitations. For example, on most PCs, volume control is not very good
|
||||
so the X server seems to fake low volume with a reduced duration of
|
||||
the sound. Thus, if the settings do not seem to do anything, this is
|
||||
because the X server and/or the hardware do not support anything
|
||||
better.</para></note>
|
||||
|
||||
<para> Select <guilabel>Use system bell instead of system notification</guilabel>
|
||||
then you are able to set the following parameters for the bell:</para>
|
||||
|
||||
<variablelist>
|
||||
|
||||
<varlistentry>
|
||||
<term><guilabel>Volume</guilabel> (percentage of <quote>maximum</quote> volume)</term>
|
||||
<listitem><para>Here you can customize the volume of the system bell.</para></listitem>
|
||||
</varlistentry>
|
||||
|
||||
<varlistentry>
|
||||
<term><guilabel>Pitch</guilabel> (in Hz)</term>
|
||||
<listitem><para>Here you can customize the pitch of the system bell.</para></listitem>
|
||||
</varlistentry>
|
||||
|
||||
<varlistentry>
|
||||
<term><guilabel>Duration</guilabel> (in milliseconds)</term>
|
||||
<listitem><para>Here you can customize the duration of the system bell.</para></listitem>
|
||||
</varlistentry>
|
||||
|
||||
</variablelist>
|
||||
|
||||
<para>For further customization of the bell, see the <guilabel>Accessibility</guilabel> &systemsettings; module.</para>
|
||||
|
||||
<para>You can use the <guibutton>Test</guibutton> button to hear how
|
||||
the current settings will sound.</para>
|
||||
|
||||
</article>
|
||||
|
|
@ -1,2 +0,0 @@
|
|||
########### install files ###############
|
||||
kde4_create_handbook(index.docbook INSTALL_DESTINATION ${HTML_INSTALL_DIR}/en SUBDIR kcontrol/bookmarks)
|
||||
|
|
@ -1,101 +0,0 @@
|
|||
<?xml version="1.0" ?>
|
||||
<!DOCTYPE article PUBLIC "-//KDE//DTD DocBook XML V4.2-Based Variant V1.1//EN"
|
||||
"dtd/kdex.dtd" [
|
||||
<!ENTITY % addindex "IGNORE">
|
||||
<!ENTITY % English "INCLUDE" > <!-- change language only here -->
|
||||
]>
|
||||
|
||||
<article id="bookmarks" lang="&language;">
|
||||
<articleinfo>
|
||||
|
||||
<title>Bookmarks</title>
|
||||
<authorgroup>
|
||||
<author>
|
||||
<personname><firstname>Xavier</firstname><surname>Vello</surname></personname>
|
||||
<email>xavier.vello@gmail.com</email>
|
||||
</author>
|
||||
<!-- TRANS:ROLES_OF_TRANSLATORS -->
|
||||
</authorgroup>
|
||||
|
||||
<date>2010-09-24</date>
|
||||
<releaseinfo>0.2 (&kde; 4.5)</releaseinfo>
|
||||
|
||||
<keywordset>
|
||||
<keyword>KDE</keyword>
|
||||
<keyword>KControl</keyword>
|
||||
<keyword>bookmarks</keyword>
|
||||
<keyword>KIO</keyword>
|
||||
</keywordset>
|
||||
</articleinfo>
|
||||
<sect1 id="conf">
|
||||
<title>Bookmarks home page</title>
|
||||
<para>This module lets you configure the bookmarks home page.</para>
|
||||
<para>To view the bookmarks home page enter <userinput>bookmarks:/</userinput> in
|
||||
the location bar.</para>
|
||||
<para>The settings in this module are also accessible by entering
|
||||
<userinput>bookmarks:/config</userinput> in the location bar.</para>
|
||||
<sect2 id="conf-general">
|
||||
<title>General settings</title>
|
||||
<variablelist>
|
||||
<varlistentry>
|
||||
<term><guilabel>Number of columns to show</guilabel></term>
|
||||
<listitem>
|
||||
<para>Folders are automatically distributed in several columns. The optimal number of columns depends on the width of the konqueror window and the number of bookmarks you have.</para>
|
||||
</listitem>
|
||||
</varlistentry>
|
||||
|
||||
<varlistentry>
|
||||
<term><guilabel>Show folder backgrounds</guilabel></term>
|
||||
<listitem>
|
||||
<para>Disable it on slow system to disable background images.</para>
|
||||
</listitem>
|
||||
</varlistentry>
|
||||
</variablelist>
|
||||
</sect2>
|
||||
|
||||
<sect2 id="conf-bookmark">
|
||||
<title>Bookmarks</title>
|
||||
<variablelist>
|
||||
<varlistentry>
|
||||
<term><guilabel>Show bookmarks without folder</guilabel></term>
|
||||
<listitem>
|
||||
<para>If this option is unchecked, bookmarks at the root of the hierarchy (not in a folder) are not displayed. If checked, they are gathered in a "root" folder.</para>
|
||||
</listitem>
|
||||
</varlistentry>
|
||||
|
||||
<varlistentry>
|
||||
<term><guilabel>Flatten bookmarks tree</guilabel></term>
|
||||
<listitem>
|
||||
<para>Sub-folders are shown within their parent by default. If you activate this option, sub-folders are displayed on their own. It looks less nice but it may help if you have a very big folder you want to spread in two columns.</para>
|
||||
</listitem>
|
||||
</varlistentry>
|
||||
|
||||
<varlistentry>
|
||||
<term><guilabel>Show system places</guilabel></term>
|
||||
<listitem>
|
||||
<para>Show a box with KDE places (Home, Network, ...). Useful if you use konqueror as a file manager.</para>
|
||||
</listitem>
|
||||
</varlistentry>
|
||||
</variablelist>
|
||||
</sect2>
|
||||
|
||||
<sect2 id="conf-cache">
|
||||
<title>Pixmap cache</title>
|
||||
<variablelist>
|
||||
<varlistentry>
|
||||
<term><guilabel>Disk cache size</guilabel></term>
|
||||
<listitem>
|
||||
<para>Specify how much disk space is used to cache the pixmaps.</para>
|
||||
</listitem>
|
||||
</varlistentry>
|
||||
|
||||
<varlistentry>
|
||||
<term><guilabel>Clear Cache</guilabel></term>
|
||||
<listitem>
|
||||
<para>Remove all cached images. This may be necessary if some favicons become corrupt and don't refresh automatically.</para>
|
||||
</listitem>
|
||||
</varlistentry>
|
||||
</variablelist>
|
||||
</sect2>
|
||||
</sect1>
|
||||
</article>
|
||||
2
doc/kcontrol/cache/CMakeLists.txt
vendored
2
doc/kcontrol/cache/CMakeLists.txt
vendored
|
|
@ -1,2 +0,0 @@
|
|||
########### install files ###############
|
||||
kde4_create_handbook(index.docbook INSTALL_DESTINATION ${HTML_INSTALL_DIR}/en SUBDIR kcontrol/cache)
|
||||
66
doc/kcontrol/cache/index.docbook
vendored
66
doc/kcontrol/cache/index.docbook
vendored
|
|
@ -1,66 +0,0 @@
|
|||
<?xml version="1.0" ?>
|
||||
<!DOCTYPE article PUBLIC "-//KDE//DTD DocBook XML V4.2-Based Variant V1.1//EN"
|
||||
"dtd/kdex.dtd" [
|
||||
<!ENTITY % addindex "IGNORE">
|
||||
<!ENTITY % English "INCLUDE" > <!-- change language only here -->
|
||||
]>
|
||||
|
||||
<article id="cache" lang="&language;">
|
||||
<title>Cache</title>
|
||||
<articleinfo>
|
||||
|
||||
<authorgroup>
|
||||
<author><firstname>Lauri</firstname><surname>Watts</surname></author>
|
||||
|
||||
<!-- TRANS:ROLES_OF_TRANSLATORS -->
|
||||
</authorgroup>
|
||||
|
||||
<date>2009-11-20</date>
|
||||
<releaseinfo>&kde; 4.4</releaseinfo>
|
||||
|
||||
<keywordset>
|
||||
<keyword>KDE</keyword>
|
||||
<keyword>Systemsettings</keyword>
|
||||
<keyword>Konqueror</keyword>
|
||||
<keyword>Cache</keyword>
|
||||
</keywordset>
|
||||
</articleinfo>
|
||||
|
||||
<para>This module allows you to control the size of the local cache
|
||||
folder used by &konqueror;. Note that each user account on your
|
||||
computer has a separate cache folder, and this folder is not
|
||||
shared with other web browsers such as &Netscape;.</para>
|
||||
|
||||
<para>Storing local copies of web pages that you have visited allows
|
||||
&konqueror; to quickly load their contents on subsequent visits. It
|
||||
will only be necessary to reload the contents from the original site
|
||||
if they have changed since your last visit, or if you click the reload
|
||||
button in &konqueror;.</para>
|
||||
|
||||
<para>If you really do not want any of the web pages you visit to be
|
||||
stored on your computer, you can disable &konqueror;'s disk cache by
|
||||
clearing the checkbox labeled <guilabel>Use cache</guilabel>.</para>
|
||||
|
||||
<para>You can set here how aggressively &konqueror; keeps the cache up
|
||||
to date. <guilabel>Keep cache in sync</guilabel> means that &konqueror;
|
||||
will hit the cache for all objects, downloading them if they are not
|
||||
there, and then display the item from the cache. <guilabel>Use cache
|
||||
whenever possible</guilabel> means that &konqueror; will try the cache,
|
||||
and if an object is not there, it will directly download it for display.
|
||||
<guilabel>Offline browsing mode</guilabel> means that &konqueror; will
|
||||
try the cache, and if an object is not there, it will not attempt to
|
||||
download it from the Internet.</para>
|
||||
|
||||
<para>You can control the size of the cache by typing a number into the
|
||||
text box labeled <guilabel>Disk cache size</guilabel>. This is the
|
||||
average amount of space in kilobytes that the cache folder is allowed
|
||||
to use. When the cache grows too large, &konqueror; will delete older
|
||||
files to reduce the size of the cache folder.</para>
|
||||
|
||||
<para>This is however, only an average, and during a browsing session
|
||||
the cache could become substantially larger.</para>
|
||||
|
||||
<para>You can use the <guibutton>Clear Cache</guibutton> button to empty
|
||||
the cache at any time.</para>
|
||||
|
||||
</article>
|
||||
|
|
@ -1,2 +0,0 @@
|
|||
########### install files ###############
|
||||
kde4_create_handbook(index.docbook INSTALL_DESTINATION ${HTML_INSTALL_DIR}/en SUBDIR kcontrol/clock)
|
||||
|
|
@ -1,90 +0,0 @@
|
|||
<?xml version="1.0" ?>
|
||||
<!DOCTYPE article PUBLIC "-//KDE//DTD DocBook XML V4.2-Based Variant V1.1//EN"
|
||||
"dtd/kdex.dtd" [
|
||||
<!ENTITY % addindex "IGNORE">
|
||||
<!ENTITY % English "INCLUDE" > <!-- change language only here -->
|
||||
]>
|
||||
|
||||
<article id="clock" lang="&language;">
|
||||
<articleinfo>
|
||||
<title>Date & Time</title>
|
||||
<authorgroup>
|
||||
<author>&Mike.McBride; &Mike.McBride.mail;</author>
|
||||
<!-- TRANS:ROLES_OF_TRANSLATORS -->
|
||||
</authorgroup>
|
||||
|
||||
<date>2013-12-05</date>
|
||||
<releaseinfo>4.12</releaseinfo>
|
||||
|
||||
<keywordset>
|
||||
<keyword>KDE</keyword>
|
||||
<keyword>Systemsettings</keyword>
|
||||
<keyword>clock</keyword>
|
||||
<keyword>date</keyword>
|
||||
<keyword>time</keyword>
|
||||
<keyword>set</keyword>
|
||||
<keyword>configure</keyword>
|
||||
</keywordset>
|
||||
</articleinfo>
|
||||
|
||||
<sect1 id="datetime">
|
||||
|
||||
<title>Date & Time</title>
|
||||
|
||||
<para>You can use this module to alter the system date and time, using a
|
||||
convenient graphical interface.</para>
|
||||
|
||||
<note><para>As these settings do not only affect you as a user,
|
||||
but rather the whole system, you must have system administrator (<systemitem
|
||||
class="username">root</systemitem>) access to change the system date and
|
||||
time. If you do not have this access level, this module will only show
|
||||
you the current settings, but your changes will not be saved.</para></note>
|
||||
|
||||
<sect2 id="date-change">
|
||||
<title>Date and Time</title>
|
||||
|
||||
<para>If you check <guilabel>Set date and time automatically</guilabel> you are able
|
||||
to select a <guilabel>Time server</guilabel> from the drop down box and all other
|
||||
settings in this dialog are disabled.</para>
|
||||
|
||||
<note>
|
||||
<para>The applications <command>rdate</command> or <command>ntpdate</command> are used in
|
||||
this module to fetch date and time from a time server. This happens when you log in to &kde;
|
||||
while being online or when you later connect to the Internet and access to time
|
||||
servers is possible.</para>
|
||||
<para>Both applications are simple <acronym>NTP</acronym> clients that set a system's clock
|
||||
to match the time obtained by communicating with one or more <acronym>NTP</acronym> servers.
|
||||
This is not sufficient, however, for maintaining an accurate clock in the long run.
|
||||
This is useful for occasionally setting the time on machines that do not have full-time
|
||||
network access, such as laptops.</para>
|
||||
</note>
|
||||
|
||||
<para>If you do not use a time server, you are able to set the date manually
|
||||
using the lower half of the tab. Simply
|
||||
choose your month and year using the controls at the top of the calendar
|
||||
and the day of the month by clicking on the day in the
|
||||
calendar.</para>
|
||||
<para>Use the controls at the bottom of the calendar
|
||||
to select the current date, enter the date in the edit box or select the
|
||||
week of the year from the drop down box.</para>
|
||||
|
||||
<para>You set the time using the spin boxes at the bottom of the analog clock.
|
||||
You can also directly enter your value.</para>
|
||||
<!--Outdated
|
||||
<note><para>The time is represented in 24 hour format. If you want
|
||||
the system time to be set to 8:00 PM, you need to set the hour spinbox
|
||||
to <guilabel>20</guilabel> (8 + 12). If you want the system time set
|
||||
to 8:00 AM, you should set the hour spinbox to
|
||||
<guilabel>8</guilabel>.</para></note>
|
||||
-->
|
||||
</sect2>
|
||||
|
||||
<sect2 id="date-time-tone">
|
||||
<title>Time Zone</title>
|
||||
<para>To set a new time zone, simply select your area from the list below.
|
||||
Use the filter box to find the desired <guilabel>Area</guilabel> or <guilabel>Region</guilabel>.</para>
|
||||
</sect2>
|
||||
|
||||
</sect1>
|
||||
|
||||
</article>
|
||||
|
|
@ -1,2 +0,0 @@
|
|||
########### install files ###############
|
||||
kde4_create_handbook(index.docbook INSTALL_DESTINATION ${HTML_INSTALL_DIR}/en SUBDIR kcontrol/colors)
|
||||
|
|
@ -1,399 +0,0 @@
|
|||
<?xml version="1.0" ?>
|
||||
|
||||
<!DOCTYPE article PUBLIC "-//KDE//DTD DocBook XML V4.2-Based Variant V1.1//EN"
|
||||
"dtd/kdex.dtd" [
|
||||
<!ENTITY % addindex "IGNORE">
|
||||
<!ENTITY % English "INCLUDE" > <!-- change language only here -->
|
||||
]>
|
||||
|
||||
<article id="colors" lang="&language;">
|
||||
<articleinfo>
|
||||
<title>Colors</title>
|
||||
<authorgroup>
|
||||
<author>&Matthew.Woehlke; &Matthew.Woehlke.mail;</author>
|
||||
<!-- TRANS:ROLES_OF_TRANSLATORS -->
|
||||
</authorgroup>
|
||||
|
||||
<date>2013-11-05</date>
|
||||
<releaseinfo>4.12</releaseinfo>
|
||||
|
||||
<keywordset>
|
||||
<keyword>KDE</keyword>
|
||||
<keyword>KControl</keyword>
|
||||
<keyword>color</keyword>
|
||||
<keyword>kcm</keyword>
|
||||
</keywordset>
|
||||
</articleinfo>
|
||||
|
||||
<sect1 id="color">
|
||||
<title>Colors</title>
|
||||
|
||||
<sect2 id="color-intro">
|
||||
<title>Introduction</title>
|
||||
|
||||
<para>The Color Selection module is comprised of several sections:</para>
|
||||
|
||||
<itemizedlist>
|
||||
<listitem><para>
|
||||
<link linkend="color-scheme">The <guilabel>Scheme</guilabel> tab</link>,
|
||||
used to manage schemes.
|
||||
</para></listitem>
|
||||
<listitem><para>
|
||||
<link linkend="color-options">The <guilabel>Options</guilabel> tab</link>,
|
||||
used to change the options of the current scheme.
|
||||
</para></listitem>
|
||||
<listitem><para>
|
||||
<link linkend="color-colors">The <guilabel>Colors</guilabel> tab</link>,
|
||||
used to change the colors of the current scheme.
|
||||
</para></listitem>
|
||||
<listitem><para>
|
||||
<link linkend="color-effects">The state effects tabs</link>
|
||||
(<guilabel>Inactive</guilabel>, <guilabel>Disabled</guilabel>), used to
|
||||
change the state effects of the current scheme.
|
||||
</para></listitem>
|
||||
</itemizedlist>
|
||||
|
||||
<para>Note: This documentation will sometimes refer to the
|
||||
"current" scheme, or the "active" scheme.
|
||||
The "current" scheme is the set of colors and color scheme options
|
||||
that was most recently applied, &ie; what you would get if you choose
|
||||
<guibutton>Cancel</guibutton>. The "active" scheme is the set of
|
||||
colors as has been most recently edited by you, &ie; what you would get if
|
||||
you choose <guibutton>Apply</guibutton>.</para>
|
||||
</sect2>
|
||||
|
||||
<sect2 id="color-scheme">
|
||||
<title>Scheme Management</title>
|
||||
|
||||
<para>The <guilabel>Scheme</guilabel> tab lets you manage the color schemes
|
||||
on your machine. Only one scheme is active at once, but you may save schemes,
|
||||
allowing you to quickly change the scheme later. When you have created a
|
||||
scheme you like, you can save it with <guibutton>Save Scheme...</guibutton>.
|
||||
You can remove schemes using <guibutton>Remove Scheme</guibutton>.
|
||||
Note that system schemes cannot be removed; trying to do so will display an
|
||||
error.</para>
|
||||
|
||||
<para>&kde; ships with several schemes. If you have an Internet connection,
|
||||
you can also browse and retrieve user-created schemes using <guibutton>Get
|
||||
New Schemes...</guibutton>.</para>
|
||||
|
||||
<sect3>
|
||||
<title>Importing Schemes</title>
|
||||
|
||||
<para>You can also import schemes that you have downloaded or otherwise
|
||||
obtained, as well as import &kde; 3 schemes. &kde; 4 color schemes are
|
||||
named like "*.colors", while &kde; 3 schemes are named like
|
||||
"*.kcsrc".</para>
|
||||
|
||||
<para>Because &kde; 4 has many more color roles than &kde;, importing a
|
||||
&kde; 3 scheme is different from importing a &kde; 4 scheme. When a
|
||||
&kde; 4 scheme is imported, it becomes part of your saved scheme
|
||||
collection. When a &kde; 3 scheme is imported, the colors that exist in
|
||||
&kde; 3 are overlaid onto the active scheme, and the result is not
|
||||
automatically saved into your collection. After importing a &kde; 3 scheme,
|
||||
you will likely need to adjust the colors that are new in &kde; 4, as well
|
||||
as the state effects. For best results, before importing a &kde; 3 scheme,
|
||||
select a similar &kde; 4 scheme (you do not need to apply the scheme before
|
||||
importing).</para>
|
||||
</sect3>
|
||||
</sect2>
|
||||
|
||||
<sect2 id="color-options">
|
||||
<title>Color Scheme Options</title>
|
||||
|
||||
<para>The <guilabel>Options</guilabel> tab allows you to change some
|
||||
properties that deal with how the color scheme is used, as well as some
|
||||
options that change the color scheme that are different from actually
|
||||
assigning colors.</para>
|
||||
|
||||
<itemizedlist>
|
||||
<listitem><para><guilabel>Apply inactive window color effects</guilabel>
|
||||
— If checked, state effects (see below) will be applied to inactive
|
||||
windows. This can help visually identify active versus inactive windows,
|
||||
and may have aesthetic value, depending on your taste. However, some
|
||||
users feel that it causes distracting "flickering" since
|
||||
windows must be repainted when they become inactive. Unlike desktop
|
||||
effects, color state effects do not require compositing support and will
|
||||
work on all systems, however they will only work on &kde; 4 applications.
|
||||
</para></listitem>
|
||||
<listitem><para><guilabel>Inactive selection changes color</guilabel>
|
||||
— If checked, the current selection in elements which do not have
|
||||
input focus will be drawn using a different color. This can assist visual
|
||||
identification of the element with input focus in some applications,
|
||||
especially those which simultaneously display several lists.
|
||||
</para></listitem>
|
||||
<listitem><para><guilabel>Shade sorted column in lists</guilabel>
|
||||
— If checked, multi-column lists will use a slightly different
|
||||
color to paint the column whose information is being used to sort the
|
||||
items in the list.
|
||||
</para></listitem>
|
||||
<listitem><para><guilabel>Apply colors to non-KDE4 applications</guilabel>
|
||||
— If checked, &kde; will attempt to export its color scheme so that
|
||||
non-&kde; 4 applications will use the same colors. Most applications will
|
||||
honor the exported scheme to varying degrees, though some may have bugs
|
||||
or otherwise not honor the exported scheme.
|
||||
</para></listitem>
|
||||
<listitem><para><guilabel>Contrast</guilabel>
|
||||
— This slider controls the contrast of shaded elements, such as
|
||||
frame borders and the "3D" effects used by most styles. A lower
|
||||
value gives less contrast and therefore softer edges, while a higher
|
||||
value makes such edges "stand out" more.
|
||||
</para></listitem>
|
||||
</itemizedlist>
|
||||
|
||||
</sect2>
|
||||
|
||||
<sect2 id="color-colors">
|
||||
<title>Colors</title>
|
||||
|
||||
<para>The <guilabel>Colors</guilabel> tab allows you to change the colors in
|
||||
the active color scheme.</para>
|
||||
|
||||
<para>Creating or changing a scheme is a simple matter of clicking on the
|
||||
swatch in the color list and selecting a new color. You can check your
|
||||
changes at any time by pressing <guibutton>Apply</guibutton>. It is suggested
|
||||
that you save your scheme (via the <guilabel>Scheme</guilabel> tab) when you
|
||||
are done.</para>
|
||||
|
||||
<para>The <guilabel>Common Colors</guilabel> set, which is displayed
|
||||
initially, is not actually a "set" in the sense used by &kde; (see
|
||||
next section), but presents a number of color roles in a way that makes it
|
||||
easier to edit the scheme as a whole. When creating a new color scheme, you
|
||||
will usually change these colors first, and use the other sets to tweak
|
||||
specific colors if needed.</para>
|
||||
|
||||
<para>Note that <guilabel>Common Colors</guilabel> makes available roles from
|
||||
all sets. For example, "View Background" here is shorthand for the
|
||||
Normal Background role from the View set. Also, setting colors that do not
|
||||
refer to a specific set will change that color in <emphasis>all</emphasis>
|
||||
sets. (As an exception, "Inactive Text" will change the color for
|
||||
all sets <emphasis>except</emphasis> for Selection; there is a separate
|
||||
"Selection Inactive Text" for Inactive Text in the Selection set.)
|
||||
Some roles may not be visible under <guilabel>Common Colors</guilabel> at
|
||||
all, and can only be changed (if needed) by selecting the appropriate
|
||||
set.</para>
|
||||
|
||||
<sect3>
|
||||
<title>Color Sets</title>
|
||||
|
||||
<para>&kde; 4 breaks the color scheme into several sets based on the type
|
||||
of user interface element, as follows:</para>
|
||||
<itemizedlist>
|
||||
<listitem><para><guilabel>View</guilabel> —
|
||||
information presentation elements, such as lists, trees, text input boxes, etc.
|
||||
</para></listitem>
|
||||
<listitem><para><guilabel>Window</guilabel> —
|
||||
window elements that are not buttons or views.
|
||||
</para></listitem>
|
||||
<listitem><para><guilabel>Button</guilabel> —
|
||||
buttons and similar elements.
|
||||
</para></listitem>
|
||||
<listitem><para><guilabel>Selection</guilabel> —
|
||||
selected text and items.
|
||||
</para></listitem>
|
||||
<listitem><para><guilabel>Tooltip</guilabel> —
|
||||
tool tips, "What's This" tips, and similar elements.
|
||||
</para></listitem>
|
||||
<listitem><para>Window Manager —
|
||||
window title bars and related elements.
|
||||
</para></listitem>
|
||||
</itemizedlist>
|
||||
|
||||
<para>Each set contains a number of color roles. Except for the Window
|
||||
Manager colors, each set has the same roles. All colors are associated with
|
||||
one of the above sets.</para>
|
||||
</sect3>
|
||||
|
||||
<sect3>
|
||||
<title>Color Roles</title>
|
||||
|
||||
<para>Each color set is made up of a number of roles which are available in
|
||||
all other sets. (The Window Manager set is an exception; it has its own
|
||||
unique roles that do not exist in any other set, and does not use the same
|
||||
roles as the other sets.) In addition to the obvious Normal Text and Normal
|
||||
Background, these roles are as follows:</para>
|
||||
|
||||
<itemizedlist>
|
||||
<listitem><para>Alternate Background —
|
||||
used when there is a need to subtly change the background to aid in
|
||||
item association. This might be used ⪚ as the background of a
|
||||
heading, but is mostly used for alternating rows in lists, especially
|
||||
multi-column lists, to aid in visually tracking rows.
|
||||
</para></listitem>
|
||||
<listitem><para>Link Text —
|
||||
used for hyperlinks or to otherwise indicate "something which may
|
||||
be visited", or to show relationships.
|
||||
</para></listitem>
|
||||
<listitem><para>Visited Text —
|
||||
used for "something (⪚ a hyperlink) that has been
|
||||
visited", or to indicate something that is "old".
|
||||
</para></listitem>
|
||||
<listitem><para>Active Text —
|
||||
used to indicate an active element or attract attention, ⪚ alerts,
|
||||
notifications; also for hovered hyperlinks.
|
||||
</para></listitem>
|
||||
<listitem><para>Inactive Text —
|
||||
used for text which should be unobtrusive, ⪚ comments,
|
||||
"subtitles", unimportant information, etc.
|
||||
</para></listitem>
|
||||
<listitem><para>Negative Text —
|
||||
used for errors, failure notices, notifications that an action may be
|
||||
dangerous (⪚ unsafe web page or security context), etc.
|
||||
</para></listitem>
|
||||
<listitem><para>Neutral Text —
|
||||
used to draw attention when another role is not appropriate; ⪚
|
||||
warnings, to indicate secure/encrypted content, etc.
|
||||
</para></listitem>
|
||||
<listitem><para>Positive Text —
|
||||
used for success notices, to indicate trusted content, etc.
|
||||
</para></listitem>
|
||||
</itemizedlist>
|
||||
|
||||
<para>As well as the text roles, there are a few additional
|
||||
"decoration" roles that are used for drawing lines or shading
|
||||
UI elements (while the above may, in appropriate circumstances, also be
|
||||
used for this purpose, the following are specifically
|
||||
<emphasis>not</emphasis> meant for drawing text). These are:</para>
|
||||
|
||||
<itemizedlist>
|
||||
<listitem><para>Focus Decoration —
|
||||
used to indicate the item which has active input focus.
|
||||
</para></listitem>
|
||||
<listitem><para>Hover Decoration —
|
||||
used for mouse-over effects, ⪚ the "illumination" effects for
|
||||
buttons.
|
||||
</para></listitem>
|
||||
</itemizedlist>
|
||||
|
||||
<para>In addition, except for Inactive Text, there is a corresponding
|
||||
background role for each of the text roles. Currently (except for Normal
|
||||
and Alternate Background), these colors are not chosen by the user, but are
|
||||
automatically determined based on Normal Background and the corresponding
|
||||
Text color. These colors may be previewed by selecting one of the sets
|
||||
other than "Common Colors".</para>
|
||||
|
||||
<para>The choice of color role is left to the developer; the above are
|
||||
guidelines intended to represent typical usage.</para>
|
||||
</sect3>
|
||||
|
||||
<sect3>
|
||||
<title>Window Manager Colors</title>
|
||||
|
||||
<para>As previously stated, the Window Manager set has its own roles,
|
||||
independent of those in other sets. These are (currently) only accessible
|
||||
via <guilabel>Common Colors</guilabel>, and are as follows:</para>
|
||||
|
||||
<itemizedlist>
|
||||
<listitem><para>Active Titlebar —
|
||||
used to draw the title bar background, borders, and/or decorations for
|
||||
the active window (that is, the one with input focus). Not all window
|
||||
decorations will use this in the same way, and some may even use the
|
||||
Normal Background from the Window set to draw the title bar.
|
||||
</para></listitem>
|
||||
<listitem><para>Active Titlebar Text —
|
||||
used to draw the title bar text when Active Titlebar is used to draw
|
||||
the title bar background. May also be used for other foreground
|
||||
elements which use Active Titlebar as the background.
|
||||
</para></listitem>
|
||||
</itemizedlist>
|
||||
|
||||
<para>The Inactive Titlebar [Text] roles are the same as the above, but for
|
||||
inactive windows, rather than active windows.</para>
|
||||
</sect3>
|
||||
|
||||
</sect2>
|
||||
|
||||
<sect2 id="color-effects">
|
||||
<title>Color State Effects</title>
|
||||
|
||||
<para>Color state effects are applied to interface elements in the inactive
|
||||
(windows that do not have focus; only if <guilabel>Apply inactive window
|
||||
color effects</guilabel> is enabled) or disabled states. By changing the
|
||||
effects, the appearance of elements in these states can be changed. Usually,
|
||||
inactive elements will have reduced contrast (text fades slightly into the
|
||||
background) and may have slightly reduced intensity, while disabled elements
|
||||
will have strongly reduced contrast and are often notably darker or lighter.
|
||||
</para>
|
||||
|
||||
<para>Three types of effect may be applied to each state (with the effects
|
||||
of the two states being independent). These are Intensity, Color and
|
||||
Contrast. The first two (Intensity, Color) control the overall color, while
|
||||
the last (Contrast) deals with the foreground colors relative to the
|
||||
background.</para>
|
||||
|
||||
<sect3>
|
||||
<title>Intensity</title>
|
||||
|
||||
<para>Intensity allows the overall color to be lightened or darkened.
|
||||
Setting the slider to the middle produces no change. The available effects
|
||||
are:</para>
|
||||
|
||||
<itemizedlist>
|
||||
<listitem><para>Shade —
|
||||
makes everything lighter or darker in a controlled manner. Each
|
||||
"tick" on the slider increases or decreases the overall
|
||||
intensity (&ie; perceived brightness) by an absolute amount.
|
||||
</para></listitem>
|
||||
<listitem><para>Darken —
|
||||
changes the intensity to a percentage of the initial value. A slider
|
||||
setting halfway between middle and maximum results in a color half as
|
||||
intense as the original. The minimum gives a color twice as intense as
|
||||
the original.
|
||||
</para></listitem>
|
||||
<listitem><para>Lighten —
|
||||
conceptually the opposite of darken; lighten can be thought of as
|
||||
working with "distance from white", where darken works with
|
||||
"distance from black". The minimum is a color twice as
|
||||
"far" from white as the original, while halfway between
|
||||
middle and maximum gives an intensity halfway between the original
|
||||
color and white.
|
||||
</para></listitem>
|
||||
</itemizedlist>
|
||||
</sect3>
|
||||
|
||||
<sect3>
|
||||
<title>Color</title>
|
||||
|
||||
<para>Color also changes the overall color, but is not limited to
|
||||
intensity. The available effects are:</para>
|
||||
|
||||
<itemizedlist>
|
||||
<listitem><para>Desaturate —
|
||||
changes the relative chroma. The middle setting produces no change;
|
||||
maximum gives a gray whose perceptual intensity equals that of the
|
||||
original color. Lower settings increase the chroma, giving a color that
|
||||
is less gray / more "vibrant" than the original.
|
||||
</para></listitem>
|
||||
<listitem><para>Fade —
|
||||
smoothly blends the original color into a reference color. The minimum
|
||||
setting on the slider produces no change; maximum gives the reference
|
||||
color.
|
||||
</para></listitem>
|
||||
<listitem><para>Tint —
|
||||
similar to Fade, except that the color (hue and chroma) changes more
|
||||
quickly while the intensity changes more slowly as the slider value is
|
||||
increased.
|
||||
</para></listitem>
|
||||
</itemizedlist>
|
||||
</sect3>
|
||||
|
||||
<sect3>
|
||||
<title>Contrast</title>
|
||||
|
||||
<para>The contrast effects are similar to the color effects, except they
|
||||
apply to the text, using the background color as the reference color, and
|
||||
desaturate is not available. Fade produces text that "fades out"
|
||||
more quickly, but keeps its color longer, while Tint produces text that
|
||||
changes color to match the background more quickly while keeping a greater
|
||||
intensity contrast for longer (where "longer" means higher
|
||||
settings on the slider). For Contrast effects, the minimum setting on the
|
||||
slider produces no change, while maximum causes the text to completely
|
||||
disappear into the background.</para>
|
||||
</sect3>
|
||||
|
||||
</sect2>
|
||||
|
||||
</sect1>
|
||||
|
||||
</article>
|
||||
<!-- kate: indent-width 2; replace-tabs on; -->
|
||||
|
|
@ -1,2 +0,0 @@
|
|||
########### install files ###############
|
||||
kde4_create_handbook(index.docbook INSTALL_DESTINATION ${HTML_INSTALL_DIR}/en SUBDIR kcontrol/componentchooser)
|
||||
|
|
@ -1,68 +0,0 @@
|
|||
<?xml version="1.0" ?>
|
||||
<!DOCTYPE article PUBLIC "-//KDE//DTD DocBook XML V4.2-Based Variant V1.1//EN"
|
||||
"dtd/kdex.dtd" [
|
||||
<!ENTITY % addindex "IGNORE">
|
||||
<!ENTITY % English "INCLUDE" > <!-- change language only here -->
|
||||
]>
|
||||
|
||||
<article lang="&language;" id="default-components">
|
||||
<articleinfo>
|
||||
|
||||
<title>Default Applications</title>
|
||||
<authorgroup>
|
||||
<author><personname><firstname>Burkhard</firstname><surname>Lück</surname></personname>
|
||||
<email>lueck@hube-lueck.de</email>
|
||||
</author>
|
||||
|
||||
<!-- TRANS:ROLES_OF_TRANSLATORS -->
|
||||
</authorgroup>
|
||||
|
||||
<date>2013-12-05</date>
|
||||
<releaseinfo>&kde; 4.12</releaseinfo>
|
||||
|
||||
<keywordset>
|
||||
<keyword>KDE</keyword>
|
||||
<keyword>Systemsettings</keyword>
|
||||
<keyword>component</keyword>
|
||||
</keywordset>
|
||||
</articleinfo>
|
||||
|
||||
<para>In this module you can change &kde; default components.</para>
|
||||
|
||||
<para>Components are programs that handle basic tasks, like the terminal emulator, the text
|
||||
editor and the email client. Different &kde; applications sometimes need to
|
||||
invoke a console emulator, send a mail or display some text.</para>
|
||||
|
||||
<para>To do so consistently, these applications always call the same components. Here you
|
||||
can select which programs these components are.</para>
|
||||
|
||||
<para>The list on the left shows the configurable component types:</para>
|
||||
<itemizedlist>
|
||||
<listitem>
|
||||
<para>Email Client</para>
|
||||
</listitem>
|
||||
<listitem>
|
||||
<para>Embedded Text Editor</para>
|
||||
</listitem>
|
||||
<listitem>
|
||||
<para>File Manager</para>
|
||||
</listitem>
|
||||
<listitem>
|
||||
<para>Instant Messenger</para>
|
||||
</listitem>
|
||||
<listitem>
|
||||
<para>Terminal Emulator</para>
|
||||
</listitem>
|
||||
<listitem>
|
||||
<para>Web Browser</para>
|
||||
</listitem>
|
||||
<listitem>
|
||||
<para>Window Manager</para>
|
||||
</listitem>
|
||||
</itemizedlist>
|
||||
|
||||
<para> Click the component you want to configure. In the right part of the dialog then all available
|
||||
applications for this service are displayed and you are able to select your favorite terminal emulator, text
|
||||
editor and the email client &etc;</para>
|
||||
|
||||
</article>
|
||||
Some files were not shown because too many files have changed in this diff Show more
Loading…
Add table
Reference in a new issue