generic: remove dead and irrelevant links references

Signed-off-by: Ivailo Monev <xakepa10@gmail.com>

cmake/modules/README

@@ -1,19 +1,3 @@
 these are additional cmake modules required for compiling KDE4
 applications with cmake. Some of them are enhanced versions of the files 
-coming with cmake, some of them are NOT yet part of cmake.
+coming with cmake, some of them are NOT part of cmake.
-To use them, copy them into the cmake Module directory or
-run "cmake ."  followed by "make install"
-
-Changes to any files should follow the 
-
-cmake commit policy 
-
-    at http://techbase.kde.org/Policies/CMake_Commit_Policy
-
-and the cmake coding style 
-
-    at http://techbase.kde.org/Policies/CMake_Coding_Style
-
-
-Alex <neundorf@kde.org>
-

interfaces/ktexteditor/view.h

@@ -138,9 +138,8 @@ class Document;
  * \author Christoph Cullmann \<cullmann@kde.org\>
  */
 // KDE5: consider deriving from QFrame instead of QWidget, since e.g. the Oxygen style
-// http://lxr.kde.org/source/kde/kde-workspace/kstyles/oxygen/oxygenstyle.cpp#614
+// (kde-workspace/kstyles/oxygen/oxygenstyle.cpp) checks for a QFrame. This is needed because the
-// checks for a QFrame and then KStyle::pixelMetric returns a better margin (Frame_FrameWidth)
+// Oxygen "focus border" paints over the line numbers otherwise.
-// This is needed because the Oxygen "focus border" paints over the line numbers otherwise.
 class KTEXTEDITOR_EXPORT View :  public QWidget, public KXMLGUIClient
 {
   Q_OBJECT

kdecore/config/DESIGN

@@ -1,6 +1,3 @@
-If you add a major new feature, suggest using it in
-http://techbase.kde.org/Development/Tutorials/KConfig
-
 kconfigdata.h contains definitions of the data formats used by kconfig.
 
 Configuration entries are stored as "KEntry". They are indexed with "KEntryKey".
@@ -102,5 +99,3 @@ KConfigDialogManager: Class that links widgets in a dialog up with their
 MyConfigWidget: Dialog generated from a .ui description file. Widget names
                 in the dialog that start with "kcfg_" refer to configuration
                 options.
-
-See http://techbase.kde.org/Development/Tutorials/Using_KConfig_XT

kdecore/config/kconfig.h

@@ -60,7 +60,7 @@ class KConfigPrivate;
  * KSharedConfig provides a set of open methods as counterparts for the
  * KConfig constructors.
  *
- * \sa KSharedConfig, KConfigGroup, <a href="http://techbase.kde.org/index.php?title=Development/Tutorials/KConfig">the techbase HOWTO on KConfig</a>.
+ * \sa KSharedConfig, KConfigGroup
  */
 class KDECORE_EXPORT KConfig : public KConfigBase
 {

kdecore/kernel/kaboutdata.cpp

@@ -745,12 +745,13 @@ QList<KAboutPerson> KAboutData::translators() const
 
 QString KAboutData::aboutTranslationTeam()
 {
-    return i18nc("replace this with information about your translation team",
+    return i18nc(
-            "<p>KDE is translated into many languages thanks to the work "
+        "replace this with information about your translation team",
-            "of the translation teams all over the world.</p>"
+        "<p>KDE is translated into many languages thanks to the work "
-            "<p>For more information on KDE internationalization "
+        "of the translation teams all over the world.</p>"
-            "visit <a href=\"http://l10n.kde.org\">http://l10n.kde.org</a></p>"
+        "<p>For more information on KDE internationalization "
-            );
+        "visit <a href=\"%1\">%1</a></p>", QLatin1String(KDE_HOME_URL)
+    );
 }
 
 QString KAboutData::otherText() const

kdecore/localization/klocalizedstring.h

@@ -35,7 +35,6 @@ class KLocalizedStringPrivate;
 /**
  * I18N_NOOP marks a string to be translated without translating it.
  * Do not use this unless you know you need it.
- * http://developer.kde.org/documentation/other/developer-faq.html#q2.11.2
  *
  * Example usage where say_something() returns either "hello" or "goodbye":
  * \code
@@ -275,20 +274,11 @@ class KLocalizedStringPrivate;
  *
  * \section other_ref Further References
  *
- * <a href="http://techbase.kde.org/">KDE Techbase</a> contains a
- * <a href="http://techbase.kde.org/Development/Tutorials/Localization">
- * series of tutorials</a> on preparing the code for localization (and on
- * internationalization process in general), where the intended patterns of
- * usage of i18n API are covered in great detail.
- *
  * All i18n'd messages, whether sent to widgets expecting plain text or
- * allowing Qt rich text (HTML), support the new KDE semantic markup for
+ * allowing Katie rich text (HTML), support the new KDE semantic markup for
  * user interface text, KUIT in short. Semantic markup both increases the
  * consistency of visual presentation for the end user, and provides extra
  * information to translators, so that translations can be of higher quality.
- * KUIT is documented in an
- * <a href="http://techbase.kde.org/Development/Tutorials/Localization/i18n_Semantics">
- * Techbase article</a> as well.
  *
  * @see KLocale
  * @author Chusslove Illich \<caslav.ilic@gmx.net\>

kdecore/localization/kuitsemantics.cpp

@@ -512,8 +512,6 @@ void KuitSemanticsPrivate::setFormattingPatterns ()
                 I18N_NOOP2("@title/plain",
     // i18n: The following messages, with msgctxt "@tag/modifier",
     // are KUIT patterns for formatting the text found inside semantic tags.
-    // For review of the KUIT semantic markup, see the article on Techbase:
-    // http://techbase.kde.org/Development/Tutorials/Localization/i18n_Semantics
     // The "/modifier" tells if the pattern is used for plain text, or rich text
     // which can use HTML tags.
     // You may be in general satisfied with the patterns as they are in the

kdecore/localization/kuitsemantics_p.h

@@ -53,9 +53,6 @@ class KuitSemantics
      *
      * @param text text containing the semantic markup
      * @param ctxt context of the text
-     *
-     * @see More information on semantic markup in UI messages in the
-     * <a href="http://techbase.kde.org/Development/Tutorials/Localization/i18n_Semantics">article on Techbase</a>.
      */
     QString format (const QString &text, const QString &ctxt) const;
 

kdecore/services/kmimetypetrader.h

@@ -72,7 +72,6 @@ public:
      *
      * @return A list of services that satisfy the query, sorted by preference
      * (preferred service first)
-     * @see http://techbase.kde.org/Development/Tutorials/Services/Traders#The_KTrader_Query_Language
      */
     KService::List query( const QString& mimeType,
                           const QString& genericServiceType = QString::fromLatin1("Application"),

kdecore/services/kservice.h

@@ -44,9 +44,6 @@ class KServicePrivate;
  * The types of service a plugin provides is taken from the accompanying desktop file
  * where the 'ServiceTypes=' field is used.
  *
- * For a tutorial on how to build a plugin-loading mechanism and how to write plugins
- * in general, see http://techbase.kde.org/Development/Tutorials#Services:_Applications_and_Plugins
- *
  * @see KServiceType
  * @see KServiceGroup
  * @author Torben Weis

kdecore/services/kservicetypetrader.h

@@ -94,7 +94,6 @@ public:
      *                    get all services of the given @p servicetype
      *
      * @return A list of services that satisfy the query
-     * @see http://techbase.kde.org/Development/Tutorials/Services/Traders#The_KTrader_Query_Language
      */
     KService::List query( const QString& servicetype,
                           const QString& constraint = QString() ) const;

kdecore/sycoca/ksycocaentry.h

@@ -36,7 +36,6 @@ class KSycocaEntryPrivate;
  * the common functionality for servicetypes and services.
  *
  * @internal
- * @see http://techbase.kde.org/Development/Architecture/KDE3/System_Configuration_Cache
  */
 class KDECORE_EXPORT KSycocaEntry : public QSharedData
 {

kdeui/actions/kstandardaction.h

@@ -38,8 +38,7 @@ class KToggleFullScreenAction;
  *
  * These actions should be used instead of hardcoding menubar and
  * toolbar items.  Using these actions helps your application easily
- * conform to the KDE UI Style Guide
+ * conform to the general KDE UI style.
- * @see http://developer.kde.org/documentation/standards/kde/style/basics/index.html .
  *
  * All of the documentation for KAction holds for KStandardAction
  * also.  When in doubt on how things work, check the KAction

kdeui/itemviews/klinkitemselectionmodel.h

@@ -86,8 +86,6 @@ class KLinkItemSelectionModelPrivate;
     view2->setSelectionModel( view2SelectionModel );
   @endcode
 
-  See also <a href="http://websvn.kde.org/trunk/KDE/kdelibs/kdeui/tests/proxymodeltestapp/proxyitemselectionwidget.cpp?view=markup">kdelibs/kdeui/tests/proxymodeltestapp/proxyitemselectionwidget.cpp</a>.
-
   @since 4.5
   @author Stephen Kelly <steveire@gmail.com>
 

kdeui/kernel/kglobalsettings.h

@@ -109,9 +109,7 @@ public:
     static int dndEventDelay();
 
     /**
-     * Returns whether KDE runs in single (default) or double click
+     * Returns whether KDE runs in single (default) or double click mode.
-     * mode.
-     * see http://developer.kde.org/documentation/standards/kde/style/mouse/index.html
      * @return true if single click mode, or false if double click mode.
      **/
     static bool singleClick();
@@ -163,8 +161,6 @@ public:
 
     /**
      * This enum describes the completion mode used for by the KCompletion class.
-     * See <a href="http://developer.kde.org/documentation/standards/kde/style/keys/completion.html">
-     * the styleguide</a>.
      **/
     enum Completion {
         /**

kdeui/kernel/ktoolinvocation.h

@@ -60,10 +60,6 @@ class KUrl;
  * If you call the members with signal/slot connections across threads, you can't use the return values
  * If a function is called from the wrong thread and it has a return value -1 is returned
  * Investigate if this is really needed or if D-Bus is threadsafe anyway
- *
- * For more details see <a
- * href="http://techbase.kde.org/Development/Architecture/KDE4/Starting_Other_Programs#KToolInvocation::startServiceByDesktopPath">techbase</a>.
- *
  */
 class KDECORE_EXPORT KToolInvocation : public QObject
 {

kdeui/widgets/kcmodule.h

@@ -89,9 +89,6 @@ class KComponentData;
  * The example executes the given code in a shell and uses the stdout output for
  * the Hidden value (so it's either Hidden=true or Hidden=false).
  *
- * See http://techbase.kde.org/Development/Tutorials/KCM_HowTo
- * for more detailed documentation.
- *
  * @author Matthias Hoelzer-Kluepfel <hoelzer@kde.org>
  */
 class KDEUI_EXPORT KCModule : public QWidget

kdeui/xmlgui/kxmlguiwindow.h

@@ -48,12 +48,8 @@ class KXmlGuiWindowPrivate;
  * toolbar buttons and actions to it by hand, this class can be used to load an
  * rc file to manage the main window's actions.
  *
- * See http://techbase.kde.org/Development/Tutorials/Using_KActions#XMLGUI
- * for essential information on the XML file format and usage of this class.
- *
  * @see KMainWindow
  * @author Reginald Stadlbauer (reggie@kde.org) Stephan Kulow (coolo@kde.org), Matthias Ettrich (ettrich@kde.org), Chris Schlaeger (cs@kde.org), Sven Radej (radej@kde.org). Maintained by Sven Radej (radej@kde.org)
-
  */
 
 class KDEUI_EXPORT KXmlGuiWindow : public KMainWindow, public KXMLGUIBuilder, virtual public KXMLGUIClient

kfile/kdiroperator.h

@@ -65,9 +65,7 @@ class DeleteJob;
  * utilizing KIO::PreviewJob.
  *
  * Currently, those classes don't support Drag&Drop out of the box -- there
- * you have to use your own view-classes. You can use some DnD-aware views
+ * you have to use your own view-classes.
- * from Björn Sahlström <bjorn@kbear.org> until they will be integrated
- * into this library. See http://devel-home.kde.org/~pfeiffer/DnD-classes.tar.gz
  *
  * This widget is the one used in the KFileDialog.
  *

plasma/README

@@ -8,22 +8,3 @@ common GUI elements, data and service interaction, search system, etc.
 Domain specific sets of functionality, e.g. for network awareness or sensors,
 are not found here but as DataEngine, Service, Applet, PackageStructure, etc
 plugins.
-
-Commit Guidelines:
-* If your patch is not an obvious or trivial bug fix, have it peer reviewed
-  by another Plasma developer; http://reviewboard.kde.org is your friend :)
-
-* All code MUST follow the kdelibs coding style, as found at:
-        http://techbase.kde.org/Policies/Kdelibs_Coding_Style
-
-* All new public API MUST have apidox written before committing and must go
-  through an API review with another Plasma developer. We have to maintain
-  binary compatibility, remember!
-
-Unit tests are next to godliness. (Though as you can see, right now libplasma
-is hellbound.)
-
-Please refer to the Plasma website (http://plasma.kde.org) and Plasma wiki
-(http://techbase.kde.org/Projects/Plasma) for API documentation and design
-documents regarding this library.
-

plasma/applet.h

@@ -69,8 +69,6 @@ class Package;
  * look and feel in just one line of code for applets), loading and starting
  * of scripting support for each applet, providing access to the associated
  * plasmoid package (if any) and access to configuration data.
- *
- * See techbase.kde.org for tutorials on writing Applets using this class.
  */
 class PLASMA_EXPORT Applet : public QGraphicsWidget
 {

plasma/containment.h

@@ -64,8 +64,6 @@ class AbstractToolBox;
  * Containments are differentiated from Applets by being marked with the ServiceType
  * of Plasma/Containment. Plugins registered with both the Applet and the Containment
  * ServiceTypes can be loaded for us in either situation.
- *
- * See techbase.kde.org for a tutorial on writing Containments using this class.
  */
 class PLASMA_EXPORT Containment : public Applet
 {