Customization for distributions - Revision history

Blu256: Added categories

2022-01-05T14:41:41Z

Added categories

Blu256: Removed WIP, but still needs additions.

2022-01-05T14:40:36Z

Removed WIP, but still needs additions.

Blu256: /* Suggested documentation */ Added link to Themes for Individual Applications

2022-01-05T14:34:06Z

Suggested documentation: Added link to Themes for Individual Applications

Blu256: Added generic notes on overriding configuration, suggested documentation

2022-01-05T14:06:10Z

Added generic notes on overriding configuration, suggested documentation

Blu256: Small fixes

2022-01-05T12:29:56Z

Small fixes

Blu256: Added Kicker launchers customization info

2022-01-05T12:29:11Z

Added Kicker launchers customization info

Blu256: Created page

2022-01-05T12:07:01Z

Created page

New page

This page is meant to contain customization notes and tips for packagers and distributions that want to offer a custom Trinity experience.

{{WIP|Blu256}}

@@ Line 52: / Line 52: @@
 * [[Themes for Individual Applications]] section on this wiki
 * [http://web.archive.org/web/20061014025645/http://www.kde.org/areas/sysadmin/config_file.php KDE for System Administrators (archived page)]
+[[Category:Packagers]]
+[[Category:Developers]]

@@ Line 51: / Line 51: @@
 Other useful resources:
+* [[Themes for Individual Applications]] section on this wiki
 * [http://web.archive.org/web/20061014025645/http://www.kde.org/areas/sysadmin/config_file.php KDE for System Administrators (archived page)]

@@ Line 1: / Line 1: @@
 {{WIP|Blu256}}
 This page is meant to contain customization notes and tips for packagers and distributions that want to offer a custom Trinity experience.
@@ Line 7: / Line 6: @@
 __TOC__
+= Generic notes =
+== Overriding default configuration ==
+Configuration of the environment and its applications is stored in simple INI-style text files. These files can be stored in several places.
+According to the old ''KDE for System Administrators'' guide:
+<blockquote>
+There can be multiple configuration files with the same name in the share/config sub-directory of the various KDE Directory Trees. In that case the information of all these configuration files is combined on a key by key basis. If the same key within a certain group is defined in more than one place, the key value read from the directory tree with the highest precedence will be used. Configuration files under $KDEHOME always have the highest precedence. If a key in a certain group is defined multiple times in a single file, the value of the last entry is used.
+KDE's cascading configuration scheme can be used to provide users with system or organisation wide default settings while it still allows the users to make individual changes to these settings. KDE will not write entries to the users configuration file under $KDEHOME that match any default settings provided this way. This way changes made to the default settings will immediately be propagated to the user. Note that differs from the traditional way of providing default settings for users through the use of /etc/skel, changes to /etc/skel will only be propagated when creating a new user account.
+</blockquote>
+This means that a system typically uses two levels of configuration - the system-provided one (stored in <tt>$TDEPREFIX/share/config</tt>) and the user-definen one (stored in <tt>$TDEHOME/share/config</tt>). You can define more TDE prefixes by modifying the environment variable <tt>$TDEDIRS</tt> (e.g. to provide distribution-specific overrides). This will cause TDE to look for documentation in <tt>[PREFIX]/share/config</tt> for each of the prefixes, in the order that they are specified.
+= Desktop Environment =
 == Kicker ==
@@ Line 23: / Line 40: @@
   libreoffice-writer.desktop
   vlc.desktop
+= Applications =
+{{TODO}}
+= Suggested documentation =
+Make sure you read the "Trinity Administrator Guide" (via the Trinity Help Center), as it contains useful information on deployment and advanced configuration of Trinity.
+Other useful resources:
+* [http://web.archive.org/web/20061014025645/http://www.kde.org/areas/sysadmin/config_file.php KDE for System Administrators (archived page)]

@@ Line 6: / Line 6: @@
 __TOC__
 == Kicker ==
@@ Line 17: / Line 18: @@
 As an example, the following modified <tt>default-apps</tt> will add the Home and the Help buttons, as well as an Amarok, a LibreOffice Writer and a VLC launcher.
+  Home.desktop
-<syntaxhighlight>
-Home.desktop
+  Help.desktop
-Help.desktop
+  amarok.desktop
-amarok.desktop
+  libreoffice-writer.desktop
-libreoffice-writer.desktop
+  vlc.desktop
-vlc.desktop
-</syntaxhighlight>

@@ Line 1: / Line 1: @@
+{{WIP|Blu256}}
 This page is meant to contain customization notes and tips for packagers and distributions that want to offer a custom Trinity experience.
-{{WIP|Blu256}}
+__TOC__
+== Kicker ==
+=== Launchers ===
+You can change the default launchers that get added to Kicker on first start by modifying the file <tt>$TDEPREFIX/share/apps/kicker/default-apps</tt>.
+In that file, each line contains a reference to a desktop file. [https://mirror.git.trinitydesktop.org/gitea/TDE/tdebase/src/branch/master/kicker/kicker/core/default-apps By default] a Home button and a Konqueror launcher are placed there. You can add launchers for any applications you want as long as their desktop files are located under <tt>$TDEPREFIX/share/appplications/</tt>.
+As an example, the following modified <tt>default-apps</tt> will add the Home and the Help buttons, as well as an Amarok, a LibreOffice Writer and a VLC launcher.
+<syntaxhighlight>
+Home.desktop
+Help.desktop
+amarok.desktop
+libreoffice-writer.desktop
+vlc.desktop
+</syntaxhighlight>