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/quickopen
Timothy Pearson f9a9d3f59e
Fix ServiceTypes, ExcludeServiceTypes, and DocPath desktop file entries to match XDG specifications
10 years ago
..
CMakeLists.txt Revert "Finish renaming tdevelop components" 11 years ago
Makefile.am Revert "Finish renaming tdevelop components" 11 years ago
README.dox Copy the KDE 3.5 branch to branches/trinity for new KDE 3.5 features. 15 years ago
kdevpart_quickopen.rc Revert "Finish renaming tdevelop components" 11 years ago
kdevquickopen.desktop Fix ServiceTypes, ExcludeServiceTypes, and DocPath desktop file entries to match XDG specifications 10 years ago
quickopen_part.cpp Revert "Finish renaming tdevelop components" 11 years ago
quickopen_part.h Revert "Finish renaming tdevelop components" 11 years ago
quickopenbase.ui Rename many classes and header files to avoid conflicts with KDE4 12 years ago
quickopenclassdialog.cpp Revert "Finish renaming tdevelop components" 11 years ago
quickopenclassdialog.h Additional k => tde renaming and fixes 11 years ago
quickopendialog.cpp Additional k => tde renaming and fixes 11 years ago
quickopendialog.h Additional k => tde renaming and fixes 11 years ago
quickopenfiledialog.cpp Revert "Finish renaming tdevelop components" 11 years ago
quickopenfiledialog.h Additional k => tde renaming and fixes 11 years ago
quickopenfunctionchooseform.cpp Rename additional header files to avoid conflicts with KDE4 12 years ago
quickopenfunctionchooseform.h Fix inadvertent "TQ" changes. 13 years ago
quickopenfunctionchooseformbase.ui Rename many classes and header files to avoid conflicts with KDE4 12 years ago
quickopenfunctiondialog.cpp Revert "Finish renaming tdevelop components" 11 years ago
quickopenfunctiondialog.h Rename KComp to avoid conflicts with KDE4 12 years ago

README.dox

/** \class QuickOpenPart
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 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.

*/