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.
tdesdk/kapptemplate
Slávek Banko 3dd9fca200
Fix various cmake build issues
12 years ago
..
admin Fix various cmake build issues 12 years ago
appframework Update lsm files. 13 years ago
existing Fix inadvertent tq changes. 12 years ago
kapp Fix inadvertent tq changes. 12 years ago
kpartapp Fix inadvertent tq changes. 12 years ago
kpartplugin Remove spurious TQ_OBJECT instances 13 years ago
CMakeLists.txt Fix various cmake build issues 12 years ago
ChangeLog Additional renaming of kde to tde 13 years ago
Makefile.am Fix build error in kapptemplate/Makefile.am. 13 years ago
Makefile.cvs Copy the KDE 3.5 branch to branches/trinity for new KDE 3.5 features. 15 years ago
README Branding cleanup: KDE -> TDE. 13 years ago
VERSION Copy the KDE 3.5 branch to branches/trinity for new KDE 3.5 features. 15 years ago
existing.module Copy the KDE 3.5 branch to branches/trinity for new KDE 3.5 features. 15 years ago
kapptemplate.cmake [kdesdk] added cmake support for "cervisia" and "kapptemplate" 14 years ago
kapptemplate.common rename the following methods: 13 years ago
kapptemplate.in rename the following methods: 13 years ago
kapptemplate.lsm Update lsm files. 13 years ago
kapptemplate.module Copy the KDE 3.5 branch to branches/trinity for new KDE 3.5 features. 15 years ago
kpartapp.module Copy the KDE 3.5 branch to branches/trinity for new KDE 3.5 features. 15 years ago
kpartplugin.module Copy the KDE 3.5 branch to branches/trinity for new KDE 3.5 features. 15 years ago
mkinstalldirs Copy the KDE 3.5 branch to branches/trinity for new KDE 3.5 features. 15 years ago

README

KAppTemplate v1.1
Kurt Granroth <granroth@kde.org>
----------------------------------------------------------------------

What is it?
-----------
KAppTemplate is a shell script that will create the necessary
framework to develop various TDE applications.  It takes care of the
autoconf/automake code as well as providing a skeleton and example of
what the code typically looks like.

Currently, KAppTemplate creates four different types of frameworks:

1) Full featured KDE application

   This is a "normal" KDE application with nearly every bleeding edge
   feature.

2) KPart application

   This creates a KDE application that uses KParts as both the Shell
   and the Part (KParts::MainWindow and KParts::ReadWritePart)

3) KPart plugin

   This creates a sample KPart plugin that acts on KHTMLPart

4) Existing application conversion

   This will take existing source and put it in a KDE automake/autoconf
   framework

What is a framework?
--------------------
When I say "framework", I mean all of the source files as well as the
autoconf/automake stuff.  When KAppTemplate is done, all you will need
to do to compile and install your app is:
    ./configure
    make && make install

What do I need to use this?
---------------------------
o KDE 3.x
o autoconf
o automake

How do I install it?
--------------------
If you have a standalone kapptemplate.tar.bz2, do:
  ./configure
  make && make install
If you are installing from tdesdk, then just
  make && make install
If you are installing from .deb or .rpm, then install like any other
normal package

How does <whatever> work?
-------------------------
Before you email me, look through the kapptemplate file.  It is a
shell script so it should be pretty easy to understand what is going
on.

I have a suggest, question, or comment
--------------------------------------
Well, email me, then!

Have fun!
Kurt Granroth <granroth@kde.org>