On Mon, Dec 11, 2006 at 02:22:28PM -0600, Tim Keitt wrote: > What I occasionally wonder is whether the LyX experience -- easy structured > document editing -- could be brought to OOffice? It has a full programming > API. One could code a new editor using UNO or modify the current word > processor with macros, etc. Export to latex is already in-place (but would > need major improvements to match lyx). For me, pretty output is not actually > that important as my main consumers are collaborators and editors. Its the > beauty of what-you-see-is-what-you-mean (sorry, I forget if that's the exact > phrase) that to me matters. Seems with some creativity, that experience > could be migrated to OOffice. The big gain would be ODF support and all the > underlying infrastructure for spell checking and revision features.
I think going to an XML based file format would already increase interoperability a lot. > Some will see red at the suggestion. Fine. I suspect this will get dropped > on the floor. I'm not really asking for something, just sharing a thought. I > realize its hard to get volunteer developers to work on code they may not > like. (I'm the same way.) It would require abandoning the not-invented-here > reaction and believing that the long-term benefits of a being part of a > large code ecosystem evolving around OOffice outweigh the (admittedly > substantial) cost of changing platforms. Guess I've always been a fan of > convergences. I certainly do not mind. >From a pure coding point of view, OOo was a mess at least on par with LyX last time I looked at it. Andre'
