Development/Architecture/KDE4/Starting Other Programs (zh TW) - Revision history

Alisha at 07:05, 3 January 2010

2010-01-03T07:05:13Z

Alisha at 03:31, 3 December 2009

2009-12-03T03:31:16Z

Alisha at 15:49, 1 December 2009

2009-12-01T15:49:36Z

Alisha at 15:48, 1 December 2009

2009-12-01T15:48:34Z

Alisha: Created page with '{{Template:I18n/Language Navigation Bar|Development/Architecture/KDE4/Starting Other Programs}} '''KDE 架構 - 啟動程式''' 在 KDE 中，有許多方法可以讓您的應...'

2009-12-01T15:09:03Z

Created page with '{{Template:I18n/Language Navigation Bar|Development/Architecture/KDE4/Starting Other Programs}} '''KDE 架構 - 啟動程式''' 在 KDE 中，有許多方法可以讓您的應...'

New page

{{Template:I18n/Language Navigation Bar|Development/Architecture/KDE4/Starting Other Programs}}

'''KDE 架構 - 啟動程式'''

在 KDE 中，有許多方法可以讓您的應用程式啟動其他程式。這裡總結了一些你應該和不應該使用的方法和理由。

== fork + exec ==
You never want to use this unless you have a very good reason why it is impossible to use KProcess.

== system ==
Other than the reasons about why you should not use fork + exec, system is also synchronous, thus it will block the application that run it.

== KProcess ==
You want to use [http://api.kde.org/4.x-api/kdelibs-apidocs/kdecore/html/classKProcess.html KProcess] class if you need to start a new process which needs to be a child of your process, e.g. because you want to catch stdout/stderr or need to send it data via stdin. You should never use this to start other KDE applications (unless your application is a debugger :-)

== KToolInvocation::startServiceByDesktopPath ==
[http://api.kde.org/4.x-api/kdelibs-apidocs/kdecore/html/classKToolInvocation.html KToolInvocation::startServiceByDesktopPath] is the preferred way to launch desktop (KDE/Gnome/X) applications or KDE services. The application/service must have a .desktop file, and you must know the name of that file. KToolInvocation asks the klauncher process, via DBUS, to start the program.
=== klauncher ===
klauncher will wait until the application registers to DBUS if the desktop file specifies the [http://api.kde.org/4.x-api/kdelibs-apidocs/kdecore/html/classKToolInvocation.html#_details X-DBUS-StartupType] key. This allows to make DBUS calls to the application once startServiceByDesktopPath returns, without the risk of race conditions. Note that klauncher needs to know under which name the application will register to DBUS: by default that is assumed to be org.kde.<i>binaryname</i>, but you can configure this by setting X-DBUS-ServiceName in the .desktop file. If you don't, you will get an error from klauncher which will think the application failed to start, since the expected dbus name never showed up.
=== kdeinit ===
klauncher makes use of KDEinit for increased startup performance and lower memory usage. These benefits only apply to applications available as KDEinit loadable module (KLM).

== KRun ==
Generic way to open documents/applications/shell commands. Uses startServiceByDesktopPath where applicable. Offers the additional benefit of startup-notification.<br/> [http://api.kde.org/4.x-api/kdelibs-apidocs/kio/html/classKRun.html KRun] can start any application, from the binary or the desktop file, it will determine the mimetype of a file before running the preferred handler for it, and it can also start shell commands. This makes KRun the recommended way to run another program in KDE.

== KToolInvocation::invokeBrowser ==
[http://api.kde.org/4.x-api/kdelibs-apidocs/kdecore/html/classKToolInvocation.html KToolInvocation::invokeBrowser] launches a web browser. The difference with using the more generic KRun on the webpage URL is that KRun has to determine the mimetype of the URL first (which, for HTTP, involves starting a download to read the headers), so if you know that the URL is an HTML webpage, use invokeBrowser, it will be faster.

More details: the problem with KRun for webpages is that it delays the appearance of the browser window, and if the user's preferred browser is a non-kde application like firefox then it has to start a second download while konqueror which can reuse the kioslave started by KRun. On the other hand if the URL might be an image or anything else than html, then KRun is the right solution, so that the right application is started.

[[Category:KDE4]]
[[Category:Architecture]]

← Older revision		Revision as of 07:05, 3 January 2010
Line 1:		Line 1:
−	{{Template:I18n/Language Navigation ~~Bar~~\|Development/Architecture/KDE4/Starting Other Programs}}	+	{{Template:I18n/Language Navigation Bar_(zh_TW)\|Development/Architecture/KDE4/Starting Other Programs}}

	'''KDE 架構 - 啟動程式'''		'''KDE 架構 - 啟動程式'''

@@ Line 28: / Line 28: @@
 == KRun ==
-打開文件、應用程式、Shell指令的一般方法。適當的使用 startServiceByDesktopPath，提供額外的啟動通知好處。<br/> [http://api.kde.org/4.x-api/kdelibs-apidocs/kio/html/classKRun.html KRun] 可以從二進位檔或 desktop檔啟動任何應用程式。他會判斷檔案的 MIME 類型，再執行最佳的處理方式，這同樣可以啟動 Shell 指令。This makes KRun the recommended way to run another program in KDE.
+打開文件、應用程式、Shell指令的一般方法。適當的使用 startServiceByDesktopPath，可以提供額外的啟動通知好處。<br/> [http://api.kde.org/4.x-api/kdelibs-apidocs/kio/html/classKRun.html KRun] 可以從二進位檔或 desktop檔啟動任何應用程式。他會判斷檔案的 MIME 類型，再執行最佳的處理方式，這同樣可以啟動 Shell 指令。This makes KRun the recommended way to run another program in KDE.
 == KToolInvocation::invokeBrowser ==

@@ Line 10: / Line 10: @@
 == system ==
-Other than the reasons about why you should not use fork + exec, system is also synchronous, thus it will block the application that run it.
 == KProcess ==
@@ Line 21: / Line 22: @@
 === klauncher ===
-klauncher will wait until the application registers to DBUS if the desktop file specifies the [http://api.kde.org/4.x-api/kdelibs-apidocs/kdecore/html/classKToolInvocation.html#_details X-DBUS-StartupType] key. This allows to make DBUS calls to the application once startServiceByDesktopPath returns, without the risk of race conditions. Note that klauncher needs to know under which name the application will register to DBUS: by default that is assumed to be org.kde.<i>binaryname</i>, but you can configure this by setting X-DBUS-ServiceName in the .desktop file. If you don't, you will get an error from klauncher which will think the application failed to start, since the expected dbus name never showed up.
+如果 desktop 檔指定了[http://api.kde.org/4.x-api/kdelibs-apidocs/kdecore/html/classKToolInvocation.html#_details X-DBUS-StartupType]鍵，那 KLauncher 將一直等到應用程式註冊到 DBUS 上。一旦 startServiceByDesktopPath 返回，DBUS才會呼叫用程式，而避免了競爭的風險。注意 KLauncher 需要知道應用程式註冊 DBUS 的名稱；預設是 org.kde.<i>二進位檔名</i>，但你也可以透過 .desktop 檔裡的 X-DBUS-ServiceName 配置他。如果你不這麼做，KLauncher 會拋出一個錯誤，說這個應用程式無法啟動，因為期望的 dbus 名稱沒有出現。
 === kdeinit ===
-klauncher makes use of KDEinit for increased startup performance and lower memory usage. These benefits only apply to applications available as KDEinit loadable module (KLM).
+klauncher 利用 KDEinit 來提高啟動性能和降低記憶體使用量。這只適合應用程式可用於 KDEinit loadable module（KLM）時。
 == KRun ==
-打開文件、應用程式、Shell指令的一般方法。適當的使用 startServiceByDesktopPath，可以提供額外的啟動通知好處。<br/> [http://api.kde.org/4.x-api/kdelibs-apidocs/kio/html/classKRun.html KRun] 可以從二進位檔或 desktop檔啟動任何應用程式。他會判斷檔案的 MIME 類型，再執行最佳的處理方式，這同樣可以啟動 Shell 指令。This makes KRun the recommended way to run another program in KDE.
+打開文件、應用程式、Shell指令的一般方法。適當的使用 startServiceByDesktopPath，可以提供額外的啟動通知好處。<br/> [http://api.kde.org/4.x-api/kdelibs-apidocs/kio/html/classKRun.html KRun] 可以從二進位檔或 desktop 檔啟動任何應用程式。他會判斷檔案的 MIME 類型，再執行最佳的處理方式，這同樣可以啟動 Shell 指令。這就是我們推薦使用 KRun 執行其他程式的原因。
 == KToolInvocation::invokeBrowser ==
-[http://api.kde.org/4.x-api/kdelibs-apidocs/kdecore/html/classKToolInvocation.html KToolInvocation::invokeBrowser] launches a web browser. The difference with using the more generic KRun on the webpage URL is that KRun has to determine the mimetype of the URL first (which, for HTTP, involves starting a download to read the headers), so if you know that the URL is an HTML webpage, use invokeBrowser, it will be faster.
+[http://api.kde.org/4.x-api/kdelibs-apidocs/kdecore/html/classKToolInvocation.html KToolInvocation::invokeBrowser] 將啟動網頁瀏覽器。相較於通用性的 KRun，網頁 URL 在 KRun 會先測定 URL 的 MIME類型（如果是HTTP，那麼他會開始下載，並讀取標頭）。如果你已經知道 URL 是一個 HTML 網頁，直接用 invokeBrowser 會快很多。
-More details: the problem with KRun for webpages is that it delays the appearance of the  browser window, and if the user's preferred browser is a non-kde application like firefox then it has to start a second download while konqueror which can reuse the kioslave started by KRun. On the other hand if the URL might be an image or anything else than html, then KRun is the right solution, so that the right application is started.
+更多細節：the problem with KRun for webpages is that it delays the appearance of the  browser window, and if the user's preferred browser is a non-kde application like firefox then it has to start a second download while konqueror which can reuse the kioslave started by KRun. On the other hand if the URL might be an image or anything else than html, then KRun is the right solution, so that the right application is started.
 [[Category:KDE4]]
 [[Category:Architecture]]