tdevelop

History

Timothy Pearson bd3c603465 Rename additional header files to avoid conflicts with KDE4		12 years ago
..
CMakeLists.txt	[kdevelop] initial cmake support	14 years ago
Makefile.am	Additional renaming of kde to tde	13 years ago
README.dox	Additional renaming of kde to tde	13 years ago
custombuildoptionswidget.cpp	Rename a number of libraries and executables to avoid conflicts with KDE4	12 years ago
custombuildoptionswidget.h	Remove spurious TQ_OBJECT instances	13 years ago
custombuildoptionswidgetbase.ui	Rename obsolete tq methods to standard names	13 years ago
custommakeconfigwidget.cpp	Rename additional header files to avoid conflicts with KDE4	12 years ago
custommakeconfigwidget.h	Remove spurious TQ_OBJECT instances	13 years ago
custommakeconfigwidgetbase.ui	Fix QString -> TQString.	12 years ago
custommanagerwidget.cpp	Rename additional header files to avoid conflicts with KDE4	12 years ago
custommanagerwidget.h	Remove spurious TQ_OBJECT instances	13 years ago
custommanagerwidgetbase.ui	Rename old tq methods that no longer need a unique name	13 years ago
customotherconfigwidget.cpp	Rename additional header files to avoid conflicts with KDE4	12 years ago
customotherconfigwidget.h	Remove spurious TQ_OBJECT instances	13 years ago
customotherconfigwidgetbase.ui	Fix QString -> TQString.	12 years ago
customprojectpart.cpp	Rename additional header files to avoid conflicts with KDE4	12 years ago
customprojectpart.h	Rename a number of classes to enhance compatibility with KDE4	12 years ago
kdevcustomproject.desktop	Branding: KDevelop -> TDevelop, fix menu	13 years ago
kdevcustomproject.rc	Copy the KDE 3.5 branch to branches/trinity for new KDE 3.5 features.	15 years ago
selectnewfilesdialog.cpp	Rename additional header files to avoid conflicts with KDE4	12 years ago
selectnewfilesdialog.h	Remove spurious TQ_OBJECT instances	13 years ago
selectnewfilesdialogbase.ui	Rename many classes and header files to avoid conflicts with KDE4	12 years ago

README.dox

/** \class CustomProjectPart
This is the custom build tools part.
Put a more detailed description of your part in these lines. It can span
over several lines. You can even use some html commands in these lines like:
<code>This is code</code>, html links <a href="http://somelocation">link text</a>,
and images.

\authors <a href="mailto:bernd AT tdevelop.org">Bernd Gehrmann</a>

\unmaintained This part is currently un-maintained

\feature Describe the first feature
\feature Describe the second feature
...
\feature Describe the last feature

\bug bugs in <a href="http://bugs.kde.org/buglist.cgi?product=tdevelop&component=customproject&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&order=Bug+Number">customproject component at Bugzilla database</a>
\bug Describe a the 1st bug that you know of, but probably hasn't been reported yet.
..
\bug Describe a the nth bug that you know of, but probably hasn't been reported yet.

\requirement Describe a the 1st requirement of your part.
\requirement Describe a the 2nd requirement of your part.
...
\requirement Describe a the nth requirement of your part.

\todo Describe a the 1st TODO of your part.
\todo Describe a the 2nd TODO of your part.
...
\todo Describe a the nth TODO of your part.

\faq <b>First frequenly asked question about your part ?</b> Answer.
\faq <b>Second frequenly asked question about your part ?</b> Answer.
...
\faq <b>Last frequenly asked question about your part ?</b> Answer.

\note First note text.
\note Second note text.
...
\note Last note text.

\warning First warning text.
\warning Second warning text.
...
\warning Last warning text.

*/