Question #246992 on qpdfview changed:
https://answers.launchpad.net/qpdfview/+question/246992
Status: Open => Answered
Adam Reichold proposed the following answer:
Hello bendirko,
thanks for sharing your idea! Towards implementing a split view, the main
problem I see is making it so that the idea of a current tab stays applicable
to the main window, i.e. the split view should implement more or less the same
interface as the document view does, so that all the assumptions currently made
by the main window still hold.
So it might be more elegant to look towards extending the tab widget, so that
it can not just handle tabs in a stacked manner but would also be able to merge
them into split views (of course, using an appropriate helper widget). In this
way, one could keep the document views in a flat list with a current index
towards the main window, hence side-stepping the problem of deepening the class
hierarchy. The resulting widget would probably be of more general use as well
(but also more difficult to implement).
What IMHO is a bit smelly here, is that this would really push qpdfview towards
window-manager-like behaviour, but of course tabs are firmly within that
category already. So to decide whether the use case merits the additional
complexity, one should probably look at a proof-of-concept implementation.
Best regards, Adam.
--
You received this question notification because you are a member of
qpdfview, which is an answer contact for qpdfview.
--
Mailing list: https://launchpad.net/~qpdfview
Post to : [email protected]
Unsubscribe : https://launchpad.net/~qpdfview
More help : https://help.launchpad.net/ListHelp
