faq
flatforty
contribute
subscribe
configure
search
rdf
main
parent
|
And why not fixing the bugs first?
by me on Monday 05/Jun/2006, @15:57
|
Instead of reinventing the wheel, why don't they just try to fix the compatibility issues with ODF? You can't write ODF formulas (they're lost when you save them) and so you can't have any formulas at all in KWord's defauolt format.
The spreadsheet is a joke, Kword is fast, but lacks so many things... Only Krita seems to get proper attention.
So, why not make it usable after all and then start implementing innovations? |
|
|
The Fine Print: The following comments
are owned by whomever posted them.
( Reply )
|
Re: And why not fixing the bugs first?
by Henrique Marks on Monday 05/Jun/2006, @17:20
|
Good idea. I suggest we fork the project and implement what is missing. Contact me by email to do this, if you are really interested.
Why developers dont do this ? Because they do not want, and thats the point of open-source development: do it for fun, in the first place. i just hope all this work will bring a better koffice for all.
And i dont think kword is so bad, in the first place. i use it sometimes, and if any problem occurs and i dont like it anymore i can switch to openoffice anytime i want, thanks to the work of koffice developers who changed the file format.
|
[
Reply To This | View ]
|
Re: And why not fixing the bugs first?
by me on Tuesday 06/Jun/2006, @01:01
|
I just don't have the skills :-)
The Koffice crew seem to be quite talented, it's just that it just isn't as good as OpenOffice yet, in my opinion. I can't really use it for real work (I've tried before), but I'd like to because it's promising and cool.
|
[
Reply To This | View ]
|
Re: And why not fixing the bugs first?
by Boudewijn Rempt on Tuesday 06/Jun/2006, @01:07
|
Well, before I started on Krita I hadn't got the skills either. I had never written more than a dozen lines of C++, but it's an easy thing to learn on the job. It's just a matter of getting started and after that some perseverance.
|
[
Reply To This | View ]
|
Re: And why not fixing the bugs first?
by somekool on Saturday 10/Jun/2006, @19:58
|
lets make things straight. OpenOffice is slow as hell and unsable. their pretending compatibility with microsoft product is a joke. and only Microsoft Office really works with those documents. also OpenOffice only copy what Microsoft did and really does not improove anywhere.
KOffice however is lighting fast and has great stuff that no other suite has. it does miss few important features and still have bugs. but its a charm to use. I do use it for production use as well as many other KDE user I'm sure. ideas in this suit are way ahead and koffice is the only Office suite that actually considered what computer life will be from 2007
also remember there is not many koffice developers. and what they did since 1.0 is amazing. clap clap clap
keep going guys. you're doing an awesome job. dont listen to flamers and gives us the best office suite for KDE 4
gambatte kudasai
|
[
Reply To This | View ]
|
Re: And why not fixing the bugs first?
by Thomas Zander on Tuesday 06/Jun/2006, @01:23
|
I support you implementing whats missing, very good idea! You don't even need to fork you can do it right into the KOffice svn repository, all you need to do is send in the patches.
|
[
Reply To This | View ]
|
Re: And why not fixing the bugs first?
by josel on Wednesday 07/Jun/2006, @08:31
|
Great. Someone raises valid concern/criticism and you just tell him to code it himself. Regardless it its developed for fun maybe the developers would like to have and use the critique positively.
He's just wront about krita.
|
[
Reply To This | View ]
|
Re: And why not fixing the bugs first?
by Ariya on Wednesday 07/Jun/2006, @13:02
|
What kind of concern/criticism? Let me quote: "The spreadsheet is a joke" does not tell the developers anything.
Not everyone has a crystal ball. At least, I don't.
|
[
Reply To This | View ]
|
Spreadsheet
by Juergen on Wednesday 07/Jun/2006, @17:25
|
Even OOo Calc lacks some important features in the graphical representation of numbers. The scaling of x/y isn't up to snuff. Then the embedded programming language isn't really usable either for serious work. I use OOo Writer and sometimes KOffice (rarely) but Excel unfortunatelty is still way ahead and the only winDOS program of use (but big one).
Juergen
|
[
Reply To This | View ]
|
Re: Spreadsheet
by PGK1 on Sunday 10/Sep/2006, @05:30
|
OOCalc is a very good spreadsheet as I find it much more stable than MS Excel when working on the same large data sets. I tried to open up the same ODS sheets in KSpread but it crashed (perhaps 25 columns of 10,000-12,500 data points is too much?) but I do have a few things that OOCalc should have:
1. The ability to put the equation of the best-fit line ON the graph.
2. The ability to plot multiple data sets on an XY graph and have them be independent data sets as in MS Excel.
3. To not have to completely recalculate the graph if I move it on a page but do not resize.
4. To be able to scale the X-axis in a regular line graph instead of putting a marker for each X value down there.
|
[
Reply To This | View ]
|
Re: And why not fixing the bugs first?
by Anonymous Coward on Friday 09/Jun/2006, @02:27
|
The spreadsheet _is_ a joke (or at least was last time I checked).
gnumeric is the only good spreadsheet I've found for any platform.
Constructivly:
The charting-functionality seems to be pretty bad. When I use spreadsheets what I mostly do is dump in some numbers from somewhere, then graph them. With gnumeric it's a breeze .. with kSpread .. I don't find the graph in the image that is generated!
Hmf.
|
[
Reply To This | View ]
|
They are not bugs, they are missing features
by Bilbophile on Sunday 11/Jun/2006, @22:54
|
I am not sure these are bugs, they may be a lack of features/immaturity of the concept. I do think that the metaphors used by KOffice make more sense than the ones of MS Office - cloned by OpenOffice.org - and I would very much like to learn it and use it for work and play.
Unfortunately, I translate doc and pps documents written by people who would not learn MS Office properly, let alone learn how to use another suite on a different OS altogether; or worse, I sometimes work on documents developed by several people - often embedding more different source data - with less experienced people ignoring and mangling the careful settings of the more experienced ones because of the dumb, opaque interface.
With KOffice I resent the lack of adecquate language tools and more importantly the lack of good compatibility with the MS Office file formats. Those are the reasons I am not learning how to use KOffice and why I use it only to edit/change the format of PDFs I occasionally have to translate.
|
[
Reply To This | View ]
|
Re: They are not bugs, they are missing features
by Madman on Sunday 25/May/2008, @18:49
|
<i>on a different OS altogether;</i>
Ermem, KDE 4 ==> Windows port. Can't wait to use a fully functional Koffice 2.0 in Windows.
|
[
Reply To This | View ]
|
|
Re: And why not fixing the bugs first?
by bug buster on Monday 05/Jun/2006, @17:48
|
> you can't have any formulas at all in KWord's defauolt format
Fixed. Thanks for the support.
|
[
Reply To This | View ]
|
Re: And why not fixing the bugs first?
by Tim Beaulen on Monday 05/Jun/2006, @22:16
|
Maybe you don't know this, but KOffice is being developed in three branches at the moment.
- A 1.5.x branch for bug fixes
- A 1.6 branch
- A 2.0 branch (which is trunk)
So, there still get many bugs fixed in the 1.5 and 1.6 branches, while all the innovations get added in trunk.
You're always more than welcome to help with any aspect of KOffice, there's more to do than only coding.
|
[
Reply To This | View ]
|
Re: And why not fixing the bugs first?
by Cyrille Berger on Monday 05/Jun/2006, @22:34
|
Because some problems (like font kerning) can't be fixed without those innovation. And flake will bring some innovations, but it is first about code sharing between apps, which means that in the future instead of fixing a bug in kword, and in kpresenter, and in karbon and in kivio and in etc, you will fix in flake and fix for all. That's the innovative part of code sharing ;)
|
[
Reply To This | View ]
|
Re: And why not fixing the bugs first?
by Cyrille Berger on Monday 05/Jun/2006, @22:34
|
Because some problems (like font kerning) can't be fixed without those innovation. And flake will bring some innovations, but it is first about code sharing between apps, which means that in the future instead of fixing a bug in kword, and in kpresenter, and in karbon and in kivio and in etc, you will fix in flake and fix for all. That's the innovative part of code sharing ;)
|
[
Reply To This | View ]
|
Re: And why not fixing the bugs first?
by Carsten Niehaus on Tuesday 06/Jun/2006, @02:09
|
>The spreadsheet is a joke
What is wrong with KSpread? It is actually quite good and fast. .ods-import works well for me, only the diagrams keep me from using it (I am using the sloooow OOCalc2).
|
[
Reply To This | View ]
|
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.
|
[
Reply To This | View ]
|
The Fine Print: The previous
comments are owned by whomever posted them.
( Reply )
|
|
![[KDE Dot News]](http://www.kde.org/dot/Images/kdedotnews.gif)
