diff --git a/CMakeLists.txt b/CMakeLists.txt index e376de1..62c4e34 100644 --- a/CMakeLists.txt +++ b/CMakeLists.txt @@ -110,8 +110,8 @@ option( BUILD_ARK "Build ark" ${BUILD_ALL} ) option( BUILD_CHARSELECTAPPLET "Build charselectapplet" ${BUILD_ALL} ) option( BUILD_KCALC "Build kcalc" ${BUILD_ALL} ) option( BUILD_KCHARSELECT "Build kcharselect" ${BUILD_ALL} ) -option( BUILD_KDELIRC "Build kdelirc" ${BUILD_ALL} ) -option( BUILD_KDESSH "Build kdessh" ${BUILD_ALL} ) +option( BUILD_TDELIRC "Build tdelirc" ${BUILD_ALL} ) +option( BUILD_TDESSH "Build tdessh" ${BUILD_ALL} ) option( BUILD_KDF "Build kdf" ${BUILD_ALL} ) option( BUILD_KEDIT "Build kedit" ${BUILD_ALL} ) option( BUILD_KFLOPPY "Build kfloppy" ${BUILD_ALL} ) @@ -160,8 +160,8 @@ tde_conditional_add_subdirectory( BUILD_DOC doc ) tde_conditional_add_subdirectory( BUILD_CHARSELECTAPPLET charselectapplet ) tde_conditional_add_subdirectory( BUILD_KCALC kcalc ) tde_conditional_add_subdirectory( BUILD_KCHARSELECT kcharselect ) -tde_conditional_add_subdirectory( BUILD_KDELIRC kdelirc ) -tde_conditional_add_subdirectory( BUILD_KDESSH kdessh ) +tde_conditional_add_subdirectory( BUILD_TDELIRC tdelirc ) +tde_conditional_add_subdirectory( BUILD_TDESSH tdessh ) tde_conditional_add_subdirectory( BUILD_KDF kdf ) tde_conditional_add_subdirectory( BUILD_KEDIT kedit ) tde_conditional_add_subdirectory( BUILD_KFLOPPY kfloppy ) diff --git a/README b/README index 9e3708e..cc3dbeb 100644 --- a/README +++ b/README @@ -14,7 +14,7 @@ What it is the clipboard * charselectapplet: dito, but as a Kicker applet * kdepasswd: like 'passwd', a graphical password changer -* kdessh: front end to ssh +* tdessh: front end to ssh * kdf: like 'df', a graphical free disk space viewer * kedit: a simple text editor, without formatting like bold, italics etc * kfloppy: format a floppy disks with this app diff --git a/doc/kdelirc/CMakeLists.txt b/doc/tdelirc/CMakeLists.txt similarity index 100% rename from doc/kdelirc/CMakeLists.txt rename to doc/tdelirc/CMakeLists.txt diff --git a/doc/kdelirc/Makefile.am b/doc/tdelirc/Makefile.am similarity index 100% rename from doc/kdelirc/Makefile.am rename to doc/tdelirc/Makefile.am diff --git a/doc/kdelirc/irkick/CMakeLists.txt b/doc/tdelirc/irkick/CMakeLists.txt similarity index 100% rename from doc/kdelirc/irkick/CMakeLists.txt rename to doc/tdelirc/irkick/CMakeLists.txt diff --git a/doc/kdelirc/irkick/Makefile.am b/doc/tdelirc/irkick/Makefile.am similarity index 100% rename from doc/kdelirc/irkick/Makefile.am rename to doc/tdelirc/irkick/Makefile.am diff --git a/doc/kdelirc/irkick/index.docbook b/doc/tdelirc/irkick/index.docbook similarity index 84% rename from doc/kdelirc/irkick/index.docbook rename to doc/tdelirc/irkick/index.docbook index 83c25f3..6ea5f3e 100644 --- a/doc/kdelirc/irkick/index.docbook +++ b/doc/tdelirc/irkick/index.docbook @@ -1,7 +1,7 @@ IRKick"> - KDE LIRC"> + TDE LIRC"> @@ -11,7 +11,7 @@ -&irkick;: The KDE LIRC Server Handbook +&irkick;: The TDE LIRC Server Handbook @@ -34,14 +34,14 @@ &FDLNotice; -&kdelirc; is the infrastructure for the KDE's +&tdelirc; is the infrastructure for the TDE's Infrared Remote Control functionality; &irkick; is the server component of that infrastructure. -KDE +TDE irkick -kdelirc +tdelirc kcmlirc lirc @@ -66,8 +66,8 @@ TDE Control Center or directly from the menu of &irkick;. Requirements -For the KDELirc framework to be utilised you must have setup a LIRC -on your KDE machine. If it is properly set up, the &irkick; icon in +For the TDELirc framework to be utilised you must have setup a LIRC +on your TDE machine. If it is properly set up, the &irkick; icon in the system tray will light up red. If not, it will be grey and crossed out. @@ -90,7 +90,7 @@ remote controls. -Using the right-mouse-button menu, you can configure the KDE infrared remote +Using the right-mouse-button menu, you can configure the TDE infrared remote control framework. @@ -99,7 +99,7 @@ control framework. Credits and Licenses -&kdelirc;: The KDE LIRC Framework Copyright (c) 2004 Gav Wood +&tdelirc;: The TDE LIRC Framework Copyright (c) 2004 Gav Wood gav@kde.org. diff --git a/doc/kdelirc/kcmlirc/CMakeLists.txt b/doc/tdelirc/kcmlirc/CMakeLists.txt similarity index 100% rename from doc/kdelirc/kcmlirc/CMakeLists.txt rename to doc/tdelirc/kcmlirc/CMakeLists.txt diff --git a/doc/kdelirc/kcmlirc/Makefile.am b/doc/tdelirc/kcmlirc/Makefile.am similarity index 100% rename from doc/kdelirc/kcmlirc/Makefile.am rename to doc/tdelirc/kcmlirc/Makefile.am diff --git a/doc/kdelirc/kcmlirc/index.docbook b/doc/tdelirc/kcmlirc/index.docbook similarity index 85% rename from doc/kdelirc/kcmlirc/index.docbook rename to doc/tdelirc/kcmlirc/index.docbook index e3507c3..c60e125 100644 --- a/doc/kdelirc/kcmlirc/index.docbook +++ b/doc/tdelirc/kcmlirc/index.docbook @@ -1,7 +1,7 @@ KDE LIRC Control Center Module"> - KDE LIRC"> + TDE LIRC Control Center Module"> + TDE LIRC"> @@ -10,7 +10,7 @@ -KDE Infrared Remote Control Configuration +TDE Infrared Remote Control Configuration @@ -33,13 +33,13 @@ &FDLNotice; -&kdelirc; configuration: The infrastructure for the KDE's +&tdelirc; configuration: The infrastructure for the TDE's Infrared Remote Control functionality. -KDE +TDE irkick -kdelirc +tdelirc kcmlirc lirc @@ -56,8 +56,8 @@ Infrared Remote Control functionality. Requirements -For the KDELirc framework to be utilised you must have setup a LIRC -on your KDE machine. If it is properly set up, the &kdelirc; icon in +For the TDELirc framework to be utilised you must have setup a LIRC +on your TDE machine. If it is properly set up, the &tdelirc; icon in the system tray (show icon here) will light up red. If not, it will be grey and crossed out. @@ -88,7 +88,7 @@ Each remote control can be in at most one mode at once (it may also be in no mod -The list contains any remote controls detected on your system. Modes may be added and removed by selecting the desired remote control and using the buttons directly below the list Add, Remove. Modes may be renamed "inline" in the standard KDE fashion by first selecting the mode in the list box, and then clicking it again after a short pause. The Edit button allows mode names to be edited, and also allows you to define an icon that will show up in the system tray when that mode is entered. +The list contains any remote controls detected on your system. Modes may be added and removed by selecting the desired remote control and using the buttons directly below the list Add, Remove. Modes may be renamed "inline" in the standard TDE fashion by first selecting the mode in the list box, and then clicking it again after a short pause. The Edit button allows mode names to be edited, and also allows you to define an icon that will show up in the system tray when that mode is entered. @@ -97,7 +97,7 @@ The list contains any remote controls detected on your system. Modes may be adde Action-Button Bindings -An action/button binding ("action") is a connection between a button press and an effect. The effect may be to switch modes, to start a KDE program or to execute a function in a KDE program (using DCOP). +An action/button binding ("action") is a connection between a button press and an effect. The effect may be to switch modes, to start a TDE program or to execute a function in a TDE program (using DCOP). @@ -109,7 +109,7 @@ To add an action/button binding simply use the Add button. Removal may be perfor -Actions may also be "automatically" populated. This handles the instance when you have a supported remote control and you wish to map its buttons to a supported application's functions. &kdelirc; can attempt to match buttons to functions for you; this behaviour may have to be tweaked, however. +Actions may also be "automatically" populated. This handles the instance when you have a supported remote control and you wish to map its buttons to a supported application's functions. &tdelirc; can attempt to match buttons to functions for you; this behaviour may have to be tweaked, however. @@ -118,7 +118,7 @@ Actions may also be "automatically" populated. This handles the instance when yo Loaded Extensions -There is another tab available named "Loaded Extensions". This details the applications and remote controls that &kdelirc; recognises. &kdelirc; can also use unsupported remote controls and applications, but the Auto-Populate function will not work as well (if at all). +There is another tab available named "Loaded Extensions". This details the applications and remote controls that &tdelirc; recognises. &tdelirc; can also use unsupported remote controls and applications, but the Auto-Populate function will not work as well (if at all). @@ -132,7 +132,7 @@ By clicking on an entry you can see information on it such as the author's detai Credits and Licenses -&kdelirc; KDE LIRC Framework Copyright (c) 2004 Gav Wood +&tdelirc; TDE LIRC Framework Copyright (c) 2004 Gav Wood gav@kde.org. Documentation Copyright (c) 2004 by Gav Wood diff --git a/kdelirc/Makefile.am b/kdelirc/Makefile.am deleted file mode 100644 index bb18f1c..0000000 --- a/kdelirc/Makefile.am +++ /dev/null @@ -1,3 +0,0 @@ - -SUBDIRS = icons kdelirc irkick kcmlirc profiles remotes - diff --git a/kdelirc/icons/Makefile.am b/kdelirc/icons/Makefile.am deleted file mode 100644 index 8b53beb..0000000 --- a/kdelirc/icons/Makefile.am +++ /dev/null @@ -1,3 +0,0 @@ -kdelirciconsdir = $(kde_datadir)/irkick/icons -kdelircicons_ICON = AUTO - diff --git a/kdessh/Makefile.am b/kdessh/Makefile.am deleted file mode 100644 index f716244..0000000 --- a/kdessh/Makefile.am +++ /dev/null @@ -1,17 +0,0 @@ -## Makefile.am for kdessh -AM_CPPFLAGS = -DQT_NO_CAST_ASCII - -INCLUDES= $(all_includes) - -## kdessh -bin_PROGRAMS = kdessh -kdessh_SOURCES = kdessh.cpp sshdlg.cpp -kdessh_LDFLAGS = $(all_libraries) $(KDE_RPATH) $(LIB_QT) -lDCOP $(LIB_TDECORE) $(LIB_TDEUI) -ltdefx $(LIB_KIO) -ltdetexteditor -kdessh_LDADD = $(LIB_TDEUI) -ltdesu -kdessh_METASOURCES = AUTO -noinst_HEADERS = sshdlg.h - -## Messages -messages: - $(XGETTEXT) $(kdessh_SOURCES) -o $(podir)/kdessh.pot - diff --git a/kdessh/README b/kdessh/README deleted file mode 100644 index b897486..0000000 --- a/kdessh/README +++ /dev/null @@ -1,3 +0,0 @@ -kdessh: A KDE front end to ssh. - -Please report bugs to Geert Jansen . diff --git a/kdelirc/AUTHORS b/tdelirc/AUTHORS similarity index 100% rename from kdelirc/AUTHORS rename to tdelirc/AUTHORS diff --git a/kdelirc/CMakeLists.txt b/tdelirc/CMakeLists.txt similarity index 93% rename from kdelirc/CMakeLists.txt rename to tdelirc/CMakeLists.txt index 156165f..251c9db 100644 --- a/kdelirc/CMakeLists.txt +++ b/tdelirc/CMakeLists.txt @@ -12,6 +12,6 @@ add_subdirectory( icons ) add_subdirectory( irkick ) add_subdirectory( kcmlirc ) -add_subdirectory( kdelirc ) +add_subdirectory( tdelirc ) add_subdirectory( profiles ) add_subdirectory( remotes ) diff --git a/kdelirc/COPYING b/tdelirc/COPYING similarity index 100% rename from kdelirc/COPYING rename to tdelirc/COPYING diff --git a/tdelirc/Makefile.am b/tdelirc/Makefile.am new file mode 100644 index 0000000..1b42dee --- /dev/null +++ b/tdelirc/Makefile.am @@ -0,0 +1,3 @@ + +SUBDIRS = icons tdelirc irkick kcmlirc profiles remotes + diff --git a/kdelirc/README b/tdelirc/README similarity index 90% rename from kdelirc/README rename to tdelirc/README index 31af5d0..8ae6875 100644 --- a/kdelirc/README +++ b/tdelirc/README @@ -1,7 +1,7 @@ -kdelirc +tdelirc ------- -KDELIRC is a KDE frontend for the Linux Infrared Remote Control system. It has +TDELIRC is a TDE frontend for the Linux Infrared Remote Control system. It has two aims: 1. Provide a control center module for configuration of: @@ -9,7 +9,7 @@ two aims: 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 + TDE (applications), in order to launch DCOP requests (and potentially other IPC signals) to applications (and potentially collect/display results). @@ -19,7 +19,7 @@ Nothing but the normal ./configure && make && su -c "make install". SETUP -For the KDELirc system to work properly, you *must* have lircd configured and +For the TDELirc 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). diff --git a/kdelirc/README.profile-creation b/tdelirc/README.profile-creation similarity index 95% rename from kdelirc/README.profile-creation rename to tdelirc/README.profile-creation index 95d9e78..80ec429 100644 --- a/kdelirc/README.profile-creation +++ b/tdelirc/README.profile-creation @@ -6,12 +6,12 @@ by Gav Wood, 2003. Introduction ------------ -All DCOP-using applications under KDE have basic lirc support, since KDELirc has +All DCOP-using applications under KDE have basic lirc support, since TDELirc 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 +application the real professional touch when using it with TDELirc, I recommend you create a profile for it. -A profile tells KDELirc (and the user!) what the various DCOP calls do. +A profile tells TDELirc (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" @@ -38,7 +38,7 @@ necessary). 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 +a .profile.xml document, examples of which may be found in the tdelirc/profiles directory. A quick guide is given here: a) First create top level "profile" tags with the DCOP application id and KDE @@ -52,7 +52,7 @@ 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 +may optionally describe the default behavior TDELirc 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 diff --git a/kdelirc/README.remote-creation b/tdelirc/README.remote-creation similarity index 90% rename from kdelirc/README.remote-creation rename to tdelirc/README.remote-creation index 5cf5213..a9342c5 100644 --- a/kdelirc/README.remote-creation +++ b/tdelirc/README.remote-creation @@ -1,4 +1,4 @@ -How to give your LIRC remote control KDELIRC functionality +How to give your LIRC remote control TDELIRC functionality ========================================================== by Gav Wood, 2003. @@ -6,8 +6,8 @@ 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 +All LIRC-understandable remote controls automatically function in TDELirc. +However, to get the advanced (really cool) TDELirc 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. @@ -17,7 +17,7 @@ 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 +(gav at kde dot org) for inclusion in the distribution of TDELirc. It may soon be possible to distribute the remote.xml files along with the lircd.conf files. Method @@ -52,8 +52,8 @@ 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 +help TDELirc match it to any application's action. For a list of all button +classes, look in the remote.dtd file which comes with TDELirc. 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 @@ -120,7 +120,7 @@ to the far less cluttered and simpler: