<br><br><div class="gmail_quote">On Mon, Dec 13, 2010 at 15:55, Jon Ander Peņalba <span dir="ltr"><<a href="mailto:jonan.debian@gmail.com">jonan.debian@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
<div class="gmail_quote">2010/12/13 Benjamin Poulain <span dir="ltr"><<a href="mailto:benjamin.poulain@nokia.com" target="_blank">benjamin.poulain@nokia.com</a>></span><div class="im"><br><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
>> -refactor the MainView to completely decouple the tab bar. Ideally, I<br><div>
>> would like an independant TabBar and MainView. The main problem being<br>
>> implementing the corner widget (more advanced, ask for more info if you<br>
>> want to do that).<br>
> Now I'd like to have the "more info" :-)<br>
<br>
</div>In the future, I want to get rid of the tab widget. Instead, it would be<br>
nice to have a single QGraphicsView containing all the pages.<br>
<br>
One of the things in the way of using graphics view is the TabWidget.<br>
Ideally, MainView would be composed of a independant tab bar, and a<br>
widget with the webviews.<br>
<br>
One of the pesky details of that decoupling is the corner widget. The<br>
widget is unfortunately a concept of QTabWidget, not QTabBar. A new tab<br>
bar widget could handle the tab bar and the corner widget.</blockquote></div></div><br>Hi Benjamin,<br><br>I've recently had to look at that code and I also think that it should be improved not only because it would be easier to maintain, but because it would make a few features I want to implement (and probably lots more that will be implemented in the future) easier and less hackish.<br>
I was thinking in ways to improve it and I had the intention to do it myself soon, but I never thought of removing the tab widget. Why would we want to do that? AFAIK the tab widget is perfect to handle the tabs. We currently have some limitations but I think it's our implementation's fault rather than the tab widget's.<br>
<br>_______________________________________________<br>
rekonq mailing list<br>
<a href="mailto:rekonq@kde.org">rekonq@kde.org</a><br>
<a href="https://mail.kde.org/mailman/listinfo/rekonq" target="_blank">https://mail.kde.org/mailman/listinfo/rekonq</a><br>
<br></blockquote><div><br>Hi Jon,<br><br>I'll let Benjamin expand on this but his first email explains why the tabwidget is in the way: "have a single QGraphicsView containing all the pages" (via QGraphicsWebView).<br>
In this case, you only want a tab bar giving you an index and everything else would take place in the view. Still a bit curious to hear about the full vision, so Benjamin, feel free to give more details on this.<br><br>Cheers,<br>
--<br>Pierre<br> </div></div><br>