On Thu, Nov 02, 2006 at 01:34:20PM +0100, Peter Kümmel wrote:
Thanks Abdel, this is very good. We should add it some where in the wiki.
And to the code somewhere. Perhaps BufferView.C with pointers from
buffer and LyXView.
Andre'
On Thu, Nov 02, 2006 at 01:34:20PM +0100, Peter Kümmel wrote:
> Thanks Abdel, this is very good. We should add it some where in the wiki.
And to the code somewhere. Perhaps BufferView.C with pointers from
buffer and LyXView.
Andre'
Bo Peng wrote:
What is TabWidget? I will be satisfied with a split (vertical or
horizontal) window option, even if there are at most two windows, and
the split has to be half half.
I agree. A split window would be fine.
Michael
Bo Peng wrote:
What is TabWidget? I will be satisfied with a split (vertical or
horizontal) window option, even if there are at most two windows, and
the split has to be half half.
I agree. A split window would be fine.
Michael
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
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
Abdelrazak Younes wrote:
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).
But we could also explain it to the user how it works:
Beware there
Peter Kümmel wrote:
A other solution is to somehow handle within the views which part
of the buffer is viewed.
This is what we have already: Each LyXView (WorkArea really) has its own
unique BufferView which is a view of one part of the document. Except
for some cursor bug (the famous dEPM
Abdelrazak Younes wrote:
Peter Kümmel wrote:
A other solution is to somehow handle within the views which part
of the buffer is viewed.
This is what we have already: Each LyXView (WorkArea really) has its own
unique BufferView which is a view of one part of the document. Except
for some
Abdelrazak Younes [EMAIL PROTECTED] writes:
| Peter Kümmel wrote:
|
| A other solution is to somehow handle within the views which part
| of the buffer is viewed.
|
| This is what we have already: Each LyXView (WorkArea really) has its
| own unique BufferView which is a view of one part of
Peter Kümmel wrote:
Abdelrazak Younes wrote:
Peter Kümmel wrote:
A other solution is to somehow handle within the views which part
of the buffer is viewed.
This is what we have already: Each LyXView (WorkArea really) has its own
unique BufferView which is a view of one part of the document.
Lars Gullik Bjønnes wrote:
Abdelrazak Younes [EMAIL PROTECTED] writes:
| Peter Kümmel wrote:
|
| A other solution is to somehow handle within the views which part
| of the buffer is viewed.
|
| This is what we have already: Each LyXView (WorkArea really) has its
| own unique BufferView
Abdelrazak Younes [EMAIL PROTECTED] writes:
| Lars Gullik Bjønnes wrote:
| Abdelrazak Younes [EMAIL PROTECTED] writes:
| | Peter Kümmel wrote:
| | | A other solution is to somehow handle within the views which
| part
| | of the buffer is viewed.
| | | This is what we have already: Each
Abdelrazak Younes wrote:
Peter Kümmel wrote:
Abdelrazak Younes wrote:
Peter Kümmel wrote:
A other solution is to somehow handle within the views which part
of the buffer is viewed.
This is what we have already: Each LyXView (WorkArea really) has its own
unique BufferView which is a view of
Abdelrazak Younes wrote:
Peter Kümmel wrote:
Abdelrazak Younes wrote:
Peter Kümmel wrote:
A other solution is to somehow handle within the views which part
of the buffer is viewed.
This is what we have already: Each LyXView (WorkArea really) has its own
unique BufferView which is a view of
Lars Gullik Bjønnes wrote:
Abdelrazak Younes [EMAIL PROTECTED] writes:
| Lars Gullik Bjønnes wrote:
| Abdelrazak Younes [EMAIL PROTECTED] writes:
| | Peter Kümmel wrote:
| | | A other solution is to somehow handle within the views which
| part
| | of the buffer is viewed.
| | | This is
Georg is right, the LyX core is not ready for Multiple-view. There's too
much that needs to be re-designed. So either someone steps up and
cleanup that mess by putting the rows calculation outside of the Buffer
or we disable the multi-windows feature.
I would be really disappointed to see
Bo Peng wrote:
Georg is right, the LyX core is not ready for Multiple-view. There's too
much that needs to be re-designed. So either someone steps up and
cleanup that mess by putting the rows calculation outside of the Buffer
or we disable the multi-windows feature.
I would be really
1) make sure that the two windows size (the BufferView) are exactly the
same size.
2) Instead of multi-window we could implement the multi-workarea within
one window using the TabWidget solution I have outlined earlier. Then,
we will be sure that two BufferView of the same Buffer would have the
Bo Peng wrote:
1) make sure that the two windows size (the BufferView) are exactly the
same size.
2) Instead of multi-window we could implement the multi-workarea within
one window using the TabWidget solution I have outlined earlier. Then,
we will be sure that two BufferView of the same Buffer
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
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
Abdelrazak Younes wrote:
> 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).
But we could also explain it to the user how it works:
"Beware
Peter Kümmel wrote:
A other solution is to somehow handle within the views which part
of the buffer is viewed.
This is what we have already: Each LyXView (WorkArea really) has its own
unique BufferView which is a view of one part of the document. Except
for some cursor bug (the famous dEPM
Abdelrazak Younes wrote:
> Peter Kümmel wrote:
>
>>
>> A other solution is to somehow handle within the views which part
>> of the buffer is viewed.
>
> This is what we have already: Each LyXView (WorkArea really) has its own
> unique BufferView which is a view of one part of the document.
Abdelrazak Younes <[EMAIL PROTECTED]> writes:
| Peter Kümmel wrote:
|
| > A other solution is to somehow handle within the views which part
| > of the buffer is viewed.
|
| This is what we have already: Each LyXView (WorkArea really) has its
| own unique BufferView which is a view of one part
Peter Kümmel wrote:
Abdelrazak Younes wrote:
Peter Kümmel wrote:
A other solution is to somehow handle within the views which part
of the buffer is viewed.
This is what we have already: Each LyXView (WorkArea really) has its own
unique BufferView which is a view of one part of the document.
Lars Gullik Bjønnes wrote:
Abdelrazak Younes <[EMAIL PROTECTED]> writes:
| Peter Kümmel wrote:
|
| > A other solution is to somehow handle within the views which part
| > of the buffer is viewed.
|
| This is what we have already: Each LyXView (WorkArea really) has its
| own unique
Abdelrazak Younes <[EMAIL PROTECTED]> writes:
| Lars Gullik Bjønnes wrote:
| > Abdelrazak Younes <[EMAIL PROTECTED]> writes:
| > | Peter Kümmel wrote:
| > | | > A other solution is to somehow handle within the views which
| > part
| > | > of the buffer is viewed.
| > | | This is what we have
Abdelrazak Younes wrote:
> Peter Kümmel wrote:
>> Abdelrazak Younes wrote:
>>> Peter Kümmel wrote:
>>>
A other solution is to somehow handle within the views which part
of the buffer is viewed.
>>> This is what we have already: Each LyXView (WorkArea really) has its own
>>> unique
Abdelrazak Younes wrote:
> Peter Kümmel wrote:
>> Abdelrazak Younes wrote:
>>> Peter Kümmel wrote:
>>>
A other solution is to somehow handle within the views which part
of the buffer is viewed.
>>> This is what we have already: Each LyXView (WorkArea really) has its own
>>> unique
Lars Gullik Bjønnes wrote:
Abdelrazak Younes <[EMAIL PROTECTED]> writes:
| Lars Gullik Bjønnes wrote:
| > Abdelrazak Younes <[EMAIL PROTECTED]> writes:
| > | Peter Kümmel wrote:
| > | | > A other solution is to somehow handle within the views which
| > part
| > | > of the buffer is viewed.
| >
Georg is right, the LyX core is not ready for Multiple-view. There's too
much that needs to be re-designed. So either someone steps up and
cleanup that mess by putting the rows calculation outside of the Buffer
or we disable the multi-windows feature.
I would be really disappointed to see
Bo Peng wrote:
Georg is right, the LyX core is not ready for Multiple-view. There's too
much that needs to be re-designed. So either someone steps up and
cleanup that mess by putting the rows calculation outside of the Buffer
or we disable the multi-windows feature.
I would be really
1) make sure that the two windows size (the BufferView) are exactly the
same size.
2) Instead of multi-window we could implement the multi-workarea within
one window using the TabWidget solution I have outlined earlier. Then,
we will be sure that two BufferView of the same Buffer would have the
Bo Peng wrote:
1) make sure that the two windows size (the BufferView) are exactly the
same size.
2) Instead of multi-window we could implement the multi-workarea within
one window using the TabWidget solution I have outlined earlier. Then,
we will be sure that two BufferView of the same Buffer
36 matches
Mail list logo