* George De Bruin <[EMAIL PROTECTED]> [010604 20:02]:
> On Tuesday 29 May 2001 23:46, Allan Rae wrote:
>
> > FWIW, a number of Python folk are interested in LyX -- both for personal
> > use (with python.cls etc.) and as a possible unofficial documenting tool.
> > Their official documenting tools are a couple of scripts and any text
> > editor and they aren't about to change that in a hurry. I know a couple
> > of people in particular who are Python gurus (one's a Python Team member)
> > who would love to get their hands dirty in LyX (with Python of course).
>
> This would appear to support the idea I was putting forth: for each language,
> we should have someone (or multiple people) interested in doing the support
> of that langauge within LyX. That way we (a) gain their expertise, and (b)
> we don't dilute the development efforts of the LyX Team.
Nobody said anything about having only a single language, we just want
to have one "official" language. This will be the language that we, the
developers, will be commited to update.
I will be doing Python support when there will be a scripting language
support, simply because I like Python. The official language could be
Assembler for all I care, my scripts for my personal use will most
likely be done in Python. But we still need an official language so that
those who don't care about the language and only care about LyX
performing as it should will have all the features that come with LyX.
As was said already, we intend to out-source various functions of LyX to
the scripts, so the users will need some scripting language.
In fact I implemented an initial thing like this, but it requires
changes in LyX so this work is postponed until a better time (one
requirement is that I have more time).
> > Anyway, past discussions have usually ended up with Python as best because
> > it's readable/writable even for newbies. Scheme/Lisp usually dropped as a
> > bad idea because no-one cares to type all the ()'s and Perl as a possible
> > second language.
>
> Would it be such a big deal if someone actually wanted to do it (ie, support
> Scheme/Lisp)? Assuming that we make the space for them to work available,
> then we could share in knowledge, and gain from having more languages
> available.
No one cares if you implement a Lisp support for LyX, we will most
probably integrate it into LyX assuming it was done properly. We will
also accept a frontend for braile text if you care to write one. What is
being said is just that we want to define an official language that the
developers will commit to its support.
--
Baruch Even
http://baruch.ev-en.org/
