On Mon, Oct 06, 2008 at 03:29:05PM +0200, Vincent van Ravesteijn - TNW wrote:
>  
> >Abdelrazak Younes <[EMAIL PROTECTED]> writes:
> >> I did not checked, hence the conditional :-)
> >>
> >> Why not create a Cursor::replaceSelection() instead?
> >
> >I really think that changing replaceSelection(cur) to
> >cur.replaceSelection() (one more character, BTW) is not a 
> >useful task.
> 
> >Cursor is already much too fat. 
> 
> Indeed, I'm really eager to clean the Cursor, DocIterator and
> CursorSlice classes as most methods don't have any functionality besides
> relaying. There must be some really fancy design model. 

'Design' in this case is spelled 'Fighting History'.

There was a time when the cursor was slice-by-slice part of the 
corresponding LyXText. Big fun, especially within math where there
is no LyXText and never has been.

It might be hard to imagine, but things can be way worse than what we
have now. There was, e.g., no way to iterate though a document.

Having said that, it was clear from the beginning of the standalone
cursor is too fat. There was a certain hope that parts get back into the
insets, which, in a few cases even came true.

I am by now also questioning some of the principles that guided that
part of the making of the standalone cursor that actually saw something
like a 'design' phase. I was a big(ger) fan of value-semantics then, so
the 'parentless' inset was sort of natural, but leaving unresolved ('the
caption problem') or computationaly expensive (label updating) problems
behind.

Andre'

Reply via email to