Getting Started/Set up KDE 4 for development (zh TW) - Revision history

AnneW at 13:45, 18 July 2012

2012-07-18T13:45:49Z

Neverendingo: Text replace - "" to ""

2011-06-29T20:57:13Z

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

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


2011-06-29T20:47:40Z
Text replace - "<code>" to "<syntaxhighlight lang="text">"

				
				
				
				
			
			← Older revision
			Revision as of 20:47, 29 June 2011
			
Line 70:
Line 70:
    
  Although your X server should accept incoming TCP connections, this is often switched off as a distribution default (like with Kubuntu Feisty). When using <tt>kdm</tt> you must edit <tt>/etc/kde3/kdm/kdmrc</tt> as root and make sure it does not contain:   Although your X server should accept incoming TCP connections, this is often switched off as a distribution default (like with Kubuntu Feisty). When using <tt>kdm</tt> you must edit <tt>/etc/kde3/kdm/kdmrc</tt> as root and make sure it does not contain:
− <code>ServerArgsLocal=-nolisten tcp</code> + <syntaxhighlight lang="text">ServerArgsLocal=-nolisten tcp</code>
  Once you have fixed this, you will need to restart your X server. The <tt>xhost</tt> command should no longer return an "unable to open display" error.   Once you have fixed this, you will need to restart your X server. The <tt>xhost</tt> command should no longer return an "unable to open display" error.



Neverendingo: Text replace - "" to ""

2011-06-29T20:41:40Z
Text replace - "<code bash>" to "<syntaxhighlight lang="bash">"
Show changes


Neverendingo: Text replace - "" to ""

2011-06-29T20:38:03Z
Text replace - "<code ini>" to "<syntaxhighlight lang="ini">"

				
				
				
				
			
			← Older revision
			Revision as of 20:38, 29 June 2011
			
Line 121:
Line 121:
  A simple .desktop file that runs KWrite would have the following contents:   A simple .desktop file that runs KWrite would have the following contents:
    
− <code ini> + <syntaxhighlight lang="ini">
  [Desktop Entry]   [Desktop Entry]
  Categories=Qt;KDE;TextEditor;   Categories=Qt;KDE;TextEditor;
Line 183:
Line 183:
  On Kubuntu, you can enable it by changing   On Kubuntu, you can enable it by changing
    
− <code ini> + <syntaxhighlight lang="ini">
  [Xdmcp]   [Xdmcp]
  # Whether KDM should listen to incoming XDMCP requests.   # Whether KDM should listen to incoming XDMCP requests.
Line 192:
Line 192:
  in {{path|/etc/kde3/kdm/kdmrc}} to   in {{path|/etc/kde3/kdm/kdmrc}} to
    
− <code ini> + <syntaxhighlight lang="ini">
  [Xdmcp]   [Xdmcp]
  # Whether KDM should listen to incoming XDMCP requests.   # Whether KDM should listen to incoming XDMCP requests.
Line 259:
Line 259:
  or you can can add it to your login manager. If you are using KDM (or a compatible login manager) this is done by creating a .desktop file in either {{path|`kde-config --prefix`/share/apps/kdm/sessions/}} or in {{path|/usr/share/xsessions/}}. The easiest thing to do is to copy an existing {{path|kde.desktop}} file and name it {{path|kde4.desktop}}. Open this new .desktop file in a text editor and change the <tt>Exec</tt>, <tt>TryExec</tt> and <tt>Name</tt> entries to look something like this:   or you can can add it to your login manager. If you are using KDM (or a compatible login manager) this is done by creating a .desktop file in either {{path|`kde-config --prefix`/share/apps/kdm/sessions/}} or in {{path|/usr/share/xsessions/}}. The easiest thing to do is to copy an existing {{path|kde.desktop}} file and name it {{path|kde4.desktop}}. Open this new .desktop file in a text editor and change the <tt>Exec</tt>, <tt>TryExec</tt> and <tt>Name</tt> entries to look something like this:
    
