Re: And why not fixing the bugs first?

faq
flatforty
contribute
subscribe
configure
search
rdf

main
parent
thread

Re: And why not fixing the bugs first?
by James Richard Tyrer on Thursday 08/Jun/2006, @14:14

While it is my general position that more effort should be put into fixing bugs and I would always error on the side of caution when implementing new technologies, we have to consider that with version 2.0 KOffice will be based on Qt-4.

Therefore, this is the time to break binary compatibility and some wheels are going to have be reinvented for some of the bugs (that can only be fixed by going to Qt-4) to be fixed. The main example that we are all familiar with is the text formating issues which cannot be fixed with Qt-3's PostScript driver.

In some cases, it might be better to wait till after the 2.0 release to implement new technologies. But, there is always a trade off since it would not be possible to, then, replace existing APIs (that would break binary compatibility) but rather to only add additional APIs (all APIs in 2.0 would have to remain till 3.0). In this case, since KOffice is not really yet a mature application, I see nothing wrong with doing some things over if the current implementions are not working very well.

Bug fixes can continue with the KOffice version 1.x branches and can be front ported to the version 2 trunk.

Related Links

·   Articles on KDE Office Suite
·   Also by James Richard Tyrer
·   Contact author

The Fine Print: The following comments are owned by whomever posted them.
( Reply )


		"I didn't know there was a superlative of 'Warmduscher'." -- Carsten Pfeiffer
KDE®, "K Desktop Environment", "KDE Dot News", "got the dot?" and the KDE Logo® are trademarks or registered trademarks of KDE e.V. in the European Union, the United States and other countries. All other trademarks and copyrights on this page are owned by their respective owners. Comments are owned by the poster. The rest: Copyright © 2000-2008 KDE e.V. for The KDE Project. For further information or comments on this site, please contact the Webmaster.