You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
tdevelop/languages/cpp/app_templates/kxt
Slávek Banko e197223420
Additional k => tde renaming and fixes
11 years ago
..
.kdev_ignore Copy the KDE 3.5 branch to branches/trinity for new KDE 3.5 features. 15 years ago
CMakeLists.txt Additional renaming of kde to tde 13 years ago
Makefile.am Additional renaming of kde to tde 13 years ago
README Rename a number of libraries and executables to avoid conflicts with KDE4 12 years ago
app.cpp Rename additional header files to avoid conflicts with KDE4 12 years ago
app.desktop Branding cleanup: *.desktop files 13 years ago
app.h Rename common header files for consistency with class renaming 12 years ago
app.kcfg Copy the KDE 3.5 branch to branches/trinity for new KDE 3.5 features. 15 years ago
app.tdevelop Automatically update admin submodule and copy sustem libtool files before first build 12 years ago
appui.rc Copy the KDE 3.5 branch to branches/trinity for new KDE 3.5 features. 15 years ago
appview.cpp Rename additional header files to avoid conflicts with KDE4 12 years ago
appview.h Remove spurious TQ_OBJECT instances 13 years ago
appview_base.ui Remove the tq in front of these incorrectly TQt4-converted methods/data members: 14 years ago
kxt.kdevtemplate Rename KCModule, KConfig, KIO, KServer, and KSocket to avoid conflicts with KDE4 12 years ago
kxt.png Copy the KDE 3.5 branch to branches/trinity for new KDE 3.5 features. 15 years ago
main.cpp Rename additional header files to avoid conflicts with KDE4 12 years ago
prefs-base.ui Rename old tq methods that no longer need a unique name 13 years ago
prefs.cpp Copy the KDE 3.5 branch to branches/trinity for new KDE 3.5 features. 15 years ago
prefs.h Copy the KDE 3.5 branch to branches/trinity for new KDE 3.5 features. 15 years ago
preview.png Copy the KDE 3.5 branch to branches/trinity for new KDE 3.5 features. 15 years ago
settings.kcfgc Rename a number of libraries and executables to avoid conflicts with KDE4 12 years ago
src-Makefile.am Additional k => tde renaming and fixes 11 years ago
src-configure.in.in Automatically update admin submodule and copy sustem libtool files before first build 12 years ago
subdirs Copy the KDE 3.5 branch to branches/trinity for new KDE 3.5 features. 15 years ago

README

-----------------------------------------------
Kde templates quickstart
Author: Thomas Nagy
Date: 2004-03-22
-----------------------------------------------

This README file explains you basic things for starting with
this application template.


** Building and installing **

* Build the configure script by "make -f Makefile.cvs"

* To clean, use "make clean", and to clean everything 
(remove the makefiles, etc), use "make distclean"

* To distribute your program, try "make dist".
This will make a compact tarball archive of your release with the
necessary scripts inside.

* Modifying the auto-tools scripts
for automake scripts there is an excellent tutorial there :
http://developer.kde.org/documentation/other/makefile_am_howto.html

* Simplify your life : install the project in your home directory for
testing purposes.
./configure --prefix=/home/user/dummyfolder/
In the end when you finished the development you can
rm -rf /home/user/dummyfolder/
without fear.


** Technologies **

* Build the menus of your application easily
kde applications now use an xml file (*ui.rc file) to build the menus.
This allow a great customization of the application. However, when
programming the menu is shown only after a "make install"

For more details, consult :
http://devel-home.kde.org/~larrosa/tutorial/p9.html
http://developer.kde.org/documentation/tutorials/xmlui/preface.html

* Use TDEConfig XT to create your configuration dialogs and make 
them more maintainable.

For that, you will need to write two simple configuration files 
in the src directory : <myproject>.kcfg and a <settings>.kcfgc
The configure.in.in will need to be modified : change the line #MIN_CONFIG(3.0.0) 
into #MIN_CONFIG(3.2.0)

Take an example on the many apps found in the tdegames source package and consult :
http://developer.kde.org/documentation/tutorials/tdeconfigxt/tdeconfigxt.html

* With KParts, you can embed other kde components in your program, or make your program
embeddable in other apps. For example, the kmplayer kpart can be called to play videos
in your app.

For more details, consult :
http://www-106.ibm.com/developerworks/library/l-tdeparts/
http://developer.kde.org/documentation/tutorials/dot/writing-plugins.html
http://developer.kde.org/documentation/tutorials/developing-a-plugin-structure/index.html

* With dcop, you can control your app from other applications
Make sure to include K_DCOP and a kdcop: section in your .h file
http://developer.kde.org/documentation/tutorials/dot/dcopiface/dcop-interface.html


** Documentation **

* For the translations :
1. Download a patched gettext which can be found at:
 http://public.kde.planetmirror.com/pub/kde/devel/gettext-kde/
2. Install that gettext in ~/bin/
3. cd ~/yourproject, export PATH=~/bin:$PATH, export
TDEDIR=/where_your_TDE3_is
4. make -f admin/Makefile.common package-messages
5. make package-messages
6. Translate the po files (not the pot!!) with kbabel or xemacs

* Do not forget to write the documentation for your kde app 
edit the documentation template index.docbook in doc/