− <code ini> + <syntaxhighlight lang="ini">
  Exec=$HOME/kde/bin/startkde   Exec=$HOME/kde/bin/startkde
  TryExec=$HOME/kde/bin/startkde   TryExec=$HOME/kde/bin/startkde
Line 273:
Line 273:
    
  this   this
− <code ini>kdehome=$HOME/.kde</code> + <syntaxhighlight lang="ini">kdehome=$HOME/.kde</code>
  to this   to this
− <code ini>kdehome=$HOME/.kde4</code> + <syntaxhighlight lang="ini">kdehome=$HOME/.kde4</code>
  or paste this   or paste this
− <code ini> + <syntaxhighlight lang="ini">
  export KDEDIR=`kde4-config --prefix`   export KDEDIR=`kde4-config --prefix`
  export LD_LIBRARY_PATH=$KDEDIR/lib   export LD_LIBRARY_PATH=$KDEDIR/lib



Alisha at 04:13, 3 December 2009
2009-12-03T04:13:05Z


				
				
				
				
			
			← Older revision
			Revision as of 04:13, 3 December 2009
			
Line 2:
Line 2:
  {{TutorialBrowser_(zh_TW)|   {{TutorialBrowser_(zh_TW)|
    
− series=開始| + series=入門|
    
  name=建立開發用的 KDE 4|   name=建立開發用的 KDE 4|
Line 292:
Line 292:
  This section will explain how to use KDevelop 3.4 to develop KDE 4 applications. If you have any questions, corrections or rants about this section, please post them on the discussion page.   This section will explain how to use KDevelop 3.4 to develop KDE 4 applications. If you have any questions, corrections or rants about this section, please post them on the discussion page.
    
− ==== Prerequisites ==== + ==== 事前需求====
    
  You need at least KDevelop 3.4 for this, which is still a KDE 3 application. Versions lower than 3.4 do not have Qt 4 support among other things. The KDE 4 version of KDevelop is not yet ready for serious development. You can get KDevelop at the [http://www.kdevelop.org/index.html?filename=3.4/download.html KDevelop homepage]. Make sure you install KDevelop like all other KDE 3 applications, '''not''' with your ''kde-devel'' user.     You need at least KDevelop 3.4 for this, which is still a KDE 3 application. Versions lower than 3.4 do not have Qt 4 support among other things. The KDE 4 version of KDevelop is not yet ready for serious development. You can get KDevelop at the [http://www.kdevelop.org/index.html?filename=3.4/download.html KDevelop homepage]. Make sure you install KDevelop like all other KDE 3 applications, '''not''' with your ''kde-devel'' user.  
Line 308:
Line 308:
    su - kde-devel     su - kde-devel
    
− ==== Setting up the environment ==== + ==== 建立環境 ====
    
  KDevelop has no native support for CMake projects. Fortunately, CMake has the ability to generate KDevelop project files itself. In order to do this, you need to pass the ''-GKDevelop3'' flag to the ''cmake'' command. This tells CMake to generate project files for KDevelop alongside the normal makefiles. The best way to do this is to modify your ''cmakekde'' function in your [[Getting_Started/Increased_Productivity_in_KDE4_with_Scripts/.bashrc|{{path|.bashrc}}]]. Just change   KDevelop has no native support for CMake projects. Fortunately, CMake has the ability to generate KDevelop project files itself. In order to do this, you need to pass the ''-GKDevelop3'' flag to the ''cmake'' command. This tells CMake to generate project files for KDevelop alongside the normal makefiles. The best way to do this is to modify your ''cmakekde'' function in your [[Getting_Started/Increased_Productivity_in_KDE4_with_Scripts/.bashrc|{{path|.bashrc}}]]. Just change
Line 370:
Line 370:
  -->   -->
    
− ===== TroubleShooting ===== + ===== 疑難排解 =====
    
  '''Symptome:''' kdevelop says "cannot talk to klauncher". You cannot open a file.   '''Symptome:''' kdevelop says "cannot talk to klauncher". You cannot open a file.
Line 492:
Line 492:
  Refer to the [http://docs.kde.org/development/en/kdevelop/kdevelop/ KDevelop manual] for general help using KDevelop. The following section will only deal with special cases for KDE 4.   Refer to the [http://docs.kde.org/development/en/kdevelop/kdevelop/ KDevelop manual] for general help using KDevelop. The following section will only deal with special cases for KDE 4.
    
− ===== Debugging ===== + ===== 除錯 =====
    
  KDE apps have many symbols, which means that you need a lot of memory to get a decent loading times for debugging. To quote a GDB developer: "I would be reluctant to debug KDE on something with <1GB RAM."   KDE apps have many symbols, which means that you need a lot of memory to get a decent loading times for debugging. To quote a GDB developer: "I would be reluctant to debug KDE on something with <1GB RAM."
Line 603:
Line 603:
  : Choose Project -> Properties -> C/C++ Build -> Builder Settings. Un-tag "use default build command", set "cmake" instead. Choose Project -> Properties -> C/C++ Build -> Behavior. Replace "all" by ".".   : Choose Project -> Properties -> C/C++ Build -> Builder Settings. Un-tag "use default build command", set "cmake" instead. Choose Project -> Properties -> C/C++ Build -> Behavior. Replace "all" by ".".
    
− ==== See also ==== + ==== 另見 ====
    
  * http://javathreads.de/2008/07/subversion-unter-eclipse-ganymede-konfigurieren/   * http://javathreads.de/2008/07/subversion-unter-eclipse-ganymede-konfigurieren/



Alisha at 13:58, 29 November 2009
2009-11-29T13:58:42Z


				
				
				
				
			
			← Older revision
			Revision as of 13:58, 29 November 2009
			
Line 502:
Line 502:
  KDevelop does not yet support modifing the CMake build system. This means you can not use KDevelop to add or remove files from the project or to change any other aspect of your project's build process.   KDevelop does not yet support modifing the CMake build system. This means you can not use KDevelop to add or remove files from the project or to change any other aspect of your project's build process.
    
− You need to modify the CMake files by hand and then rerun <tt>cmakekde</tt> instead. Read the [[Development/Tutorials/CMake|CMake tutorial]] to learn how to do this. + You need to modify the CMake files by hand and then rerun <tt>cmakekde</tt> instead. Read the [[Development/Tutorials/CMake_(zh_TW)|CMake tutorial]] to learn how to do this.
  }}   }}
    



Alisha at 16:06, 10 November 2009
2009-11-10T16:06:30Z


				
				
				
				
			
			← Older revision
			Revision as of 16:06, 10 November 2009
			
Line 608:
Line 608:
  * http://nienhueser.de/blog/?p=19     * http://nienhueser.de/blog/?p=19  
    
− === QtCreator === + === Qt Creator ===
− This describes how to use QtCreator to develop KDE 4 applications. It has been tested with QtCreator 1.2.80 and SUSE Linux 11.1 but should work same or similar with every combination. As an example KDE application we use [http://userbase.kde.org/ktimetracker ktimetracker] from the kdepim module, other applications short work analog. + 這裡說明如何使用 Qt Creator 開發 KDE 4 應用程式。It has been tested with QtCreator 1.2.80 and SUSE Linux 11.1 but should work same or similar with every combination.我們使用來自 kdepim 模塊的[http://userbase.kde.org/ktimetracker ktimetracker]作為 KDE 應用程式的範例。
    
− ==== Load an existing project ==== + ==== 載入現有專案 ====
− As discussed here we use ktimetracker as example project. +  
− * Import the CMakeLists.txt file + 我們使用 ktimetracker 作為範例專案。
  + * 匯入 CMakeLists.txt 檔案
  File -> Open -> kdepim/CMakeLists.txt.   File -> Open -> kdepim/CMakeLists.txt.
− * Configure qtcreator to build only ktimetracker + * 配置 Qt Creator 只建構 ktimetracker
  Projects -> ktimetracker -> build settings -> Add a configuration ktimetracker.   Projects -> ktimetracker -> build settings -> Add a configuration ktimetracker.
    
  As build directory choose /home/youruser/kdepim/ktimetracker. As arguments for cmake use ...   As build directory choose /home/youruser/kdepim/ktimetracker. As arguments for cmake use ...
    
− ==== Start a KDE project ====   + ==== 開始 KDE 專案 ====  
− To start a new project you need to tell qtcreator to use the KDE libraries when building. So, choose File -> New... and create your project. We will call it ''yourproject'' here. To be able to use KDE's libraries, go to your home directory, cd into ''yourproject'' and modify ''yourproject.pro''. Add a line + 想要開始一個新的專案你需要告訴 Qt Creator 建構時使用 KDE 程式庫。因此，選擇 File -> New... 並創建您的專案。在這裡我們稱為''yourproject''。為了能夠使用 KDE 程式庫，在你的家目錄，cd 進入''yourproject''並修改 ''yourproject.pro''。加上
    LIBS += -lkdeui     LIBS += -lkdeui
    
  [[Category:KDE4]]   [[Category:KDE4]]



Alisha at 03:47, 6 November 2009
2009-11-06T03:47:04Z


				
				
				
				
			
			← Older revision
			Revision as of 03:47, 6 November 2009
			
Line 33:
Line 33:
  ==== 在普通的 shell 裡使用 sux ====   ==== 在普通的 shell 裡使用 sux ====
    
− 使用這個方法需要 '''sux''' 工具(http://fgouget.free.fr/sux/sux-readme.shtml )。'''sux''' 在大多數發行版上都有提供。Otherwise you could rely on the ''normal shell without sux'' method below. '''sux''' allows you to change to another user with an implicit managing of the X forwarding details (authentication and DISPLAY exporting) in a clean and simple way. + 使用這個方法需要 '''sux''' 工具(http://fgouget.free.fr/sux/sux-readme.shtml )。'''sux''' 在大多數發行版上都有提供。當然你也可以參考下一篇的'' 在普通的 shell 裡不用 sux''文件。'''sux''' 可以讓您用一種干淨而簡潔的方式在切換到其他使用者帳號時隱式地管理 X 轉發（認證和顯示輸出）。
    
− To login, type <code bash>sux - kde-devel</code> + 登錄時請輸入 <code bash>sux - kde-devel</code>
  +  
  + 您的{{path|[[Getting_Started/Increased_Productivity_in_KDE4_with_Scripts/.bashrc|.bashrc]]}}腳本將幫助您正確地建立所有環境變量和其他相關配置。如果要啟動一個應用程式，只需簡單地輸入程式名稱；例如 
  +  
  + <code bash>kwrite</code>
    
− All environment variables and everything else should be set up correctly by your {{path|[[Getting_Started/Increased_Productivity_in_KDE4_with_Scripts/.bashrc|.bashrc]]}}. To start an application, simply type it's name; for example <code bash>kwrite</code>  
  {{Note_(zh_TW)|   {{Note_(zh_TW)|
− If you get errors about missing mimetypes or such, try the following: + 如果您遇到諸如 MIME 類型丟失的錯誤，請嘗試：
− * run <code bash>unset XDG_DATA_DIRS ; kbuildsycoca4</code> + * 執行 <code bash>unset XDG_DATA_DIRS ; kbuildsycoca4</code>
  }}   }}
    
  ==== 在普通的 shell 裡不用 sux ====   ==== 在普通的 shell 裡不用 sux ====
− The simplest method to launch KDE 4 applications is using <tt>su</tt> to login as the <tt>kde-devel</tt> user and then simply start any KDE 4 application from command line. To login, type + 啟動 KDE 4 應用程式最簡單的方法是使用 <tt>su</tt> 登錄 <tt>kde-devel</tt> 使用者，然後從命令列啟動程式。請輸入以下文字登錄
  +  
  <code bash>su - kde-devel</code>   <code bash>su - kde-devel</code>
− and then, after entering your password +  
  + 然後，輸入你的密碼
  +  
  <code bash>export DISPLAY=:0</code>   <code bash>export DISPLAY=:0</code>
− {{Note_(zh_TW)|Exporting the <tt>DISPLAY</tt> variable is necessary so that the KDE 4 applications appear on your normal KDE 3 desktop.}} +  
− All environment variables and everything else should be set up correctly by your {{path|[[Getting_Started/Increased_Productivity_in_KDE4_with_Scripts/.bashrc|.bashrc]]}}. To start an application, simply type it's name; for example <code bash>kwrite</code> + {{Note_(zh_TW)|必須導入<tt>DISPLAY</tt>變數，這樣 KDE 4 程式才能在 KDE 3 桌面顯示並運行。}}
  +  
  + 所有的環境變數和其他設定應該參照下面的連接設置正確{{path|[[Getting_Started/Increased_Productivity_in_KDE4_with_Scripts/.bashrc|.bashrc]]}}。如果想要啟動一個程式只需要簡單輸入程序的名字就可以了;例如
  + <code bash>kwrite</code>
  +  
  {{Note_(zh_TW)|   {{Note_(zh_TW)|
  If you get errors about missing mimetypes or such, try the following:   If you get errors about missing mimetypes or such, try the following:



Alisha at 15:51, 18 October 2009
2009-10-18T15:51:29Z


				
				
				
				
			
			← Older revision
			Revision as of 15:51, 18 October 2009
			
Line 33:
Line 33:
  ==== 在普通的 shell 裡使用 sux ====   ==== 在普通的 shell 裡使用 sux ====
    
− 使用這個方法需要 '''sux''' 工具(http://fgouget.free.fr/sux/sux-readme.shtml)。'''sux''' 提供在大多數發行版上。Otherwise you could rely on the ''normal shell without sux'' method below. '''sux''' allows you to change to another user with an implicit managing of the X forwarding details (authentication and DISPLAY exporting) in a clean and simple way. + 使用這個方法需要 '''sux''' 工具(http://fgouget.free.fr/sux/sux-readme.shtml )。'''sux''' 在大多數發行版上都有提供。Otherwise you could rely on the ''normal shell without sux'' method below. '''sux''' allows you to change to another user with an implicit managing of the X forwarding details (authentication and DISPLAY exporting) in a clean and simple way.
    
  To login, type <code bash>sux - kde-devel</code>   To login, type <code bash>sux - kde-devel</code>
Line 82:
Line 82:
  <code bash>ssh -X kde-devel@localhost kwrite</code>   <code bash>ssh -X kde-devel@localhost kwrite</code>
    
− {{Note| + {{Note_(zh_TW)|
  If this gives you any errors, try the troubleshooting tips from the section above.   If this gives you any errors, try the troubleshooting tips from the section above.
  }}   }}
Line 97:
Line 97:
  <code bash>ssh -X kde-devel@localhost $HOME/kde/bin/kwrite</code>   <code bash>ssh -X kde-devel@localhost $HOME/kde/bin/kwrite</code>
    
− {{warning|Using a passwordless SSH login has certain '''security risks''', so make sure you protect your <tt>~/.ssh/id_rsa</tt> file by restricting access to it with   + {{warning_(zh_TW)|Using a passwordless SSH login has certain '''security risks''', so make sure you protect your <tt>~/.ssh/id_rsa</tt> file by restricting access to it with  
  <code bash>chmod og-xrw ~/.ssh/id_rsa</code>(although the file should have these permissions when it is created)}}   <code bash>chmod og-xrw ~/.ssh/id_rsa</code>(although the file should have these permissions when it is created)}}
    
  ===== SSH 桌面檔案 =====   ===== SSH 桌面檔案 =====
  If you want to be able to launch apps more easily than running them with an SSH command from the command line, one way is to create <tt>.desktop</tt> files that <tt>ssh</tt> into the other account.     If you want to be able to launch apps more easily than running them with an SSH command from the command line, one way is to create <tt>.desktop</tt> files that <tt>ssh</tt> into the other account.  
− {{Note|This will only be useful if your desktop environment supports .desktop files, but at least KDE and GNOME do.}} + {{Note_(zh_TW)|This will only be useful if your desktop environment supports .desktop files, but at least KDE and GNOME do.}}
    
  You can start with an existing .desktop file as a template (like one from your desktop) or you can make one from scratch. The main idea is to prefix the command being run with this string:   You can start with an existing .desktop file as a template (like one from your desktop) or you can make one from scratch. The main idea is to prefix the command being run with this string:
Line 233:
Line 233:
    
  The above code assumes you work with user ''kde-devel''.   The above code assumes you work with user ''kde-devel''.
− {{Note|In most cases you have to replace ''startkde-modified'' with ''startkde''}} + {{Note_(zh_TW)|In most cases you have to replace ''startkde-modified'' with ''startkde''}}
  -----   -----
    
Line 385:
Line 385:
  Now it is time to open the project you want to work on by clicking ''Project->Open Project...''. The project files are located in the build directory. For example, if you want to work on Konsole, you need to open {{path|$KDE_BUILD/KDE/kdebase/apps/konsole/konsole.kdevelop}}. You now need to adjust a few project-specific settings in ''Project->Project Options''. You need to do this every time you start to work on a different project.   Now it is time to open the project you want to work on by clicking ''Project->Open Project...''. The project files are located in the build directory. For example, if you want to work on Konsole, you need to open {{path|$KDE_BUILD/KDE/kdebase/apps/konsole/konsole.kdevelop}}. You now need to adjust a few project-specific settings in ''Project->Project Options''. You need to do this every time you start to work on a different project.
    
− {{note| + {{note_(zh_TW)|
  Sometimes, a KDevelop project file is not present for the folder you want to work on.   Sometimes, a KDevelop project file is not present for the folder you want to work on.
    
Line 400:
Line 400:
  :Now, add the database for Qt 4 by selecting ''KDevelop Qt4 PCS Importer'' this time. You need to select the Qt 4 include directory, which is {{path|$HOME/qt-copy/include}}.   :Now, add the database for Qt 4 by selecting ''KDevelop Qt4 PCS Importer'' this time. You need to select the Qt 4 include directory, which is {{path|$HOME/qt-copy/include}}.
    
− {{note|The Qt4 PCS Importer is only needed if you didn't install Qt4, i.e. you use it directly from the build directory. The drawback of using the Qt4 importer is that it doesn't show progress and the application seems to hang while it imports. The alternative is to use the Custom Directory PCS Importer for this too}} + {{note_(zh_TW)|The Qt4 PCS Importer is only needed if you didn't install Qt4, i.e. you use it directly from the build directory. The drawback of using the Qt4 importer is that it doesn't show progress and the application seems to hang while it imports. The alternative is to use the Custom Directory PCS Importer for this too}}
    
  * ''C++ Support->Qt Options''   * ''C++ Support->Qt Options''
Line 495:
Line 495:
  }}   }}
    
− {{tip|When you work on libraries, you first need to install them before you can test or debug your changes.   + {{tip_(zh_TW)|When you work on libraries, you first need to install them before you can test or debug your changes.  
  Since this is cumbersome and time consuming, you should create symlinks ''(ln -s)'' pointing from the build directory to the installation directory for all affected libraries.     Since this is cumbersome and time consuming, you should create symlinks ''(ln -s)'' pointing from the build directory to the installation directory for all affected libraries.

← Older revision		Revision as of 13:45, 18 July 2012
Line 1:		Line 1:
−	~~{{Template:I18n/Language Navigation Bar\|Getting_Started/Set_up_KDE_4_for_development}}~~	+
	{{TutorialBrowser_(zh_TW)\|		{{TutorialBrowser_(zh_TW)\|