From 36d1594949e416e812ed681ed3c84d80649fbf20 Mon Sep 17 00:00:00 2001 From: Michele Calgaro Date: Fri, 28 Sep 2018 14:42:41 +0900 Subject: qt -> tqt conversion: kdeqt -> kdetqt qtkde -> tqtkde qtdesigner -> tqtdesigner Signed-off-by: Michele Calgaro --- doc/tdevelop/unixdev.docbook | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) (limited to 'doc') diff --git a/doc/tdevelop/unixdev.docbook b/doc/tdevelop/unixdev.docbook index 8151f30b..0687651e 100644 --- a/doc/tdevelop/unixdev.docbook +++ b/doc/tdevelop/unixdev.docbook @@ -143,7 +143,7 @@ The main drawback of CORBA is its rather low speed. While this may be tolerable DCOP -Another evolution on &UNIX;-like scripting is the DCOP protocol which was devised for communication between &kde; applications to overcome the limitations of CORBA. +Another evolution on &UNIX;-like scripting is the DCOP protocol which was devised for communication between &kde; applications to overcome the limitations of CORBA. &DCOP; stands for Desktop Communication Protocol and is implemented as a simple IPC/RPC mechanism built to operate over sockets. In effect this provides facilities similar to the traditional &UNIX; pipe mechanism. @@ -155,7 +155,7 @@ Traditional shell scripting is based on fairly small tool programs which were de There are drawbacks, however. To use &DCOP; a program must be designed to contain a special &DCOP; interface. And the &DCOP; communication process runs somewhat slowly (although a lot faster than CORBA). But it returns much of the power and flexibility of &UNIX; scripting to high-level programs which are based on a graphical user interface. -For more information, see the DCOP: Desktop COmmunications Protocol paper or The &DCOP; Desktop Communication Protocol library &API; reference of the &kde; dcop library. +For more information, see the DCOP: Desktop COmmunications Protocol paper or The &DCOP; Desktop Communication Protocol library &API; reference of the &kde; dcop library. -- cgit v1.2.3