From 2bda8f7717adf28da4af0d34fb82f63d2868c31d Mon Sep 17 00:00:00 2001 From: toma Date: Wed, 25 Nov 2009 17:56:58 +0000 Subject: Copy the KDE 3.5 branch to branches/trinity for new KDE 3.5 features. BUG:215923 git-svn-id: svn://anonsvn.kde.org/home/kde/branches/trinity/kdeutils@1054174 283d02a7-25f6-0310-bc7c-ecb5cbfe19da --- kdelirc/AUTHORS | 3 + kdelirc/COPYING | 340 +++++ kdelirc/ChangeLog | 0 kdelirc/Makefile.am | 3 + kdelirc/README | 55 + kdelirc/README.profile-creation | 145 ++ kdelirc/README.remote-creation | 129 ++ kdelirc/TODO | 6 + kdelirc/icons/Makefile.am | 3 + kdelirc/icons/hi16-action-ledblue.png | Bin 0 -> 709 bytes kdelirc/icons/hi16-action-ledgreen.png | Bin 0 -> 641 bytes kdelirc/icons/hi16-action-ledlightblue.png | Bin 0 -> 732 bytes kdelirc/icons/hi16-action-ledlightgreen.png | Bin 0 -> 718 bytes kdelirc/icons/hi16-action-ledorange.png | Bin 0 -> 698 bytes kdelirc/icons/hi16-action-ledpurple.png | Bin 0 -> 702 bytes kdelirc/icons/hi16-action-ledred.png | Bin 0 -> 659 bytes kdelirc/icons/hi16-action-ledyellow.png | Bin 0 -> 672 bytes kdelirc/icons/hi32-action-ledblue.png | Bin 0 -> 1384 bytes kdelirc/icons/hi32-action-ledgreen.png | Bin 0 -> 1265 bytes kdelirc/icons/hi32-action-ledlightblue.png | Bin 0 -> 1378 bytes kdelirc/icons/hi32-action-ledlightgreen.png | Bin 0 -> 1464 bytes kdelirc/icons/hi32-action-ledorange.png | Bin 0 -> 1378 bytes kdelirc/icons/hi32-action-ledpurple.png | Bin 0 -> 1327 bytes kdelirc/icons/hi32-action-ledred.png | Bin 0 -> 1207 bytes kdelirc/icons/hi32-action-ledyellow.png | Bin 0 -> 1354 bytes kdelirc/irkick/Makefile.am | 42 + kdelirc/irkick/hi16-app-irkick.png | Bin 0 -> 954 bytes kdelirc/irkick/hi22-app-irkick.png | Bin 0 -> 1457 bytes kdelirc/irkick/hi32-app-irkick.png | Bin 0 -> 2421 bytes kdelirc/irkick/icons/Makefile.am | 3 + kdelirc/irkick/icons/hi16-action-irkick.png | Bin 0 -> 954 bytes kdelirc/irkick/icons/hi16-action-irkickflash.png | Bin 0 -> 892 bytes kdelirc/irkick/icons/hi16-action-irkickoff.png | Bin 0 -> 1016 bytes kdelirc/irkick/irkick.cpp | 336 +++++ kdelirc/irkick/irkick.desktop | 116 ++ kdelirc/irkick/irkick.h | 132 ++ kdelirc/irkick/irkick.project | 12 + kdelirc/irkick/kdedmodule_stub.h | 34 + kdelirc/irkick/klircclient.cpp | 241 ++++ kdelirc/irkick/klircclient.h | 114 ++ kdelirc/irkick/lo16-app-irkick.png | Bin 0 -> 381 bytes kdelirc/irkick/lo32-app-irkick.png | Bin 0 -> 603 bytes kdelirc/irkick/main.cpp | 39 + kdelirc/kcmlirc/Makefile.am | 15 + kdelirc/kcmlirc/addaction.cpp | 375 +++++ kdelirc/kcmlirc/addaction.h | 73 + kdelirc/kcmlirc/addactionbase.ui | 1608 ++++++++++++++++++++++ kdelirc/kcmlirc/editaction.cpp | 362 +++++ kdelirc/kcmlirc/editaction.h | 55 + kdelirc/kcmlirc/editactionbase.ui | 1287 +++++++++++++++++ kdelirc/kcmlirc/editmode.cpp | 38 + kdelirc/kcmlirc/editmode.h | 33 + kdelirc/kcmlirc/editmodebase.ui | 303 ++++ kdelirc/kcmlirc/kcmlirc.cpp | 544 ++++++++ kdelirc/kcmlirc/kcmlirc.desktop | 119 ++ kdelirc/kcmlirc/kcmlirc.h | 83 ++ kdelirc/kcmlirc/kcmlircbase.ui | 506 +++++++ kdelirc/kcmlirc/kcmlircbase.ui.h | 37 + kdelirc/kcmlirc/modeslist.cpp | 33 + kdelirc/kcmlirc/modeslist.h | 33 + kdelirc/kcmlirc/newmode.ui | 158 +++ kdelirc/kcmlirc/newmode.ui.h | 24 + kdelirc/kcmlirc/selectprofile.ui | 128 ++ kdelirc/kdelirc/Makefile.am | 45 + kdelirc/kdelirc/arguments.cpp | 36 + kdelirc/kdelirc/arguments.h | 32 + kdelirc/kdelirc/iraction.cpp | 155 +++ kdelirc/kdelirc/iraction.h | 88 ++ kdelirc/kdelirc/iractions.cpp | 90 ++ kdelirc/kdelirc/iractions.h | 52 + kdelirc/kdelirc/mode.cpp | 51 + kdelirc/kdelirc/mode.h | 50 + kdelirc/kdelirc/modes.cpp | 128 ++ kdelirc/kdelirc/modes.h | 62 + kdelirc/kdelirc/profileserver.cpp | 159 +++ kdelirc/kdelirc/profileserver.h | 142 ++ kdelirc/kdelirc/prototype.cpp | 67 + kdelirc/kdelirc/prototype.h | 54 + kdelirc/kdelirc/remoteserver.cpp | 109 ++ kdelirc/kdelirc/remoteserver.h | 89 ++ kdelirc/profiles/Makefile.am | 5 + kdelirc/profiles/klauncher.profile.xml | 18 + kdelirc/profiles/konqueror.profile.xml | 17 + kdelirc/profiles/noatun.profile.xml | 75 + kdelirc/profiles/profile.dtd | 28 + kdelirc/remotes/Makefile.am | 6 + kdelirc/remotes/RM-0010.remote.xml | 49 + kdelirc/remotes/cimr100.remote.xml | 31 + kdelirc/remotes/hauppauge.remote.xml | 29 + kdelirc/remotes/remote.dtd | 15 + kdelirc/remotes/sherwood.remote.xml | 61 + kdelirc/remotes/sonytv.remote.xml | 30 + 92 files changed, 9340 insertions(+) create mode 100644 kdelirc/AUTHORS create mode 100644 kdelirc/COPYING create mode 100644 kdelirc/ChangeLog create mode 100644 kdelirc/Makefile.am create mode 100644 kdelirc/README create mode 100644 kdelirc/README.profile-creation create mode 100644 kdelirc/README.remote-creation create mode 100644 kdelirc/TODO create mode 100644 kdelirc/icons/Makefile.am create mode 100644 kdelirc/icons/hi16-action-ledblue.png create mode 100644 kdelirc/icons/hi16-action-ledgreen.png create mode 100644 kdelirc/icons/hi16-action-ledlightblue.png create mode 100644 kdelirc/icons/hi16-action-ledlightgreen.png create mode 100644 kdelirc/icons/hi16-action-ledorange.png create mode 100644 kdelirc/icons/hi16-action-ledpurple.png create mode 100644 kdelirc/icons/hi16-action-ledred.png create mode 100644 kdelirc/icons/hi16-action-ledyellow.png create mode 100644 kdelirc/icons/hi32-action-ledblue.png create mode 100644 kdelirc/icons/hi32-action-ledgreen.png create mode 100644 kdelirc/icons/hi32-action-ledlightblue.png create mode 100644 kdelirc/icons/hi32-action-ledlightgreen.png create mode 100644 kdelirc/icons/hi32-action-ledorange.png create mode 100644 kdelirc/icons/hi32-action-ledpurple.png create mode 100644 kdelirc/icons/hi32-action-ledred.png create mode 100644 kdelirc/icons/hi32-action-ledyellow.png create mode 100644 kdelirc/irkick/Makefile.am create mode 100644 kdelirc/irkick/hi16-app-irkick.png create mode 100644 kdelirc/irkick/hi22-app-irkick.png create mode 100644 kdelirc/irkick/hi32-app-irkick.png create mode 100644 kdelirc/irkick/icons/Makefile.am create mode 100644 kdelirc/irkick/icons/hi16-action-irkick.png create mode 100644 kdelirc/irkick/icons/hi16-action-irkickflash.png create mode 100644 kdelirc/irkick/icons/hi16-action-irkickoff.png create mode 100644 kdelirc/irkick/irkick.cpp create mode 100644 kdelirc/irkick/irkick.desktop create mode 100644 kdelirc/irkick/irkick.h create mode 100644 kdelirc/irkick/irkick.project create mode 100644 kdelirc/irkick/kdedmodule_stub.h create mode 100644 kdelirc/irkick/klircclient.cpp create mode 100644 kdelirc/irkick/klircclient.h create mode 100644 kdelirc/irkick/lo16-app-irkick.png create mode 100644 kdelirc/irkick/lo32-app-irkick.png create mode 100644 kdelirc/irkick/main.cpp create mode 100644 kdelirc/kcmlirc/Makefile.am create mode 100644 kdelirc/kcmlirc/addaction.cpp create mode 100644 kdelirc/kcmlirc/addaction.h create mode 100644 kdelirc/kcmlirc/addactionbase.ui create mode 100644 kdelirc/kcmlirc/editaction.cpp create mode 100644 kdelirc/kcmlirc/editaction.h create mode 100644 kdelirc/kcmlirc/editactionbase.ui create mode 100644 kdelirc/kcmlirc/editmode.cpp create mode 100644 kdelirc/kcmlirc/editmode.h create mode 100644 kdelirc/kcmlirc/editmodebase.ui create mode 100644 kdelirc/kcmlirc/kcmlirc.cpp create mode 100644 kdelirc/kcmlirc/kcmlirc.desktop create mode 100644 kdelirc/kcmlirc/kcmlirc.h create mode 100644 kdelirc/kcmlirc/kcmlircbase.ui create mode 100644 kdelirc/kcmlirc/kcmlircbase.ui.h create mode 100644 kdelirc/kcmlirc/modeslist.cpp create mode 100644 kdelirc/kcmlirc/modeslist.h create mode 100644 kdelirc/kcmlirc/newmode.ui create mode 100644 kdelirc/kcmlirc/newmode.ui.h create mode 100644 kdelirc/kcmlirc/selectprofile.ui create mode 100644 kdelirc/kdelirc/Makefile.am create mode 100644 kdelirc/kdelirc/arguments.cpp create mode 100644 kdelirc/kdelirc/arguments.h create mode 100644 kdelirc/kdelirc/iraction.cpp create mode 100644 kdelirc/kdelirc/iraction.h create mode 100644 kdelirc/kdelirc/iractions.cpp create mode 100644 kdelirc/kdelirc/iractions.h create mode 100644 kdelirc/kdelirc/mode.cpp create mode 100644 kdelirc/kdelirc/mode.h create mode 100644 kdelirc/kdelirc/modes.cpp create mode 100644 kdelirc/kdelirc/modes.h create mode 100644 kdelirc/kdelirc/profileserver.cpp create mode 100644 kdelirc/kdelirc/profileserver.h create mode 100644 kdelirc/kdelirc/prototype.cpp create mode 100644 kdelirc/kdelirc/prototype.h create mode 100644 kdelirc/kdelirc/remoteserver.cpp create mode 100644 kdelirc/kdelirc/remoteserver.h create mode 100644 kdelirc/profiles/Makefile.am create mode 100644 kdelirc/profiles/klauncher.profile.xml create mode 100644 kdelirc/profiles/konqueror.profile.xml create mode 100644 kdelirc/profiles/noatun.profile.xml create mode 100644 kdelirc/profiles/profile.dtd create mode 100644 kdelirc/remotes/Makefile.am create mode 100644 kdelirc/remotes/RM-0010.remote.xml create mode 100644 kdelirc/remotes/cimr100.remote.xml create mode 100644 kdelirc/remotes/hauppauge.remote.xml create mode 100644 kdelirc/remotes/remote.dtd create mode 100644 kdelirc/remotes/sherwood.remote.xml create mode 100644 kdelirc/remotes/sonytv.remote.xml (limited to 'kdelirc') diff --git a/kdelirc/AUTHORS b/kdelirc/AUTHORS new file mode 100644 index 0000000..c6474a8 --- /dev/null +++ b/kdelirc/AUTHORS @@ -0,0 +1,3 @@ +Code mostly by Gav Wood +LIRC interface code adapted from Noatun/Infrared by Malte Starostik. + diff --git a/kdelirc/COPYING b/kdelirc/COPYING new file mode 100644 index 0000000..c13faf0 --- /dev/null +++ b/kdelirc/COPYING @@ -0,0 +1,340 @@ + GNU GENERAL PUBLIC LICENSE + Version 2, June 1991 + + 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. + + END OF TERMS AND CONDITIONS + + How to Apply These Terms to Your New Programs + + If you develop a new program, and you want it to be of the greatest +possible use to the public, the best way to achieve this is to make it +free software which everyone can redistribute and change under these terms. + + To do so, attach the following notices to the program. It is safest +to attach them to the start of each source file to most effectively +convey the exclusion of warranty; and each file should have at least +the "copyright" line and a pointer to where the full notice is found. + + + Copyright (C) + + This program is free software; you can redistribute it and/or modify + it under the terms of the GNU General Public License as published by + the Free Software Foundation; either version 2 of the License, or + (at your option) any later version. + + This program is distributed in the hope that it will be useful, + but WITHOUT ANY WARRANTY; without even the implied warranty of + MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the + GNU General Public License for more details. + + You should have received a copy of the GNU General Public License + along with this program; if not, write to the Free Software + Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301 USA + + +Also add information on how to contact you by electronic and paper mail. + +If the program is interactive, make it output a short notice like this +when it starts in an interactive mode: + + Gnomovision version 69, Copyright (C) year name of author + Gnomovision comes with ABSOLUTELY NO WARRANTY; for details type `show w'. + This is free software, and you are welcome to redistribute it + under certain conditions; type `show c' for details. + +The hypothetical commands `show w' and `show c' should show the appropriate +parts of the General Public License. Of course, the commands you use may +be called something other than `show w' and `show c'; they could even be +mouse-clicks or menu items--whatever suits your program. + +You should also get your employer (if you work as a programmer) or your +school, if any, to sign a "copyright disclaimer" for the program, if +necessary. Here is a sample; alter the names: + + Yoyodyne, Inc., hereby disclaims all copyright interest in the program + `Gnomovision' (which makes passes at compilers) written by James Hacker. + + , 1 April 1989 + Ty Coon, President of Vice + +This General Public License does not permit incorporating your program into +proprietary programs. If your program is a subroutine library, you may +consider it more useful to permit linking proprietary applications with the +library. If this is what you want to do, use the GNU Library General +Public License instead of this License. diff --git a/kdelirc/ChangeLog b/kdelirc/ChangeLog new file mode 100644 index 0000000..e69de29 diff --git a/kdelirc/Makefile.am b/kdelirc/Makefile.am new file mode 100644 index 0000000..bb18f1c --- /dev/null +++ b/kdelirc/Makefile.am @@ -0,0 +1,3 @@ + +SUBDIRS = icons kdelirc irkick kcmlirc profiles remotes + diff --git a/kdelirc/README b/kdelirc/README new file mode 100644 index 0000000..31af5d0 --- /dev/null +++ b/kdelirc/README @@ -0,0 +1,55 @@ +kdelirc +------- + +KDELIRC is a KDE frontend for the Linux Infrared Remote Control system. It has +two aims: + +1. Provide a control center module for configuration of: + a) Application bindings to remote control buttons. + b) Actual remote controls installed (i.e. lirc configuration). + +2. Provide a system-tray applet to act as a proxy between the LIRC system and + KDE (applications), in order to launch DCOP requests (and potentially + other IPC signals) to applications (and potentially collect/display + results). + +INSTALLATION + +Nothing but the normal ./configure && make && su -c "make install". + +SETUP + +For the KDELirc system to work properly, you *must* have lircd configured and +running. If you have already had a Lirc program running, then you most likely +have Lirc set up properly. If not, be sure that you have a correct kernel module +loaded for your IR receiver (1) and that the lircd program is running (2). + +You must also have some remote controls configured in "/etc/lircd.conf". Go to +the lircd website (www.lirc.org) for more information on this. + +(1) /sbin/lsmod | grep lirc +If you see some output, you have a lirc kernel module loaded (that's not to say +it's the right module for your hardware). + +(2) ps aux | grep -v grep | grep lircd +If you see some output, you have the lircd program running. This is good. + +DESIGN + +The design of the system is really quite simple---a control center module +modifies a centralised configuration file to determine what action(s) should +be taken on a remote control's button press. + +The same(?) module also provides a front-end for the input of /etc/lircd.conf, +necessary to specify remote controls to the LIRC system. An extra (standard +format XML-based) may be provided with the remote control description to give +less sucky (lower case, no spaces/symbols) names. + +The /etc/lircd.conf frontend has not yet been implemented, though all other +features are. + +The system tray applet interfaces with LIRC in order to catch key presses on +remote controls. It is then able to communicate with and potentially start +applications through DCOP. + +Gav Wood, 2003 (gav at kde dot org). diff --git a/kdelirc/README.profile-creation b/kdelirc/README.profile-creation new file mode 100644 index 0000000..95d9e78 --- /dev/null +++ b/kdelirc/README.profile-creation @@ -0,0 +1,145 @@ +How to give your KDE application IR support under KDE. +====================================================== + +by Gav Wood, 2003. + +Introduction +------------ + +All DCOP-using applications under KDE have basic lirc support, since KDELirc has +the ability to interface any button to any DCOP call. However, to give your +application the real professional touch when using it with KDELirc, I recommend +you create a profile for it. + +A profile tells KDELirc (and the user!) what the various DCOP calls do. +Essentially this is a kind of documentation for the DCOP calls. You don't have +to include all DCOP calls - just the ones that you feel would benefit end-users +the most (usually "interface adjusting" calls rather the "information gathering" +calls). + + +Method +------ + +1. DCOP + +The first thing to do is to give your application DCOP functionality. This is +*very* easy and essentially amounts to adding a declaration to each object you +want to give DCOP accessibility and adding an entry to your Makefile. I wont go +into it here as the KDE documentation already provides a suitable resource for +such information. + +Ensure you provide a full accessibility to your application's interface by DCOP, +and especially in the case of IR-interfacing, try not to have functions with too +many parameters, or with exotic types (stick to ints and QStrings where +necessary). + +2. Create a profile + +Having coded the necessary DCOP functionality into your application, the only +other thing to do is describe how it works to the user. This is done by means of +a .profile.xml document, examples of which may be found in the kdelirc/profiles +directory. A quick guide is given here: + +a) First create top level "profile" tags with the DCOP application id and KDE +service name (found in the .desktop file) as attributes of them: + + + + + + +b) Inside populate with name and author information. If your application is not a +KUniqueApplication, you **must** declare this with an "instances" tag, giving the +attribute "unique" a value of "0" (it defaults to "1", a KUniqueApplication). You +may optionally describe the default behavior KDELirc should take should there be +more than one instance of the application, with the attribute "ifmulti" which may +take one of "dontsend" (do nothing if >1 instance), "sendtoone" (send call to one +arbitrarily chosen instance) and "sendtoall" (send to all instances). The default +is "dontsend", however, "sendtoone" may be the most useful in many circumstances. + + + + + My Application + Me + + + +c) Populate the profile with action tags, for each DCOP action you want to be +available to the user. Each action tag should have DCOP object name and function +prototype. + Several optional attrubutes to specify are the key-class (an identifier to +act as an abstract binding between remote controls and applications). There are +several defined; see the DTD files for a current list. The other options, repeat +and autostart are boolean specificers to tell whether the action should repeat +or automatically start the program by default. + + + + + My Application + Me + + + + + +d) Give the action a name and comment: + + + + + My Application + Me + + + Show Integers + Shows a configurable integer + + + +e) Describe each argument with a comment and type attribute. Valid types are +found in the profile.dtd file. If you cant find the exact type, just use one +that is silently castable. You should declare a default value between the +default tags: + + + + + My Application + Me + + + Show Integers + Shows a configurable integer + + 5 + The integer to be shown + + + + +When you have created your profile.xml file, put in your project's main source +tree. + +3. Profile installation + +There is a data directory in KDE reserved for profiles such as these; it's path +is "$(kde_datadir)/profiles". These extra lines must therefore be added to your +Makefile.am in the directory of your profile.xml: + + profiledata_DATA = [YOURAPPHERE].profile.xml + profiledatadir = $(kde_datadir)/profiles + EXTRA_DIST = $(profiledata_DATA) + +(replace [YOURAPPHERE] with your application name---the prefix to your +profile.xml file.) + + +4. Finished + +That's it you're done! Your KDE application is now fully IR enabled. diff --git a/kdelirc/README.remote-creation b/kdelirc/README.remote-creation new file mode 100644 index 0000000..3582351 --- /dev/null +++ b/kdelirc/README.remote-creation @@ -0,0 +1,129 @@ +How to give your LIRC remote control KDELIRC functionality +========================================================== + +by Gav Wood, 2003. + +Introduction +------------ + +All LIRC-understandable remote controls automatically function in KDELirc. +However, to get the advanced (really cool) KDELirc stuff you'll need to create a +remote.xml file for your remote control. The files are simple and easy to create +so don't be put off. + +The function of the remote.xml file is to describe what the remote controls' +buttons do in a general manner and to provide free-form text names for them, +since LIRC only allows non-spaces, non-symbolic charecters in the remote control +definition files. + +When you're finished your remote.xml, you might want to send it to me +(gav at kde dot org) for inclusion in the distribution of KDELirc. It may soon +be possible to distribute the remote.xml files along with the lircd.conf files. + +Method +------ + +a) Start with the basic template and define the LIRC ID of the remote control. +The LIRC ID is most important, and must be the identifier (look for the line +"name <...>" after the "begin remote" line). put the text after "name" into "id" +attribute of the "remote" tag in the "lircd.conf" file ("/etc/lircd.conf"). + In addition to this, fill in the author and name tags with your name and the +"nice" name of the remote control. Any extra information you may wish to give it +(such as alternate names, multimedia bundles/system is comes with etc) may be +enclosed between optional information tags: + + + + + + My Remote Control + Me + As bundled with ACME LinTV + + +This would compliment a "lircd.conf" file: + + begin remote + name myremote + ... + end remote + +b) With the hard work out of the way, just start going though each button on the +remote control. For each button, make sure the "id" attribute is the same as in +the lircd.conf file. + For each (common) button, you might also want to specify the class, which will +help KDELirc match it to any application's action. For a list of all button +classes, look in the remote.dtd file which comes with KDELirc. If the class type +is one which encompasses many buttons, for example "number", then you should also +specify which number it is in the parameter attribute. Currently, this only +actually applies to "number" - all other classes are simple and do not require a +parameter attribute. + Note: If no "class" is given, it will default to the "id". In the unlikely +case that this is not what you want, simply define it to be null (class=""). + + + + + + My Remote Control + Me + + + + +This would compliment a "lircd.conf" file: + + begin remote + name myremote + ... + begin raw_codes + name num0 + ... + name rec + ... + end raw_codes + end remote + +c) The last thing to define in each of your buttons is the "nice" name. This may +be descriptive and use spaces, symbols and mixed case text, in a similar fashion +to the remote control's name. There is no need to copy the remote control's label +verbatim. If necessary expand the description to provide a readable, aethetically +pleasing label e.g. you should name the "CC" button "Closed Captions" or the "Rec" +button "Record". + + + + + + My Remote Control + Me + + + + + Note: The name of a button will automatically default to its "id", so you can +save yourself some time and effort with buttons which share the same name and id +by changing + + + +to the far less cluttered and simpler: + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + diff --git a/kdelirc/remotes/cimr100.remote.xml b/kdelirc/remotes/cimr100.remote.xml new file mode 100644 index 0000000..5dfc36d --- /dev/null +++ b/kdelirc/remotes/cimr100.remote.xml @@ -0,0 +1,31 @@ + + + + + Creative CIMR-100 + Gav Wood + + + + + + + + + + + + + + + diff --git a/kdelirc/remotes/hauppauge.remote.xml b/kdelirc/remotes/hauppauge.remote.xml new file mode 100644 index 0000000..4d2a402 --- /dev/null +++ b/kdelirc/remotes/hauppauge.remote.xml @@ -0,0 +1,29 @@ + + + + + Hauppauge + Dirk Ziegelmeier + Bundled with WinTV PCI, PVR + + + + + + + + + + + + diff --git a/kdelirc/remotes/remote.dtd b/kdelirc/remotes/remote.dtd new file mode 100644 index 0000000..a09b4b6 --- /dev/null +++ b/kdelirc/remotes/remote.dtd @@ -0,0 +1,15 @@ + + + + + + + + + + + + + diff --git a/kdelirc/remotes/sherwood.remote.xml b/kdelirc/remotes/sherwood.remote.xml new file mode 100644 index 0000000..db628ba --- /dev/null +++ b/kdelirc/remotes/sherwood.remote.xml @@ -0,0 +1,61 @@ + + + + + Sherwood RM-RD-61 + Gav Wood + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + diff --git a/kdelirc/remotes/sonytv.remote.xml b/kdelirc/remotes/sonytv.remote.xml new file mode 100644 index 0000000..4e5ee97 --- /dev/null +++ b/kdelirc/remotes/sonytv.remote.xml @@ -0,0 +1,30 @@ + + + + + SonyTV + Bundled with some Sony TVs + Dirk Ziegelmeier + + + + + + + + + + + + + -- cgit v1.2.1