Frameworks/Epics/KTextEditor

From KDE Community Wiki
Revision as of 19:33, 12 November 2013 by Dhaumann (talk | contribs) (Created page with "The KTextEditor interfaces together with its implementation Kate Part build a framework. This page describes the todo-list for the migration to frameworks 5. ==KTextEditor Ta...")
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)

The KTextEditor interfaces together with its implementation Kate Part build a framework. This page describes the todo-list for the migration to frameworks 5.

KTextEditor Tasks

First, port to Qt5 and Frameworks 5 modules. Then, the cleanup starts.

Status Description Coordination
TO DO KTE::DocumentCursor to the KTextEditor interfaces. Currently in part/kte5/documentcursor.* ? <{{{3}}}>
TO DO merge KTE::CodeCompletionModel v1-4 into a single interface ? <{{{3}}}>
TO DO remove KTE::LoadSaveFilterCheckPlugin ? <{{{3}}}>
TO DO remove any occurance of SmartCursor and SmartRange ? <{{{3}}}>
TO DO merge KTE::CoordinatesToCursorInterface into KTE::View ? <{{{3}}}>
TO DO merge KTE::ParameterizedSessionConfigInterface into SessionConfigInterface ? <{{{3}}}>
TO DO merge KTE::TeplateInterface 1 + 2 ? <{{{3}}}>
TO DO properly implement KTE::Document::isValidTextPosition(), with surrogate support ? <{{{3}}}>
TO DO rename KTE::Document::character() to ::characterAt() ? <{{{3}}}>
TO DO add KTE::Document::wordAt() and ::wordRangeAt() ? <{{{3}}}>
TO DO merge Highlight Selection plugin into the built-in search in KatePart ? <{{{3}}}>
TO DO merge HTML export plugin into KatePart ? <{{{3}}}>
TO DO make KTE::Cursor non-virtual + mark as Q_MOVABLE ? <{{{3}}}>
TO DO make KTE::Range non-virtual + mark as Q_MOVABLE ? <{{{3}}}>
TO DO KTE::Range & Cursor: inline as much as possible ? <{{{3}}}>
TO DO fix API of KTE::Range: setStartPosition(), setEndPosition() ? <{{{3}}}>
TO DO remove KTE::Plugin support ? <{{{3}}}>
TO DO add KTE::Document::readWriteChanged, remove from KateDocument ? <{{{3}}}>
TO DO discuss dropping MarkInterface, see part/TODO ? <{{{3}}}>
TO DO KTE::Command, possibly merge wite KTE::RangeCommand ? ? <{{{3}}}>