Current State of Kate on 5

Just a quick update on the frameworks 5 port: KTextEditor,  Kate Part and KWrite build and run. Kate is not yet ported and does not compile. These changes were already committed:

  • made KTE::Cursor and KTE::Range non-virtual for maximum speed
  • removed KTE::EditorChooser, since Kate Part is the only implementation since over 10 years. Just use KTE::Editor* editor = KTE::editor(); to get KatePart.
  • new signal KTE::Document::readWriteChanged()
  • removed KTE::LoadSaveFilterCheckPlugin, was unused since years
  • removed all KTE::Smart* classes in favor of KTE::Moving* classes
  • merged KTE::CoordinatesToCursorInterface into KTE::View
  • new: KTE::Range KTE::Document::wordRangeAt(KTE::Cursor)
  • new: QString KTE::Document::wordAt(KTE::Cursor)
  • new: KTE::DocumentCursor
  • ported lots of KSharedPtr to QSharedData
  • updated Mainpage.dox to reflect porting notes
  • some small interface cleanups and additions

Please feel free to join the porting fun. Just follow the Frameworks compile guide and checkout the git branch “frameworks” in the Kate git module.

4 thoughts on “Current State of Kate on 5”

  1. >> removed KTE::EditorChooser, since Kate Part is the only implementation since over 10 years. Just use KTE::Editor* editor = KTE::editor(); to get KatePart. < standard componentes -> embedded text-editor option will be abondend?
    Honestly I don’t know of any other KParts that make use of it but it would be great to have an Emacs editor part. So I think it’s a kind of sad to remove this functionality though nobody uses it at the moment, albeit I’m not aware of possible positive impacts…
    If this commit is about entirely different stuff, I beg your pardon!
    Thanks for the work on KDE!

  2. Somehow part of my comment has been gone, try again with different quoting.

    [quote] removed KTE::EditorChooser, since Kate Part is the only implementation since over 10 years. Just use KTE::Editor* editor = KTE::editor(); to get KatePart. [/quote]
    Does that mean the systemsettings -> standard componentes -> embedded text-editor option will be abondend?

    1. Correct, the control module does not exist anymore. If someone decides to start a new KTextEditor implementation, it can still be added again. That is no problem at all. But it’s very unlikely, given the last 10 years…

      1. Beside the “vi mode” shows that an additional editing mode can be implemented in KatePart just fine, even a “strange” one like vi :) If there is interest to have some Emacs support in KatePart, patches are welcome, but the idea to have xx different editor parts around for the KTextEditor interfaces never has taken off.

Leave a Reply