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/languages/cpp/app_templates/kdevpart
Michele Calgaro dd8130b361
LIB_QT -> LIB_TQT conversion to align to updated admin module
6 years ago
..
.kdev_ignore Copy the KDE 3.5 branch to branches/trinity for new KDE 3.5 features. 15 years ago
CMakeLists.txt Add gnu tar detection 9 years ago
Makefile.am Revert to .kdevelop files with <kdevelop> entity name for project files. 10 years ago
README.dox Update bug reports url to bugs.trinitydesktop.org 6 years ago
app.kdevelop Revert to .kdevelop files with <kdevelop> entity name for project files. 10 years ago
globalconfig.cpp Revert "Finish renaming tdevelop components" 11 years ago
globalconfig.h Revert "Finish renaming tdevelop components" 11 years ago
globalconfigbase.ui Revert "Finish renaming tdevelop components" 11 years ago
kdevpart.desktop Fix ServiceTypes, ExcludeServiceTypes, and DocPath desktop file entries to match XDG specifications 10 years ago
kdevpart.kdevtemplate Revert to .kdevelop files with <kdevelop> entity name for project files. 10 years ago
kdevpart.png Fix invalid headers in PNG files and optimize for size 8 years ago
kdevpart_part.cpp Revert "Finish renaming tdevelop components" 11 years ago
kdevpart_part.h Revert "Finish renaming tdevelop components" 11 years ago
kdevpart_part.rc Revert "Finish renaming tdevelop components" 11 years ago
kdevpart_widget.cpp Revert "Finish renaming tdevelop components" 11 years ago
kdevpart_widget.h Revert "Finish renaming tdevelop components" 11 years ago
projectconfig.cpp Revert "Finish renaming tdevelop components" 11 years ago
projectconfig.h Revert "Finish renaming tdevelop components" 11 years ago
projectconfigbase.ui Revert "Finish renaming tdevelop components" 11 years ago
src-Makefile.am LIB_QT -> LIB_TQT conversion to align to updated admin module 6 years ago

README.dox

/** \class %{APPNAME}
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=YOUR_COMPONENT_NAME&
bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&order=Bug+Number">
YOUR_COMPONENT_NAME 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.

*/