Abdelrazak Younes wrote: > Bo Peng wrote: >>> Yeah, it was not that hard (see below). It's just that I don't have much >>> time. >> >> This does solves my bookmark problem, but are you sure it is a good >> idea to open all buffers that was opened in the parent window? > > I know you understand the difference but for the sake of clarity let me > repeat that again: The buffers are not opened again in the second > window. They are opened once and only once.
Maybe it helps when we describe it in other words. Due to Abdel's great work we now have a Model/View design. The buffers are the models and the Windows are the views. As you know there is only one model but arbitrarily much views. The problem is now, what do we with the views, they are all identical, because currently they are a whole view of the model. Maybe it is really the best do disable the multiple-view support until we know how we will handle this. One idea is to divide the one bug buffer into several smaller ones which all are viewed by a view, which doesn't know anything about other buffers. But then a multiple view of one document becomes impossible. To have this we could use something like a buffer-proxy... A other solution is to somehow handle within the views which part of the buffer is viewed. > A window can only show one buffer at a time. The new tabbar is designed > to show a list of all available buffer (this is Peter's doing, not > mine). So this is independent from the number of opened windows. > > As it is now, the TabBar is just a shortcut for the View->Document > submenu, that's all. I've already warned you all about that multiple times. > >> My proposal was that we do not open any buffer but allow users to >> switch to them from view menu item. That was just my preference >> though. > > Read above: the Buffer is not opened again, only shown. With the new > tabbar, it is all or nothing, you don't have a choice. > > All, please listen: > > I propose to remove the multi-window feature from the menu, or even > remove the LFUN entirely. We can have it back when the new TabWidget > that will replace the tabbar is ready (most probably in 1.6). > > Abdel. > > -- Peter Kümmel
