diff options
| author | Timothy Pearson <kb9vqf@pearsoncomputing.net> | 2011-12-16 09:59:34 -0600 |
|---|---|---|
| committer | Timothy Pearson <kb9vqf@pearsoncomputing.net> | 2011-12-16 09:59:34 -0600 |
| commit | 83677e35509b4dafac63b76995652bdf3b49f209 (patch) | |
| tree | 591f1dc22278addb439726c42896376b17bb42bd /ksirc/puke/HOWTO-PUKE.pod | |
| parent | 808e453c56036211f57482ed847d54aca01bba68 (diff) | |
| download | tdenetwork-83677e35509b4dafac63b76995652bdf3b49f209.tar.gz tdenetwork-83677e35509b4dafac63b76995652bdf3b49f209.zip | |
Revert "Rename a number of old tq methods that are no longer tq specific"
This reverts commit 808e453c56036211f57482ed847d54aca01bba68.
Diffstat (limited to 'ksirc/puke/HOWTO-PUKE.pod')
| -rw-r--r-- | ksirc/puke/HOWTO-PUKE.pod | 10 |
1 files changed, 5 insertions, 5 deletions
diff --git a/ksirc/puke/HOWTO-PUKE.pod b/ksirc/puke/HOWTO-PUKE.pod index c6bf8136..600f2111 100644 --- a/ksirc/puke/HOWTO-PUKE.pod +++ b/ksirc/puke/HOWTO-PUKE.pod @@ -11,7 +11,7 @@ under Linux. Puke's a generic protocol allowing dsirc to communicate with ksirc. Communications works over a unix domain socket between multiple client dsirc process's to a single ksirc process. All communications -is done via a variable length message with the following layout: +is done via a variable length message with the following tqlayout: =begin text @@ -68,17 +68,17 @@ supporting perl5-oop object. The C++ code must be able to hand all required settings and messages for the widget. Each new widget iherites it's parent and so forth -allowing for a nice oop layout. The widget structure the author is +allowing for a nice oop tqlayout. The widget structure the author is following is the same as Qt's. Their seems to work well, why re-invent the wheel? =item 2.1.1 General Layout, etc Figure where your new widget goes in the heirachy. If it's a simple -Qt widget, I recommend using their existing layout. Man pages list +Qt widget, I recommend using their existing tqlayout. Man pages list what widgets inherit what. -The general idea behind the widget layout should be to be to provide +The general idea behind the widget tqlayout should be to be to provide all the functionality of the widget to dsirc perl script. Incoming messages are handled via the messageHandler and ALL messages should return an ACK with current state info. @@ -106,7 +106,7 @@ These set and return your widget. If you care about inheritance, which you should, all these functions should be virtual. (Since we are using pointers to PWidget's -everywhere, it's a good bet you want your children's overriden +everywhere, it's a good bet you want your tqchildren's overriden functions called, not yours) The structure internally will have to hold a local copy of the widget, |