On Fri, Aug 09, 2002 at 03:38:15PM +0100, Angus Leeming wrote: > Your argument about rows and cols would be stronger if we only tried to do > one thing with each inset. Instead, however, we try and do many, many things, > to the point where > > One Thing, One File > > starts to be at least an attractive alternative to > > One Class, One File
I don't think the problem is how many things are done with a paragraph but how they are done. Currently there is the problem that's not easy to see which code does the work and which is "just there to make it work". It looks as if e.g. iteration was fixed several hundreds of lines would magically disappear.. > I ask myself how complicated is the concept of a Paragraph and then I ask > myself how well I understand (even, how often have I ventured inside!) the > current Paragraph code? > > The answers, invariably, start with "Not very"! MathTextInset does basic line breaking in 164 lines or so. Adding all the bells and whistles to get it on par with Paragraph should not take more than say 500 more lines which make a total of a third of paragraph*.C. So I'd actually go for the code cleaning first and if things are still too big afterwards I'd think about Visitor etc.... Andre' -- Those who desire to give up Freedom in order to gain Security, will not have, nor do they deserve, either one. (T. Jefferson)
