From a6d58bb6052ac8cb01805a48c4ad2f129126116f Mon Sep 17 00:00:00 2001 From: tpearson Date: Wed, 24 Feb 2010 02:13:59 +0000 Subject: Added KDE3 version of kvirc git-svn-id: svn://anonsvn.kde.org/home/kde/branches/trinity/applications/kvirc@1095341 283d02a7-25f6-0310-bc7c-ecb5cbfe19da --- doc/COPYING | 302 ++++++++ doc/INSTALL-MacOS.txt | 168 +++++ doc/Makefile.am | 11 + doc/firefox.hack.txt | 32 + doc/hackers.guide.txt | 935 +++++++++++++++++++++++++ doc/scriptexamples/Makefile.am | 7 + doc/scriptexamples/README | 6 + doc/scriptexamples/antiidle/Makefile.am | 5 + doc/scriptexamples/antiidle/antiidle.kvs | 159 +++++ doc/scriptexamples/class1.kvs | 102 +++ doc/scriptexamples/exprtest.kvs | 24 + doc/scriptexamples/label1.kvs | 39 ++ doc/scriptexamples/mail.kvs | 159 +++++ doc/scriptexamples/minesweeper/Makefile.am | 5 + doc/scriptexamples/minesweeper/minesweeper.kvs | 131 ++++ doc/scriptexamples/mp3_kdemediaplayers.kvs | 206 ++++++ doc/scriptexamples/mp3info.kvs | 109 +++ doc/scriptexamples/mp3share/Makefile.am | 5 + doc/scriptexamples/mp3share/mp3share.kvs | 84 +++ doc/scriptexamples/mp3share/mp3share_icon.png | Bin 0 -> 1828 bytes doc/scriptexamples/newkvstest.kvs | 101 +++ doc/scriptexamples/playing/Makefile.am | 5 + doc/scriptexamples/playing/playing.kvs | 108 +++ doc/scriptexamples/playing/playing_icon.png | Bin 0 -> 1487 bytes doc/scriptexamples/popup1.kvs | 17 + doc/scriptexamples/popup2.kvs | 124 ++++ doc/scriptexamples/popup3.kvs | 46 ++ doc/scriptexamples/popup4.kvs | 40 ++ doc/scriptexamples/relay.kvs | 33 + doc/scriptexamples/runmenu/Makefile.am | 5 + doc/scriptexamples/runmenu/runmenu.kvs | 111 +++ doc/scriptexamples/signal1.kvs | 47 ++ doc/scriptexamples/simplehttp/Makefile.am | 5 + doc/scriptexamples/simplehttp/simplehttp.kvs | 105 +++ doc/scriptexamples/socket1.kvs | 45 ++ doc/scriptexamples/srfs.kvs | 42 ++ doc/scriptexamples/switchstress.kvs | 46 ++ doc/scriptexamples/timer1.kvs | 25 + doc/scriptexamples/tutorial/Makefile.am | 5 + doc/scriptexamples/tutorial/minesweeper1.kvs | 78 +++ doc/scriptexamples/tutorial/minesweeper2.kvs | 93 +++ doc/scriptexamples/tutorial/minesweeper3.kvs | 147 ++++ doc/scriptexamples/tutorial/minesweeper4.kvs | 187 +++++ doc/scriptexamples/tutorial/minesweeper5.kvs | 201 ++++++ doc/scriptexamples/tutorial/minesweeper6.kvs | 254 +++++++ doc/scriptexamples/tutorial/minesweeper7.kvs | 253 +++++++ doc/scriptexamples/widget1.kvs | 20 + doc/scriptexamples/widget2.kvs | 23 + doc/scripting.faq.txt | 48 ++ doc/themes.howto.txt | 123 ++++ doc/translations.howto.txt | 134 ++++ doc/ui-style.tips.txt | 40 ++ doc/win32.compiling.1.2.txt | 269 +++++++ 53 files changed, 5269 insertions(+) create mode 100644 doc/COPYING create mode 100644 doc/INSTALL-MacOS.txt create mode 100644 doc/Makefile.am create mode 100644 doc/firefox.hack.txt create mode 100644 doc/hackers.guide.txt create mode 100644 doc/scriptexamples/Makefile.am create mode 100644 doc/scriptexamples/README create mode 100644 doc/scriptexamples/antiidle/Makefile.am create mode 100644 doc/scriptexamples/antiidle/antiidle.kvs create mode 100644 doc/scriptexamples/class1.kvs create mode 100644 doc/scriptexamples/exprtest.kvs create mode 100644 doc/scriptexamples/label1.kvs create mode 100644 doc/scriptexamples/mail.kvs create mode 100644 doc/scriptexamples/minesweeper/Makefile.am create mode 100644 doc/scriptexamples/minesweeper/minesweeper.kvs create mode 100644 doc/scriptexamples/mp3_kdemediaplayers.kvs create mode 100644 doc/scriptexamples/mp3info.kvs create mode 100644 doc/scriptexamples/mp3share/Makefile.am create mode 100644 doc/scriptexamples/mp3share/mp3share.kvs create mode 100644 doc/scriptexamples/mp3share/mp3share_icon.png create mode 100644 doc/scriptexamples/newkvstest.kvs create mode 100644 doc/scriptexamples/playing/Makefile.am create mode 100644 doc/scriptexamples/playing/playing.kvs create mode 100644 doc/scriptexamples/playing/playing_icon.png create mode 100644 doc/scriptexamples/popup1.kvs create mode 100644 doc/scriptexamples/popup2.kvs create mode 100644 doc/scriptexamples/popup3.kvs create mode 100644 doc/scriptexamples/popup4.kvs create mode 100644 doc/scriptexamples/relay.kvs create mode 100644 doc/scriptexamples/runmenu/Makefile.am create mode 100644 doc/scriptexamples/runmenu/runmenu.kvs create mode 100644 doc/scriptexamples/signal1.kvs create mode 100644 doc/scriptexamples/simplehttp/Makefile.am create mode 100644 doc/scriptexamples/simplehttp/simplehttp.kvs create mode 100644 doc/scriptexamples/socket1.kvs create mode 100644 doc/scriptexamples/srfs.kvs create mode 100644 doc/scriptexamples/switchstress.kvs create mode 100644 doc/scriptexamples/timer1.kvs create mode 100644 doc/scriptexamples/tutorial/Makefile.am create mode 100644 doc/scriptexamples/tutorial/minesweeper1.kvs create mode 100644 doc/scriptexamples/tutorial/minesweeper2.kvs create mode 100644 doc/scriptexamples/tutorial/minesweeper3.kvs create mode 100644 doc/scriptexamples/tutorial/minesweeper4.kvs create mode 100644 doc/scriptexamples/tutorial/minesweeper5.kvs create mode 100644 doc/scriptexamples/tutorial/minesweeper6.kvs create mode 100644 doc/scriptexamples/tutorial/minesweeper7.kvs create mode 100644 doc/scriptexamples/widget1.kvs create mode 100644 doc/scriptexamples/widget2.kvs create mode 100644 doc/scripting.faq.txt create mode 100644 doc/themes.howto.txt create mode 100644 doc/translations.howto.txt create mode 100644 doc/ui-style.tips.txt create mode 100644 doc/win32.compiling.1.2.txt (limited to 'doc') diff --git a/doc/COPYING b/doc/COPYING new file mode 100644 index 00000000..7381eeed --- /dev/null +++ b/doc/COPYING @@ -0,0 +1,302 @@ +This is the KVIrc Irc Client license. +It is based on the GNU General Public License Version 2. +It contains all the GPL terms and conditions and adds a special exception +(see Terms and Conditions , clause 13) to the distribution limitations. + +Note that the GPL below is copyrighted by the Free Software +Foundation, but the instance of code that it refers to is copyrighted by +Szymon Stefanek and other members of the KVIrc Development Team. + +The source code for all versions of KVIrc is available at http://www.kvirc.net + +Have fun! +Szymon Stefanek :) + +------------------------------------------------------------------------------ + GNU GENERAL PUBLIC LICENSE + Version 2, June 1991 + Extended by Szymon Stefanek + + Copyright (C) 1989, 1991 Free Software Foundation, Inc. + 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301 USA + Everyone is permitted to copy and distribute verbatim copies + of this license document, but changing it is not allowed. + + Preamble + + The licenses for most software are designed to take away your +freedom to share and change it. By contrast, the GNU General Public +License is intended to guarantee your freedom to share and change free +software--to make sure the software is free for all its users. This +General Public License applies to most of the Free Software +Foundation's software and to any other program whose authors commit to +using it. (Some other Free Software Foundation software is covered by +the GNU Library General Public License instead.) You can apply it to +your programs, too. + + When we speak of free software, we are referring to freedom, not +price. Our General Public Licenses are designed to make sure that you +have the freedom to distribute copies of free software (and charge for +this service if you wish), that you receive source code or can get it +if you want it, that you can change the software or use pieces of it +in new free programs; and that you know you can do these things. + + To protect your rights, we need to make restrictions that forbid +anyone to deny you these rights or to ask you to surrender the rights. +These restrictions translate to certain responsibilities for you if you +distribute copies of the software, or if you modify it. + + For example, if you distribute copies of such a program, whether +gratis or for a fee, you must give the recipients all the rights that +you have. You must make sure that they, too, receive or can get the +source code. And you must show them these terms so they know their +rights. + + We protect your rights with two steps: (1) copyright the software, and +(2) offer you this license which gives you legal permission to copy, +distribute and/or modify the software. + + Also, for each author's protection and ours, we want to make certain +that everyone understands that there is no warranty for this free +software. If the software is modified by someone else and passed on, we +want its recipients to know that what they have is not the original, so +that any problems introduced by others will not reflect on the original +authors' reputations. + + Finally, any free program is threatened constantly by software +patents. We wish to avoid the danger that redistributors of a free +program will individually obtain patent licenses, in effect making the +program proprietary. To prevent this, we have made it clear that any +patent must be licensed for everyone's free use or not licensed at all. + + The precise terms and conditions for copying, distribution and +modification follow. + + GNU GENERAL PUBLIC LICENSE + TERMS AND CONDITIONS FOR COPYING, DISTRIBUTION AND MODIFICATION + + 0. This License applies to any program or other work which contains +a notice placed by the copyright holder saying it may be distributed +under the terms of this General Public License. The "Program", below, +refers to any such program or work, and a "work based on the Program" +means either the Program or any derivative work under copyright law: +that is to say, a work containing the Program or a portion of it, +either verbatim or with modifications and/or translated into another +language. (Hereinafter, translation is included without limitation in +the term "modification".) Each licensee is addressed as "you". + +Activities other than copying, distribution and modification are not +covered by this License; they are outside its scope. The act of +running the Program is not restricted, and the output from the Program +is covered only if its contents constitute a work based on the +Program (independent of having been made by running the Program). +Whether that is true depends on what the Program does. + + 1. You may copy and distribute verbatim copies of the Program's +source code as you receive it, in any medium, provided that you +conspicuously and appropriately publish on each copy an appropriate +copyright notice and disclaimer of warranty; keep intact all the +notices that refer to this License and to the absence of any warranty; +and give any other recipients of the Program a copy of this License +along with the Program. + +You may charge a fee for the physical act of transferring a copy, and +you may at your option offer warranty protection in exchange for a fee. + + 2. You may modify your copy or copies of the Program or any portion +of it, thus forming a work based on the Program, and copy and +distribute such modifications or work under the terms of Section 1 +above, provided that you also meet all of these conditions: + + a) You must cause the modified files to carry prominent notices + stating that you changed the files and the date of any change. + + b) You must cause any work that you distribute or publish, that in + whole or in part contains or is derived from the Program or any + part thereof, to be licensed as a whole at no charge to all third + parties under the terms of this License. + + c) If the modified program normally reads commands interactively + when run, you must cause it, when started running for such + interactive use in the most ordinary way, to print or display an + announcement including an appropriate copyright notice and a + notice that there is no warranty (or else, saying that you provide + a warranty) and that users may redistribute the program under + these conditions, and telling the user how to view a copy of this + License. (Exception: if the Program itself is interactive but + does not normally print such an announcement, your work based on + the Program is not required to print an announcement.) + +These requirements apply to the modified work as a whole. If +identifiable sections of that work are not derived from the Program, +and can be reasonably considered independent and separate works in +themselves, then this License, and its terms, do not apply to those +sections when you distribute them as separate works. But when you +distribute the same sections as part of a whole which is a work based +on the Program, the distribution of the whole must be on the terms of +this License, whose permissions for other licensees extend to the +entire whole, and thus to each and every part regardless of who wrote it. + +Thus, it is not the intent of this section to claim rights or contest +your rights to work written entirely by you; rather, the intent is to +exercise the right to control the distribution of derivative or +collective works based on the Program. + +In addition, mere aggregation of another work not based on the Program +with the Program (or with a work based on the Program) on a volume of +a storage or distribution medium does not bring the other work under +the scope of this License. + + 3. You may copy and distribute the Program (or a work based on it, +under Section 2) in object code or executable form under the terms of +Sections 1 and 2 above provided that you also do one of the following: + + a) Accompany it with the complete corresponding machine-readable + source code, which must be distributed under the terms of Sections + 1 and 2 above on a medium customarily used for software interchange; or, + + b) Accompany it with a written offer, valid for at least three + years, to give any third party, for a charge no more than your + cost of physically performing source distribution, a complete + machine-readable copy of the corresponding source code, to be + distributed under the terms of Sections 1 and 2 above on a medium + customarily used for software interchange; or, + + c) Accompany it with the information you received as to the offer + to distribute corresponding source code. (This alternative is + allowed only for noncommercial distribution and only if you + received the program in object code or executable form with such + an offer, in accord with Subsection b above.) + +The source code for a work means the preferred form of the work for +making modifications to it. For an executable work, complete source +code means all the source code for all modules it contains, plus any +associated interface definition files, plus the scripts used to +control compilation and installation of the executable. However, as a +special exception, the source code distributed need not include +anything that is normally distributed (in either source or binary +form) with the major components (compiler, kernel, and so on) of the +operating system on which the executable runs, unless that component +itself accompanies the executable. + +If distribution of executable or object code is made by offering +access to copy from a designated place, then offering equivalent +access to copy the source code from the same place counts as +distribution of the source code, even though third parties are not +compelled to copy the source along with the object code. + + 4. You may not copy, modify, sublicense, or distribute the Program +except as expressly provided under this License. Any attempt +otherwise to copy, modify, sublicense or distribute the Program is +void, and will automatically terminate your rights under this License. +However, parties who have received copies, or rights, from you under +this License will not have their licenses terminated so long as such +parties remain in full compliance. + + 5. You are not required to accept this License, since you have not +signed it. However, nothing else grants you permission to modify or +distribute the Program or its derivative works. These actions are +prohibited by law if you do not accept this License. Therefore, by +modifying or distributing the Program (or any work based on the +Program), you indicate your acceptance of this License to do so, and +all its terms and conditions for copying, distributing or modifying +the Program or works based on it. + + 6. Each time you redistribute the Program (or any work based on the +Program), the recipient automatically receives a license from the +original licensor to copy, distribute or modify the Program subject to +these terms and conditions. You may not impose any further +restrictions on the recipients' exercise of the rights granted herein. +You are not responsible for enforcing compliance by third parties to +this License. + + 7. If, as a consequence of a court judgment or allegation of patent +infringement or for any other reason (not limited to patent issues), +conditions are imposed on you (whether by court order, agreement or +otherwise) that contradict the conditions of this License, they do not +excuse you from the conditions of this License. If you cannot +distribute so as to satisfy simultaneously your obligations under this +License and any other pertinent obligations, then as a consequence you +may not distribute the Program at all. For example, if a patent +license would not permit royalty-free redistribution of the Program by +all those who receive copies directly or indirectly through you, then +the only way you could satisfy both it and this License would be to +refrain entirely from distribution of the Program. + +If any portion of this section is held invalid or unenforceable under +any particular circumstance, the balance of the section is intended to +apply and the section as a whole is intended to apply in other +circumstances. + +It is not the purpose of this section to induce you to infringe any +patents or other property right claims or to contest validity of any +such claims; this section has the sole purpose of protecting the +integrity of the free software distribution system, which is +implemented by public license practices. Many people have made +generous contributions to the wide range of software distributed +through that system in reliance on consistent application of that +system; it is up to the author/donor to decide if he or she is willing +to distribute software through any other system and a licensee cannot +impose that choice. + +This section is intended to make thoroughly clear what is believed to +be a consequence of the rest of this License. + + 8. If the distribution and/or use of the Program is restricted in +certain countries either by patents or by copyrighted interfaces, the +original copyright holder who places the Program under this License +may add an explicit geographical distribution limitation excluding +those countries, so that distribution is permitted only in or among +countries not thus excluded. In such case, this License incorporates +the limitation as if written in the body of this License. + + 9. The Free Software Foundation may publish revised and/or new versions +of the General Public License from time to time. Such new versions will +be similar in spirit to the present version, but may differ in detail to +address new problems or concerns. + +Each version is given a distinguishing version number. If the Program +specifies a version number of this License which applies to it and "any +later version", you have the option of following the terms and conditions +either of that version or of any later version published by the Free +Software Foundation. If the Program does not specify a version number of +this License, you may choose any version ever published by the Free Software +Foundation. + + 10. If you wish to incorporate parts of the Program into other free +programs whose distribution conditions are different, write to the author +to ask for permission. For software which is copyrighted by the Free +Software Foundation, write to the Free Software Foundation; we sometimes +make exceptions for this. Our decision will be guided by the two goals +of preserving the free status of all derivatives of our free software and +of promoting the sharing and reuse of software generally. + + NO WARRANTY + + 11. BECAUSE THE PROGRAM IS LICENSED FREE OF CHARGE, THERE IS NO WARRANTY +FOR THE PROGRAM, TO THE EXTENT PERMITTED BY APPLICABLE LAW. EXCEPT WHEN +OTHERWISE STATED IN WRITING THE COPYRIGHT HOLDERS AND/OR OTHER PARTIES +PROVIDE THE PROGRAM "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED +OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF +MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. THE ENTIRE RISK AS +TO THE QUALITY AND PERFORMANCE OF THE PROGRAM IS WITH YOU. SHOULD THE +PROGRAM PROVE DEFECTIVE, YOU ASSUME THE COST OF ALL NECESSARY SERVICING, +REPAIR OR CORRECTION. + + 12. IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING +WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MAY MODIFY AND/OR +REDISTRIBUTE THE PROGRAM AS PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES, +INCLUDING ANY GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING +OUT OF THE USE OR INABILITY TO USE THE PROGRAM (INCLUDING BUT NOT LIMITED +TO LOSS OF DATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY +YOU OR THIRD PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER +PROGRAMS), EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE +POSSIBILITY OF SUCH DAMAGES. + + 13. As a special exception, Szymon Stefanek gives permission to link this +program with Qt non-commercial edition for Windows, and distribute the +resulting executable, without including the source code for the Qt +non-commercial edition in the source distribution. The Qt non-commercial +edition library is covered by the Qt Non-Commercial license. +See http://www.trolltech.com for informations. + diff --git a/doc/INSTALL-MacOS.txt b/doc/INSTALL-MacOS.txt new file mode 100644 index 00000000..e0733aeb --- /dev/null +++ b/doc/INSTALL-MacOS.txt @@ -0,0 +1,168 @@ +Thomas Kalla, 29.06.2006 +######################### + +This document contains step-by-step instructions for compiling kvirc on a MacOS X system. +I compiled several versions of kvirc (beginning with 3.0.0 up to recent CVS) on a Powerbook G4, 1.5GHz, 512 MB RAM and MacOS X 10.3.3-9. + + +All this has worked fine several times for me. I've been using KVirc on Mac since May 2004 without any crashes & faults. Only the sound interface does not work, but I have no use for it within an IRC client. However, I cannot guarantee that this instructions will work for you as they do for me and I'm not responsible for any problems or damage you may encounter after following them. You should always understand what you are doing! + + + +IMPORTANT: These instructions refer to Qt/Mac. If you want Qt/X11 which is included in Fink you are on your own. There is no support for the latter and most probably you don't get a working build. + + +######################### +Compilation with QT-MAC +######################### + +IMPORTANT: When compiled with QT-MAC, kvirc has to be run out of a bundle! Otherwise the application won't dispatch the keyboard events correctly and will be pretty unusable for you. + +A bundle is "just" a special directory structure on Mac systems which contains the application binary, dependant libraries, plugins, modules and other resources. So all we have to do is to run configure with proper paths and relink the binary, libraries and modules with relative paths after the compilation. + +For details look at http://doc.trolltech.com/qq/qq09-mac-deployment.html and the documentation on http://developer.apple.com, please. + +Prerequisites: + +1. Apple XCode +Get the latest version from Apple. I've been using only V1.5 for building with QT-MAC + +2. QT-MAC +Get the latest V3.*-version from Trolltech. + +3. GNU gettext +Get the latest sources from your favourite GNU mirror. + +Prerequisites installation: + +1) Install XCode +If not included on your Panther install media or if you want the latest version, you have to register at http://developer.apple.com (it's free), download XCode and follow the install instructions in the documentation. + +2) Install QT-MAC +You have to compile QT yourself. As far as I know there are no compiled binaries avaiable. Download and unpack the sources and follow the documentation. + +I used V3.3.4 + +Add the following two lines to your ~/.profile file, otherwise the compilation if Qt may fail. + +export QTDIR=/Developer/qt-mac-free-3.3.4 +export DYLD_FALLBACK_LIBRARY_PATH=$QTDIR/lib + + +Open a terminal window +# cd /Developer +# tar -xjf /qt-mac-free-3.3.4.tar.bz2 +# cd qt-mac-free-3.3.4 +# ./configure -thread -qt-gif -fast -no-exceptions -debug +# make sub-tools + +(If you don't want to build with debug information, remove the "-debug" switch in te configure line. You may also want to change "QMAKE_CFLAGS_RELEASE = -Os" in the mkspec/macx-g++/qmake.conf file to -O2. If you want the tutorial and examples, run "make" instead of "make sub-tools") + +3) Install GNU gettext +If you want non-english locales, you need GNU gettext. +If you already installed Fink, you already have gettext so you may skip this step. + +I used V0.14.5 + +Open a terminal window +# cd /Developer +# tar -xzf /gettext-0.14.5.tar.gz +# cd gettext-0.14.5 +# ./configure +# make +# make install + + +######################### +KVirc installation: + + +1) Get the KVirc sources: + +IMOPRTANT: Only the CVS sources compile cleanly with QT-MAC for now! + +# cvs -d:pserver:anonymous@cvs.kvirc.net:/cvs login + +You will be asked for a password: just hit return. + +# cvs -z3 -d:pserver:anonymous@cvs.kvirc.net:/cvs co kvirccvs + +Run autogen: +# cd kvirccvs/kvirc +# ./autogen.sh + + +2) Run configure + +The application bundle will be built in the kvirc sources directory. +Feel free to remove --enable-debug if you don't want to have a debuggable build and use addictional options like --enable-optimisation=2 or --with-big-channels. + +# ./configure --enable-pipes --enable-debug --exec-prefix=$(pwd)/KVirc.app/Contents/Resources --prefix=$(pwd)/KVirc.app/Contents --bindir=$(pwd)/KVirc.app/Contents/MacOS --libdir=$(pwd)/KVirc.app/Contents/Frameworks --datadir=$(pwd)//KVirc.app/Contents/Resources --disable-x-support + + +3) Run make + +CAUTION!!! Because of a problem with libtool you have to remove or rename the file libqt-mt.la (or libqt.la if you compiled QT without threads). It is located in $QTDIR/lib/. Otherwise the compilation will stop with a link error. + +# mv $QTDIR/lib/libqt-mt.la $QTDIR/lib/libqt-mt.la.bak + +Now run make and relax :-) + +# make + +(A debuggable, non-optimized build takes about 40 minutes on my PowerBook.) + + +4) Run make install + +# make install + + +5) Relinking + +KVirc and its modules depend on libkvilib and libqt which are not in the dynamic linker search path by default. The paths set during the compilation are absolute paths and have to be changed to be realtive to the executable path. + +The following commands do this for libkvilib: + +# install_name_tool -id @executable_path/../Frameworks/libkvilib.3.dylib $(pwd)/KVirc.app/Contents/Frameworks/libkvilib.3.dylib +# install_name_tool -change $(pwd)/KVirc.app/Contents/Frameworks/libkvilib.3.dylib @executable_path/../Frameworks/libkvilib.3.dylib $(pwd)/KVirc.app/Contents/MacOS/kvirc +# find $(pwd)/KVirc.app/Contents -name '*.so' | xargs -n1 install_name_tool -change $(pwd)/KVirc.app/Contents/Frameworks/libkvilib.3.dylib @executable_path/../Frameworks/libkvilib.3.dylib + +Now you have to decide whether you want to include libqt within the bundle or not. This is useful if you consider to share your bundle with your friends and they don't want to compile QT themselves. + + +a) You don't want to include libqt within the bundle + +Make sure the dynamic linker is able to find libqt. The easiest way is to make symlinks in the /usr/lib directory. + +# ln -sf $QTDIR/lib/libqt-mt.3.dylib /usr/lib +# ln -sf $QTDIR/lib/libqui.1.dylib /usr/lib + + +b) You want to include libqt within the bundle + +Copy libqt into the bundle: + +# cp $QTDIR/lib/libqt-mt.3.dylib $(pwd)/KVirc.app/Contents/Frameworks/ + +Relinking commands for libqt: + +# install_name_tool -id @executable_path/../Frameworks/libqt-mt.3.dylib $(pwd)/KVirc.app/Contents/Frameworks/libqt-mt.3.dylib +# install_name_tool -change libqt-mt.3.dylib @executable_path/../Frameworks/libqt-mt.3.dylib $(pwd)/KVirc.app/Contents/MacOS/kvirc +# install_name_tool -change libqt-mt.3.dylib @executable_path/../Frameworks/libqt-mt.3.dylib $(pwd)/KVirc.app/Contents/Frameworks/libkvilib.3.dylib +# find $(pwd)/KVirc.app/Contents -name '*.so' | xargs -n1 install_name_tool -change libqt-mt.3.dylib @executable_path/../Frameworks/libqt-mt.3.dylib + +6) Cleaning up + +The bundle is funtional but is looks better with a nice icon :-) +Copy the icon file from the data/resources_mac directory to the resources directory and the Info.plist file to the contents directory + +# cp data/resources_mac/kvirc.icns $(pwd)/KVirc.app/Contents/Resources +# cp data/resources_mac/Info.plist $(pwd)/KVirc.app/Contents + + +7) Enjoy :-) + +Open Finder, move your bundle into a better location (e.g. /Applications), and double click to start. + + diff --git a/doc/Makefile.am b/doc/Makefile.am new file mode 100644 index 00000000..c23bd7d6 --- /dev/null +++ b/doc/Makefile.am @@ -0,0 +1,11 @@ +############################################################################### +# KVirc IRC client Makefile - 16.12.98 Szymon Stefanek +############################################################################### + +SUBDIRS = scriptexamples + +EXTRA_DIST = COPYING *.txt + + +tmpdir = $(licensedir) +tmp_DATA = COPYING diff --git a/doc/firefox.hack.txt b/doc/firefox.hack.txt new file mode 100644 index 00000000..4cdd239e --- /dev/null +++ b/doc/firefox.hack.txt @@ -0,0 +1,32 @@ +Firefox Hack Guide - HelLViS69 - 2007.02.08 +------------------------------------------------------------------------------- + +@ Prologue + +This guide is meant to be a simple hack to add protocols handlers to Firefox, +such as irc:// +This guide is been tested on Linux, Mac and Windows. + +@ How To + +- Open Firefox at the url about:config + You'll find the Firefox configuration + +- Click with right button, select New, then Boolean + As Name insert network.protocol-handler.external.irc and true as Value + +- Click with right button, select New, then String + As Name insert network.protocol-handler.app.irc + As Value you have to insert the path of KVIrc binary, eg /usr/bin/kvirc , + `which kvirc` or C:\Programs\Firefox\firefox.exe + +- Make sure that network.protocol-handler.expose-all are setted as true + +With these simple steps you can handle irc://irc.something.tld from Firefox + +If you want to add more protocols handlers, just follow the same steps changing +the protocol you want to add in firefox and the application you want to use to +handle the new protcol + +Elvio Basello + diff --git a/doc/hackers.guide.txt b/doc/hackers.guide.txt new file mode 100644 index 00000000..5eddcc8c --- /dev/null +++ b/doc/hackers.guide.txt @@ -0,0 +1,935 @@ +KVIrc hackers guide - Szymon Stefanek - 2004.05.26 +------------------------------------------------------------------------------- + +This is an always-work-in-progress guide for KVIrc source code hackers. + +------------------------------------------------------------------------------- +The source tree +------------------------------------------------------------------------------- + +/ Root directory. +| This is almost completely automake and autoconf stuff. +| +|-- admin Administrative files used during the compilation +| automake, autoconf and document generation scripts. +| +|-- data Data for the KVIrc program. Most of this stuff is +| | installed in $(prefix)/share/kvirc/$VERSION/ +| | +| |-- applnk *.desktop and menu entries for KDE +| | +| |-- config Default configuration files +| | +| |-- defscript The default script +| | +| |-- deftheme The default themes +| | +| |-- doctemplates Some document templates that get parsed by gendoc.pl +| | when the html documentation is generated +| | +| |-- helppics Data pictures for the html documentation +| | +| |-- icons Icons in various sizes +| | +| |-- man The manual pages +| | +| |-- mimelnk *.desktop entries for the *.kvs and *.kvc file types +| | that are respectively kvirc scripts and kvirc +| | configuration files. This is all stuff for KDE +| | +| |-- msgcolors Default sets of message colors +| | +| |-- pics Most of the pictures that KVIrc uses +| | +| |-- protocols irc:// and irc6:// protocol definitions for konqueror +| | +| `-- resources Resources for the windows compilation. +| +|-- debian Debian mantainer's stuff +|-- debian.robin +| +|-- doc Any kind of documentation +| | +| `-- scriptexamples Various script examples +| +|-- no-dist Stuff that does NOT end in the final distribution + +|-- po Internationalisation (i18n :) +| | +| |-- kvirc Translations for kvilib and the main KVIrc executable +| | +| `-- modules Translations for the modules +| +|-- scripts Some SHELL scripts. Probably only config is used atm. +| +|-- src The sources +| | +| |-- kvilib KVIrc library. Any source code snippet that can be +| | | abstracted enough to not depend on the KVIrc core +| | | ends up here. kvilib depends only on external stuff. +| | | +| | |-- build This is the build directory for automake. +| | | The main Makefile.am is here. +| | | +| | |-- config The headers that control the compile-time +| | | configuration. +| | | +| | |-- core The really basic classes: strings, memory management, +| | | error code defines etc.. +| | | +| | |-- ext Here ends everything that has no other specific place +| | | in kvilib. +| | | +| | |-- file File management and file utilities +| | | +| | |-- include Compile-time generated include files. these are +| | | only links. +| | | +| | |-- irc IRC protocol related classes. +| | | +| | |-- net Networking related stuff: sockets, ssl, http ... +| | | +| | |-- system System function wrappers or stuff that depends +| | | on the strict operating system support. +| | | Threads, localisation, env, time, shared library.. +| | | +| | `-- tal Toolkit Abstraction Layer: wrapper classes that +| | inherit from KDE* or QT classes, depending on the +| | compilation type. +| | +| |-- kvirc The KVIrc executable sources +| | | +| | |-- build Again the build directory for automake. +| | | Makefile.am is here. +| | | +| | |-- include Again compile-time include files. Only links. +| | | +| | |-- kernel The core of the executable. The main function is +| | | here. Here is also the KviApp object and the options +| | | core management. +| | | +| | |-- kvs The NEW shiny scripting engine. +| | | At the time of writing this two-stage UNICODE +| | | KVS interpreter is not finished yet and thus almost +| | | nothing here is really hardwired to the rest +| | | of the core. +| | | +| | |-- module The module management stuff: the loader, the module +| | | interface definitions etc.. +| | | +| | |-- sparser The IRC server parser +| | | +| | |-- ui User interface. 99% of the core GUI is here. +| | | Here you can find KviFrame (the main window) +| | | KviMdiManager, KviWindow, KviChannel, KviQuery, +| | | KviConsole, KviInput, KviIrcView and KviUserListView +| | | which are the most common widgets in kvirc. +| | | +| | `-- uparser The currently used scripting engine (user parser). +| | If you want to implement just some simple features +| | (like new commands or functions) then this is the +| | place to look at. If you want to make some long +| | term hacks then it's probably better to look at the +| | kvs directory instead. +| | +| `-- modules Yes, the modules :D +| | +| |-- about The about dialog +| | +| |-- aliaseditor The alias editor window +| | +| |-- avatar Avatar manipulation stuff +| | +| |-- chan $chan.* scripting stuff +| | +| |-- channelsjoin The channelsjoin dialog +| | +| |-- clock This was a clock applet but actually it is not +| | working and thus not compiled. +| | +| |-- codetester The codetester window +| | +| |-- config config.* scripting stuff +| | +| |-- dcc This module implements the whole DCC protocol. +| | Windows, transfer threads etc: everyting is here. +| | +| |-- dialog dialog.* scripting stuff +| | +| |-- dockwidget The dock widget for KDE and windows. +| | +| |-- editor The scripting editor core widget. +| | +| |-- eventeditor The event editor window +| | +| |-- file file.* scripting stuff +| | +| |-- filetransferwindow The file transfers window +| | +| |-- help The help browser +| | +| |-- http http.* scripting stuff +| | +| |-- ident A small ident daemon +| | +| |-- iograph Another applet that is not compiled for now. +| | +| |-- lag Lag meter +| | +| |-- lamerizer A crypt/text-transformation engine +| | +| |-- links The links window +| | +| |-- list The channel list window +| | +| |-- log log.* scripting stuff +| | +| |-- logview The logviewer window +| | +| |-- mask mask.* scripting stuff +| | +| |-- mircimport A server entry importer from the mirc's servers.ini +| | +| |-- mp3player mp3player.* scripting stuff +| | This is an interface to the xmms program on unix +| | and to winamp on windows. On unix libxmms.so is +| | loaded at runtime. On windows there is also +| | a gen_kvirc.dll plugin for winamp that needs +| | to be loaded by the winamp program in order to make +| | communications with KVIrc possible. +| | +| |-- my my.* scripting stuff +| | +| |-- objects All the object oriented scripting stuff +| | +| |-- options The options dialog +| | +| |-- popupeditor The popup editor window +| | +| |-- raweditor The raw events editor window +| | +| |-- regchan regchan.* scripting stuff +| | +| |-- reguser reguser.* scripting stuff +| | +| |-- rijndael A crypting engine +| | +| |-- setup The module that is loaded when KVIrc is started +| | for the first time. It contains the initial +| | configuration wizard. +| | +| |-- sharedfile sharedfile.* scripting stuff +| | +| |-- sharedfileswindow The shared files window +| | +| |-- snd snd.* scripting stuff +| | +| |-- socketspy The socketspy window +| | +| |-- spaste spaste.* scripting stuff +| | +| |-- str str.* scripting stuff +| | +| |-- system system.* scripting stuff +| | +| |-- tb_options The options toolbar +| | +| |-- tb_scripting The scripting toolbar +| | +| |-- tb_winops The window operations toolbar +| | +| |-- term The embedded terminal emulator (needs KDE) +| | +| |-- tip The tip of the day +| | +| |-- tmphighlight tmphighlight.* scripting stuff +| | +| |-- toolbar toolbar.* scripting stuff +| | +| |-- toolbareditor The toolbar editor window +| | +| |-- url The url window +| | +| `-- window window.* scripting stuff +| +`-- win32build The directory for Windows builds + + +[pragma@phoenix src]# cat $(find ./ -name \*.h) | wc -l + 60189 +[pragma@phoenix src]# cat $(find ./ -name \*.cpp) | wc -l + 164400 + + +------------------------------------------------------------------------------- +The coding style +------------------------------------------------------------------------------- + +The coding style helps the reader a lot. In a large project you tend +to forget the exact meaning of some functions or variables. +A good naming convention makes the code "auto commenting": by looking +at the name of a variable or function you can understand its type +and guess its meaning and usage. +Following these rules is not strictly mandatory (maybe with the +exception of the first one) but it is highly appreciated. + +- INDENT WITH TABS (the only MANDATORY rule) + + Go back to the line above and read it again. + + INDENT, TABS. + + Tabs can be assigned any number of spaces in any decent source code + editor. + + Actually 95% of the KVIrc code is indented in BSD/Allman style + but the K&R style is also tolerated. + +- Try to use the following variable naming conventions + + g_* : global variables + m_* : member variables + no prefix : any other scope + + [prefix]pName : pointer to something named Name + [prefix]iName : integer (signed) variable named Name + [prefix]uName : unsigned integer + [prefix]szName : string named Name + [prefix]dName : floating point vars + [prefix]eName : enumerated value variables + [prefix]tName : kvi_time_t values + + i,j,k,tmp,aux,p : short names are used for short term variables + like the temporaries used in functions. + Do NOT name a member or global variable i. + + So finally: + + g_pApp is a global pointer to the application object + m_pData is a member variable pointer to some data object + m_szName is a string member variable named Name + szPippo is a string variable named Pippo + tmp is a short term temporary variable + i,j,k are probably some short term iteration variables + ... + + +- Function names + + C++ class member functions + Function names start with lower case letters. Each word except the first + one should start with an upper case letter. Try to use descriptive names + and not acronyms or shortcuts (unless they are really obvious). + For example: + fillUserList, setAutoDelete, joinChannel, markQueryAsDead ... + Standalone C/C++ functions + For standalone functions you can follow the C++ rule but the + kernel-like syntax is also acceptable (all low case letters with + underscore separators). + If you're defining a widely used C function (maybe in kvilib) + then adding a kvi_ prefix is also a good idea. + +- Class names + + The class names start with an upper case letter. In most cases + there is a Kvi prefix and the rest follows the rule for function names. + KviApp, KviConsole, KviWindow, KviStr, KviConfig, KviUserParser ... + + If possible, do not use "shortcut" names. + Actually KviCommand is preferred over KviCmd unless the KviCmd class + is REALLY widely used across the source (like KviStr for example). + + This helps a lot in remembering the class names: with the shortcuts + you're often forced to open the corresponding header file to look up + which letters have been left off... + + Structure names usually follow the same conventions. + +- Simple data types + + If you need to define a simple data type then something like kvi_typename_t + is a good choice. + +- Preprocessor + + Preprocessor macros should be all uppercase with undescores separating + words. + +- Comment the code + + You don't need to write poems: two lines describing what a function + does will be enough. + If a function is simple and its meaning is clear from its name + then comments are not needed (this is why we're using expressive + variable and function names). + Single line C++ comments are preferred over the C style comments. + +------------------------------------------------------------------------------- +Coding tips +------------------------------------------------------------------------------- + +- Don't use C++ exceptions: they make the code unmanteinable in the long term + +- If you need to access some system function then first look if there is + an existing kvi_* wrapper and use that one instead. The wrapper is there + because of portability issues. + +- Don't use the STL features: anything that you need IS either in the Qt library + or in kvilib. + +- Windows compilation has COMPILE_ON_WINDOWS #defined and a KDE compilation + has COMPILE_KDE_SUPPORT #defined. + +- Modularize, abstract, modularize, abstract ... + +- When your objects need to be allocated with new in a module and destroyed + in the kvirc core or kvilib (or viceversa) then derive the class from + KviHeapObject that will provide the new and delete operators. + This is a workaround for Windows that uses a separate + heap for each executable module (*.exe or *.dll). Data allocated on one + heap must be freed on the same heap. + +------------------------------------------------------------------------------- +The strings +------------------------------------------------------------------------------- + +This is the list of the various string types used in KVIrc. + +(const) char * + The classic C null terminated string. + +KviStr + The basic KVIrc string class. It has been first implemented as a hack + around various bugs of the original QString class (the NOT unicode one + that now has been renamed to QCString). It has the property of being + always non null and it has no reference counting. + Actually many occurences of this string are replaced by QString + (especially in GUI modules) to handle correctly the UNICODE character set. + +QString + The Qt UNICODE string. See the Qt documentation for details. + This is the string that should be mostly used in KVIrc in the near future. + Take care: in general it is NOT null terminated. + There is a KviQString wrapper namespace (#include "kvi_qstring.h") that + adds some missing functionality. For example, + KviQString::sprintf(qstring_buffer,qstring_format,...) + allows formatting a QString with a format string that is a QString itself + (and thus it is UNICODE). + QString uses reference counting. An assigment of a QString to another + QString does NOT make an immediate copy, it just increases the reference + count instead. The copy is made at the first modification of one of the + two strings (the operation is called "detaching"). While generally this + is not an issue, you must take care when passing QString objects between + concurrent threads. + +(const) QChar * + The array of Qt chars. This is usually obtained by callling + KviQString::nullTerminatedArray() which itself is a hack... + This array is used in some functions that were written for + const char * strings and haven't been ported completely. + +QCString + The Qt non UNICODE string. See the Qt documentation for details. + +The Goal: + - Use KviStr only where it is strictly needed (for protocol or performance + related issues). One of such places is the IRC server parser (but there + are more). + - Use QString everywhere in the user interface and in any other + place where KviStr is not strictly needed. Save and restore + strings in the UTF8 format. + - Get rid of ALL occurences of KviWStr and kvi_wchar_t * : DONE on 2004.11.02 + +------------------------------------------------------------------------------- +Strings and localisation +------------------------------------------------------------------------------- + +Any string that is shown to the user should be translated to the user's local +language. To make a string translaetable use one of the __tr* macros. +The most common one across the sources is __tr("string") that returns +a const char * translation of "string". +Actually __tr() is being phased out in favor of __tr2qs() that returns +a QString instead of a const char * pointer. +The arguments of these macros are extracted from the sources by the +gettext program and are used to build the translation hashes loaded at runtime. +Remember that the arguments must be string constants and not variables. + +The list that follows describes briefly the localisation macros +defined in kvi_locale.h + +CSTRING is an US-ASCII null terminated C string. + +__tr2qs(CSTRING) : translates CSTRING to a QString & +__tr(CSTRING) : translates CSTRING to another CSTRING + This should disappear in favor of __tr2qs + +These macros are NOT THREAD SAFE: you can't call them from non GUI threads. +If you need to translate some string in a slave thread (probably when +sending a message event to the main GUI thread) then you need to use the +__tr_no_lookup() (on the slave side) and __tr_no_xgettext() (on the master side). + + +------------------------------------------------------------------------------- +Anatomy of an IRC context +------------------------------------------------------------------------------- + + +KviIrcContext [persistent set of resources] + | + +--KviIrcConnection [changed at every connection, with (almost) all the children] + | | + | +--KviIrcConnectionTarget [target server, proxy to use and address to bind] + | | | + | | +--KviIrcServer + | | | + | | +--KviProxy [null if not using a proxy] + | | + | +--KviIrcLink [high level network link: trasmits and receives IRC messages] + | | | + | | +--(KviIrcConnectionTargetResolver) [kickstarts the connection] + | | | + | | +--KviIrcSocket [low level network link: transmits packets of bytes] + | | + | +--KviPtrList [active channels] + | | + | +--KviPtrList [active queries] + | | + | +--KviIrcConnectionUserInfo [nick, user, host, local ip...] + | | + | +--KviIrcConnectionServerInfo [name, supported modes, supported flags...] + | | + | +--KviNotifyListManager [kvi_notifylist.h] + | | + | +--... + | + +--KviConsole [persistent] + | + +--(KviLinksWindow), (KviListWindow) [other may-be-persistent context windows] + | + +--KviPtrList [dead channels] + | + +--KviPtrList [dead queries] + | + +--... + +KviIrcContext is the set of resources used to deal with a single irc +connection. An irc context is persistent and reusable until the user decides to +destroy it. The irc context owns the console window (KviConsole) that is +strictly tied to the lifetime of the context itself. The console is created +when the IRC context is created and when the user closes the console then +the IRC context is destroyed too. +In earlier KVIrc versions there was only KviConsole that did the role of both +KviConsole and KviIrcContext, but since the class has grown in complexity +to a point where it started to be unmantainable the splitting has been unavoidable. + +KviIrcConnection rappresents an IRC connection: it is the highest protocol +implementation on the KVIrc's networking stack. A KviIrcConnection +owns a KviIrcLink (that is the lower level). KviIrcConnection is NOT reusable: +it lives only for the lifetime of a single IRC connection inside the parent +irc context. KviIrcConnection talks to the parent's KviConsole. +The connection target is a KviIrcConnectionTarget class and it contains +the KviIrcServer, KviProxy and the eventual bind address. The owned target +is passed down the networking stack to the lower level classes. +The connection contains also the lists of queries and channels currently opened. +When a channel or query is marked as dead then its ownership is passed to +the KviIrcContext (it becomes permanent between two connections). +The connection owns a lot of other interesting classes to take a look at: +KviIrcConnectionUserInfo, KviIrcConnectionServerInfo, KviNotifyListManager... + +KviIrcLink is the middle level of the KVIrc's networking stack. +It handles host lookups, the connection startup and data stream input and output. +This is meant to be a "pluggable" class: it should be flexible enough to allow +inheritance and protocol overriding. KviIrcLink owns and manages the KviIrcSocket. +It takes care of extracting IRC protocol messages from the KviIrcSocket raw data +stream and of formatting the outgoing messages by adding the trailing CRLF. +The host lookups are done by the means of KviIrcConnectionTargetResolver. + +KviIrcSocket is the lowest level of the KVIrc's networking stack. +It manages the connection through proxies and accesses the system level +socket directly. The incoming data stream is passed to KviIrcLink::processData() +and the outgoing data stream is received through KviIrcSocket::sendPacket() +KviIrcSocket also manages the outgoing send queue and implements the +"anti-server-flood" algorithm. +This class doesn't know anything about the IRC protocol: it just receives +and sends out raw data packets! + + +....... + +kvirc (KviApp) + | + +-frame window (KviFrame) + | + +-irc_context 1 (KviIrcContext) + | | + | +-irc_connection (KviIrcConnection) + | | | + | | +-list of channels + | | | + | | +-list of queries + | | | + | | +-irc_link + | | + | +-console (KviConsole) + | + +-irc_context 2 + | ... + + +KviConsole <-> KviIrcContext + +------------------------------------------------------------------------------- +Important global variables +------------------------------------------------------------------------------- + +All these variables are almost alwas set (and point to a real alive object). +The only critical moments where these variables must be double checked +are the startup phase and the shutdown phase. +Do not attempt to change the values of these variables unless you REALLY know +what you're doing. + + +KviApp * g_pApp; + The one and only application object + Declared in "kvi_app.h" + Always set. + +KviServerParser * g_pServerParser; + The one and only server parser + Declared in "kvi_sparser.h" + Almost always set (critical phases at early startup and late shutdown) + +KviFrame * g_pFrame; + The one and only main window + Declared in "kvi_frame.h" + Almost always set (critical phases at early startup and late shutdown) + +KviWindow * g_pActiveWindow; + The one and only active window + Declared in "kvi_window.h" + Almost always set (critical phases at early startup and late shutdown) + +Note for C++ purists: In fact we could be using the protected singleton pattern +on most of these variables and access it by the means of Class::instance(). +The global var names save some typing and can be written by any other class +without having to worry about friends or write-access functions. + +------------------------------------------------------------------------------- +The charset mess +------------------------------------------------------------------------------- + +IRC is not UNICODE :/ ... sigh ... +The fact is that every user wants his local encoding to be used. +KVIrc tries to be even smarter and allow a different encoding for each window. +This is a difficult task since we simply can't translate the strings that +come from and go to the server just at the socket level. + +User -> Server + +We need to allow the local user to write UNICODE data, encode it to the +proper charset (again depending on the window the text was typed in) and +send it down to the server. +When the user writes commands this is going to become a little mess since +nicknames, channel names or usernames may or may not be encoded in the +encoding of the current window. + +Server -> User + +We need to carry the plain 8bit data (in whatever encoding it is) from the +server up to the GUI level, then convert to UNICODE by choosing the proper +decode routine just when we know in which window the text is going to be +displayed. In (non RFC) servers that allow encoded characters in nicknames +this is going to become a real mess since the same 8bit nick may result in +a different UNICODE string depending on the window it was "decoded" on. + +(Partial) Solution: +- Each server has an encoding set. If empty then the network encoding is used. +- Each network han and encoding set. If empty then the default system encoding + is used. +- The system encoding is set by the user. If empty then the encoding is guessed + from the user's locale. +- Each window (with the exception of the console) has its own encoding used + ONLY for private messages and notices. This allows one to join + a channel with a "special" encoding and still see what's being written in. + The real utility of this last feature still needs to be evaluated. + +------------------------------------------------------------------------------- +Output levels +------------------------------------------------------------------------------- + +There are few macros that specify the output level that the user desires. +These marcors are defined in "kvi_options.h" + +_OUTPUT_MUTE: returns true if the user wants KVIrc to spit less useless output + possible. The goal of the user is to chat on IRC so print only data + relevant to this. If stuff goes wrong then print the errors in + short forms (one liners) and do it only in case of serious ones. + Don't print any transient error or warning. + Usage: if(!_OUTPUT_MUTE)output... + +_OUTPUT_QUIET: returns true if the uses wants KVIrc to spit less output than + normal. The goal of the user is to chat visually on IRC so print + only data relevant to this. + Usage: if(!_OUTPUT_QUIET)output... + +: Reference output level: here stuff is printed unconditionally. + Usage: output... + +_OUTPUT_VERBOSE: returns true if the users allows KVIrc to print some + additional output. This is intended mainly for scripters and + curious pepole that want detailed informations about what is going + on around them. + Usage: if(_OUTPUT_VERBOSE)output... + +_OUTPUT_PARANOIC: returns true if the users allows KVIrc to print anything + including debug info. This is intended mainly for developers. + Usage: if(_OUTPUT_PARANOIC)output... + +------------------------------------------------------------------------------- +Rule for safe text output +------------------------------------------------------------------------------- + +If the format string you're going to output is not constant (i.e. it +comes from the server) you MUST use KviWindow::outputNoFmt() instead +of KviWindow::output(). + +BAD: + QString szText = pConnection->decodeText(msg.safeTrailing()); + pWindow->output(KVI_OUT_SOMETHING,szText); <--potential crash/security hole + +GOOD: + QString szText = pConnection->decodeText(msg.safeTrailing()); + pWindow->outputNoFmt(KVI_OUT_SOMETHING,szText); <--faster and no crashes + +------------------------------------------------------------------------------- +KVIrc (and script) versioning +------------------------------------------------------------------------------- + +- Standard definition + +The KVIrc versioning follows a really common standard: we use a +string of numbers separated by dots with decreasing weight from left to right. + + ........ + +where each is a number. + +Theoretically there is no limit on the parts the version can be composed +of but in fact we use either three or four part versions. The omitted +parts on the right are implicitly assumed to be 0. + +The first part is called the major release number and it is bumped +up only when really big changes occur in the source tree. A bump from N to N+1 +in the major version number means that a great milestone has been achieved +and the software is really different from what it was in the moment +when the major number was bumped from N-1 to N. This usually also means +that the software might be somewhat incompatible with the previous major release. + +When the major number is bumped up all the following parts are reset to 0 +(and could be even temporairly omitted). + +The second part is called minor release number and it is increased +more often than the major. A bump from N to N+1 in the minor version number +means that an ordinary (small) development milestone has been achieved. +Software versions with the same major and close minor numbers are likely +to be totally compatible with each other. + +When the minor number is bumped up all the following parts are reset to 0. + +The third part is called (public) revision number and it is increased often. +A bump from N to N+1 in the revision number usually means that a set of bugfixes +or some new features have been included in the software. Compatibility +should be assumed unless explicitly noted. Again, when the revision number +is bumped up all the following parts are reset to 0. + +The fourth part is actually used only on the svn tree and it is usually not +present in the official public releases (it is assumed to be 0 for comparison +purposes). It is called the "internal revision" number and when taken +out of the version string it may assume a meaning on its own (but it's not +required in fact). KVIrc uses the ISO sources date in the format YYYYMMDD for this +number. The sources date number is defined in src/kvilib/config/kvi_sourcesdate.h +and is also displayed by kvirc --version. Some packagers prefer to use the svn +revision number instead of the sources date. This is not "official" but it's +still ok as long as it follows the "order-preserving" rule (see below). + +It is unlikely that you will find a KVIrc versioned with more than +four numbers... but if you will (for some strange reason) then it will +still follow the same rules: it will be increased for yet minor changes +(two versions within a single day ?) and will be reset to (implicit) +zero when the fourth part changes. + +- Comparison of version strings + +The comparison of two version strings is defined as follows. +Let N1.N2.N3.N4.N5..... and M1.M2.M3.M4.M5..... be version strings. +To find out which one is greater compare each couple of numbers Ni-Mi at the same +position i (with the same weight) until Ni and Mi differ or both Ni and +Mi are omitted. If both Ni and Mi are omitted then the version strings +are equal, otherwise the greater version string is the one that +contains the greater of the Ni - Mi couple. Easy, right ? + +This means that to compare 3.2.6.3.4 and 3.2.9 you first compare +3 with 3 and find that they are equal. Then you compare 2 with 2 +and find that they are equal. Then compare 6 with 9 and find that +they are different and 9 is greater. This allows you to say that +the first version string is greater than the second. + +To compare 3.2.6.1 with 3.2.6 you compare 3 and 3, 2 and 2, 6 and 6 +and 1 with (implicit) 0, that tells you that the first version string +is greater than the second one. + +This also means that 3 and 3.0.0 are assumed to be EQUAL since +the algorithm above finds that at the fourth comparison step +both numbers are omitted (thus zero from there up to infinity). + +This comparison function is monotonically increasing or in +other words order-preserving. This is a *requirement* for a consistent +versioning scheme. + +- Package versioning schemes with letters + +It is common for packages to add letters to some of the parts +of the version string. This causes the string to lose the +advantage of being universally comparable but it might still +define a consistent scheme for some package line. In the case +that letters are added to a version string (like 3.2.6.svn10) +we say that it is comparable only to the version strings +that have the same letter pattern: 3.2.6.svn10 and 4.3.1.svn344 +are comparable but 3.2.6.svn10 and 3.2.6.cvs15 are not. +For comparable strings we strip the letters in order to make the comparison. + +- Stable and unstable versions + +Our numbering scheme does NOT tell which versions are stable +and which are unstable. The versions are declared to be (more or less) stable +by other means (read: the mailing list and the www site). +It is true, tough, that stable versions are likely to have +more numbers omitted (read: 3.5 looks more "stable" than 3.4.5.43), +but this is not a strict requirement. It is also true that +almost all "unstable" versions come out from the svn tree and +usually contain all the four parts. + +- Official, semi-official and unofficial packages + +We tend to have three types of packages. The official packages are the +ones considered to be stable and released on the site in all the supported forms +(source and various kinds of binaries). The official releases are also announced +in tracker sites and spread between distributors. Since "most" stable, the +official releases are the ones likely to be included in the OS distributions. +The official packages have md5 sums and a gpg signature of one of the KVIrc +developers (with a public key available from a "trusteable" location such +as the KVIrc web site). + +The semi-official packages are snapshots of the source tree made when +some important changes have occured. They are announced on the KVIrc site +only and are likely to be stable (but are not declared officially to be so). +The semi-official packages usually are at least in the source form but +there are likely to be some binaries available too. +We do not sign the semi-official packages but it's still somewhat +granted that WE (the KVIrc Development Team) make them and thus the +source can be trusted. + +The unofficial packages are random snapshots of the svn source tree made +by anyone who wants to do it at any time. They are not announced on the KVIrc +web site (but might be uploaded to ftp.kvirc.net) but rather announced and available +at some other internet location. Since we always try to keep the svn +tree clean and compilable they should work fine but there is no guarantee. +There is no rule for the unofficial package format: there might be source-only +or binary only packages. We *suggest* to use the four part version string format +but in fact they might contain third party patches and even follow their own +derived version numbering scheme. The general rule is: we don't control +the unofficial packages and don't provide support if they don't compile/work +as expected the user/packager is on his own.. but we'll try to be helpful, +if possible :) + +- Putting it all together + +At the moment of writing the KVIrc svn tree has version 3.2.6.20070115. +Today is 15 Jan 2007 and the current svn revision number is 174. +The latest "semi-official" release was 3.2.6 (where the internal revision number +was omitted and implicitly assumed to be 0). +If tomorrow we had to emit a quick fix for the semi-official release we'd either +use 3.2.7 (increasing the public revision for a large set of bugfixes) or +(unlikely) 3.2.6.20060116 (expliciting the internal revision number for a small +set of quick, and probably dirty, bugfixes). The next "semi-official" +release is likely to be 3.2.7 while the next official stable release +might be 3.3, 3.4 or even 4. + +------------------------------------------------------------------------------- +Porting to Qt 4.x (while mantaining Qt 3.x compatibility) (Work In Progress) +------------------------------------------------------------------------------- + +For the moment, in random order: + +- Avoid using QString::null, use KviQString::empty instead. + This is because Qt 4.x does NOT have a null static variable. Qt 4.x in fact + does not have the distinction between null and empty strings (Note that for + KviStr this choice was made since the beginning). + Do NOT replace all the uses of QString::null with QString() (as the qt 4.x + porting documentation suggests) since for Qt 3.x this construct is SLOW. + +- We're building a compatibility layer in kvilib. + Before using ANY Qt class, look if there is an override in kvilib. + In fact always, prefer Kvi* classes over the Q* ones and include + the "kvi_*.h" files instead of the ones. + +- Widgets will be probably abstracted in kvilib/tal. + +- Qt 4.x has no QCString anymore. It uses QByteArray instead. From my own + point of view this is ugly since the name is misleading and QByteArray + is forced to mantain the null terminator which is not needed + in normal "byte array" operations...but well, we have to live with it. + kvilib has kvi_qcstring.h that defines the KviQCString MACRO. + It expands to QCString under Qt 3.x and QByteArray under Qt 4.x. + +- Use: + #ifdef COMPILE_USE_QT4 + to check if the compilation requires Qt 4.x or Qt 3.x. + Later this *might* be automatically replaced with + #if QT_VERSION >= 0x040000 + +- Use: + ./configure --enable-debug --enable-qt4 --with-qt4-moc=/path/moc + make clean + make + to switch to Qt 4.x + Use: + ./configure --enable-debug + make clean + make + to switch back to Qt 3.x + +- Use less possible Qt3Compat features. + +- Before committing to the svn always test your changes under Qt 3.x: this is + the primary goal for now: keeping 3.x compatibility. + Qt 3.x-only developers are encouraged (but not required) to test their + changes agains Qt 4.x. + +- Use the KviQString::* wrapper functions around QString (take a look at + kvi_qstring.h) even if there exist QString functions that do the same + thing. This is because the QString interface has changed a lot between + Qt 3.x and Qt 4.x and KviQString introduces a compatibility layer. + +- Do not use the "char * c = KviQString::toUtf8(string).data();" construct. + It leads to crashes on many compilers since the returned KviQCString + goes out of scope just at the end of the instruction. + +------------------------------------------------------------------------------- +Code documentation +------------------------------------------------------------------------------- + +KVIrc is LARGE. We need to start documenting the source code if we want +to understand our own code in a year from now and if we want help from +others. + +Use doxygen. + +There is a Doxyfile in the admin subdirectory. You can either +run doxygen from there or simply type "make devdocs" from the +top directory of the source tree. +Then take a look at doc/api/html/annotated.html + +Let's also try to document the code we write: the doxygen syntax +is trivial and you can find a 5 minute tutorial by googling. + diff --git a/doc/scriptexamples/Makefile.am b/doc/scriptexamples/Makefile.am new file mode 100644 index 00000000..a63d4435 --- /dev/null +++ b/doc/scriptexamples/Makefile.am @@ -0,0 +1,7 @@ +############################################################################### +# KVirc IRC client Makefile - 16.12.98 Szymon Stefanek +############################################################################### + +SUBDIRS = antiidle minesweeper mp3share playing runmenu simplehttp tutorial + +EXTRA_DIST = *.kvs diff --git a/doc/scriptexamples/README b/doc/scriptexamples/README new file mode 100644 index 00000000..be35ddce --- /dev/null +++ b/doc/scriptexamples/README @@ -0,0 +1,6 @@ +This directory and the subdirectories contain a set of KVIrc scripting examples/tests. + +The *.kvs files in this directory are mostly tests written while implementing scripting +language features. They're rather simple (but also useless) so you can use them to learn basic scripting :) + +The subdirectories contain more complex scripts written with the demonstration purpose. diff --git a/doc/scriptexamples/antiidle/Makefile.am b/doc/scriptexamples/antiidle/Makefile.am new file mode 100644 index 00000000..840a6b4e --- /dev/null +++ b/doc/scriptexamples/antiidle/Makefile.am @@ -0,0 +1,5 @@ +############################################################################### +# KVirc IRC client Makefile - 16.12.98 Szymon Stefanek +############################################################################### + +EXTRA_DIST = antiidle.kvs diff --git a/doc/scriptexamples/antiidle/antiidle.kvs b/doc/scriptexamples/antiidle/antiidle.kvs new file mode 100644 index 00000000..a4b59cca --- /dev/null +++ b/doc/scriptexamples/antiidle/antiidle.kvs @@ -0,0 +1,159 @@ +# +# anti idle script +# : some people like it, some people need it +# : by Balboy :)) +# + +# creating the main alias + +alias(aidle) +{ + # using a switch to see what option has been selected + switch($0) + { + # ok, so the script should start + case(start): + { + # checking if it wasn't running already + if(!%Aidlestatus{$ic}) + { + # the script wasn't running already, so it should be started by calling the + # script with the run parameter + aidle internal_run + # saving the status of the anti idle script + %Aidlestatus{$ic} = 1 + # an anti idle var is set, to define the speed of the anti itde script + # there are 2 possible ways + %Aidletype{$ic} = 1 + echo "Anti idle has been enabled" + } else { + # the script was already running + echo "Anti idle has already been enabled on this server" + } + } + break + # the script should be halted + case(stop): + { + # checking if it was already running + if(%Aidlestatus{$ic}) + { + # the script was running, so it should be stopped by killing the timer + killtimer antiidle{$ic} + # clearing variabled + %Aidlestatus{$ic} = "" + %Aidletype{$ic} = "" + echo "Anti idle has been disabled" + } else { + # the script wasn't running + echo "Anti idle has not been enabled on this server" + } + } + break + # the script status should be shown + case(status): + { + # checking the status variable + if(%Aidlestatus{$ic}) + { + echo "anti idle is enabled on this server" + } else { + echo "anti idle is disabled on this server" + } + } + break + # this is a parameter that should only be called by the script itself + # this is where the idle time gets actualy killed + + case(internal_run): + { + # this part will make a varianle to switch random anti idle modes (fast/slow) + # note: once a type has been decided, changing the type works by a small chance + %aidletypecheck{$ic} = $rand(100) + if(%aidletypecheck{$ic} < 10) + { + if(%Aidletype{$ic} == 1) + { + %Aidletype{$ic} = 2 + } else { + %Aidletype{$ic} = 1 + } + } + # use the var just created to start one of the anti idle modes + if(%Aidletype{$ic} == 1){ + # starting a timer who will keep sending messages to yourself, no output will be shown + timer -r=$console -s (antiidle{$ic},$(10000 + $rand(50000))) + { + aidle internal_run + # checking if we are online + if($server) + { + raw -q privmsg $me : + } + } + } else { + # this part is simular as above + timer -r=$console -s (antiidle{$ic},$(10000 + $rand(30000))) + { + aidle internal_run + if($server) + { + raw -q privmsg $me : + } + } + } + } + break + # the script should be uninstalled + case(uninstall): + { + echo "the anti idle script has been uninstalled succesfully" + # defining the alias by empty code will remove it + alias(aidle){} + event(412,aidle){} + + } + break + # if help was asked + case(help): + { + echo "usage: /aidle