Development/Architecture/KDE3/Standard Resources - Revision history

AnneW: Marked this version for translation

2012-07-11T19:13:19Z

Marked this version for translation

AnneW: Split list into smaller units for translation

2012-07-11T19:13:08Z

Split list into smaller units for translation

Phanect at 16:18, 25 May 2012

2012-05-25T16:18:44Z

Neverendingo: Text replace - "" to ""

2011-06-29T18:30:50Z

Text replace - "</code>" to "</syntaxhighlight>"

Neverendingo: Text replace - "`" to ""`


2011-06-29T18:29:07Z
Text replace - "<code cppqt>" to "<syntaxhighlight lang="cpp-qt">"

				
				
				
				
			
			← Older revision
			Revision as of 18:29, 29 June 2011
			
Line 78:
Line 78:
  * A resource file is read but is never written. A system default is supplied but the user can override this default in his local .kde directory:   * A resource file is read but is never written. A system default is supplied but the user can override this default in his local .kde directory:
    
− <code cppqt> + <syntaxhighlight lang="cpp-qt">
  // Code example   // Code example
  myFile = locate("appdata", "groups.lst")   myFile = locate("appdata", "groups.lst")
Line 86:
Line 86:
  * A resource file is read and written. If the user has no local version of the file the system default is used. The resource file is always written to the users local .kde directory.   * A resource file is read and written. If the user has no local version of the file the system default is used. The resource file is always written to the users local .kde directory.
    
− <code cppqt> + <syntaxhighlight lang="cpp-qt">
  // Code example   // Code example
  myFile = locate("appdata", "groups.lst")   myFile = locate("appdata", "groups.lst")
Line 99:
Line 99:
  * A resource file is read and written. No system default is used if the user has no local version of the file. The resource file is always written to the users local {{path|.kde}} directory.   * A resource file is read and written. No system default is used if the user has no local version of the file. The resource file is always written to the users local {{path|.kde}} directory.
    
− <code cppqt> + <syntaxhighlight lang="cpp-qt">
  // Code example   // Code example
  myFile = locateLocal("appdata", "groups.lst");   myFile = locateLocal("appdata", "groups.lst");



Pino: {{file}} -> {{path}}
2007-05-28T23:56:36Z
{{file}} -> {{path}}

				
				
				
				
			
			← Older revision
			Revision as of 23:56, 28 May 2007
			
Line 46:
Line 46:
  For this it encapsulates all informations from the application   For this it encapsulates all informations from the application
  and applications always refer to a file with a resource type   and applications always refer to a file with a resource type
− (e.g. apps) and a filename (e.g. {{file|Home.desktop}}). In an ideal world + (e.g. apps) and a filename (e.g. {{path|Home.desktop}}). In an ideal world
  the application would make no assumption where this file is and   the application would make no assumption where this file is and
  leaves it up to <tt>KStandardDirs::findResource("apps", "Home.desktop")</tt>   leaves it up to <tt>KStandardDirs::findResource("apps", "Home.desktop")</tt>
Line 97:
Line 97:
  </code>   </code>
    
− * A resource file is read and written. No system default is used if the user has no local version of the file. The resource file is always written to the users local .kde directory. + * A resource file is read and written. No system default is used if the user has no local version of the file. The resource file is always written to the users local {{path|.kde}} directory.
    
  <code cppqt>   <code cppqt>





Dhaumann: Development/Architecture/KDE 3 Architecture/Standard Resources moved to Development/Architecture/KDE3/Standard Resources
2007-03-11T21:34:11Z
Development/Architecture/KDE 3 Architecture/Standard Resources moved to Development/Architecture/KDE3/Standard Resources

			
			← Older revision
			Revision as of 21:34, 11 March 2007
			


Pino at 22:14, 7 March 2007
2007-03-07T22:14:18Z


				
				
				
				
			
			← Older revision
			Revision as of 22:14, 7 March 2007
			
Line 40:
Line 40:
  This is one of the most central classes in kdelibs as   This is one of the most central classes in kdelibs as
  it provides a basic service: it knows where the files   it provides a basic service: it knows where the files
− reside on the user's harddisc. And it's meant to be the + reside on the user's harddisk. And it's meant to be the
  only one that knows - to make the real location as   only one that knows - to make the real location as
  transparent as possible to both the user and the applications.   transparent as possible to both the user and the applications.
Line 46:
Line 46:
  For this it encapsulates all informations from the application   For this it encapsulates all informations from the application
  and applications always refer to a file with a resource type   and applications always refer to a file with a resource type
− (e.g. apps) and a filename (e.g. Home.desktop). In an ideal world + (e.g. apps) and a filename (e.g. {{file|Home.desktop}}). In an ideal world
  the application would make no assumption where this file is and   the application would make no assumption where this file is and
  leaves it up to <tt>KStandardDirs::findResource("apps", "Home.desktop")</tt>   leaves it up to <tt>KStandardDirs::findResource("apps", "Home.desktop")</tt>
  to apply this knowledge.   to apply this knowledge.
    
− The main idea behind KStandardDirs is that there are several + The main idea behind {{class|KStandardDirs}} is that there are several
  toplevel prefixes where files are below. One of this prefixes is   toplevel prefixes where files are below. One of this prefixes is
  the one where the user installed kdelibs into, one where the   the one where the user installed kdelibs into, one where the





Dhaumann: Category:Architecture
2007-01-23T09:33:15Z
Category:Architecture

				
				
				
				
			
			← Older revision
			Revision as of 09:33, 23 January 2007
			
Line 113:
Line 113:
    
  [[Category:KDE3]]   [[Category:KDE3]]
  + [[Category:Architecture]]





CuCullin: Category KDE3
2007-01-10T02:36:22Z
Category KDE3

				
				
				
				
			
			← Older revision
			Revision as of 02:36, 10 January 2007
			
Line 111:
Line 111:
    
  ''Initial Author:'' Stephan Kulow [mailto:coolo@kde.org (coolo@kde.org)]   ''Initial Author:'' Stephan Kulow [mailto:coolo@kde.org (coolo@kde.org)]
  + 
  + [[Category:KDE3]]

@@ Line 2: / Line 2: @@
 <translate>
 '''KDE Architecture - Accessing Standard Resource Directories'''
-== Overview ==
+== Overview == <!--T:2-->
 KDE offers several ways to access the files that your application
 installed on your user's hard disc while making it transparent
@@ Line 15: / Line 17: @@
 expect ''man'' to lookup man pages in <tt>PATH</tt>.
 Similiar to that concept KDE seperates search paths for different
 things to make it simpler to add paths for a specific resource without
@@ Line 20: / Line 23: @@
 requiring you to put everything into one directory.
 The types of resources KDE offers are
 * apps - applications menu (.desktop files)
 * cgi - CGIs to run from khelpcenter</translate><translate>
 * config - configuration files
 * data - where applications store data</translate><translate>
 * exe - executables installed privatly for KDE's use
 * html - HTML documentation</translate><translate>
 * icon - application icons to appear in the window manager or the panel
 * lib - libraries and to be dlopened modules</translate><translate>
 * locale - translation files for KLocale
 * mime - mime types</translate><translate>
 * sound - application sounds
 * toolbar - toolbar pictures
 * wallpaper - wallpapers
 For all of them exist also Makefile aliases that configures created by the development
 tools provided for KDE (e.g. kdevelop) will know about.
-== KStandardDirs ==
+== KStandardDirs == <!--T:13-->
 This is one of the most central classes in kdelibs as
 it provides a basic service: it knows where the files
@@ Line 47: / Line 59: @@
 transparent as possible to both the user and the applications.
 For this it encapsulates all informations from the application
 and applications always refer to a file with a resource type
@@ Line 54: / Line 67: @@
 to apply this knowledge.
 The main idea behind {{class|KStandardDirs}} is that there are several
 toplevel prefixes where files are below. One of this prefixes is
@@ Line 63: / Line 77: @@
 {{path|share/apps/&lt;appname&gt;/pics}}.
 So the search algorithm basicly appends to each prefix each registered
 suffix and tries to locate the file there.
@@ Line 71: / Line 86: @@
 example for icons.
-=== On the usage of <tt>locate</tt> and <tt>locateLocal</tt> ===
+=== On the usage of <tt>locate</tt> and <tt>locateLocal</tt> === <!--T:18-->
 locate and locateLocal are both convenient functions that make the use of
 KStandardDirs as simple as possible. You have however the possibility to
 use the full power of KStandardDirs without them.
 Typical KDE applications use resource files in one out of three ways:
 * A resource file is read but is never written. A system default is supplied but the user can override this default in his local .kde directory:
 <syntaxhighlight lang="cpp-qt">
 // Code example
@@ Line 87: / Line 106: @@
 </syntaxhighlight>
 * A resource file is read and written. If the user has no local version of the file the system default is used. The resource file is always written to the users local .kde directory.
 <syntaxhighlight lang="cpp-qt">
 // Code example
@@ Line 100: / Line 121: @@
 </syntaxhighlight>
 * A resource file is read and written. No system default is used if the user has no local version of the file. The resource file is always written to the users local {{path|.kde}} directory.
 <syntaxhighlight lang="cpp-qt">
 // Code example
@@ Line 113: / Line 136: @@
 </syntaxhighlight>
 ''Initial Author:'' Stephan Kulow [mailto:coolo@kde.org (coolo@kde.org)]
 [[Category:KDE3]]
 [[Category:Architecture]]
 </translate>

@@ Line 23: / Line 23: @@
 * apps - applications menu (.desktop files)
-* cgi - CGIs to run from khelpcenter
+* cgi - CGIs to run from khelpcenter</translate><translate>
 * config - configuration files
-* data - where applications store data
+* data - where applications store data</translate><translate>
 * exe - executables installed privatly for KDE's use
-* html - HTML documentation
+* html - HTML documentation</translate><translate>
 * icon - application icons to appear in the window manager or the panel
-* lib - libraries and to be dlopened modules
+* lib - libraries and to be dlopened modules</translate><translate>
 * locale - translation files for KLocale
-* mime - mime types
+* mime - mime types</translate><translate>
 * sound - application sounds
 * toolbar - toolbar pictures

@@ Line 1: / Line 1: @@
 '''KDE Architecture - Accessing Standard Resource Directories'''
@@ Line 114: / Line 117: @@
 [[Category:KDE3]]
 [[Category:Architecture]]

← Older revision		Revision as of 09:33, 23 January 2007
Line 113:		Line 113:

	[[Category:KDE3]]		[[Category:KDE3]]
		+	[[Category:Architecture]]

← Older revision		Revision as of 02:36, 10 January 2007
Line 111:		Line 111:

	''Initial Author:'' Stephan Kulow [mailto:coolo@kde.org (coolo@kde.org)]		''Initial Author:'' Stephan Kulow [mailto:coolo@kde.org (coolo@kde.org)]
		+
		+	[[Category:KDE3]]