For the most part, I really have no idea what you're talking about.
And I may be bringing up issues for 1.3 rather than 1.1, but . . .
> > ?? What kind of a remark is that?
> OK, maybe I'm wrong, but it seems that LyX >= 1.1.x will use much more
> memory and process time for the same document. That's the price we'll pay
> to do some things better, since we'll gain in much other places, I'm not
> discussing that. Furthermore there's a lot of work to do yet.
Some things in 1.0 already push my 486. Generating postscript I avoid,
but the backspace issue, for example, screams out when it comes up.
> > Why do you think this is (only) gui dependant?
> GUI, lyx server and scripting. Which else? All them will use high level
> functions to have access to the kernel. My point is to make this stuff as
> independent as possible from external clients.
I have no idea how any of this works, but I'll put my two-cents in
anyway on scripting type issues, since I've done some rather exotic &
extended stuff *with* scripts & mail merges.. There shouldn't be
*anything* that can only be done from the keyboard/GUI. In some form
or another, it needs to be possible to set a "recorder" running for the
sequence of key commands. It doesn't necessarily matter that menus come
down, etc., but only that the correspondences isssue so that a
mechanical translation of the activities to a set of commands can be
made. THis is more a novice user issue than anything else--but it's
still an easier way to make some scripts than typing them out. Get the
script this way, then edit it.
The other is that it must be *possible* to do everything from a script
that can be done from the keyboard/gui. Otherwise we end up in a
situation where we're second-guessing what the user may legitimately
need, and get into a "you can do what is permitted, ratehr than what
isn't prohibited." situation (which I"ve been in, and is a pain.)
I'm not sure how clear this is, my coffee is still brewing . . .
--
