Notes / Observations while embedding KTextEditor::Plugin(s) into a new host application

[Thomas Friedrichsmeier]

On Thu, 16 Jan 2020 10:36:27 +0100
Thomas Friedrichsmeier <thomas.friedrichsmeier at ruhr-uni-bochum.de>
wrote:
> However, there are still some advantages over the current approach:
> 1) *Existing* functions can be offered as virtuals in the
> "host-facing" MainWindowImpl in KF6, allowing for:
> 1a) having default implementations in the base-class, where possible.
> Perhaps e.g. for (read/write)SessionConfig, or findUrl().

D'uh, ignore the part about (read/write)SessionConfig, please, I don't
know what I was thinking. But there's still several calls, where I could
easily imagine a default implementation (reducing the bureaucracy
involved in writing a host application):

  MainWindow::closeView()
  MainWindow::window()
  MainWindow::pluginView()
  MainWindow::showPluginConfigPage()
  Application::plugin()
  Application::findUrl()
  Application::closeDocument()
  Application::closeDocuments()
  Application::documents()

It's a good thing that all of these can be customized, but they could
have defaults.

Regards
Thomas
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 833 bytes
Desc: OpenPGP digital signature
URL: <http://mail.kde.org/pipermail/kwrite-devel/attachments/20200116/c01d2b5a/attachment.sig>