Warning, /frameworks/ktexteditor/docs/apidocs-groups.dox is written in an unsupported language. File is not indexed.

 /** \defgroup kte_group_doc_extensions Document Extension Interfaces
 A KTextEditor implementation may implement a Document extension interface, but
 it does not \e need to. So as a KTextEditor user you have to cast the Document
 to the desired interface and then check, whether the cast returns NULL or the
 valid interface.
 
 Use qobject_cast to cast a Document \e doc into the
 \e DesiredExtensionInterface, example:
 \code
   // doc is of type KTextEditor::Document*
   auto iface = qobject_cast<KTextEditor::DesiredExtensionInterface*>(doc);
 
   if (iface) {
       // the implementation supports the interface
       // do stuff
   } else {
       // the implementation does not support the interface
   }
 \endcode
 
 \see KTextEditor::Document
 
 The following classes are a list of all available Document extension interfaces.
 <!-- The classes are defined by the \ingroup doxygen command -->
 */
 
 
 
 
 
 /** \defgroup kte_group_moving_classes MovingCursors and MovingRanges
 \ingroup kte_group_doc_extensions
 
 If the KTextEditor implementation supports the KTextEditor::MovingInterface,
 there are several \e moving classes available.
 
 Instances of the \e moving classes are bound to a specific Document, and
 maintain their position in that document regardless of changes to the text.
 Changes to KTextEditor::MovingRange%s can be caught by using the class
 KTextEditor::MovingRangeFeedback.
 
 The following is a list of all classes that are available when the document
 supports the KTextEditor::MovingInterface:
 
 <!-- The classes are defined by the \ingroup doxygen command -->
 */
 
 
 
 
 
 /** \defgroup kte_group_view_extensions View Extension Interfaces
 A KTextEditor implementation may implement a View extension interface, but
 it does not \e need to. So as a KTextEditor user you have to cast the View
 to the desired interface and then check, whether the cast returns NULL or the
 valid interface.
 
 Use qobject_cast to cast a View \e view into the
 \e DesiredExtensionInterface, example:
 \code
   // view is of type KTextEditor::View*
   auto iface = qobject_cast<KTextEditor::DesiredExtensionInterface*>(view);
 
   if (iface) {
       // the implementation supports the interface
       // do stuff
   } else {
       // the implementation does not support the interface
   }
 \endcode
 
 \see KTextEditor::View
 
 The following classes are a list of all available View extension interfaces.
 <!-- The classes are defined by the \ingroup doxygen command -->
 */
 
 
 
 
 
 /** \defgroup kte_group_editor_extensions Editor Extension Interfaces
 A KTextEditor implementation may implement an Editor extension interface, but
 it does not \e need to. So as a KTextEditor user you have to cast the Editor
 to the desired interface and then check, whether the cast returns NULL or the
 valid interface.
 
 Use qobject_cast to cast a Editor \e editor into the
 \e DesiredExtensionInterface, example:
 \code
   // editor is of type KTextEditor::Editor*
   auto iface = qobject_cast<KTextEditor::DesiredExtensionInterface*>(view);
 
   if (iface) {
       // the implementation supports the interface
       // do stuff
   } else {
       // the implementation does not support the interface
   }
 \endcode
 
 \see KTextEditor::Editor
 
 The following classes are a list of all available Editor extension interfaces.
 <!-- The classes are defined by the \ingroup doxygen command -->
 */
 
 
 
 
 
 /** \defgroup kte_group_plugin_extensions Plugin Extension Interfaces
 A KTextEditor Plugin can use extension interfaces, but it does not \e need
 to. So as a KTextEditor implementator you have to cast the Plugin to the desired
 interface and then check, whether the cast returns NULL or the valid interface.
 
 Use qobject_cast to cast a Plugin \e plugin into the
 \e DesiredExtensionInterface, example:
 \code
   // plugin is of type KTextEditor::Plugin*
   auto iface = qobject_cast<KTextEditor::DesiredExtensionInterface*>(plugin);
 
   if (iface) {
       // the implementation supports the interface
       // do stuff
   } else {
       // the implementation does not support the interface
   }
 \endcode
 
 \see KTextEditor::Plugin
 */
 
 
 
 
 
 /** \defgroup kte_group_command_extensions Command Extension Interfaces
 A KTextEditor command-line Command can use extension interfaces, but it does not
 \e need to. So as a KTextEditor implementator you have to cast the Command to
 the desired interface and then check, whether the cast returns NULL or the valid
 interface.
 
 Use qobject_cast to cast a Command \e cmd into the
 \e DesiredExtensionInterface, example:
 \code
   // cmd is of type KTextEditor::Command*
   auto iface = qobject_cast<KTextEditor::DesiredExtensionInterface*>(cmd);
 
   if (iface) {
       // the implementation supports the interface
       // do stuff
   } else {
       // the implementation does not support the interface
   }
 \endcode
 
 \see KTextEditor::Command
 */
 
 
 
 /** \defgroup kte_group_ccmodel_extensions CodeCompletionModel Extension Interfaces
 A CodeCompletionModel implementation may implement a CodeCompletionModel
 extension interface, but it does not \e need to.
 
 \see KTextEditor::CodeCompletionModel
 */