Juergen Vigna <[EMAIL PROTECTED]> writes:
| >
| > If we want to get 1.1.6 out before Christmas you should not do that...
| > And if we decide to skip 1.1.6 and go directly at 1.2.0 we should make
| > that decision now, then we need to enable NEW_INSETS too.
| >
|
| Why do we need to enable NEW_INSETS too? I think that lyx-tabulars
| are pretty good modularized and we could learn a lot (if not all)
| of the problems we have with text-insets.
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?
| > Actually I am not really oposed to this idea, but it will require a
| > lot more testing before a release can be done.
| >
|
| Yes but as you say noone will test this :)
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.
| > What do others say?
|
| I think we have to wait until they return from holidays ;)
Or! We could just make a decision now! I am inclined to think that we
should move directly for 1.2.0, any way a lot of the coding have been
done on features that is not supposed to be there in 1.1.6...and that
is not good form a testing viewpoint.
| P.S.: Do you like the new Document-Layout? Can I remove the old
| > code?
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.
Lgb
