Andre Poenitz <[EMAIL PROTECTED]> writes:
| On Sun, Jul 16, 2006 at 11:40:10AM +0200, Lars Gullik Bjønnes wrote:
| > | Python would be extended by, e.g. a module 'lyx' and each lfun would be
| > | wrapped in a python function in this module. In the end you'd call
| > | something like
| > |
| > | lyx.CursorForward
| >
| > And how does this module communicate with the lyx process?
| > (Agree on how you would use the lyx module in python scripts, but that
| > is only a small part of the solution.)
| >
| > (My pow is that this is best done through a mechanism similar to the
| > lyxserver. Then we have no script/language specific mechanism inside
| > lyx itself.)
|
| This smell like starting a 'SLI project (Scripting Language
| Independency).
No, it is provicing a clear protocol on how to communicate with LyX.
You don't even have to use a scripting language...
| Is that really necessary?
IMHO this is one of the simplest solutions, and probably also a very
robust one. (Both wrt changes, but also exe stability.)
--
Lgb
