"Andre' Poenitz" <[EMAIL PROTECTED]> writes:
| Maybe you could provide a few more relations?
|
| BufferView : Buffer = ? : ? // I guess 1 : 1, too.
It is 1:1
| I see it as a complete different interface to a different thing.
|
| This 'new' Dispatch provides an interface to a single buffer. Currently
| this means 'Load it, save it'. It should IMO more general. The buffer
| should keep a special position ('cursor'), move it around and allow to
| insert or delete at this position. Currently this is done in BufferView,
| but I don't see a reason to have such 'low level functionality' in an
| object, that has 'FL_OBJECT *' members (Brrrr...) .
I agree... even if I wrote those classes...
| Of course the 'old' Dispatch should remain, too, because it provides
| other functionality at another level. 'Ask me in some kind of dialog
| where a file is _and_ load it into a buffer _and_ display the result'.
| Once you you 'low level "load buffer"' this splits nicely at the
| _and_'s. The buffer never needs to know that it is used by somebody.
| *Never*. It's the 'pull and push thing' again ;-)
I'll have a look at this patch later.
| > I would prefer this feature to work with the
| > original dispatcher of LyXFunc. Maybe you could do some work
| > to loosen the immediate dependencies of LyXFunc, and then
| > get a more clean patch?
|
| I'd like to move buffer related things to the buffer and to move
| thing like Buffer::updateTitles() to a place far away. However, a
|'clean'
| patch most likely will be a monster. Since the 'command line export'
| it is a feature I had longed for since 0.8 or 0.10...) I would rather
| see it incorporated in the CVS tree as soon as possible and I don't see
| this coming if the patch is too large.
Separate features separate patches...
| I think the patch is not *much* worse than the 'rest of LyX'.
| But I'll clean it up a bit... maybe I can get rid of the GUI
| altogether...
Yes, please. I'll have a look at it after it has been cleaned up.
Lgb
