It is exposed in KParts::NavigationExtension, but effectively only used in Konqueror.
What it does is providing some generic-ish mechanism for Konqueror and the part to communicate via method calls. Can we solve that differently?
It is exposed in KParts::NavigationExtension, but effectively only used in Konqueror.
What it does is providing some generic-ish mechanism for Konqueror and the part to communicate via method calls. Can we solve that differently?
Status | Assigned | Task | ||
---|---|---|---|---|
Open | None | T12223 Meta task: KParts | ||
Open | None | T16782 Move KParts::BrowserInterface to Konqueror |
An option could be to make a new extension class similar to BrowserExtension/NavigationExtension that only has
void setBrowserInterface(BrowserInterface *impl); BrowserInterface *browserInterface() const;
then move BrowserInterface to libkonq.
A bit boilerplate-y but minimal architectural changes in Konqueror. Or can we do something simpler?