*Alejandro Aguilar Sierra writes:
| On 15 Dec 1998, Lars Gullik Bj�nnes wrote:
|| I am currently trying to figure out how the scripts will connect to
|| buffers (which buffer to perform the operation on), and this is a
|| problem regardless of how we interface to the LyXFuncs. Actually I
|| don't think this will be a huge problem since most (all?) siod
|| functions will be initiated from inside lyx, so we can just set a
|| state variable. We will also have to creat some new siod types,
|| buffer, bufferview...something like that.
| I really don't think we have to hack lyxfunc just to integrate
| siod. Which things can't be done just by calling lyxfunc->dispatch?
| I know some of them.
the point is "how to know which lyxfunc to do the dispatch on".
if we have
(lyx-dispatch "char-forward") (or (char-forward) )
in the script, where should this be done? What lyxfunc should
lyx-dispatch call? In this case using the BufferView->owner->lyxfunc
that has focus would probably be the best.
I think we have to decide that commands in the embedded language can
only be instiated interactively by the user. Then we will always know
which lyxfunc to use.
Another point is that LISP is type safe...
| We have currently a nice client/server mechanism. Should we drop
| it all and start again?
The current client/server mechanism is not nice at all. It has no idea
on which buffer its commands work, and it is impossible to have
several clients at the same time. (there is only the stupid connection
"string")
btw. I fail to see what relevance you comment about "start again" has
to the embedded scripting language.
To me the server and the embedded language is completely separate.
Do you mean that we should let the embedded languge work through the
lyxsever?
Lgb
