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/parts/classview
Darrell Anderson d0848d4c3c
Branding: KDevelop -> TDevelop, fix menu
13 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.dox Additional renaming of kde to tde 13 years ago
classtooldlg.cpp Rename obsolete tq methods to standard names 13 years ago
classtooldlg.h Remove spurious TQ_OBJECT instances 13 years ago
classtoolwidget.cpp Additional renaming of kde to tde 13 years ago
classtoolwidget.h Remove spurious TQ_OBJECT instances 13 years ago
classtreebase.cpp Rename old tq methods that no longer need a unique name 13 years ago
classtreebase.h Remove spurious TQ_OBJECT instances 13 years ago
classviewpart.cpp Additional renaming of kde to tde 13 years ago
classviewpart.h Remove spurious TQ_OBJECT instances 13 years ago
classviewwidget.cpp Rename old tq methods that no longer need a unique name 13 years ago
classviewwidget.h Remove spurious TQ_OBJECT instances 13 years ago
digraphview.cpp Remove additional unneeded tq method conversions 13 years ago
digraphview.h Remove spurious TQ_OBJECT instances 13 years ago
hierarchydlg.cpp Rename additional global TQt functions 13 years ago
hierarchydlg.h Remove spurious TQ_OBJECT instances 13 years ago
kdevclassview.desktop Branding: KDevelop -> TDevelop, fix menu 13 years ago
kdevclassview.rc Copy the KDE 3.5 branch to branches/trinity for new KDE 3.5 features. 15 years ago
navigator.cpp Additional renaming of kde to tde 13 years ago
navigator.h Remove spurious TQ_OBJECT instances 13 years ago
viewcombos.cpp rename the following methods: 13 years ago
viewcombos.h rename the following methods: 13 years ago

README.dox

/** \class ClassViewPart
Put a brief description here, the brief description ends at the first dot.
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:$EMAIL$">$AUTHOR$</a>
\authors <a href="mailto:2nd author AT provider.com">2nd author full name</a>
...
\authors <a href="mailto:nth author AT provider.com">nth author full name</a>

\maintainer <a href="mailto:$EMAIL$">$AUTHOR$</a>
\maintainer <a href="mailto:2nd maintainer AT provider.com">2nd maintainer full name</a>
...
\maintainer <a href="mailto:nth maintainer AT provider.com">nth maintainer full name</a>

\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=classview&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&order=Bug+Number">classview 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.

*/