[EMAIL PROTECTED] wrote:
On Mon, 13 Aug 2007, Abdelrazak Younes wrote:
I think I've done that already. If nobody listen (I am not talking
about you) then I am not going to explain it again.
Let me repeat it again:
one Buffer -> one BufferView -> one WorkArea.
one LyXView will create WorkAreas on demand.
As simple as that.
The above is a compact overview, but I assume you've sent more detailed
messages to the list. How about copying stuff from those and pasting it
as introductory comments in a suitable source file? A lazier approach
would be to just insert a link to the posts, but that means it's not
possible to modify the explanations in the code later on.
An even lazier approach would be to let those interested to just look at
the code ;-). I repeat again: the changes are not that complicated. Most
of the patch is about:
- bv->buffer() which becomes bv.buffer()
- all test on nullity of bv->buffer() are obviously deleted.
I replaced the home made Tabbar with a proper QTabWidget. This means
that, for Buffer switching, I transfered the decision logic from the
kernel to the frontend. Clicking on a Tab to do a Buffer-switch won't
even trigger an LFUN_BUFFER_SWITCH. A menu triggered LFUN_BUFFER_SWITCH
will simply ask the frontend to switch to _the_ wWorkArea that is
currently displaying this asked Buffer. If the WorkArea is not there, it
will be created automatically by the frontend, transparently to the kernel.
Abdel.
