TDE
/
tdevelop
mirror of https://mirror.git.trinitydesktop.org/gitea/TDE/tdevelop
0
0
Fork 0
Code Issues Releases Wiki Activity
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.
Branches Tags
${ item.name }
Create tag ${ searchTerm }
Create branch ${ searchTerm }
from 'master'
${ noResults }
tdevelop/languages/python
History
Michele Calgaro 37ad15ad2c
Replace Q_SIGNALS and Q_SLOTS 		3 months ago
..
app_templates Replace Q_SIGNALS and Q_SLOTS 3 months ago
doc Updated python 2 and added python 3 TDevelop documentation toc files. This relates to bug 1859. 10 years ago
file_templates Revert "Finish renaming tdevelop components" 10 years ago
CMakeLists.txt Desktop file translations: 4 years ago
Makefile.am qt -> tqt conversion: 6 years ago
README.dox Additional k => tde renaming and fixes 11 years ago
kde_pydoc.py Drop python2 support. 1 year ago
kdevpythonsupport.desktop Desktop file translations: 4 years ago
kdevpythonsupport.rc Revert "Finish renaming tdevelop components" 10 years ago
pydoc.cpp Drop python2 support. 1 year ago
pydoc.h Rename a number of libraries and executables to avoid conflicts with KDE4 11 years ago
pydoc.protocol Rename kioslaves 11 years ago
pythonconfigwidget.cpp Revert "Finish renaming tdevelop components" 10 years ago
pythonconfigwidget.h Replace Q_OBJECT with TQ_OBJECT 10 months ago
pythonconfigwidgetbase.ui Add includes to UI files to resolve FTBFS 6 years ago
pythonimplementationwidget.cpp Revert "Finish renaming tdevelop components" 10 years ago
pythonimplementationwidget.h Replace Q_OBJECT with TQ_OBJECT 10 months ago
pythonsupportpart.cpp Use new TQ_METHOD, TQ_SIGNAL, TQ_SLOT defines 4 months ago
pythonsupportpart.h Replace Q_OBJECT with TQ_OBJECT 10 months ago
tqtdesignerpythonintegration.cpp Fixed FTBFS caused by qt->tqt renaming. 6 years ago
tqtdesignerpythonintegration.h Replace Q_OBJECT with TQ_OBJECT 10 months ago

README.dox 

/** \class PythonSupportPart
This is a Python support plugin.

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 kdevelop.org">Bernd Gehrmann</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 Python support
\feature Consult \ref LangSupportStatus for a up to date features/status of this programming language support part.

\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.

*/