> My suggestion is that if you are going to add scripting support you do it in
> such a way that you can bind in any scripting lang easily, if this is
> possible.
> Then you can start off with some scripting language and if other really want
> scheme, python, perl or whatever support they can add the support
> themselves.
This is a valid concern, and SWIG is a library that allows this.
However, SWIG is not designed for embedding interpreters (only embedded
programs into an interpreter), so it's not ideal for LyX.
I know of no other general way to do this.
Also, there are some problems with a totally open scripting language: We would
not be able to write any code to depend on. The use of a scripting language
would be entirely restricted to the use of extra features.
For instance, the graphical tutorial would not become an integrate part of all
LyX installations, unless we chose a given scripting language as the "official"
LyX language.
To me, the limitation of being able to use only one scripting language is not
severe. If you are unhappy about it when we have decided, too bad. Now is the
time to speak and influence the choice.
Greets,
Asger
