diff options
Diffstat (limited to 'doc/artsbuilder/mcop.docbook')
| -rw-r--r-- | doc/artsbuilder/mcop.docbook | 14 |
1 files changed, 7 insertions, 7 deletions
diff --git a/doc/artsbuilder/mcop.docbook b/doc/artsbuilder/mcop.docbook index f140bff9..ca4a195a 100644 --- a/doc/artsbuilder/mcop.docbook +++ b/doc/artsbuilder/mcop.docbook @@ -1093,7 +1093,7 @@ interface Hello { You pass that through the &IDL; compiler by calling <userinput><command>mcopidl</command> <parameter>hello.idl</parameter></userinput>, which will in turn generate -<filename>hello.cc</filename> and <filename>hello.h</filename>. To +<filename>hello.cpp</filename> and <filename>hello.h</filename>. To implement it, you need to define a C++-class that inherits the skeleton: </para> @@ -1476,7 +1476,7 @@ Marshalling should be easy to implement. <listitem> <para> -Demarshalling requires the receiver to know what type he wants to +Demarshalling requires the receiver to know what type they want to demarshall. </para> </listitem> @@ -1991,7 +1991,7 @@ objects</quote> and <quote>the <acronym>CORBA</acronym> interface</quote> look natural, but it didn't, because <acronym>CORBA</acronym> knew nothing at all about streams. &MCOP; does. Look at the code (something like -<filename>simplesoundserver_impl.cc</filename>). Way better! Streams +<filename>simplesoundserver_impl.cpp</filename>). Way better! Streams can be declared in the interface of modules, and implemented in a natural looking way. </para> @@ -2197,12 +2197,12 @@ that, I am certainly proven wrong. While I do know that &DCOP; basically doesn't know about the data types it sends, so that you could use &DCOP; without using &Qt;, look at how it is used in daily &kde; usage: people send types like -<classname>QString</classname>, <classname>QRect</classname>, +<classname>TQString</classname>, <classname>QRect</classname>, <classname>QPixmap</classname>, <classname>QCString</classname>, ..., around. These use &Qt;-serialization. So if somebody choose to support -&DCOP; in a GNOME program, he would either have to claim to use -<classname>QString</classname>,... types (although he doesn't do so), -and emulate the way &Qt; does the streaming, or he would send other +&DCOP; in a GNOME program, they would either have to claim to use +<classname>TQString</classname>,... types (although they don't do so), +and emulate the way &Qt; does the streaming, or they would send other string, pixmap and rect types around, and thus not be interoperable. </para> |