[prev in list] [next in list] [prev in thread] [next in thread]
List: kwrite-devel
Subject: Re: Notes / Observations while embedding KTextEditor::Plugin(s) into a new host application
From: Thomas Friedrichsmeier <thomas.friedrichsmeier () ruhr-uni-bochum ! de>
Date: 2020-01-16 10:43:19
Message-ID: 20200116114319.2206d0f7 () edge
[Download RAW message or body]
On Thu, 16 Jan 2020 10:36:27 +0100
Thomas Friedrichsmeier <thomas.friedrichsmeier@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
[Attachment #3 (application/pgp-signature)]
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic