On 17-Aug-2000 Lars Gullik Bjønnes wrote:
>
> NEW_INSETS should be enabled at the same time, because:
> - keep the fileformat changes localized to on version
> - they also use the textinsets and the other insets that
> tabular uses, better testing.
> - deveopment for 1.3.0 will be a lot cleaner since we can
> remove a lot of cruft intermixing table/flotat code.
> - why should you get your code in and I not mine?
>
Well to answer you what I think:
- the fileformat will change and change again between version, as we
will change stuff and add new features, so this is bogus.
- better testing I agree completely
- well as we will have a 1.1.6 then 1.2.0 development until 1.3.0
will pass quite some time
- and to this I only have to say that probably I won't include more
of mine work then of your work! InsetCollapsable is the base for
all other text-based insets we made till now which are really only
derived insets!
Why activate NEW_TABULAR and not NEW_INSETS:
- new tabular is mainly finished, there are some problems (mainly with
mouse selection) and maybe some behaviours user don't like so much,
but I regard it a feature complete! This is the only table code I will
support from now on, there is lot's of stuff User asked for in a long
time and we could give the user a first impression of the new stuff
we will make available in the next version after 1.1.6 (1.2.0).
- We have still quite a lot of problems to resolve with other insets,
especially your baby the minipage inset is just there to be there
it's the same as a foot inset without more support and there is a
lot of work to do to make this work so we would have to stale the
release of a 1.1.6pre1 just to make all the changes necessary to implement
minipages in clean way.
- Not only that but we also have to resolve the problems in reading all
the right stuff from dummy paragraphs into the right text-inset, which
is IMO also quite a bit of work.
So you see while the tabular-inset IS ready for prime-time most (it reads
all old code correct I tried this with various files and also the UserGuide!)
the other text inset still need lot's of work.
> If we decide for 1.2.0 I will enable NEW_TABULAR and NEW_INSETS right
> away. And then you will get some testing. Also at once when we have
> the remaining bits in place we will release 1.2.0pre1 and you will
> probably get even more testing then.
No I think we should release a 1.1.6 before, we can have a vote if and
what we want to activate if all core developer (Note: this is a decission
ONLY now working developers can take, this includes all of you sending
regular patches and who took up a part of the sourcetree for their
responsability!).
My vote is 1.1.6 with ONLY NEW_TABULAR activated!
>
> It does not seem to be quite equivalent with the old code, at least
> some warnings are missing wen you switch document classes. It also
> seems to me that the new document defaults are not set.
Yes I've seen that warnings are not put out and I investigate that, but
the documents defaults ARE set I tried that, well I will put #ifdef stuff
around the old code so we'll see what will fall away and if it works when
it is not anymore there.
Jürgen
P.S.: You still didn't say if you like the new layout or if you would
like it some other way ;)
--
-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._
Dr. Jürgen Vigna E-Mail: [EMAIL PROTECTED]
Italienallee 13/N Tel/Fax: +39-0471-450260 / +39-0471-450253
I-39100 Bozen Web: http://www.sad.it/~jug
-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._
Duct tape is like the force. It has a light side, and a dark side, and
it holds the universe together ...
-- Carl Zwanzig
