[prev in list] [next in list] [prev in thread] [next in thread] 

List:       koffice-devel
Subject:    Re: KSpread's fate after Beta
From:       Philipp =?iso-8859-1?q?M=FCller?= <philipp.mueller () gmx ! de>
Date:       2002-04-12 7:08:53
[Download RAW message or body]

Am Donnerstag, 11. April 2002 18:27 schrieb Norbert Andres:
> On Thursday 11 April 2002 13:08, Ariya Hidayat wrote:
> > I just wonder if KSpread hackers had already scratched a kind of roadmap
> > for the forthcoming KOffice 1.2 release. I myself suggest that adding
> > more and more functions to KSpread should be one of the important thing
> > to do, beside of course another nice features (as was discussed last
> > month) and bug fixing. OTOH zoom support is better planned as well.
>
> A roadmap would be a good idea or at least a list of important features and
> a person working on them.
>
> There is a TODO file in the kspread directory, we can add the tasks there
> and remove obseleted parts from the file.

I totally agree with all what have been said.

I think we can easily get a double work problem and this should really be 
avoided. And we still have a high number of existing bug reports. IMHO we 
need a way how to handle this.

The only thing that I don't like is the format of such TODO files. Okay they 
are simple and don't give too much overhead, but they are ugly and unhandy.

I think there are several other possibilities, but let me simply get to my 
proposal.

What do you think, if we use the new unzipped format (thanks to David), 
generate a KSpread sheet and store it in cvs?
I have attached a proposal for this (not finalized, beautified and ... just to 
give the impression).
I assume everybody of us used spreadsheets for such tasks already, so why 
should we stick to a plain text file? 

Additional the current bug tracking system doesn't allow something like "I 
take this task" and building up a complete new bt system is oversized and 
doesn't fit to KDE.

And yes, there are disadvantages, like changed file format or replication 
conflicts, but I think the first one should be avoided at all and for the 
second one we can take care of it (maybe we enhance KSpread, so that it can 
more easily take care on its own?).

This would even give a good sign, that we use KSpread on our own and that we 
already use a new collaboration feature of KOffice.

So what do you think?

Philipp
["bugs, wishes and functions.ksp" (application/x-kspread)]
_______________________________________________
koffice-devel mailing list
koffice-devel@mail.kde.org
http://mail.kde.org/mailman/listinfo/koffice-devel

[prev in list] [next in list] [prev in thread] [next in thread]