*Richard E Hawkins Esq writes:
| lars lamented,
|| *Asger Alstrup Nielsen writes: | The "only" serious problem is to
|| decide whether Python should be | mandatory or optional. (We have
|| to solve this problem for any | scripting language which can't be
|| included in the distribution.)
|
|| IMO that is bad. The scripting language should be mandatory and
|| included in the distribution.
| I can certainly see the value for a standard language for the
| distribution. But is there any reason that the support wouldn't be
| for any arbitrary language?
I imagine that several of the functions in LyXFunc really should be
written using the script language instead. So that we only have the
basic commands implemented in C++ and the compound(?) ones written in
scripts.
f.ex. the complete spellcheker support could be written in python.
Concerning the lyx-server: to use this actively as a script/program
interface it needs rewritning. Currently it uses pipes and that means
that there is only one channel into lyx. We would need to rewrite the
server too use sockets instead to get multiple simultanous and
separate scripts/programs going. (which is something I want to do anyway)
This would also be ideal for the internal scripting language:
Imageine support for external BibTeX, therasarous(?), knowledege
databases (or an editor for editing ERT). You would just have to write
a short script/function in pythos (or whatever) that starts up the
program in question, no hardcoding.
Lgb
