Rename kdessh -> tdessh and kdelirc -> tdelirc.

pull/1/head
Darrell Anderson 11 years ago
parent 7be7990fc5
commit 359294c336

@ -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 )

@ -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

@ -1,7 +1,7 @@
<?xml version="1.0" ?>
<!DOCTYPE book PUBLIC "-//KDE//DTD DocBook XML V4.2-Based Variant V1.1//EN" "dtd/kdex.dtd" [
<!ENTITY irkick "<application>IRKick</application>">
<!ENTITY kdelirc "<application>KDE LIRC</application>">
<!ENTITY tdelirc "<application>TDE LIRC</application>">
<!ENTITY kappname "&irkick;">
<!ENTITY package "tdeutils">
<!ENTITY % English "INCLUDE" > <!-- change language only here -->
@ -11,7 +11,7 @@
<book lang="&language;">
<bookinfo>
<title>&irkick;: The KDE LIRC Server Handbook</title>
<title>&irkick;: The TDE LIRC Server Handbook</title>
<authorgroup>
<author>
@ -34,14 +34,14 @@
<legalnotice>&FDLNotice;</legalnotice>
<abstract><para>&kdelirc; is the infrastructure for the KDE's
<abstract><para>&tdelirc; is the infrastructure for the TDE's
Infrared Remote Control functionality; &irkick; is the server
component of that infrastructure.</para></abstract>
<keywordset>
<keyword>KDE</keyword>
<keyword>TDE</keyword>
<keyword>irkick</keyword>
<keyword>kdelirc</keyword>
<keyword>tdelirc</keyword>
<keyword>kcmlirc</keyword>
<keyword>lirc</keyword>
</keywordset>
@ -66,8 +66,8 @@ TDE Control Center or directly from the menu of &irkick;.
<title>Requirements</title>
<para>
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.
</para>
@ -90,7 +90,7 @@ remote controls.
</para>
<para>
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.
</para>
@ -99,7 +99,7 @@ control framework.
<chapter id="credits">
<title>Credits and Licenses</title>
<para>&kdelirc;: The KDE LIRC Framework Copyright (c) 2004 Gav Wood
<para>&tdelirc;: The TDE LIRC Framework Copyright (c) 2004 Gav Wood
<email>gav@kde.org</email>.</para>
<!-- TRANS:CREDIT_FOR_TRANSLATORS -->

@ -1,7 +1,7 @@
<?xml version="1.0" ?>
<!DOCTYPE book PUBLIC "-//KDE//DTD DocBook XML V4.2-Based Variant V1.1//EN" "dtd/kdex.dtd" [
<!ENTITY kcmlirc "<application>KDE LIRC Control Center Module</application>">
<!ENTITY kdelirc "<application>KDE LIRC</application>">
<!ENTITY kcmlirc "<application>TDE LIRC Control Center Module</application>">
<!ENTITY tdelirc "<application>TDE LIRC</application>">
<!ENTITY % English "INCLUDE" > <!-- change language only here -->
<!ENTITY % addindex "IGNORE">
@ -10,7 +10,7 @@
<book lang="&language;">
<bookinfo>
<title>KDE Infrared Remote Control Configuration</title>
<title>TDE Infrared Remote Control Configuration</title>
<authorgroup>
<author>
@ -33,13 +33,13 @@
<legalnotice>&FDLNotice;</legalnotice>
<abstract><para>&kdelirc; configuration: The infrastructure for the KDE's
<abstract><para>&tdelirc; configuration: The infrastructure for the TDE's
Infrared Remote Control functionality.</para></abstract>
<keywordset>
<keyword>KDE</keyword>
<keyword>TDE</keyword>
<keyword>irkick</keyword>
<keyword>kdelirc</keyword>
<keyword>tdelirc</keyword>
<keyword>kcmlirc</keyword>
<keyword>lirc</keyword>
</keywordset>
@ -56,8 +56,8 @@ Infrared Remote Control functionality.</para></abstract>
<title>Requirements</title>
<para>
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.
</para>
@ -88,7 +88,7 @@ Each remote control can be in at most one mode at once (it may also be in no mod
</para>
<para>
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.
</para>
</sect1>
@ -97,7 +97,7 @@ The list contains any remote controls detected on your system. Modes may be adde
<title>Action-Button Bindings</title>
<para>
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).
</para>
<para>
@ -109,7 +109,7 @@ To add an action/button binding simply use the Add button. Removal may be perfor
</para>
<para>
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.
</para>
</sect1>
@ -118,7 +118,7 @@ Actions may also be "automatically" populated. This handles the instance when yo
<title>Loaded Extensions</title>
<para>
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).
</para>
<para>
@ -132,7 +132,7 @@ By clicking on an entry you can see information on it such as the author's detai
<chapter id="credits">
<title>Credits and Licenses</title>
<para>&kdelirc; KDE LIRC Framework Copyright (c) 2004 Gav Wood
<para>&tdelirc; TDE LIRC Framework Copyright (c) 2004 Gav Wood
<email>gav@kde.org</email>.</para>
<para>Documentation Copyright (c) 2004 by Gav Wood

@ -1,3 +0,0 @@
SUBDIRS = icons kdelirc irkick kcmlirc profiles remotes

@ -1,3 +0,0 @@
kdelirciconsdir = $(kde_datadir)/irkick/icons
kdelircicons_ICON = AUTO

@ -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

@ -1,3 +0,0 @@
kdessh: A KDE front end to ssh.
Please report bugs to Geert Jansen <jansen@kde.org>.

@ -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 )

