diff options
Diffstat (limited to 'doc/man/man3/tqnetworkprotocol.3qt')
| -rw-r--r-- | doc/man/man3/tqnetworkprotocol.3qt | 22 |
1 files changed, 11 insertions, 11 deletions
diff --git a/doc/man/man3/tqnetworkprotocol.3qt b/doc/man/man3/tqnetworkprotocol.3qt index 4503d3437..25eb00d0f 100644 --- a/doc/man/man3/tqnetworkprotocol.3qt +++ b/doc/man/man3/tqnetworkprotocol.3qt @@ -135,13 +135,13 @@ Inherited by QFtp, QHttp, and QLocalFs. .SH DESCRIPTION The QNetworkProtocol class provides a common API for network protocols. .PP -This is a base class which should be used for network protocols implementations that can then be used in Qt (e.g. in the file dialog) together with the QUrlOperator. +This is a base class which should be used for network protocols implementations that can then be used in TQt (e.g. in the file dialog) together with the QUrlOperator. .PP The easiest way to implement a new network protocol is to reimplement the operation*() methods, e.g. operationGet(), etc. Only the supported operations should be reimplemented. To specify which operations are supported, also reimplement supportedOperations() and return an int that is OR'd together using the supported operations from the QNetworkProtocol::Operation enum. .PP -When you implement a network protocol this way, it is important to emit the correct signals. Also, always emit the finished() signal when an operation is done (on success \fIand\fR on failure). Qt relies on correctly emitted finished() signals. +When you implement a network protocol this way, it is important to emit the correct signals. Also, always emit the finished() signal when an operation is done (on success \fIand\fR on failure). TQt relies on correctly emitted finished() signals. .PP -For a detailed description of the Qt Network Architecture and how to implement and use network protocols in Qt, see the Qt Network Documentation. +For a detailed description of the TQt Network Architecture and how to implement and use network protocols in Qt, see the TQt Network Documentation. .PP See also Input/Output and Networking. .SS "Member Type Documentation" @@ -285,7 +285,7 @@ When implementing your own network protocol and reading children, you usually do .SH "void QNetworkProtocol::operationGet ( QNetworkOperation * op )\fC [virtual protected]\fR" When implementing a new network protocol, this method should be reimplemented if the protocol supports getting data; this method should then process the QNetworkOperation. .PP -When you reimplement this method it's very important that you emit the correct signals at the correct time (especially the finished() signal after processing an operation). Take a look at the Qt Network Documentation which describes in detail how to reimplement this method. You may also want to look at the example implementation in examples/network/networkprotocol/nntp.cpp. +When you reimplement this method it's very important that you emit the correct signals at the correct time (especially the finished() signal after processing an operation). Take a look at the TQt Network Documentation which describes in detail how to reimplement this method. You may also want to look at the example implementation in examples/network/networkprotocol/nntp.cpp. .PP \fIop\fR is the pointer to the operation object which contains all the information on the operation that has finished, including the state, etc. .PP @@ -295,7 +295,7 @@ Returns the operation, which is being processed, or 0 of no operation is being p .SH "void QNetworkProtocol::operationListChildren ( QNetworkOperation * op )\fC [virtual protected]\fR" When implementing a new network protocol, this method should be reimplemented if the protocol supports listing children (files); this method should then process this QNetworkOperation. .PP -When you reimplement this method it's very important that you emit the correct signals at the correct time (especially the finished() signal after processing an operation). Take a look at the Qt Network Documentation which describes in detail how to reimplement this method. You may also want to look at the example implementation in examples/network/networkprotocol/nntp.cpp. +When you reimplement this method it's very important that you emit the correct signals at the correct time (especially the finished() signal after processing an operation). Take a look at the TQt Network Documentation which describes in detail how to reimplement this method. You may also want to look at the example implementation in examples/network/networkprotocol/nntp.cpp. .PP \fIop\fR is the pointer to the operation object which contains all the information on the operation that has finished, including the state, etc. .PP @@ -303,25 +303,25 @@ Example: network/networkprotocol/nntp.cpp. .SH "void QNetworkProtocol::operationMkDir ( QNetworkOperation * op )\fC [virtual protected]\fR" When implementing a new network protocol, this method should be reimplemented if the protocol supports making directories; this method should then process this QNetworkOperation. .PP -When you reimplement this method it's very important that you emit the correct signals at the correct time (especially the finished() signal after processing an operation). Take a look at the Qt Network Documentation which describes in detail how to reimplement this method. You may also want to look at the example implementation in examples/network/networkprotocol/nntp.cpp. +When you reimplement this method it's very important that you emit the correct signals at the correct time (especially the finished() signal after processing an operation). Take a look at the TQt Network Documentation which describes in detail how to reimplement this method. You may also want to look at the example implementation in examples/network/networkprotocol/nntp.cpp. .PP \fIop\fR is the pointer to the operation object which contains all the information on the operation that has finished, including the state, etc. .SH "void QNetworkProtocol::operationPut ( QNetworkOperation * op )\fC [virtual protected]\fR" When implementing a new network protocol, this method should be reimplemented if the protocol supports putting (uploading) data; this method should then process the QNetworkOperation. .PP -When you reimplement this method it's very important that you emit the correct signals at the correct time (especially the finished() signal after processing an operation). Take a look at the Qt Network Documentation which describes in detail how to reimplement this method. You may also want to look at the example implementation in examples/network/networkprotocol/nntp.cpp. +When you reimplement this method it's very important that you emit the correct signals at the correct time (especially the finished() signal after processing an operation). Take a look at the TQt Network Documentation which describes in detail how to reimplement this method. You may also want to look at the example implementation in examples/network/networkprotocol/nntp.cpp. .PP \fIop\fR is the pointer to the operation object which contains all the information on the operation that has finished, including the state, etc. .SH "void QNetworkProtocol::operationRemove ( QNetworkOperation * op )\fC [virtual protected]\fR" When implementing a new network protocol, this method should be reimplemented if the protocol supports removing children (files); this method should then process this QNetworkOperation. .PP -When you reimplement this method it's very important that you emit the correct signals at the correct time (especially the finished() signal after processing an operation). Take a look at the Qt Network Documentation which is describes in detail how to reimplement this method. You may also want to look at the example implementation in examples/network/networkprotocol/nntp.cpp. +When you reimplement this method it's very important that you emit the correct signals at the correct time (especially the finished() signal after processing an operation). Take a look at the TQt Network Documentation which is describes in detail how to reimplement this method. You may also want to look at the example implementation in examples/network/networkprotocol/nntp.cpp. .PP \fIop\fR is the pointer to the operation object which contains all the information on the operation that has finished, including the state, etc. .SH "void QNetworkProtocol::operationRename ( QNetworkOperation * op )\fC [virtual protected]\fR" When implementing a new newtork protocol, this method should be reimplemented if the protocol supports renaming children (files); this method should then process this QNetworkOperation. .PP -When you reimplement this method it's very important that you emit the correct signals at the correct time (especially the finished() signal after processing an operation). Take a look at the Qt Network Documentation which describes in detail how to reimplement this method. You may also want to look at the example implementation in examples/network/networkprotocol/nntp.cpp. +When you reimplement this method it's very important that you emit the correct signals at the correct time (especially the finished() signal after processing an operation). Take a look at the TQt Network Documentation which describes in detail how to reimplement this method. You may also want to look at the example implementation in examples/network/networkprotocol/nntp.cpp. .PP \fIop\fR is the pointer to the operation object which contains all the information on the operation that has finished, including the state, etc. .SH "void QNetworkProtocol::registerNetworkProtocol ( const QString & protocol, QNetworkProtocolFactoryBase * protocolFactory )\fC [static]\fR" @@ -374,8 +374,8 @@ If you find a bug in Qt, please report it as described in .BR http://doc.trolltech.com/bughowto.html . Good bug reports help us to help you. Thank you. .P -The definitive Qt documentation is provided in HTML format; it is -located at $QTDIR/doc/html and can be read using Qt Assistant or with +The definitive TQt documentation is provided in HTML format; it is +located at $QTDIR/doc/html and can be read using TQt Assistant or with a web browser. This man page is provided as a convenience for those users who prefer man pages, although this format is not officially supported by Trolltech. |