On Mon, Dec 13, 2010 at 16:53, Jon Ander Peñalba <[email protected]>wrote:
> 2010/12/13 Pierre Rossi <[email protected]> > > 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). >> 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. >> > > I understand what he wants to do, but I don't get why is this better. > 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 :) > 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. Cheers, -- Pierre
_______________________________________________ rekonq mailing list [email protected] https://mail.kde.org/mailman/listinfo/rekonq
