RTF repoting engine problems

[Martin Terreni]

As you may be able to see there are right now ([timestamp=1249219987]) 4 bugs\issues in the first page of the thread regarding the RTF generation.
I was worndering if this feature of EA should meaby be thoroughly reviewed in Sparx to see if there isn't something fundamentaly wrong in its architecture.
Maybe  if it is important enough for the users (and I'm not necsesarily saying it is) it will be better to invest in rebuilding it then in other things.

Maybe it is just coincidence those 4 threads at one time (really might be) but it just maid me wonder...

[Graham_Moir]

As I understand it the rtf generator was not written by Sparx.  They have the source code, but it was a bought in product.   As a result there are constraints as to what they can do with it in terms of re-architecting/rewriting and of course it is now tightly coupled with the core EA product.  Also, re-writing would be an extremely expensive undertaking, and although it certainly would have benefits,  there would be serious question marks over the cost/benefit case.

[mennerrl]

Bummer - It needs to be improved

[skiwi]

I agree that the RTF engine doesn't come up to the standard of the rest of EA. In fact it lets the side down IMHO.

I don't think they need to rewrite it. In fact they shouldn't, the world doesn't need one more implementation of a word processor.
They should look at OpenOffice.org, or similar, and try to integrate that in as the RTF editor and document generator.

[Martin Terreni]

They should look at OpenOffice.org

That is a tricky one, since EA is not open source so at best it can be integrated "as is" and then we could have more trouble.
Im not saying SParx should re-write it, but they surely should give it an over-all treatment.