On Tue, Oct 24, 2006 at 02:50:08PM +0200, Jean-Marc Lasgouttes wrote: > >>>>> "Abdelrazak" == Abdelrazak Younes <[EMAIL PROTECTED]> writes: > > Abdelrazak> There are two solutions: > > Abdelrazak> 1) Make the central widget a QTabWidget in GuiView (which > Abdelrazak> is a QMainApplication). Then host a new QWorkArea for each > Abdelrazak> tab. In this context, this would mean that two WorkArea in > Abdelrazak> two tabs or in two split windows would look the same to > Abdelrazak> the parent GuiView. > > Abdelrazak> 2) Make the GuiWorkArea viewport a tab widget and handle > Abdelrazak> the buffer switch there. This would mean that there's only > Abdelrazak> one WorkArea. > > Abdelrazak> I like 1) more but 2) might be easier to do. > > I do not know how this fits in your discussion, but we could just have > a tab strip (in a backend toolbar, maybe?) and manage the switches by > hand (with LFUNs). I suspect that letting Qt handle all that will > remove some of our liberty.
I think a QTabWidget would be very unintrusive (as in 'completely unvisible to the kernel') Andre' --
