On 29 May 2001, Jean-Marc Lasgouttes wrote:
> Mike> The default user interface has to stop changing before the Doc
> Mike> Team can update everything. Don't stop changing it yet, but
> Mike> expect there to be problems until 1.2.0pre is declared ready,
> Mike> and everyone agrees the interface will be stable long enough for
> Mike> us to document it, then things will get cleaned up.
>
> How long do you need? Note that it will be possible to continue
> updateing the docs in 1.2.x, x>0
Amount of time isn't as big an issue as not knowing when the interface
will settle down, and I really don't want to redocument it six times -
none of us has the time to do that. I'm hoping that 1.2.0pre0 will freeze
the basic interface/keybindings/commandline for at least a few versions;
if so, then I would like to have the docs _completely_ updated and correct
for 1.2.0 proper. The primary reason the docs are currently lagging is
simply that many things have changed since 1.1.5 and are continuing to
change, as indicated by the spate of messages over the last couple of
days. The UI changes from 1.0.0 through 1.1.5 are actually quite small
compared to 1.1.5 -> current CVS. (LyX's guts changed considerably over
that time, but the UI didn't). Of course, new features added after 1.2.0
will require new documentation, but I'd like existing features, like the
change to math arrays, to be settled before we sharpen our pencils. (can
you sharpen a keyboard ? :-) )
Sorry to be a pain in the posterior hinterregions about this, but the
recent UI changes have been rather dizzying. Complicating things for me
personally are the fact that I can't use 1.1.6fixX at work due to the
incomplete table support, so I haven't gotten used to that yet, and CVS is
also changing too fast for me to grab a "stable" copy and try to do some
real work with it (can a "useful" snapshot be made occasionally?). We're
just in an exciting, rapidly changing phase, and the docs are going to lag
as a result - we can't document a feature before it's finished! This
brought up the idea of an Errata section on the Web. At least we can
collect the current inconsistencies and make them known there, so the
Users don't get totally frustrated with the current situation.
Mike
--
Mike Ressler
[EMAIL PROTECTED]
OK, I'm lame: I don't have my own website ...
