"Asger K. Alstrup Nielsen" <[EMAIL PROTECTED]> writes:
| On Mon, 4 Jun 2001 [EMAIL PROTECTED] wrote:
|
| > However, as we approach the 2nd half of 2001, one might ask whether
| > there is an end in site, a point at which 1.1.6 will be intended as a
| > release worthy to succeed 1.1.5fix in all respects? Has there been
| > any loss of momentum? Is it possible that this is becoming another
| > development path that has bitten off more than it can chew? Just my 2
| > cents.
|
| I think you are partially right. The development cycle up to 1.2.0 seems
| too ambitious in retrospect.
It has taken a bit too long... but apart from the mathed changes we
are basically there.
I have (almost) stopped doing new things, and am now just bringing
what we are supposed to support up to date, and some code shuffling
that I just have to do.
and I have a couple of huge projects that I want to begin later (after
1.2.0):
- store the paragraphs in a std::container
- use a visitor pattern for the export/writes
The first one is huge...
| In retrospect, the problem with the 1.1.6 work is simply that too many
| things have been done at the same time. Either the math rewrite or the
| inset stuff should have waited until the other was good enough for a
| stable release.
The inset stuff were _long_ overdue, and we have really had only small
problems with this (all things considered) (and I am not speaking of
1.1.6 but of CVS)
| However, there were many good reasons to do either at the
| point in time, the work started: The inset stuff had to be done in order
| to stabilize the table rewrite introduced in 1.1.6. And as mentioned, it
| would have been bad for morale to turn down the math effort from Andre.
And we really had to take the opurtunity to get the mathed code going
again. (and cleaned up!)
| Notice also that the GUII work that has been going on is not as
| disruptive. It's fairly seldom that work on the GUII stuff affects the
| main stability, so there is no real problem with the GUII work proceeding
| at the same time as the other core stuff.
Hmm.. yes as long as we only do dialogs the GUII work will not impact
the core. However next is the LyXView, BufferView adapiton and I guess
that will be a bit more disruptive.
| Also, we have the emergency exit: Revert the math code back to the 1.1.6
| stuff.
Yes, and this is what we will do if the mathed work cannot be
"finished" in time for 1.2.0.
| But there is good reason to believe that the necessary work can be done at
| the next LyX developers meeting. So, I don't think the prospects are that
| bad for LyX.
me neither.
| What we need now right now is more testing, and more bug reports. When we
| are in Italy, we can choose between three different activities:
|
| 1) Drink beer
| 2) Fix bugs
| 3) Build new features
4) Drink more beer.
btw. I think we should take it easy on 3) this time. Sure we can do
new stuff, but nothing large.
| Obviously 1) and 3) are the most fun, so we'll for sure do some of that.
| However, we also know that 2) is vital for the project to be succesful,
| so we will do that also. But we can only do that if we have the bug
| reports! So help us out with this. Come to Italy and work as a tester
| together with us, and/or start now at home.
This was an superb idea.
--
Lgb