@ -0,0 +1,3 @@
SUBDIRS = icons tdelirc irkick kcmlirc profiles remotes

@ -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).

@ -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

@ -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:
<button id="num0" class="number" parameter="0"/>
That's it - just save it as <id>.remote.xml, where <id> is the ID of the remote
control (*not* its name but the LIRC id!) and copy it to your KDE remotes data
control (*not* its name but the LIRC id!) and copy it to your TDE remotes data
directory (~/.trinity/share/apps/remotes).
You'll probably need to restart control center before the remote definition

@ -0,0 +1,3 @@
tdelirciconsdir = $(kde_datadir)/irkick/icons
tdelircicons_ICON = AUTO

@ -15,14 +15,14 @@ include_directories(
${CMAKE_BINARY_DIR}
${CMAKE_CURRENT_BINARY_DIR}
${CMAKE_CURRENT_SOURCE_DIR}
${CMAKE_SOURCE_DIR}/kdelirc/kdelirc
${CMAKE_SOURCE_DIR}/tdelirc/tdelirc
${TDE_INCLUDE_DIR}
${TQT_INCLUDE_DIRS}
)
link_directories(
${TQT_LIBRARY_DIRS}
${CMAKE_BINARY_DIR}/kdelirc/kdelirc
${CMAKE_BINARY_DIR}/tdelirc/tdelirc
)
@ -31,7 +31,7 @@ link_directories(
tde_add_library( irkick_common STATIC_PIC AUTOMOC
SOURCES irkick.cpp irkick.skel
irkick.stub klircclient.cpp
LINK tdeui-shared kdelirc-static
LINK tdeui-shared tdelirc-static
)

@ -7,7 +7,7 @@ tdeinit_LTLIBRARIES = irkick.la
CLEANFILES = dummy.cpp
libirkick_common_la_LIBADD = $(LIB_TDECORE) $(LIB_TDEUI) $(LIB_KSYCOCA) ../kdelirc/libkdelirc.la
libirkick_common_la_LIBADD = $(LIB_TDECORE) $(LIB_TDEUI) $(LIB_KSYCOCA) ../tdelirc/libtdelirc.la
libirkick_common_la_SOURCES = main.cpp irkick.cpp irkick.skel irkick.stub klircclient.cpp
libirkick_common_la_LDFLAGS = $(all_libraries)
@ -32,11 +32,11 @@ dummy.cpp:
#lib_LTLIBRARIES = libkded_irkick.la
#libkded_irkick_la_SOURCES = irkick.cpp irkick.skel irkick.stub klircclient.cpp
#libkded_irkick_la_LDFLAGS = $(all_libraries) -module -avoid-version
#libkded_irkick_la_LIBADD = $(LIB_TDECORE) ../kdelirc/libkdelirc.la
#libkded_irkick_la_LIBADD = $(LIB_TDECORE) ../tdelirc/libtdelirc.la
noinst_HEADERS = irkick.h klircclient.h irkick_stub.h
INCLUDES = -I$(srcdir)/../kdelirc $(all_includes)
INCLUDES = -I$(srcdir)/../tdelirc $(all_includes)
KDE_ICON = AUTO
METASOURCES = AUTO

@ -29,7 +29,7 @@ extern "C" KDE_EXPORT int kdemain(int argc, char *argv[])
TDECmdLineArgs::init( argc, argv, aboutData );
KUniqueApplication::addCmdLineOptions();
KUniqueApplication app;
TDEGlobal::locale()->insertCatalogue( "kdelirc" );
TDEGlobal::locale()->insertCatalogue( "tdelirc" );
app.disableSessionManagement();
IRKick *theIRKick = new IRKick("IRKick");

@ -12,17 +12,17 @@
include_directories(
${CMAKE_BINARY_DIR}
${CMAKE_CURRENT_BINARY_DIR}
${CMAKE_BINARY_DIR}/kdelirc/irkick
${CMAKE_BINARY_DIR}/tdelirc/irkick
${CMAKE_CURRENT_SOURCE_DIR}
${CMAKE_SOURCE_DIR}/kdelirc/irkick
${CMAKE_SOURCE_DIR}/kdelirc/kdelirc
${CMAKE_SOURCE_DIR}/tdelirc/irkick
${CMAKE_SOURCE_DIR}/tdelirc/tdelirc
${TDE_INCLUDE_DIR}
${TQT_INCLUDE_DIRS}
)
link_directories(
${TQT_LIBRARY_DIRS}
${CMAKE_BINARY_DIR}/kdelirc/kdelirc
${CMAKE_BINARY_DIR}/tdelirc/tdelirc
)
@ -34,7 +34,7 @@ tde_add_kpart( kcm_kcmlirc AUTOMOC
addaction.cpp kcmlirc.skel editactionbase.ui
editmodebase.ui editmode.cpp editaction.cpp
modeslist.cpp
LINK kdelirc-static tdeui-shared tdeio-shared
LINK tdelirc-static tdeui-shared tdeio-shared
DESTINATION ${PLUGIN_INSTALL_DIR}
)

@ -1,4 +1,4 @@
INCLUDES = -I../irkick -I$(srcdir)/../irkick -I$(srcdir)/../kdelirc $(all_includes)
INCLUDES = -I../irkick -I$(srcdir)/../irkick -I$(srcdir)/../tdelirc $(all_includes)
METASOURCES = AUTO
# Install this plugin in the KDE modules directory
@ -6,7 +6,7 @@ kde_module_LTLIBRARIES = kcm_kcmlirc.la
noinst_HEADERS = kcmlirc.h addaction.h addactionbase.h
kcm_kcmlirc_la_SOURCES = selectprofile.ui newmode.ui kcmlircbase.ui kcmlirc.cpp addactionbase.ui addaction.cpp kcmlirc.skel editactionbase.ui editmodebase.ui editmode.cpp editaction.cpp modeslist.cpp
kcm_kcmlirc_la_LIBADD = $(LIB_TDEUI) $(LIB_TDEFILE) ../kdelirc/libkdelirc.la
kcm_kcmlirc_la_LIBADD = $(LIB_TDEUI) $(LIB_TDEFILE) ../tdelirc/libtdelirc.la
kcm_kcmlirc_la_LDFLAGS = -module -avoid-version $(all_libraries) -no-undefined
xdg_apps_DATA = kcmlirc.desktop

@ -22,9 +22,9 @@ link_directories(
)
##### kdelirc (static) ##########################
##### tdelirc (static) ##########################
tde_add_library( kdelirc STATIC_PIC
tde_add_library( tdelirc STATIC_PIC
SOURCES iraction.cpp arguments.cpp
iractions.cpp prototype.cpp modes.cpp
mode.cpp profileserver.cpp remoteserver.cpp

@ -1,13 +1,13 @@
####### tdevelop will overwrite this part!!! (begin)##########
noinst_LTLIBRARIES = libkdelirc.la
noinst_LTLIBRARIES = libtdelirc.la
noinst_HEADERS = iraction.h arguments.h iractions.h prototype.h modes.h mode.h profileserver.h remoteserver.h
libkdelirc_la_SOURCES = iraction.cpp arguments.cpp iractions.cpp prototype.cpp modes.cpp mode.cpp profileserver.cpp remoteserver.cpp
libkdelirc_la_LIBADD = $(LIB_QT) $(LIB_TDECORE) $(LIB_TDEUI) $(LIBSOCKET)
libtdelirc_la_SOURCES = iraction.cpp arguments.cpp iractions.cpp prototype.cpp modes.cpp mode.cpp profileserver.cpp remoteserver.cpp
libtdelirc_la_LIBADD = $(LIB_QT) $(LIB_TDECORE) $(LIB_TDEUI) $(LIBSOCKET)
####### tdevelop will overwrite this part!!! (end)############
# These paths are KDE specific. Use them:
# These paths are TDE specific. Use them:
# kde_appsdir Where your application's menu entry (.desktop) should go to.
# kde_icondir Where your icon should go to - better use KDE_ICON.
# kde_sounddir Where your sounds should go to.
@ -25,16 +25,16 @@ libkdelirc_la_LIBADD = $(LIB_QT) $(LIB_TDECORE) $(LIB_TDEUI) $(LIBSOCKET)
# kde_bindir Where executables should go to. Use bin_PROGRAMS or bin_SCRIPTS.
# kde_libdir Where shared libraries should go to. Use lib_LTLIBRARIES.
# kde_moduledir Where modules (e.g. parts) should go to. Use kde_module_LTLIBRARIES.
# kde_styledir Where Qt/KDE widget styles should go to (new in KDE 3).
# kde_styledir Where Qt/TDE widget styles should go to (new in KDE 3).
# kde_designerdir Where Qt Designer plugins should go to (new in KDE 3).
# set the include path for X, qt and KDE
# set the include path for X, qt and TDE
INCLUDES = $(all_includes)
METASOURCES = AUTO
# the library search path.
libkdelirc_la_LDFLAGS = $(all_libraries) $(KDE_RPATH) $(LIB_QT) -lDCOP $(LIB_TDECORE) $(LIB_TDEUI) -ltdefx $(LIB_KIO) -ltdetexteditor
libtdelirc_la_LDFLAGS = $(all_libraries) $(KDE_RPATH) $(LIB_QT) -lDCOP $(LIB_TDECORE) $(LIB_TDEUI) -ltdefx $(LIB_KIO) -ltdetexteditor
# Uncomment the following two lines if you add a ui.rc file for your application to make use of
# KDE´s XML GUI builing
@ -42,4 +42,4 @@ libkdelirc_la_LDFLAGS = $(all_libraries) $(KDE_RPATH) $(LIB_QT) -lDCOP $(LIB_TDE
#rc_DATA = irkickui.rc
messages:
$(XGETTEXT) *.cpp *.h -o $(podir)/kdelirc.pot
$(XGETTEXT) *.cpp *.h -o $(podir)/tdelirc.pot

@ -26,10 +26,10 @@ add_definitions(
)
##### kdessh (executable) #######################
##### tdessh (executable) #######################
tde_add_executable( kdessh AUTOMOC
SOURCES kdessh.cpp sshdlg.cpp
tde_add_executable( tdessh AUTOMOC
SOURCES tdessh.cpp sshdlg.cpp
LINK tdeui-shared tdesu-shared
DESTINATION ${BIN_INSTALL_DIR}
)

@ -1,4 +1,4 @@
kdessh - a KDE front end to ssh
tdessh - a TDE front end to ssh
Copyright (c) 1999,2000 by Geert Jansen <jansen@kde.org>

@ -0,0 +1,17 @@
## Makefile.am for tdessh
AM_CPPFLAGS = -DQT_NO_CAST_ASCII
INCLUDES= $(all_includes)
## tdessh
bin_PROGRAMS = tdessh
tdessh_SOURCES = tdessh.cpp sshdlg.cpp
tdessh_LDFLAGS = $(all_libraries) $(KDE_RPATH) $(LIB_QT) -lDCOP $(LIB_TDECORE) $(LIB_TDEUI) -ltdefx $(LIB_KIO) -ltdetexteditor
tdessh_LDADD = $(LIB_TDEUI) -ltdesu
tdessh_METASOURCES = AUTO
noinst_HEADERS = sshdlg.h
## Messages
messages:
$(XGETTEXT) $(tdessh_SOURCES) -o $(podir)/tdessh.pot

@ -13,7 +13,7 @@
#include "sshdlg.h"
KDEsshDialog::KDEsshDialog(TQCString host, TQCString user, TQCString stub,
TDEsshDialog::TDEsshDialog(TQCString host, TQCString user, TQCString stub,
TQString prompt, bool enableKeep)
: KPasswordDialog(Password, enableKeep, 0)
{
@ -36,12 +36,12 @@ KDEsshDialog::KDEsshDialog(TQCString host, TQCString user, TQCString stub,
}
KDEsshDialog::~KDEsshDialog()
TDEsshDialog::~TDEsshDialog()
{
}
bool KDEsshDialog::checkPassword(const char *password)
bool TDEsshDialog::checkPassword(const char *password)
{
SshProcess proc(m_Host, m_User);
proc.setStub(m_Stub);

@ -11,16 +11,16 @@
#include <kpassdlg.h>
class KDEsshDialog
class TDEsshDialog
: public KPasswordDialog
{
Q_OBJECT
public:
KDEsshDialog(TQCString host, TQCString user, TQCString stub,
TDEsshDialog(TQCString host, TQCString user, TQCString stub,
TQString prompt, bool enableKeep);
~KDEsshDialog();
~TDEsshDialog();
protected:
bool checkPassword(const char *password);

@ -48,7 +48,7 @@ static TDECmdLineOptions options[] =
int main(int argc, char *argv[])
{
TDEAboutData aboutData("kdessh", I18N_NOOP("TDE ssh"),
TDEAboutData aboutData("tdessh", I18N_NOOP("TDE ssh"),
VERSION, I18N_NOOP("Runs a program on a remote host"),
TDEAboutData::License_Artistic,
"Copyright (c) 2000 Geert Jansen");
@ -169,11 +169,11 @@ int main(int argc, char *argv[])
TQCString password;
if (needpw != 0)
{
KDEsshDialog *dlg = new KDEsshDialog(host, user, stub,
TDEsshDialog *dlg = new TDEsshDialog(host, user, stub,
proc.prompt(), keep && !terminal);
dlg->addLine(i18n("Command"), command);
int res = dlg->exec();
if (res == KDEsshDialog::Rejected)
if (res == TDEsshDialog::Rejected)
exit(0);
keep = dlg->keep();
password = dlg->password();
Loading…
Cancel
Save