<br><div class="gmail_quote">On Mon, Dec 13, 2010 at 16:53, 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;">
2010/12/13 Pierre Rossi <span dir="ltr"><<a href="mailto:pierre.rossi@gmail.com" target="_blank">pierre.rossi@gmail.com</a>></span><div class="im"><br><div class="gmail_quote"><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
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><div class="gmail_quote"><div>
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>
</div></div></blockquote></div><br></div>I understand what he wants to do, but I don't get why is this better.<br>I'm not against it, just curious about the benefits. If we discuss the pros and cons I'll be glad to help in the implementation :)<br>
</blockquote></div><br>Mhh, I feel we have a bit of a misunderstanding here. I don't see how you can have a *single* graphics view in all the different pages of a QTabWidget (which is a combination of a tabbar and a stackedwidget), and I believe that would be the plan, that's where we don't have a convenient widget taking care of this for us (like QTabWidget did), and we need to design one.<br>
<br>Cheers,<br>--<br>Pierre<br>