Separate concepts of the tab and its contents

Registered by Christian Dywan on 2013-08-12

We currently have a Midori.View class and in practise that's the only thing Midori.Browser accepts as a tab widget. Midori.Tab was intended as but isn't a generic parent class: it bleeds into webkit pieces that should be in Midori.View and there's no proper way to have webkit-less tabs.

Blueprint information

Status:
Not started
Approver:
André Stösel
Priority:
High
Drafter:
Christian Dywan
Direction:
Approved
Assignee:
None
Definition:
Approved
Series goal:
Accepted for trunk
Implementation:
Unknown
Milestone target:
milestone icon garage

Whiteboard

Midori.Tab should be an interface that has
a) just enough to get an icon, a title and a URI
b) can embed a WebView or any other widget
c) has a back/forward history and state that allows recovering its contents

Midori.View should be a WebKit.WebView-specific implementation of Midori.Tab

Midori.Browser should
a) take any Midori.Tab
b) stop calling arbitrary webkit code
c) re-create and drop Tab instances automatically to conserve memory better than delayed loading currently can

(?)

Work Items

This blueprint contains Public information 
Everyone can see this information.

Subscribers

No subscribers.