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
Michele Calgaro 430aedbbce
qt -> tqt conversion:
6 years ago
..
CMakeLists.txt Revert "Finish renaming tdevelop components" 11 years ago
Makefile.am qt -> tqt conversion: 6 years ago
README.dox Update bug reports url to bugs.trinitydesktop.org 6 years ago
classtooldlg.cpp Revert "Finish renaming tdevelop components" 11 years ago
classtooldlg.h Revert "Finish renaming tdevelop components" 11 years ago
classtoolwidget.cpp Additional k => tde renaming and fixes 11 years ago
classtoolwidget.h Additional k => tde renaming and fixes 11 years ago
classtreebase.cpp Revert "Finish renaming tdevelop components" 11 years ago
classtreebase.h Additional k => tde renaming and fixes 11 years ago
classviewpart.cpp Revert "Finish renaming tdevelop components" 11 years ago
classviewpart.h Revert "Finish renaming tdevelop components" 11 years ago
classviewwidget.cpp Revert "Finish renaming tdevelop components" 11 years ago
classviewwidget.h Revert "Finish renaming tdevelop components" 11 years ago
digraphview.cpp Additional k => tde renaming and fixes 11 years ago
digraphview.h Additional k => tde renaming and fixes 11 years ago
hierarchydlg.cpp Revert "Finish renaming tdevelop components" 11 years ago
hierarchydlg.h Revert "Finish renaming tdevelop components" 11 years ago
kdevclassview.desktop Fix ServiceTypes, ExcludeServiceTypes, and DocPath desktop file entries to match XDG specifications 10 years ago
kdevclassview.rc Revert "Finish renaming tdevelop components" 11 years ago
navigator.cpp Revert "Finish renaming tdevelop components" 11 years ago
navigator.h Rename a number of classes to enhance compatibility with KDE4 12 years ago
viewcombos.cpp Rename additional header files to avoid conflicts with KDE4 12 years ago
viewcombos.h Rename additional header files to avoid conflicts with KDE4 12 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.trinitydesktop.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.

*/