KBookReader – eBook reader
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.
Michele Calgaro 8084f12a8d
Removed .lsm files. lsm database is outdated and unmaintained.
2 weeks ago
..
CMakeL10n.txt Add CMakeL10n rules. 8 months ago
CMakeLists.txt conversion to the cmake buildidng system 8 months ago
Makefile.am LIB_QT -> LIB_TQT conversion to align to updated admin module 1 year ago
README Rename a number of libraries and executables to avoid conflicts with KDE4 6 years ago
bookmark.cpp TQt4 port kbookreader 8 years ago
bookmark.h Rename old tq methods that no longer need a unique name 7 years ago
bookmarksdlg.cpp Rename additional header files to avoid conflicts with KDE4 6 years ago
bookmarksdlg.h Remove spurious TQ_OBJECT instances 7 years ago
bookreader.cpp Rename additional header files to avoid conflicts with KDE4 6 years ago
bookreader.desktop Fix ServiceTypes, ExcludeServiceTypes, and DocPath desktop file entries to match XDG specifications 4 years ago
bookreader.h Rename common header files for consistency with class renaming 6 years ago
bookreader.kcfg Rename KGlobal, KProcess, and KClipboard to avoid conflicts with KDE4 6 years ago
bookreader_client.cpp Rename common header files for consistency with class renaming 6 years ago
bookreaderiface.h TQt4 port kbookreader 8 years ago
bookreaderui.rc Initial import of kbookreader 8 years ago
bookwidget.cpp Added controlled conversions to char* instead of automatic ascii conversions. 8 months ago
bookwidget.h Remove spurious TQ_OBJECT instances 7 years ago
hi16-app-bookreader.png Fix invalid headers in PNG files and optimize for size 3 years ago
hi32-app-bookreader.png Fix invalid headers in PNG files and optimize for size 3 years ago
main.cpp Rename additional header files to avoid conflicts with KDE4 6 years ago
renderer.cpp rename the following methods: 8 years ago
renderer.h Remove spurious TQ_OBJECT instances 7 years ago
settings.kcfgc Rename a number of libraries and executables to avoid conflicts with KDE4 6 years ago
settingsdlg.ui Add includes to UI files to resolve FTBFS. 8 months ago
theme.cpp Rename additional header files to avoid conflicts with KDE4 6 years ago
theme.h TQt4 port kbookreader 8 years ago

README

-----------------------------------------------
Kde application framework template 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 more details, 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_KDE3_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/